| 1 |
>>>>> On Sun, 16 Sep 2018, Michał Górny wrote: |
| 2 |
|
| 3 |
> Just FYI: the Trustees have approved GLEP 76 aka our new copyright |
| 4 |
> policy [1]. While the exact implementation details are to be determined |
| 5 |
> yet, please note that *Signed-off-by* line will mean you are certifying |
| 6 |
> our GCO [2]. |
| 7 |
|
| 8 |
> Since some developers were giving the sign-off 'in blanco' so far, |
| 9 |
> I would like to emphasize that now it will actually mean agreeing to |
| 10 |
> the document. Unless you have read the new policy and agreed with it, |
| 11 |
> please don't do that. |
| 12 |
|
| 13 |
I wonder how we should treat those existing Signed-off-by lines in the |
| 14 |
tree. |
| 15 |
|
| 16 |
We could either say that we ignore any such lines on commits before |
| 17 |
2018-09-16 00:00:00 UTC, because there was no policy in place. |
| 18 |
|
| 19 |
Or we could say that they certify the commit under the Linux DCO 1.1 |
| 20 |
(https://developercertificate.org/), because in absence of an explicit |
| 21 |
policy that's the only meaningful interpretation of a Signed-off-by |
| 22 |
line. |
| 23 |
|
| 24 |
Presumably, the first alternative is cleaner. Especially, since there |
| 25 |
are commits with a Signed-off-by line that don't comply with the |
| 26 |
conditions of the Linux DCO. |
| 27 |
|
| 28 |
Ulrich |
| 29 |
|
| 30 |
> [1]:https://www.gentoo.org/glep/glep-0076.html |
| 31 |
> [2]:https://www.gentoo.org/glep/glep-0076.html#certificate-of-origin |
Archives