<div><span class="gmail_quote">On 9/19/07, <b class="gmail_sendername">GeertC</b> <<a href="mailto:geert.wl.claes@gmail.com">geert.wl.claes@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>What does the roadmap look like for the Squeak core image (the one downloaded<br>from <a href="http://www.squeak.org">
www.squeak.org</a>)?</blockquote>
<div> </div>
<div>As far as I've been able to tell, the roadmap looks like:</div>
<div>* The current release team will continue to correct bugs in Squeak as reported until they have decided they are done, they are exhausted, they are told to stop, or someone comes up with a new plan for version 3.11 /
4.0.</div>
<div>* The next step in the roadmap is based on someone coming up with what they want to do next, proposing it, and getting it accepted by the board. (Ideally more than 1 group would come up with an idea they would be willing to undertake, and the board could chose between them). They then start the next relase.
</div>
<div>* This continues until we as a community decide to do it some other way.</div>
<div> </div>
<div>The Board (or at least members of the board) have stated that they weren't elected to decide where Squeak was going technically, but rather to handle other issues such as the legal formation of the community and other non-technical issues. This doesn't have to be this way - and we can choose to make that change at the next election if we want too - and demand it during the election. Or, someone could propose another structure for technical direction - maybe have the board appoint a 'temporary technical dictator' that holds the title until that person is removed from office by that (or a later) board.
</div>
<div> </div>
<div>If you like that roadmap that you proposed and you can find some like-minded individuals that would like to work on that for the next release AND you have the time and dedication to follow through on it, then a great next step would be to start aggitating for the next release cycle to be those goals. Come up with a proposal (I think that mainly means specific goals, rough dates, and a team roster, maybe other stuff - I haven't actually read any of the previous ones) and forward it to the board and/or list for discussion. If it is accepted, negotiate with the current release team about their completion date and when you are going to start.
</div>
<div> </div>
<div>At least, this is my interpretation of how these things are currently being handled. I'd be happy to be corrected wherever necessary.</div>
<div> </div>
<div>-Chris</div><br> </div>