On 10/24/2016 04:18 PM, Rich Freeman wrote: > On Mon, Oct 24, 2016 at 7:12 PM, Matt Turner <matts...@gentoo.org> wrote: >> On Mon, Oct 24, 2016 at 4:03 PM, Rich Freeman <ri...@gentoo.org> wrote: >>> You cannot currently commit anything with a different copyright notice >>> to gentoo.git >> >> According to whom or what? >> > > https://devmanual.gentoo.org/ebuild-writing/file-format/index.html > Under ebuild header. > > This is a Gentoo policy. Repoman will complain if you violate this. > It will get noticed and treecleaned if you ignore repoman. Devs who > violate the policy will be warned, etc. > > The policy could be changed, and there have been discussions around > improvements: > https://dev.gentoo.org/~rich0/copyrightpolicy.xml > > The main issue I'm aware of with that draft is that it is painful to > track who has copyright on what to put the proper copyright notice on > each file. Suggestions are welcome. > This made me think of another scenario; let's say I have my own fork of Gentoo, maintained in an overlay complete with docs, etc, under an MIT or BSD license, but as a Gentoo developer, I must copyright under GPL. Could I do such dual licensing on a case-by-case basis because (in this hypothetical) I'm the original author of the ebuilds?
If so, then Matt's coworker could offer the same ebuild under a Gentoo-friendly license and maintain copyright on Google's overlay. The only question at that point would be Google's own copyright policy and whether or not its employees own any of what they produce on company time. -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
signature.asc
Description: OpenPGP digital signature
