On Sun, Feb 20, 2005 at 04:00:21PM -0400, Lex Spoon wrote:
> Giovanni wrote:
> > By the way, this saturday I am working to commit a big java 
> > project...instead of being at home at developing Celeste :-(
> > I think we can grow, I am reading
> > http://www.businessweek.com/magazine/content/05_05/b3918001_mz001.htm
> > as suggested by Frank Caggiano.
> 
> It's a cool article.  However, the exact way they organize does not seem
> to map well to what we want.  Even with all the delegation, Linus is
> still the executor and the court of last appeal.  We don't have anyone
> like that around here that everyone could be happy with.

Not to mention there are, very broadly speaking, two defined layers in
the kernel code.  One involving subsystem infrastructure (such a
memory management), and the other involving device drivers.. Linus can
safely deciede to ignore what happens at device driver level (which
is, nonetheless, a huuuge chunck of code), including how badly they
break and can concentrate efforts at the critical layer.

I don't really see how this process could this be mapped onto squeak
development (at least as the base image stands right now).
-- 
Ragnar Hojland - Project Manager
Linalco "Specialists in Linux and Free Software"
http://www.linalco.com  Tel: +34-91-4561700