1 |
During the last Gentoo council meeting, the decision was made to implement |
2 |
changes to the gentoo-dev mailing list [1]. |
3 |
|
4 |
These changes affect only the gentoo-dev mailing list, and will come into |
5 |
effect on 23 January 2018. |
6 |
|
7 |
* Subscribing to the list and receiving list mail remains as it is now. |
8 |
* Posting to the list will only be possible to Gentoo developers and |
9 |
whitelisted additional participants. |
10 |
* Whitelisting requires that one developer vouches for you. We intend this |
11 |
to be as unbureaucratic as possible. |
12 |
* Obviously, repeated off-topic posting as well as behaviour against the |
13 |
Code of Conduct [2] will lead to revocation of the posting permission. |
14 |
|
15 |
If, as a non-developer, you want to participate in a discussion on |
16 |
gentoo-dev, |
17 |
- either reply directly to the author of a list mail and ask him/her to |
18 |
forward your message, |
19 |
- or ask any Gentoo developer of your choice to get you whitelisted. |
20 |
|
21 |
If, as a developer, you want to have someone whitelisted, please comment on |
22 |
bug 644070 [3]. Similar to Bugzilla editbugs permission, if you are vouching |
23 |
for a contributor you are expected to keep an eye on their activity. |
24 |
|
25 |
[1] https://projects.gentoo.org/council/meeting-logs/20171210-summary.txt |
26 |
[2] https://wiki.gentoo.org/wiki/Project:Council/Code_of_conduct |
27 |
[3] https://bugs.gentoo.org/644070 (alias g-dev-whitelist) |
28 |
|
29 |
-- |
30 |
Andreas K. Hüttel |
31 |
dilfridge@g.o |
32 |
Gentoo Linux developer |
33 |
(council, toolchain, perl, libreoffice, comrel) |