Dan Price wrote:
On Tue 18 Apr 2006 at 08:32AM, Eric Lowe wrote:
As for the technical discussion list, as I've said before, I don't care
about the means as long as we accomplish the ends. For all I care we can
call it [EMAIL PROTECTED], and as long as everybody knows to go there
for technical questions, spec posts, and RFC submissions.
Now I'm really confused. This last statement sounds like you're
inventing new process. Are project teams now expected to cross-post
things like PSARC cases and design documents to muskoka-discuss?
Huh? I never said anything about process.
Will we have control over whether our content appears in your library?
Of course. We (the project) don't own your contributed content; you do.
First, isn't "the muskoka project" the opposite of what we've been busy
doing in creating projects and communities? I don't want to have to
I don't see how it's opposite when in fact it's meant to be complimentary.
If it doesn't have an established community or project, where else would
it go? If it has a project or community, then logically, it probably
should go over there. But nobody is going to go around policing anything
or telling anyone how to do their work. The whole point is to avoid
introducing any process. Where process is involved around documentation
that's where the content project or documentation community come into play.
monitor and refer people posting about zones to tech-discuss or
muskoka-discuss over to zones-discuss where all the expertise lives. We
have to do that today inside of Sun and it's super annoying.
It's evident that a lot of folks disagree with you, and in fact want the
B-F-D-L, myself included; the grand equivalent of LKML, refactored for the
OpenSolaris community, which builds more than just an OS kernel.
Inevitably, such a big --ing discussion list will have a lot of topics
discussed on it. Some will overlap with communities and projects, in which
case the reasonable thing would be for someone to cross-post followed by
(hopefully) the posters moving the discussion off-list once it is no
longer interesting to the technical community at large.
If you don't want to be on the BFDL, you don't have to be on it... with
enough critical mass, when a thread appears it may be interesting to a
particular community or project, I would anticipate someone stepping up to
cross post to the community or project just as is done today, and if the
discussion gets too deep for the general community, to try to move it off
list.
In my mind at least, LKML is a good model, but it's hard to explain how
such a list works if you haven't been on it and participated for any
length of time. Such a forum bridges the gaps between the various projects
which are peppered all over the place. It keeps everyone in the loop on
what's going on with the overall system from a technical standpoint. It's
a good a place for folks just starting out to figure out what technologies
they might want to participate in without having to subscribe to a
squillion community lists. And it's a good place for generalists who are
interested in everything to keep up with what's going on. Such a list is
mostly self-moderating; when someone posts something off-topic, someone on
the list deals with the post by asking the poster to please post in a more
appropriate forum. Threads that wander off-topic are moved to other lists
as appropriate, and there is plenty of cross-posting. Since the discussion
is kept technical and interesting (no "why doesn't Solaris install on my
386-16MHz machine with 2MB of RAM posts) folks with a high level of
impatience for such noise are still willing to sign up.
Second, I don't think saying: "it's a hodge-podge" and "it's moderated"
make sense together. You'd be better off with os-discuss and
Again look at LKML, if you haven't.
os-technical, both unmoderated, and no requirements about posting
specs, RFCs, etc.
It's an open forum, there are no requirements and there is no process.
And, as long as there is critical mass, there is no need for having any
moderation process as the list should be self-moderating.
[snip]
- Eric
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
