see below re traits...<br><br><div class="gmail_quote">On Mon, Dec 8, 2008 at 1:48 PM, Keith Hodges <span dir="ltr"><<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d"><br>
> I'd like to empasize this:<br>
> - Pharo has the clearly established nearly-achievable goals (good or<br>
> bad - depends on people's preferences)<br>
> - does Squeak has the same clearly established nearly-achievable goals?<br>
><br>
> If yes, then why they not on <a href="http://squeak.org" target="_blank">squeak.org</a>, but on<br>
> (<a href="http://installer.pbwiki.com/311" target="_blank">http://installer.pbwiki.com/311</a>)<br>
</div>Hi Igor,<br>
<br>
We had a meeting with everyone that was interested perhaps 9 months ago.<br>
<br>
Having re-iterated the goal, of more modularity, and better tools. It<br>
was agreed that the tools on their way at the time, particularly "MC2"<br>
(and now Sake) were likely to change the workflow to the extent that we<br>
were not in a position to establish any further goals beyond the "more<br>
modularity" and "better tools".<br>
<br>
The rationale for this being that what is achievable with the old tools<br>
and the means to get there was likely to be entirely different with the<br>
new tools.<br>
<br>
With this task based approach, you can make your own personal ideas for<br>
goals into tasks, and get started. When you are ready we simply include<br>
your task in the build. If the "release-team" dont like your task, or it<br>
is not ready for the mainstream, it may still be distributed with the<br>
release, for people to see what you were up to, and to contribute<br>
further to it. (roll on namespaces!?!)<br>
<br>
The goals of 3.11 are mainly philosophical and social.<br>
<br>
Technical goals currently on their way for 3.11 include:<br>
<br>
* LevelPlayingField as standard (Monticello itself unload/loadable<br>
without losing essential state)<br>
<br>
* Atomic Loading<br>
<br>
* Traits as standard (but removable via unload task)</blockquote><div><br></div><div>Peter Ahe of the Newspeak team at Cadence has written a script to remove traits from 3.9. If that's useful to you let me know and I'll find the code.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">* Nail the package dependencies issue provide a mechanism to get all<br>
things working for everyone.<br>
<br>
* Release a reasonably functional basic image (rather than a kernel<br>
image) but provide working unload tasks for non-essentials<br>
<br>
* Remove a few more modules (but definitely ensure they are re-loadable)<br>
<br>
* Removable tests (but definitely re-loadable)<br>
<br>
* Ship with the very latest packages (3.10 shipped with out-of-date<br>
Installer/SqueakMap etc)<br>
<br>
* Facilitate integration testing, the other side of the coin to image<br>
whittling and modularisation. i.e. be able to build and test a very full<br>
image.<br>
<br>
* Bob the Builder for testing and image building, and one-click-image<br>
building<br>
<br>
* Tidy up class organization<br>
<br>
* Auto finalize the image, e.g. Readme, Release notes etc. version<br>
controlled (in mc)<br>
<br>
+ "Fixes" as per usual (but automatically documented in verbose detail)<br>
we have about 90 so far.<br>
<br>
Items marked with a + are specific to 3.11, items marked with a * are<br>
tasks which may potentially be applied to any 3.7+ image if you have<br>
been left behind or have been forced to fork.<br>
<font color="#888888"><br>
Keith<br>
</font></blockquote></div><br>