| 1 |
On Tue, Nov 27, 2018 at 10:40:57AM -0500, Rich Freeman wrote: |
| 2 |
> On Tue, Nov 27, 2018 at 10:16 AM Michał Górny <mgorny@g.o> wrote: |
| 3 |
> > |
| 4 |
> > Will that actually solve any problem, or just add another half-baked |
| 5 |
> > solution with no benefit to the resulting status? In other words, would |
| 6 |
> > SIE suddenly stop requiring you to alter copyright in ebuilds? |
| 7 |
> |
| 8 |
> ++ |
| 9 |
> |
| 10 |
> It makes sense to ensure that the solution actually solves the problem |
| 11 |
> before we simply implement it. |
| 12 |
> |
| 13 |
> If we really need such a file it would probably also make more sense |
| 14 |
> to have it auto-generated from git commit headers, which could use a |
| 15 |
> standardized format. This would actually provide more useful data |
| 16 |
> around authorship/copyright than a generic file with a list of names |
| 17 |
> anyway. Certainly standards like SPDX should be leveraged. These |
| 18 |
> tags could be optional in git, but anybody who wants to use these tags |
| 19 |
> could do so and tools that parse them could be created by those |
| 20 |
> interested in this information. |
| 21 |
|
| 22 |
My understanding is yes. SIE legal doesn't care where the copyright is |
| 23 |
as long as it is there. |
| 24 |
|
| 25 |
A good example of this file would be the one in the golang upstream |
| 26 |
repo [1]. This file is not autogenerated and would only be updated as |
| 27 |
requested when people or organizations want to add themselves. |
| 28 |
|
| 29 |
I'm not sure auto generation is worth the work in this case since |
| 30 |
there is very little overhead in maintaining the file. You just add a |
| 31 |
person or organization when they request it. If they don't request it, |
| 32 |
they don't care. |
| 33 |
|
| 34 |
William |
| 35 |
|
| 36 |
[1] https://raw.githubusercontent.com/golang/go/master/AUTHORS |
Archives