Hi Cees,

Let's hope a bright 2006 for Squeak and Smalltalk in general!

Your idea sounds good and logical. The problem I see is finding someone to 
lead the efforts in each area. For example, the UI part. I'm the leader of 
the Morphic Stewards team, and I'm having a hard time just to find enough 
free time for reviewing the fixes and enhancements that are candidate for 
publishing. Recently I could not continue my work on splitting and safe 
removal of packages.

I have a full-time (non Squeak) job, a family (wife and daughter), I'm 
supervising the works on our new job, and I do some research on signal 
processing (wavelets and such applied to music, with stuff already published 
and more to come). Next year I plan to start serious work on developing a 
pro audio editor using the techniques I developed. I'll do it in Squeak and 
Morphic.

So, I'm a pretty busy guy. I love Squeak, and believe Morphic was meant to 
be cleaner and simpler than it got. And I want to use it very seriously in 
my next project. This is why I want to help here.

But I can't take responsibility for other UI stuff, like MVC, ToolBuilder. 
And of course Tweak is to be handled by Andreas when released. Actually, I'd 
like to go in the opposite direction. I'd like to handle Etoys to someone 
with real interest and knowledge of it.

So, I could agree with your idea if someone proposes for handling all the UI 
packages. And I'm afraid something similar could happen in the other areas. 
We are all busy people! Those of us who are lucky enough to work on Squeak 
have other projects and goals in addition to helping the development of 
Squeak itself.

I think that in addition to everybody's opinions on this matter, we should 
also need some candidates proposing themselves for these important 
positions.

Cheers,
Juan Vuletich
----- Original Message ----- 
From: "Cees De Groot" <cdegroot at gmail.com>
To: "The general-purpose Squeak developers list" 
<squeak-dev at lists.squeakfoundation.org>
Sent: Sunday, January 01, 2006 11:31 AM
Subject: Re: Steward teams


Dear Squeakers,

A happy 2006! May the Gods of Smalltalk finally prevail over the
dark-roasted side this year ;-).

Recall that I proposed, just before xmas, to move from the current
"per-package" team setup (which, in theory, would lead to 10-15 teams
maintaining small packages) to a "per logical subpart" team setup,
where the subsets would be components like "Core Class Library"
(Kernel, Objects, Collections), "I/O" (Files, Network), "UI" (Morphic,
MVC), "Development" (Tools and assorted stuff).

It's been a bit silent on the topic - this could indicate a lack of
interest, an abundance of people enjoying a holiday, or a silent
approval. For the record, Bryce, Brent and Doug reacted in a positive
manner, so so far we have 4 in favor and 0 against ;-)

Anyway, if you approve (or not), it'd be helpful to say so even with a
little "me too" posting. I think it is a simple and quite logical
step, merely fine-tuning what we are already doing, but it could well
be that I'm overlooking something here. And with just three people
publicly backing the idea, it's a little bit thin ice to start
implementing this...



-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: 12/29/2005