Opened 15 months ago

Last modified 11 months ago

#45 assigned enhancement

coop copyright

Reported by: ejs Owned by: mbooth
Priority: major Milestone: Modernisation
Component: misc Keywords:
Cc:

Description

Three ownership and licensing of the shared work, such as the wiki and services repo, should be clearly stated.

Change History (4)

comment:1 Changed 14 months ago by ejs

Owner: changed from somebody to mbooth
Status: newassigned

comment:2 Changed 12 months ago by ejs

Milestone: AGM 2018Modernisation

comment:3 Changed 11 months ago by mbooth

I would propose that we have a Contributor License Agreement that must be signed by members who are contributing to our code base. This would assign copyrights to the Co-op such that the Co-op as a whole can decide how to license our original works (mostly only ansible scripts at this point).

This has at least two benefits:

  • Protects the individual contributors -- in any license squabble, because the co-op owns the copyright, it's the co-op that becomes the target of lawsuits -- we could otherwise only be able to act on license violations for code on which we own the copyright
  • Protects the co-op from bad faith contributors -- if we get a contribution that turns out to have originated in some proprietary software and the software author tries to sue us, we can point to the CLA to shift the liability back onto the contributor because they contractually agreed via the CLA that their contributions were not infringing

I like the Apache Foundation individual contributor license agreement, which would make a good template from which to start drafting our own:

https://www.apache.org/licenses/icla.pdf

Other background reading:

http://oss-watch.ac.uk/resources/cla

comment:4 Changed 11 months ago by gjm

Yes, I would be happy with starting out from the Apache version. Some of the preamble will need a bit of a rework - it does need to be clear about the limits of what this applies to for instance.

Note: See TracTickets for help on using tickets.