[squeak-dev] Re: The future of Squeak & Pharo (was Re: [Pharo-project] [ANN] Pharo MIT license clean)

Bernhard Pieber bernhard at pieber.com
Sun Jun 28 23:25:49 UTC 2009


Am 29.06.2009 um 00:50 schrieb Klaus D. Witzel:
> On Mon, 29 Jun 2009 00:34:50 +0200, Bernhard Pieber wrote:
>> I tried to explain in my response to Igor that I think the opposite  
>> is true. We lost a lot of people because we did not value their  
>> contributions to the full image enough.
>>
>> Peace ;-),
> Sure (peace ;) so we have lost for contradicting reasons, as well.  
> Okay then, now wearing my project manger hat:
>
> and now?
Good question! :-)

Given that there is Etoys with a clear positioning towards educators  
and education software, and given that there is Pharo with a - IMHO -  
slightly less clear positioning towards commercial and software  
engineering research [1] - the question is: How should Squeak position  
itself? I see the following possibilities:
a) Merge with Etoys as Bert and David have proposed.
b) Merge with Pharo as Göran, Randal, and maybe Igor and you? could  
imagine.
c) Find some other unique positioning

I suggested one possibility for c): "Squeak-dev is the place where you  
get a full image which shows off what cool things are possible with  
such a technology. It is not ideal for production, because it has  
licence and quality issues, so if you want that go to Etoys or Pharo  
or Croquet. However, if you want to be inspired, want to give cool  
demos, or want to try out blue plane things, it is ideal!"

I don't say that this is the only possibilty for c). Juan mentioned  
another. However, I think it could be something that could create  
energy and attract contributors. There are clearly definable tasks:  
"Find some cool stuff that once worked in Squeak, take it and make it  
run again. If you do we promise to put it into the full image people  
can download from squeak.org." It is something which is doable for  
less experienced developers.

However, the real answer is: Let's discuss above variants. Let's  
brainstorm other possibilities for c). Let us argue what the  
advantages and disadvantages of the different variants are. And let's  
do it in an objective (How do you translate "sachlich"?) and not  
emotional manner. ;-)

Cheers,
Bernhard


More information about the Squeak-dev mailing list