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