1. 1 Planning Council (Easy Stuff) Standard Website Content Fly-out top-left menu on all project home pages Home, About (description, plan, leadership, minutes, committers, community), Downloads, Getting Started, Development (plan, mailing lists, cvs, bugzilla) Clean Up Old Website Content By the end of September Status Reporting Format XML file containing status information for auto-gen of timeline, roadmap, etc.

2. 2 Planning Council (Medium Stuff) Roadmap Forward Looking Statement needs to be more concrete and less marketing fluff. Explicit about the release being discussed. Should the cycle be synchronized with the release train instead of January? Changes to Bugzilla BIRT requested changes discussed, 1 of 4 adopted IP Policy Project Log Guidelines Separate musts from advice

3. 3 Planning Council (Hard Stuff) Release Train Platform, EMF, GEF, VE, DTP, WTP, TPTP, BIRT, GMF. DSDP not this time Pull milestones in by one, extend end game by 6 weeks Synchronized milestones must be happening by Nov 4. Requirements Projects are looking at RC input as part of their planning process, but only one part. The only sure way to get a requirement in is to provide compelling value to the strategic members on the project. Either a business case for the member or resources for the project or … Projects implement some requirements for the good of Eclipse. Cross-project requirements flow is happening. IP Policy Implementation is Very Bad Its so bad. It needs to get better.

4. 4 Planning Council (Fun Stuff) Committer-to-committer mentors Four experienced projects (Platform, TPTP, BIRT, WTP) will provide three mentors each N inexperience projects will provide mentees Rewards/acknowledgements at EclipseCon