I believe this proposal needs to provide further contrasts against
existing communities and projects to make aspects more clear.
opensolaris-discuss is too broad an audience for internals discussions.
opensolaris-code I thought was meant to cover code topics and questions,
but has been overloaded to handle broader topics due to lack of a better
general forum. Perhaps we could "promote" opensolaris-code to be the
official discussion forum for internals, but I personally don't feel this
is the right thing.
Regardless of the discussion forum outcome, none of the existing
discussion lists has a community page to host system internals
documentation. We still need to fill that gap. Docs seems focused on
end-user feature documentation.
As for scope I'm on the fence as far as kernel-internals versus
.*-internals. As long as there is something in between opensolaris-code
and opensolaris-discuss which is far reaching, I'm fine with it as one of
the "leaders", though I prefer to err on the side of keeping it broad.
1. What is the relationship between this community and existing,
demonstrably technical communities, like the networking, zones,
and zfs communities?
Networking, zones, zfs, etc. are focused on specific areas of the system,
and a good portion of their discussion (the vast majority in fact) centers
around learning about or using the specific features rather than learning
about the nitty-gritty technical details.
We want to create a forum which is 100% purely technical in nature.
2. What is the relationship between this community and the existing ON
(Nevada) community? Why is that alias, or a second alias (or
project) not appropriate for hosting this content? (Why not
[EMAIL PROTECTED])
Same argument as above.
3. What is the relationship between this community and the existing
opensolaris-code and opensolaris-rfe aliases (which are discussing
technical topics regarding ON components)?
Already covered above.
4. We're examining communities commenting on new community proposals
and community-to-project demotion processes on cab-discuss; no
aspect of that discussion really suggests that one community
should propose its existence based on the subsumption of others.
I certainly don't think that that's a suitable mechanism for the
alleged proliferation problem.
The communities which exist today have their place because there are
aspects around learning about and experimenting with new features.
Continuing down that path without providing a more general technical forum
means that if I want to keep up on the state of the art of the system
internals, I have to drown in non-technical information and discussion.
Linux, NetBSD, FreeBSD, and others have kernel discussion lists for this
reason. Beyond the discussion list we want to build a community page to
capture system internals documentation and provide a one-stop shop for
system internals (aside from buying the book).
--
Eric Lowe Solaris Kernel Development Austin, Texas
Sun Microsystems. We make the net work. x40577/+1(512)366-9080
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
