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