1 |
On Tue, Nov 13, 2018 at 6:46 PM William Hubbs <williamh@g.o> wrote: |
2 |
> |
3 |
> On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote: |
4 |
> > On Tue, Nov 13, 2018 at 10:32 AM William Hubbs <williamh@g.o> wrote: |
5 |
> > > |
6 |
> > > Since we do not do copyright assignment any more and the glep allows for |
7 |
> > > traditional attribution, if some entity |
8 |
> > > (company, person etc) has a desire for a copyright notice in |
9 |
> > > their work, the case for not allowing this is very weak at best, so we will |
10 |
> > > end up with more and more ebuilds that want to use traditional copyright |
11 |
> > > attribution, and once an ebuild is switched over, it is problematic to |
12 |
> > > switch back. |
13 |
> > |
14 |
> > So, the purpose of allowing specific copyright holders to be named was |
15 |
> > to cover cases where we're forking foreign code, not to basically |
16 |
> > introduce a variant on the BSD advertising clause. IMO people who are |
17 |
> > only willing to contribute FOSS if their name gets put in a prominent |
18 |
> > location might do better to contribute elsewhere. |
19 |
> |
20 |
> Do you feel this way about corporations as well? Do you think the Linux |
21 |
> kernel maintainers should go and rip out all copyright notices other |
22 |
> than Linus Torvalds and maybe the Linux Foundation? |
23 |
|
24 |
Give me an example of a Linux kernel source file that contains a |
25 |
multiline table of years and copyright holders. At best you'll find |
26 |
random notices scattered around files in my experience, mostly because |
27 |
of how the code was pulled in from outside. |
28 |
|
29 |
> > |
30 |
> > > Multiple-lines would be much easier to maintain, and |
31 |
> > > there is no cost performance wise for them. |
32 |
> > |
33 |
> > Except for spam in our files. |
34 |
> |
35 |
> And how does that affect performance? |
36 |
|
37 |
I never claimed it did. It is visual clutter. Eyeballs willing to |
38 |
maintain our ebuilds are far more scarce than CPU cycles. |
39 |
|
40 |
And if we don't care about visual clutter, then why do we have repoman |
41 |
warn about extraneous whitespace (as we should)? |
42 |
|
43 |
> |
44 |
> Look anywhere outside the Gentoo tree. For that matter, take the Linux |
45 |
> kernel, or even in the systemd source, there are several places with |
46 |
> multiple copyright notices in them. |
47 |
|
48 |
Find me any project that organizes these into tables with years and |
49 |
copyright holders at the top of the file consistently as a matter of |
50 |
policy. As far as I can tell the Linux project has no consistent |
51 |
policy on this front, and systemd inherited numerous outside source |
52 |
trees as its scope expanded. |
53 |
|
54 |
-- |
55 |
Rich |