Garrett D'Amore wrote:
Shawn Walker wrote:
This is the sort of project that needs to stay in sync with whatever
the ON community is doing so they can be aware of big gate or process
changes, and so that they can work together.
I don't like the idea of making this project formally subservient to the
ON Core Contributors (who are ultimately also its C-Team). The point of
this consolidation is to deal with stuff that has been *excluded* from ON.
I don't agree with that. The OpenSolaris constitution structure doesn't
mean that an ON-sponsored project is subservient to the ON Community
Group. If you're really that worried about that sort of influence, then
you don't want to be on opensolaris.org anyway :)
This is about communication and direction, as well as overlap. From a
strictly os.org point of view, I don't see why this shouldn't be a
sponsored project of the ON CG. To me, it fails the common test for an
independent CG. If you don't want it sponsored by ON, then I think it
needs to be sponsored by some other related CG.
I also believe the issue of where the code lives is completely separate
from community governance structures. The ON CG doesn't get control
over your project's repository just because they are your sponsor, any
more than the installer, etc. CGs get control over the pkg(5) repository
because they sponsor the Image Packaging System project..
While that doesn't directly fit what you have here, I think that
there's a lot of overlap in the needs of that project and what you've
proposed. In particular, due to the relatively low volume of external
ON contributions that are currently seen, I suspect that if we see an
increase in them, there's a good chance it will come from what has
been proposed here.
Possibly. I'm not sure that the overlap is quite what you mean though.
I'm also, btw, not sure that the SCA rules need to follow for this
consolidation. It might be that they do in order to be hosted on
opensolaris.org... the SCA is about giving Sun rights to code. If Sun
isn't integrating the code, then is an SCA truly necessary? IMO, it
isn't. But I need to check what the governance rules for SCA are.
Even if that weren't the case, I personally would be extremely
uncomfortable taking contributions from individuals who have not
provided some sort of guarantee to the community that the code they
contribute belongs to the community and that they have the right to do so.
Even FSF projects require some sort of contributor agreement for
contributions of a certain scope to gcc, etc.
The other thing is that a lot of the stuff I'm talking about would
automatically fail the current RTI process, which requires a lot of
extra things to be in place, mostly to support Sun's business needs
around OpenSolaris and Solaris. Since this consolidation is explicitly
not part of Sun's distros, it can be free from all that overhead.
Yes, but I'm assuming that a very similar formal RTI process will still
be needed for this project.
Cheers,
--
Shawn Walker
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
