4 ms·
It looks like Google owns the project and that, to contribute, you have to turn over copyrights [0]. I think the ownership makes it "by Google" more than employ
by gravypod 7y ago
It looks like Google owns the project and that, to contribute, you have to turn over copyrights [0]. I think the ownership makes it "by Google" more than employing the main dev.
[0] - https://cue.googlesource.com/cue/+/HEAD/doc/contribute.md#step-1_contributor-license-agreement https://cue.googlesource.com/cue/+/HEAD/doc/contribute.md#st...
- jsolson 7y agoThat's common to most projects released by Googlers. Options are either a getting the IP officially assigned over to yourself or releasing it under a Google copyright with a CLA: https://opensource.google.com/docs/creating/ https://opensource.google.com/docs/creating/ The latter is lower friction, in my opinion. This is especially common for "personal" projects that people end up working on or using on the clock. I don't know if this was the case with Cue specifically (this is the first I've heard of the project, but less boilerplate in my JSON has some appeal).
- magicalist 7y ago> that, to contribute, you have to turn over copyrights *grant a copyright license https://cla.developers.google.com/about/google-individual https://cla.developers.google.com/about/google-individual