1 |
On Sun, 2019-06-30 at 09:11 +0200, Patrick Lauer wrote: |
2 |
> On 6/15/19 11:49 AM, Andrew Savchenko wrote: |
3 |
> > On Sat, 15 Jun 2019 12:42:20 +0300 Andrew Savchenko wrote: |
4 |
> > > Hi all! |
5 |
> > > |
6 |
> > > Last year we had a good initiative: it addition to (or even instead |
7 |
> > > of) manifests nominees were asked questions by voters. So let's |
8 |
> > > continue this year. |
9 |
> > > |
10 |
> > > I propose to have one question per thread spawned by this e-mail to |
11 |
> > > keep discussion focused. If you have multiple questions, please |
12 |
> > > start multiple threads. If your question was already asked, please |
13 |
> > > join a thread. |
14 |
> > > |
15 |
> > > I'll ask my questions in subsequent e-mails. |
16 |
> > |
17 |
> > In my opinion GLEP 76 is the most controversial decision made by |
18 |
> > running council. While it fixed some long standing issues like |
19 |
> > copyright headers and proper acknowledgement of out of the tree |
20 |
> > contributors, it created grave problems: now some long-time |
21 |
> > contributors and even developer are seriously discriminated because |
22 |
> > they want to keep their privacy. |
23 |
> > |
24 |
> > What is your opinion on this problem? |
25 |
> |
26 |
> I think everyone involved in the discussion meant well, but different |
27 |
> cultural starting points (e.g. different ideas about what copyright |
28 |
> means), trying to find a compromise, not being experienced with legal |
29 |
> language/concepts (or even legal concepts not translating well between |
30 |
> languages) etc.etc. conspired to make this a very weirdly shaped thing |
31 |
> that imo doesn't do what people think it does. |
32 |
> |
33 |
> I mostly ignored the discussion because it was a too high volume of |
34 |
> email on a topic where I don't see a strong need to act, in hindsight |
35 |
> that was naive optimism on my side. |
36 |
|
37 |
It's funny you say that given that you've trolled the result |
38 |
for 4 months. |
39 |
|
40 |
> |
41 |
> > Should GLEP 76 be left as is? |
42 |
> |
43 |
> No,it should be improved. |
44 |
> E.g. having signed commits, and adding signed-off-by, is ... weird. |
45 |
> It also leads to semantic satiation, where every commit has |
46 |
> signed-off-by, every commit, signed-off-by, signed-off-by ... |
47 |
> |
48 |
> And since it's autogenerated it doesn't really mean anything. It would |
49 |
> make more sense to add it *only* to commits from not-gentoo-devs, since |
50 |
> all the other commits are already signed by authenticated users. |
51 |
|
52 |
How would you verify that devs have actually read the new spec, and not |
53 |
just ignored it? Do you prefer that we disabled commit access for |
54 |
everyone, and then asked everyone to make a vow? |
55 |
|
56 |
-- |
57 |
Best regards, |
58 |
Michał Górny |