1 |
On Wed, Jan 10, 2018 at 3:48 PM, M. J. Everitt <m.j.everitt@×××.org> wrote: |
2 |
|
3 |
> On 10/01/18 19:31, Alec Warner wrote: |
4 |
> |
5 |
> On Wed, Jan 10, 2018 at 2:06 PM, Michał Górny <mgorny@g.o> wrote: |
6 |
> |
7 |
>> W dniu śro, 10.01.2018 o godzinie 09∶11 -0800, użytkownik Matt Turner |
8 |
>> napisał: |
9 |
>> > On Wed, Jan 10, 2018 at 1:55 AM, Michał Górny <mgorny@g.o> |
10 |
>> wrote: |
11 |
>> > > W dniu wto, 09.01.2018 o godzinie 17∶08 -0800, użytkownik Matt Turner |
12 |
>> > > napisał: |
13 |
>> > > > On Tue, Jan 9, 2018 at 1:20 PM, Andreas K. Huettel < |
14 |
>> dilfridge@g.o> wrote: |
15 |
>> > > > > During the last Gentoo council meeting, the decision was made to |
16 |
>> implement |
17 |
>> > > > > changes to the gentoo-dev mailing list [1]. |
18 |
>> > > > > |
19 |
>> > > > > These changes affect only the gentoo-dev mailing list, and will |
20 |
>> come into |
21 |
>> > > > > effect on 23 January 2018. |
22 |
>> > > > > |
23 |
>> > > > > * Subscribing to the list and receiving list mail remains as it |
24 |
>> is now. |
25 |
>> > > > > * Posting to the list will only be possible to Gentoo developers |
26 |
>> and |
27 |
>> > > > > whitelisted additional participants. |
28 |
>> > > > > * Whitelisting requires that one developer vouches for you. We |
29 |
>> intend this |
30 |
>> > > > > to be as unbureaucratic as possible. |
31 |
>> > > > > * Obviously, repeated off-topic posting as well as behaviour |
32 |
>> against the |
33 |
>> > > > > Code of Conduct [2] will lead to revocation of the posting |
34 |
>> permission. |
35 |
>> > > > > |
36 |
>> > > > > If, as a non-developer, you want to participate in a discussion on |
37 |
>> > > > > gentoo-dev, |
38 |
>> > > > > - either reply directly to the author of a list mail and ask |
39 |
>> him/her to |
40 |
>> > > > > forward your message, |
41 |
>> > > > > - or ask any Gentoo developer of your choice to get you |
42 |
>> whitelisted. |
43 |
>> > > > > |
44 |
>> > > > > If, as a developer, you want to have someone whitelisted, please |
45 |
>> comment on |
46 |
>> > > > > bug 644070 [3]. Similar to Bugzilla editbugs permission, if you |
47 |
>> are vouching |
48 |
>> > > > > for a contributor you are expected to keep an eye on their |
49 |
>> activity. |
50 |
>> > > > |
51 |
>> > > > It seems like the obvious way this fails is some Gentoo developer |
52 |
>> acks |
53 |
>> > > > one of the problem people. I don't think that's particularly |
54 |
>> unlikely. |
55 |
>> > > > Then what do we do? |
56 |
>> > > > |
57 |
>> > > |
58 |
>> > > Then it becomes comrel business. |
59 |
>> > |
60 |
>> > If that was an effective solution, wouldn't the problem already be |
61 |
>> solved? |
62 |
>> |
63 |
>> One of the problems mentioned before was that a person could easily |
64 |
>> evade the ban via subscribing from another e-mail address. In this case |
65 |
>> it's no longer possible, as he would need to obtain the vouching for his |
66 |
>> new e-mail address, and for that he would first have to have something |
67 |
>> positive to post. |
68 |
>> |
69 |
>> Of course this relies on developers not vouching for new people out of |
70 |
>> the blue but expecting them to have something to contribute first. |
71 |
>> |
72 |
> |
73 |
> This sounds like an amazing fundraising opportunity. |
74 |
> |
75 |
> https://www.gentoo.org/donate/ |
76 |
> |
77 |
> Get membership posting privs. |
78 |
> |
79 |
> -A |
80 |
> |
81 |
> |
82 |
>> |
83 |
>> -- |
84 |
>> Best regards, |
85 |
>> Michał Górny |
86 |
>> |
87 |
>> |
88 |
>> |
89 |
> Do I read a hint of sarcasm there too Alec?! :] |
90 |
> |
91 |
|
92 |
As I (attempted badly) to explain on IRC; I don't like this decision. But |
93 |
ultimately the project elects the council to do stuff like this. |
94 |
As engineers I think we remain bad at making decisions that are imperfect, |
95 |
or based on incomplete information. I don't |
96 |
fault the council for taking action (even action I don't like) because I |
97 |
believe they felt something had to be done to improve the lists. |
98 |
|
99 |
No one should be afraid to try something because it might not work; trying |
100 |
things are how we learn. |
101 |
|
102 |
-A |