1 |
On Sat, Nov 24, 2018 at 9:04 PM Sarah White <kuzetsa@××××××××××.ovh> wrote: |
2 |
> |
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 |
|
10 |
You have to put somebody's name in the notice, and it was felt that |
11 |
"Gentoo Authors" gets the job done. "Gentoo Authors" is not Gentoo. |
12 |
They are the authors contributing to the ebuild. |
13 |
|
14 |
> There's some innuendo and/or implication that copyright |
15 |
> holders who have their own name listed in a copyright |
16 |
> notice are intending to do something other than participate |
17 |
> in FOSS/Libre work, or perhaps may not truly wish to |
18 |
> contribute in good faith. |
19 |
|
20 |
Not at all. The issue is that accumulating names creates clutter, and |
21 |
create some sense that people who are named are doing more than people |
22 |
who aren't named, which may lead to more people wanting to be named. |
23 |
|
24 |
This is also why the policy allows for an AUTHORS file or use of a |
25 |
VCS. The intent isn't to deny people credit. It is to provide credit |
26 |
in a more reasonable manner vs having it spammed on the first lines of |
27 |
every file in the tree, and try to create a culture where we don't |
28 |
equate copyright notice with credit or property. |
29 |
|
30 |
> Does gentoo have a legitimate reason |
31 |
> to substitute a gentoo copyright notice in place of an |
32 |
> otherwise valid notice? |
33 |
|
34 |
The GLEP already allows existing works that have a non-Gentoo notice |
35 |
to keep their notice and add "and others" if there are further |
36 |
additions if they are brought into Gentoo from outside. This doesn't |
37 |
mean that we keep adding names to things. This was intended for |
38 |
things like eudev where we took an entire mature code body and forked |
39 |
it. This doesn't make as much sense for somebody contributing a 10 |
40 |
line ebuild to a repository containing thousands of ebuilds. |
41 |
|
42 |
> Is there an intent to create a sort of gatekeeper role |
43 |
> within the gentoo organization to request documentation |
44 |
> if a contributor uses a non-gentoo copyright notice? |
45 |
|
46 |
As the GLEP stands developers are already gatekeepers by virtue of |
47 |
being the only ones with commit access, and being required to sign off |
48 |
on the DCO. This requires them to be aware of the copyright status of |
49 |
the works they are committing, but we do not require the accumulation |
50 |
of documentation. However, the GLEP does not provide for multi-line |
51 |
notices and the intent isn't to keep accumulating them over time. The |
52 |
intent was to be able to bring outside stuff in as-is as long as the |
53 |
notices are reasonable and then just freeze them in time with "and |
54 |
others" or simplify them with Gentoo Authors if appropriate. |
55 |
|
56 |
-- |
57 |
Rich |