| 1 |
On Tue, Nov 27, 2018 at 10:16 AM Michał Górny <mgorny@g.o> wrote: |
| 2 |
> |
| 3 |
> Will that actually solve any problem, or just add another half-baked |
| 4 |
> solution with no benefit to the resulting status? In other words, would |
| 5 |
> SIE suddenly stop requiring you to alter copyright in ebuilds? |
| 6 |
|
| 7 |
++ |
| 8 |
|
| 9 |
It makes sense to ensure that the solution actually solves the problem |
| 10 |
before we simply implement it. |
| 11 |
|
| 12 |
If we really need such a file it would probably also make more sense |
| 13 |
to have it auto-generated from git commit headers, which could use a |
| 14 |
standardized format. This would actually provide more useful data |
| 15 |
around authorship/copyright than a generic file with a list of names |
| 16 |
anyway. Certainly standards like SPDX should be leveraged. These |
| 17 |
tags could be optional in git, but anybody who wants to use these tags |
| 18 |
could do so and tools that parse them could be created by those |
| 19 |
interested in this information. |
| 20 |
|
| 21 |
-- |
| 22 |
Rich |
| 23 |
|
| 24 |
-- |
| 25 |
Rich |
Archives