1 |
On 11/25/18 4:22 AM, Rich Freeman wrote: |
2 |
> On Sat, Nov 24, 2018 at 9:04 PM Sarah White <kuzetsa@××××××××××.ovh> wrote: |
3 |
>> On 11/24/18 8:37 PM, Rich Freeman wrote: |
4 |
>> |
5 |
>> So if it isn't meant to say that gentoo will be looking |
6 |
>> after the legal aspects of a FOSS/Libre-copyleft licensed |
7 |
>> package or document or tool, then what's the purpose to |
8 |
>> put gentoo's name on it? |
9 |
> You have to put somebody's name in the notice, and it was felt that |
10 |
> "Gentoo Authors" gets the job done. "Gentoo Authors" is not Gentoo. |
11 |
> They are the authors contributing to the ebuild. |
12 |
> |
13 |
>> There's some innuendo and/or implication that copyright |
14 |
>> holders who have their own name listed in a copyright |
15 |
>> notice are intending to do something other than participate |
16 |
>> in FOSS/Libre work, or perhaps may not truly wish to |
17 |
>> contribute in good faith. |
18 |
> Not at all. The issue is that accumulating names creates clutter, and |
19 |
> create some sense that people who are named are doing more than people |
20 |
> who aren't named, which may lead to more people wanting to be named. |
21 |
> |
22 |
> This is also why the policy allows for an AUTHORS file or use of a |
23 |
> VCS. The intent isn't to deny people credit. It is to provide credit |
24 |
> in a more reasonable manner vs having it spammed on the first lines of |
25 |
> every file in the tree, and try to create a culture where we don't |
26 |
> equate copyright notice with credit or property. |
27 |
> |
28 |
|
29 |
I've already patched repoman to add my name automatically on every |
30 |
ebuild that I commit, similarily to how it works with Foundation -> |
31 |
Authors now. I also intend to join amd64 & x86 stabilization teams. Then |
32 |
when I have my name on 10 000 ebuilds, I'm sure Google will hire me! :) |