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