What is a SIG? Special Interest Group. Why should we consider SIGs for OpenSolaris?
At present the only level of abstraction that we have in the OpenSolaris community is that of communities. We have communities for high level concepts (networking) and for very specific products (zfs) as well as groups of people (sysadmin). What I would like for people to consider is to allow the idea of SIGs to form within communities. Why should a SIG form within a community rather than be a community in its own right? Size. I see SIGs as being composed of a smaller subset of people. For example, an approriate SIG in networking might be ipfilter (;-) or email or routing. And in formalising the role of SIGs in OpenSolaris, I'd like to suggest that people take pause to consider the current structure of OpenSolaris into the various communities and ask themselves if it is correct or is it just the only way to map OpenSolaris into our existing structure? In short, the current formation of OpenSolaris has largely been to fit various projects inside Sun and not to model groups of interested people. For example, why shouldn't SMF be a SIG inside the sysadmin community, as afterall, SMF is well and truely in the province of system administration. Or where would someone go that wanted to work on VFS and/or the interfaces that support filesystems in OpenSolaris? Shouldn't there be a filesystem community that brings together ZFS, UFS, CIFS, and many of the other filesystems as SIGs inside it? Why isn't there a developer community, that can be broken down into kernel development, library development, tools, build environment, etc, as SIGs? Darren _______________________________________________ opensolaris-discuss mailing list [email protected]
