Re: Squeak direction: Was: Re: Terms of Reference:

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Squeak direction: Was: Re: Terms of Reference:

Gary Dunn
On Fri, 6 Nov 2009 19:53:48 +0200 Igor Stasenko <[hidden email]> wrote:

> 2009/11/6 Miguel Enrique Cob Martinez <[hidden email]>:
>> El vie, 06-11-2009 a las 07:22 -0300, Juan Vuletich escribi:
>>
>>> Hey, nice talk. Now, what are your own great dreams with Squeak? What
>>> are you doing to pursue them?
[snip]

>> My question, in simple terms is, what are the goals of Squeak. Something
>> like, for example:
>>
>> - minimal under 10 MB core image.
>> - Etoys removal
>> - All packages removed from image and easily loaded from squeak source
>> - In core only collections, compiler, kernel and I/O.
>> - Purge of squeaksource or new squeak source with maintained packages
>> - fix of squeakmap mess
>> - new framework for managing packages/dependencies/configuration
>> (sake/packages, metacello, other) in next minimal squeak core
[snip]
>
> you are smart enough to see the Squeak's shortest reachable goals
> (listed above) in same way as i do.
> Manifest the plan and milestones , and i (and i hope many others) will
> support you.

My interest in squeak is as a foundational part of the Open Slate Project. My preference is to have a useful and engaging envirnment available right after installation. A leaner image has merits for experienced squeakers, but forcing new users to learn how to find and install packages in order to do anything will hinder it's success. I must confess to being a bit overwhelmed at first by the richness of squeak.
--
Gary Dunn, Honolulu
[hidden email]
http://openslate.net/
http://e9erust.blogspot.com/
Sent from a Newton 2100 via Mail V

Reply | Threaded
Open this post in threaded view
|

Re: Squeak direction

Jecel Assumpcao Jr
This is a very good discussion to have, but we should organize it a
little better. Juan listed several personal visions of where Squeak
should go and what these individuals are doing about it. Others have
offered criticism and/or suggestions, which I think is also valid. Igor
mentioned the board vision: relicensing and more modularity.

The board's vision will naturally be a kind of lowest common denominator
of the different directions, and so will be far less ambitious than
individual visions. The only way to improve that is to better align
everyone's particular plans for Squeak as much as possible so that the
common ground becomes larger. This thread could be a positive step in
that direction.

One thing that has greatly reduced the scope of this board's goals for
Squeak is how long the relicensing effort is taking. Given all the work
that had been done in the previous two years, I had really hoped that we
would have been finished by the end of May or so. Now I can easily see
it as a limiting factor until at least next year. This prevented us from
doing anything about "more modularity". Last year's board at least had a
roadmap where Squeak 5.0 would be based on Spoon to address this issue,
but this year we had to restrict ourselves to far more incremental
plans.

Early in Squeak history, Dan Ingalls would post a yearly "vision" email:

http://wiki.squeak.org/squeak/2902
http://wiki.squeak.org/squeak/393
http://wiki.squeak.org/squeak/920

We could continue posting plans here and discussing them. An alternative
would be to gather them all in a wiki page to make it easier to compare
them. Besides goals, talking about how to get the resources needed to
achieve them is also interesting.

-- Jecel