Thanks for the backup, Pascal :-)
    
    I want to push forward with both the Great Fix and the Hackathon for
    EclipseCon.
    
    For the Great Fix, I recommend that we target doing one per quarter
    between now and Neon. We can determine where to take it after that.
    
    I would like to focus on bugs that improve the IDE experience, which
    IMHO includes performance. Alternatively, we can maybe pick a focus
    for each round (e.g. UX in 2015Q3, Performance in 2015Q4, ...).
    
    I've already started the process of sorting out prizes: I may be
    able to swing the equivalent of a tablet/quarter for the grand prize
    and then t-shirts or other swag for runners up. I'm open to
    suggestions.
    
    Thoughts?
    
    Wayne
    
    
On 14/07/15 06:34 PM, Pascal Rapicault
      wrote:
    
    
      
      I second Wayne in thinking that
        performance problems are not good candidates for a competition,
        at least not until we have discrete problems identified.
        Historically, impacting changes in the realm of performance have
        been done after long investigations carried out by a team
        created specifically for that purpose (usually composed of
        people from various projects).
        
        At this point, I think we should first understand the exact
        scenarios we care about (which epp pack, content of the
        workspace, plug-ins installed, etc) and go from there. So if
        there is any help to be obtained from the community it is in
        collecting the scenarios that are slow.
        
        Pascal
        
        
        
        On 07/14/2015 10:18 PM, Lars Vogel wrote:
      
      
        Thanks Wayne for the clarification. The "
I disagree." did put me
            on the wrong track for the rest of your reply. ;-)
          
            
          Dani, could
              someone from your team help with a reasonable startup
              measurement test?
          
            
          Structure-wise,
              I like the Great-fix organization. Having 3 iterations and
              having three picks of winners would be great IMHO.
          
            
          As the task is relatively complex, I think the incentive
            should be more than a T-Shirt, Tablets would again be great
            IMHO or a price money from the foundation. Not sure what the
            new structure is, but sponsoring this with  the new money
            initiative might be an opportunity to motivate skilled
            developers.
          
          
          If the Eclipse IDE starts significantly faster than other
            IDEs this would be big plus for our IDE.
          
          
          Best regards, Lars
          
        
        
        
        _______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
      
      
      
      
      
      _______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
    
    
    
  IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.