1 |
On Wed, Jan 10, 2018 at 1:55 AM, Michał Górny <mgorny@g.o> wrote: |
2 |
> W dniu wto, 09.01.2018 o godzinie 17∶08 -0800, użytkownik Matt Turner |
3 |
> napisał: |
4 |
>> On Tue, Jan 9, 2018 at 1:20 PM, Andreas K. Huettel <dilfridge@g.o> wrote: |
5 |
>> > During the last Gentoo council meeting, the decision was made to implement |
6 |
>> > changes to the gentoo-dev mailing list [1]. |
7 |
>> > |
8 |
>> > These changes affect only the gentoo-dev mailing list, and will come into |
9 |
>> > effect on 23 January 2018. |
10 |
>> > |
11 |
>> > * Subscribing to the list and receiving list mail remains as it is now. |
12 |
>> > * Posting to the list will only be possible to Gentoo developers and |
13 |
>> > whitelisted additional participants. |
14 |
>> > * Whitelisting requires that one developer vouches for you. We intend this |
15 |
>> > to be as unbureaucratic as possible. |
16 |
>> > * Obviously, repeated off-topic posting as well as behaviour against the |
17 |
>> > Code of Conduct [2] will lead to revocation of the posting permission. |
18 |
>> > |
19 |
>> > If, as a non-developer, you want to participate in a discussion on |
20 |
>> > gentoo-dev, |
21 |
>> > - either reply directly to the author of a list mail and ask him/her to |
22 |
>> > forward your message, |
23 |
>> > - or ask any Gentoo developer of your choice to get you whitelisted. |
24 |
>> > |
25 |
>> > If, as a developer, you want to have someone whitelisted, please comment on |
26 |
>> > bug 644070 [3]. Similar to Bugzilla editbugs permission, if you are vouching |
27 |
>> > for a contributor you are expected to keep an eye on their activity. |
28 |
>> |
29 |
>> It seems like the obvious way this fails is some Gentoo developer acks |
30 |
>> one of the problem people. I don't think that's particularly unlikely. |
31 |
>> Then what do we do? |
32 |
>> |
33 |
> |
34 |
> Then it becomes comrel business. |
35 |
|
36 |
If that was an effective solution, wouldn't the problem already be solved? |