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