CLAs and Github

[Andrew Whitworth]

What the CLA does is basically reinforces what is already stipulated
in the Artistic License 2.0, which we use: The contributor grants a
license to the foundation to use the contributions on their behalf.
Basically, the CLA is just a signed record that the contributor agrees
to our license, which is nice but not strictly necessary. Under
section 4(c)(i) of the license, anybody who makes publicly-available
modifications to the software must release those contributions under
the same license.

The CLA is nice because it's documented proof that the foundation has
a license to do things with Parrot on the behalf of the contributors.
We obviously do want this kind of protection for the core VM. What's
not so clear is whether or not we want these kinds of records for the
other projects under the Parrot organization on github.

Parrot: Yes.
Plumage: probably
Pirate and PIRC: probably (PIRC was included under CLAs for a while
when it was in the repo anyway)
the other HLLs: probably not. Ideally, we would like many of these
things to mature and be adopted by other people

I think we really would like to be able to grant commit bits to the
HLLs for non-CLA committers.

It seems like we would want at least two teams:

1) Core committers (commit to everything)
2) Ancillary committers (commit to things that aren't "core")

We also obviously want the admin/owner group, but we may also want a
group that has admin access to the non-core repos as well, to add new
committers to that group.

There really are a lot of ways we could organize things. Thanks for
bringing it up.

--Andrew Whitworth



On Tue, Feb 15, 2011 at 5:09 PM, Jonathan "Duke" Leto <jonathan at leto.net> wrote:
> Howdy,
>
> Do all people with commit bits need to have CLAs? Do only people with
> commit bits to parrot.git need CLAs?
>
> Do we want to separate out "core commit bits" from "HLL commit bits" ?
> It would be easy to do with Github teams, the question is:
>
> Do we want to?
>
> Please discuss.
>
> Duke
>
> --
> Jonathan "Duke" Leto
> jonathan at leto.net
> http://leto.net
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>