Hi Maxim and Andreas,
On 8/3/26 06:16, Maxim Cournoyer wrote:
Hi Andreas,
Andreas Enge <[email protected]> writes:
>
So if someone ticks the box "this code is not redistributable", I will
not redistribute it... If someone hides the fact that their code is not
redistributable, I may apply it since we assume that by making a pull
request, contributors take the stance that the code is under their
copyright and they take responsibility for it.
We could start using 'Signed-of-by' git trailers the way the project
that created them uses them, that is, as some kind of legally binding (I
assume, not being a lawyer) confirmation from the author that they
believe the copyright on the changes submitted is owned by them and
clear of licensing issues.
One thing I'm confused about, is that there seems to be no
company/organizational copyright lines in Guix. I would expect that
some of us have created Guix packages as "work for hire", which often
means the copyright is with their employer. Which is fine, because
employers can like open source too.
I was assuming that we assume that contributors believe they can
distribute the code, either because they have the copyright themselves,
or because they have permission by the copyright holder (e.g. their
employer, or another GPL project, etc.), or because there is no
copyright on the contribution (e.g. public domain, or because there was
no creativity involved, etc.).
Something similar to what GitHub has this in it's Terms of Service [1]:
> 6. Contributions Under Repository License
>
> Whenever you add Content to a repository containing notice of a
> license, you license that Content under the same terms, and you agree
> that you have the right to license that Content under those terms. If
> you have a separate agreement to license that Content under different
> terms, such as a contributor license agreement, that agreement will
> supersede.
>
> Isn't this just how it works already? Yep. This is widely accepted as
> the norm in the open-source community; it's commonly referred to by
> the shorthand "inbound=outbound". We're just making it explicit.
[1]
https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
Hugo
