Since the OGB is an SMI liaison, I was hoping they could work this issue
out.
In my opinion, forcibly requiring an SCA for community-initiated and
maintained projects is not conducive to the growth or spirit of the
opensolaris.org community. I also believe that Sun (SMI) genuinely
intends to foster growth of the community and so assume this just a
simple oversight.
Projects that are completely community-initiated by community members
that are not Sun employees should not be required to require an SCA for
their contributors at the very least.
The only time an SCA should be required is if that project intends to
re-integrate formally via contribution back to an SMI-maintained codebase.
My hope was that the OGB be able to correct the policy or further
clarify it based on communications with SMI to better reflect the
community growth that I believe SMI intended to foster when it founded
opensolaris.org.
I completely accept the requirement of the SCA as it relates to
SMI-maintained or initiated projects, but feel that it is not beneficial
to attempt to apply the same restriction to other projects.
Requiring every project here to require an SCA (does sourcejuicer even
require that I wonder...) will simply discourage community members from
sharing their innovations in the most beneficial way possible with the
opensolaris.org community, or will cause them to initiate those projects
elsewhere simply to avoid the silly requirement.
Under the current system, a project could easily be created and approved
and simply host everything but the actual code on opensolaris.org
therefore bypassing the SCA requirement and making the whole thing look
rather silly to start with.
Cheers,
John Plocher wrote:
This sounds more like a SMI issue than an OGB one, since the SCA
policy is one invented by SMI for its own use; I am not sure what you
wish the OGB to do here - or if the OGB can do it. Can you tell us
more?
-John
On Sun, Dec 6, 2009 at 4:17 PM, Shawn Walker <swal...@opensolaris.org> wrote:
Alan Burlison wrote:
Shawn Walker wrote:
While we require SCAs for those that contribute patches to pkg(5), that
is not true of all os.org repositories.
No, that's wrong. All contributions to any repository that we host must
to be covered by an SCA, or by virtue of Sun employment.
http://hub.opensolaris.org/bin/view/Main/lead_reference
Then the policy is wrong as well and seems questionable at best. Not a
problem for you Alan, but...
Not all code used everywhere on os.org even *needs* an SCA.
And it seems like there is a good chance this policy is not being enforced
100%.
Can we please fix this policy?
--
Shawn Walker
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
