Alan Burlison wrote: > Shawn Walker wrote: > >>> 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... > > The policy has been that way since the start. You may not personally > agree with it, that doesn't mean it is incorrect.
It is wrong based on the spirit of this community and its charter IMO. >> Not all code used everywhere on os.org even *needs* an SCA. > > Any code contributed to opensolaris.org could potentially be included in > OpenSolaris, and therefore needs to be covered as such. That's no > different to the way that projects such as Apache work. Except that isn't true either. As we've discovered in the past, code that is under an acceptable license such as BSD, etc. where the author has not wanted to go through the hassle of signing an SCA can still integrated and included into OpenSolaris under a different process. Yes, I'm splitting hairs here since the person integrating is a Sun employee or someone with an SCA holder. But it does point out that technically, the author of a given work does not have to have an SCA to get the work integrated. And as I also mentioned before, not *all* projects here need an SCA. I completely and totally understand the requirement for SMI maintained or initiated projects. That is not what I take issue with. I take issue with the blanket application to all projects on os.org which is a different problem. >> Can we please fix this policy? > > Only Sun Microsystems have the ability to change the policy. And the OGB is the liaison for that, hence the CC. As I said before, not a problem for you to solve, but it is a problem nonetheless. Cheers, -- Shawn Walker
