1 |
On Wed, Jul 28, 2021 at 10:42 AM Sam James <sam@g.o> wrote: |
2 |
|
3 |
> |
4 |
> |
5 |
> > On 28 Jul 2021, at 12:50, Thomas Deutschmann <whissi@g.o> wrote: |
6 |
> > |
7 |
> > Hi, |
8 |
> > |
9 |
> > this was also my understanding. GLEP 76 applies to everyone -- no |
10 |
> exception and during discussion we explicit agreed that it's better to |
11 |
> reject any contribution from individual(s) who cannot do the sign-off for |
12 |
> whatever reason. |
13 |
> > |
14 |
> > Keep in mind: Whoever will proxy such a commit will be 100% responsible |
15 |
> in the end. For purely self-protection reasons nobody should proxy a commit |
16 |
> he/she doesn't understand, doesn't know the origin or in general has any |
17 |
> doubts about. _You_ will be responsible for this because _you_ introduced |
18 |
> the commit in Gentoo. |
19 |
> |
20 |
> Agreed, but s/commit/contribution/? |
21 |
> |
22 |
> > |
23 |
> > That said, an individual who doesn't want to do the sign-off for |
24 |
> whatever reason could also contribute without getting attribution if |
25 |
> contributor will find a developer who is willing to do this (=what happens |
26 |
> for most small proposed bug fixes via b.g.o for example). |
27 |
> > |
28 |
> > |
29 |
> |
30 |
> Right. |
31 |
> |
32 |
> Part of the reason why I'm keen on this proposal is that there's no |
33 |
> practical difference between accepting a patch on Bugzilla and |
34 |
> re-committing it under my own name and just merging their PR. I suppose if |
35 |
> we're clear on guidelines, |
36 |
> dropping signoffs where people admit their names are fake would be okay, |
37 |
> but it still feels like extra work for developers when merging PRs. |
38 |
> |
39 |
> best, |
40 |
> sam |
41 |
> |
42 |
|
43 |
|
44 |
|
45 |
|
46 |
I've not followed this full discussion, but has the propensity for projects |
47 |
other than Gentoo to add the git signed-off-by field to commits on behalf |
48 |
of people been brought up? I've seen that happen in OpenWRT twice, as well |
49 |
as other random projects. |
50 |
|
51 |
I can't imagine that using the git signed-off-by field is in any way |
52 |
legally meaningful unless you're also requiring developers register their |
53 |
public key with Gentoo, and then sign their commits with their pub/priv |
54 |
key. You also have to consider that the signed-off-by field is used by |
55 |
different projects in very different ways, and there's no legal precedent |
56 |
that I'm aware of that implies that signed-off-by means "I wrote this", |
57 |
since there are project that use it as "I've approved this". |
58 |
|
59 |
Anything less than that is just asking for someone to, entirely plausibly, |
60 |
claim that they were not the person who added the signed-off-by field to |
61 |
the commit in question, and good luck proving otherwise. Or that they meant |
62 |
something very different than what Gentoo thinks they did when they added |
63 |
signed-off-by to their commit. |