Re: gnumach copyright assignment

[Olaf Buddenhagen]

Hi,

On Thu, Sep 22, 2016 at 08:45:58PM +0300, Kalle Olavi Niemitalo wrote:
> Olaf Buddenhagen <olafbuddenhagen@gmx.net> writes:

> > The FSF doesn't actually require assignments for gnumach -- almost all
> > of gnumach is foreign code without FSF copyright anyway...
> 
> Thank you.  I had assumed that the old Mach code was
> grandfathered in, and that the FSF would require copyright
> assignments for any new additions.

No, that really wouldn't make too much sense: since gnumach code is
generally under a very permissive license, there is no need for the FSF
to hold copyright to allow for license changes or to prosecute license
violations...

> What does the FSF require for GNU Mach patches, then?
> A license grant and a signed employer disclaimer, perhaps?

That's actually a good question... Traditionally, most projects just
assume that if people contribute patches to files with a free software
license statement, that implies they have the right to do so. More
recently, many projects have moved to a more explicit "Developer's
Certificate of Origin".

Since almost all projects managed by the FSF require copyright
assignments, I'm not sure this has been considered at all. Maybe we
should bring it up -- but for now, I guess it's fine if you just send
the patches...

> I assume a dual license under GPLv2-or-later and the "MIT License"
> (the same terms as in xen/public/COPYING) would be acceptable.

Since MIT-style licenses are compatible with GPL (and pretty much any
other license), dual-licensing really makes little sense... I'm stumped
why some projects consider it a good idea.

When providing patches to existing files, just keep whatever is already
there; and if you add new files, go with the variant most commonly used
in existing files.

> Does the same policy apply to MIG as well?

Since it's formally part of gnumach, I *assume* the same policy
applies...

BTW, this is slightly off-topic: but AIUI, your main objection to
signing a copyright assignment is the requirement to provide updates on
your employer? Just in case it isn't clear: this is only really relevant
when you actually keep contributing after an employment change -- it's
not like you have to keep informing the FSF of your status forever just
because you contributed something in the past...

(If your are really weary, I think you could even do an assignment only
for past contributions -- though that would be pretty annoying I think,
as you'd have to renew it every time you make further contributions...)

-antrik-