On Thu 16 Mar 2006 at 02:19PM, Stephen Hahn wrote:
> * Nils Nieuwejaar <[EMAIL PROTECTED]> [2006-03-16 12:37]:
> > On Thu 03/16/06 at 11:30 AM, [EMAIL PROTECTED] wrote:
> > > 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])
> >
> > The Nevada community seems to be shooting for a C-team kind of function,
> > while we are trying to get to more of an I-team level. Also, we want to
> > pull in historical information to help explain how we got to this point,
> > which would seem inappropriate for a Nevada-specific group.
>
> But appropriate for an ON community. That is, if the current ON
> community were refined, such that its long-running aspects were the
> community focus and its specific release were a project (or at least
> separated), then the distinctiveness of internals is lessened.
I'd like to call Stephen on a technicality, but then agree with
him :)
There is no "ON community" today. There is an onnv (OS-Net Nevada)
community. "nv" really implies a binding of that community to a
particular release-- Solaris Nevada.
So let me propose:
- Rename and refactor the 'onnv' community into 'os-net' or some
such. Remove its logical binding to the nevada release train.
- Make onnv a project, logically tied to the os-net community.
The C-team can run that project page.
- Ponder some new convention around having -internals aliases inside
of the communities (offhand, I imagine the zones, zfs, os-net
and other communities might benefit). In some cases (like
zones) we might want to move to a -users and -internals
(or -developers) model, rather than the sort of free-for-all
of -discuss.
Thumbs down to the currently proposed community. Sorry guys :(
Thanks,
-dp
--
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
