On 8/7/07, Keith M Wesolowski <keith.wesolowski at sun.com> wrote: > I'd like to see us discuss ways to incorporate new efforts that do not > fit well into projects but also lack a history of open development and > communication. The recent effort by Sun's LDoms product team is a > prime example. In many cases, these product teams are about to > release source code under an open license and are under pressure by > their managers to form a Community Group. Are Community Groups the > correct solution? Are projects? Or do we need to invent something > else (a probationary CG, perhaps)? > > Input on this from non-OGB members is strongly encouraged.
I suspect that as new technology areas blossom, what at one time seems just perfect as a community will turn out to be a specialized case of something more generic. Having a place where there is a low barrier to entry (without distinction between project and community) would be a very good thing. Over time, it is somewhat likely that it will become clear to the new entity where it belongs in the grand scheme of things. The focus should be on... - Get up and productive quickly - Gentle introduction to bureaucracy - Set time line to be absorbed by existing community, form a new community, or disband It has to be discouraging for those people that are new to OpenSolaris (and possibly open source) are being given such a hard time. I don't think this is the normal case, it is a side effect of other communities that are somewhat related being created without having an incubation period while the dust settles a bit. Mike -- Mike Gerdts http://mgerdts.blogspot.com/
