1 |
On Wed, 14 Nov 2018 07:50:48 -0800 Rich Freeman wrote: |
2 |
> On Tue, Nov 13, 2018 at 6:46 PM William Hubbs <williamh@g.o> wrote: |
3 |
> > |
4 |
> > On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote: |
5 |
> > > On Tue, Nov 13, 2018 at 10:32 AM William Hubbs <williamh@g.o> wrote: |
6 |
> > > > |
7 |
> > > > Since we do not do copyright assignment any more and the glep allows for |
8 |
> > > > traditional attribution, if some entity |
9 |
> > > > (company, person etc) has a desire for a copyright notice in |
10 |
> > > > their work, the case for not allowing this is very weak at best, so we will |
11 |
> > > > end up with more and more ebuilds that want to use traditional copyright |
12 |
> > > > attribution, and once an ebuild is switched over, it is problematic to |
13 |
> > > > switch back. |
14 |
> > > |
15 |
> > > So, the purpose of allowing specific copyright holders to be named was |
16 |
> > > to cover cases where we're forking foreign code, not to basically |
17 |
> > > introduce a variant on the BSD advertising clause. IMO people who are |
18 |
> > > only willing to contribute FOSS if their name gets put in a prominent |
19 |
> > > location might do better to contribute elsewhere. |
20 |
> > |
21 |
> > Do you feel this way about corporations as well? Do you think the Linux |
22 |
> > kernel maintainers should go and rip out all copyright notices other |
23 |
> > than Linus Torvalds and maybe the Linux Foundation? |
24 |
> |
25 |
> Give me an example of a Linux kernel source file that contains a |
26 |
> multiline table of years and copyright holders. At best you'll find |
27 |
> random notices scattered around files in my experience, mostly because |
28 |
> of how the code was pulled in from outside. |
29 |
|
30 |
Sure, from line 4 to line 10: |
31 |
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/random.c |
32 |
|
33 |
Multiline table with copyright holders and separate years for each |
34 |
one. |
35 |
|
36 |
> > Look anywhere outside the Gentoo tree. For that matter, take the Linux |
37 |
> > kernel, or even in the systemd source, there are several places with |
38 |
> > multiple copyright notices in them. |
39 |
> |
40 |
> Find me any project that organizes these into tables with years and |
41 |
> copyright holders at the top of the file consistently as a matter of |
42 |
> policy. As far as I can tell the Linux project has no consistent |
43 |
> policy on this front, and systemd inherited numerous outside source |
44 |
> trees as its scope expanded. |
45 |
|
46 |
We are not talking about demanding multiline headers for each |
47 |
ebuild, we are talking about a policy allowing such headers if |
48 |
necessary. This is the essentially same as Linux kernel does. |
49 |
|
50 |
Best regards, |
51 |
Andrew Savchenko |