1 |
On Wed, Jul 7, 2021 at 5:27 AM Ulrich Mueller <ulm@g.o> wrote: |
2 |
> |
3 |
> >>>>> On Wed, 07 Jul 2021, Robin H Johnson wrote: |
4 |
> |
5 |
> > TL;DR: |
6 |
> > Please change the format of metadata/AUTHORS to yaml-based list of "key: |
7 |
> > [value,...]" where key is the identity of a Gentoo developer, and the |
8 |
> > list is copyright holders that the developer has worked for. |
9 |
> |
10 |
> Using the Gentoo uid as the key would imply that contributors other than |
11 |
> developers cannot be listed in the file. Is this a valid assumption? |
12 |
|
13 |
I would say no. Also, you can't assume that somebody introducing |
14 |
commits owned by some entity is employed or even associated with that |
15 |
entity. |
16 |
|
17 |
Think about the eudev fiasco, which was also something that drove the |
18 |
copyright policy. Suppose I want to add some 3rd party copyrighted |
19 |
material to the repo and have done my homework to ensure it is |
20 |
license-compatible. I may need to add them to the AUTHORS file so |
21 |
that we're not just removing their copyright attribution and causing a |
22 |
huge controversy. However, I'm not associated with them in any way, |
23 |
and neither are any of my other commits. I'm just adding their stuff |
24 |
to the repo in this one commit. I don't want to be listed in the |
25 |
AUTHORS file implying in some way that I am employed by EvilCorp. I'm |
26 |
just borrowing their code, legally. |
27 |
|
28 |
The AUTHORS file is just a list of anybody who wishes (or who we |
29 |
assume might wish) to be acknowledged in the copyright attributions. |
30 |
|
31 |
If you want to be able to map commits to original copyright owners it |
32 |
would probably be better to add a git header for this. |
33 |
|
34 |
-- |
35 |
Rich |