a)
Every *single* widget is transformed into a subproject. So it can 
  follow its own release cycle, incubation state, committer election, 
   
   
 
I also +1 - I think it makes the most sense. It allows each widget to
have a separate group of committers. 
  
   
b) For 
  widgets like our nebula ones the subproject process is too heavy 
  weight IMHO (at least for the existing ones). 
   
   
 
As the maintaining-author of the official Eclipse Development Process,
I always cringe when someone says this and I'd love to understand
exactly what it is that people find too heavy. Seriously, I would. Not
just a wave of the hand "it's too heavy", but a "having to write a
proposal is too heavy", or "having to fill out the project provisioning
online form is too heavy", or even "I think it's too heavy because
there isn't a flowchart and checklist of steps I need to follow"... I
think the Eclipse process is now lighter weight (fewer hurdles, fewer
forms, and faster) than, e.g., the Apache process and I don't hear
people saying the Apache process is too heavy so I must be missing
something... 
 
Konstantin, if you could keep me in the loop on your conversations
here, I'd really *really* like to learn what the issues are so that I
can solve them. 
 
- Bjorn 
 
 |