Earlier today, like a few others I was at the foundation and I actually saw Denis putting the final touch to callisto. That was really cool and exciting since it represented for us 'the' last final step to make our work available to everybody.
Thanks again Denis, Matt and Nathan for bearing with us in your office while we were drinking your beers and watching you work.
By the way next time, get one of those to make the final push more exiting :-).
Friday, June 30, 2006
Wednesday, June 28, 2006
Release party at the foundation?
Rumor has been growing that once Denis will have released the eclipse bytes to an ecstatic crowd all hyped up by the Ian's press releases, the foundation will host a release party where we can all watch the eclipse servers and the committers go red.
Thursday, June 22, 2006
Headless build of products finally automated
For the longest time (two release cycles 3.0 and 3.1), it was a pain to automate the build of your RCP apps. The PDE Build team heard you and now the pain is gone!
Since 3.2, PDE Build provides support to build RCP applications from .product files. For more details, see the help (Plug-in Development Environment Guide > Tasks > Building an RCP Application from a product configuration).
Since 3.2, PDE Build provides support to build RCP applications from .product files. For more details, see the help (Plug-in Development Environment Guide > Tasks > Building an RCP Application from a product configuration).
Wednesday, June 21, 2006
Community plan items
As various teams are now planning 3.3 or whatever comes next, I would like to suggest the addition of a new kind of plan item, the community item.
What would it be: A work item bringing value add to eclipse, but where the effort would be driven by the community instead of the eclipse teams themselves. Such items should be relatively self contained (for example: implement a new refactoring, implement a new code formater, better high level doc on RCP, provide an simple build infrastructure, provide login infrastructure, etc.).
How would they work: Like any work item they would first be proposed. Then interested members of the community would form a working group responsible for designing and implementing a solution in adherence with the component vision, solution that would find its way in the release. To this extent, it would get assistance from appropriate committers, but it would also be submitted to the same criteria of quality with respect to stability, scalability or being done on time.
Who would submit those items: The PMC or the community, but it would likely have to be approved by the PMC to ensure the cohesion of the vision and appropriate resource is available to assist where needed (of course this is just a proposal).
Why do we need those? Current plan items read as "the team will do it for sure (committed)", "the team is investigating (proposed)". Therefore if you are willing to help you are left with the not so sexy HELPWANTED bugs. What this does is create a focal point and fosters discussions around a particular topic, that would not have necessarily emerged alone from the community. Also it is clear for companies or people willing to contribute code what things are of interest and what their energy could best used at.
In order to discuss that, I have opened bug 148149.
What would it be: A work item bringing value add to eclipse, but where the effort would be driven by the community instead of the eclipse teams themselves. Such items should be relatively self contained (for example: implement a new refactoring, implement a new code formater, better high level doc on RCP, provide an simple build infrastructure, provide login infrastructure, etc.).
How would they work: Like any work item they would first be proposed. Then interested members of the community would form a working group responsible for designing and implementing a solution in adherence with the component vision, solution that would find its way in the release. To this extent, it would get assistance from appropriate committers, but it would also be submitted to the same criteria of quality with respect to stability, scalability or being done on time.
Who would submit those items: The PMC or the community, but it would likely have to be approved by the PMC to ensure the cohesion of the vision and appropriate resource is available to assist where needed (of course this is just a proposal).
Why do we need those? Current plan items read as "the team will do it for sure (committed)", "the team is investigating (proposed)". Therefore if you are willing to help you are left with the not so sexy HELPWANTED bugs. What this does is create a focal point and fosters discussions around a particular topic, that would not have necessarily emerged alone from the community. Also it is clear for companies or people willing to contribute code what things are of interest and what their energy could best used at.
In order to discuss that, I have opened bug 148149.
Subscribe to:
Posts (Atom)