A model for Teams in squeak-dev!

goran.krampe at bluefish.se goran.krampe at bluefish.se
Tue Feb 22 12:05:32 UTC 2005


Hi!

=?ISO-8859-2?Q?Alexander_Lazarevi=E6?= <Alexander at lazarevic.de> wrote:
> goran.krampe at bluefish.se schrieb:
> > 	** This is an important part of how we want to work, please give us
> > feedback **
> 
> A month ago [1], during actionism rush hour, I also suggested that a 
> working group should be formed to build a new squeak.org site. So yes, 
> in general I think it is a good idea to organize the work on squeak in 
> teams.

Goodie. And now there is such a Team working too. :)

> > 2. The Team should work openly. No private areas or private mailinglists
> > etc. Setting up an ml or a Swiki is of course fine, but it should be
> > readable by us all. We don't want to endorse "secret" work.
> 
> I think the teams should be granted some privacy (!= secrecy) eg. to 
> discuss controversial topics. If the team feels it needs some comments 
> from the entire community they should step forward and ask for this. I 

What I meant is that new ml's or new Swikis etc should be readable - not
that the Teams are restricted to using only squeak-dev or the minnow
Swiki - that would be *very* awkward. One goal is to lower the noise
here, not raising it :) 

> could imagine that for example the new website team would like to 
> discuss different designs first without having every Squeaker express 
> his personal taste on ever single bit.

Every Squeaker will not follow every Team, so I don't think that is an
issue.

> This rule can't be enforced anyway, because of the team members using 
> private email.

That is of course true - I still want the rest of us (not being members
in the Teams) being able to "peek in" and read ml archives or look at
their work Swiki or whatever, if and when our interest is tickled.

Otherwise people will join up just in order to be able to follow - and
that is *not* good. We want *doers* on the Teams, not *lurkers*. :)

> Alex

regards, Göran



More information about the Squeak-dev mailing list