Keith M Wesolowski <keith.wesolowski at sun.com> wrote: > The code in the consolidations. The processes are variably open. ARC > is pretty open. The ON C-team is pretty closed. Other C-teams are a > mixed bag. Code review resources are available but not as well > integrated as we might like. Direct access to most consolidations is > missing. To get where (I think) we want to go, all C-teams need to be > open both for interaction and membership, all gates need to be > accessible, and the tools that support the processes need to be > available and well-integrated. DUH![*] > > Sun's products. Not our business. They can do whatever they want > with them. Hopefully they'll like what we're doing and use our work. > > Products created under our umbrella. Remains to be seen what the > community role is in these. I suspect the right answer is what Herr > Schilling has said: the responsibility for deciding what to do with > them lies with the people who actually do the work. The product teams > decide what kind of processes and internal governance they want. If > the rest of the community doesn't like the result, too bad for us. We > might as well do it this way because we cannot prevent people from > taking our stuff and doing this anyway somewhere else.
It may be worth to read this: http://www.heise.de/open/Sun-und-die-Open-Source-Community--/artikel/100564 The author is known for previous inapposite Sun/Solaris criticism but this text looks definitely more neutral. J?rg -- EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js at cs.tu-berlin.de (uni) schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
