In the Council meeting 10th of December 2017 it was determined that the gentoo-dev mailing list is to be restricted for posting for gentoo devs and users that have been whitelisted and monitored by gentoo devs. The whitelisting is tracked in bug 644070 similar to editbugs. I request that infra implementes posting restrictions according to these criteria.
Counterproposal: Council admits it made a mistake and reverts a decision that is contrary to the spirit of open communities.
(In reply to Michael Palimaka (kensington) from comment #1) > Counterproposal: Council admits it made a mistake and reverts a decision > that is contrary to the spirit of open communities. I refer you to 20180211 summary; Mailing list posting restrictions ================================= The council discussed several options, like lifting the restrictions entirely, using moderation, or blacklisting instead of a whitelisting. Finally, the previous decisions were confirmed. K_F volunteered to liaise with infra for implementation. - Vote: The council confirms its decisions taken in the 20171210 meeting about mailing list restrictions. Accepted with 4 yes votes, 1 no vote, and 2 abstentions.
(In reply to Kristian Fiskerstrand from comment #2) > (In reply to Michael Palimaka (kensington) from comment #1) > > Counterproposal: Council admits it made a mistake and reverts a decision > > that is contrary to the spirit of open communities. > > I refer you to 20180211 summary; > > Mailing list posting restrictions > ================================= > The council discussed several options, like lifting the restrictions > entirely, using moderation, or blacklisting instead of a whitelisting. > Finally, the previous decisions were confirmed. K_F volunteered to > liaise with infra for implementation. > > - Vote: The council confirms its decisions taken in the 20171210 > meeting about mailing list restrictions. > Accepted with 4 yes votes, 1 no vote, and 2 abstentions. I refer you to comment #1.
It was mentioned on the mailing list this should have been discussed months ago, yet many people did come out against this decision and were ignored.
Restricting bugs to developer-only for now to avoid the flame-fest on the mailing list swapping over to the bug tracker. This is merely about the technical implementation of the council decision.
Where is the proper outlet for these frustrations then? Not giving an outlet is just asking for problems.
I'm lifting the restriction as I don't see a need for this bug to be locked, but I would remind people that this is a place to discuss the technical implementation of a council decision, not the decision itself.
(In reply to Kristian Fiskerstrand from comment #7) > I'm lifting the restriction as I don't see a need for this bug to be locked, > but I would remind people that this is a place to discuss the technical > implementation of a council decision, not the decision itself. As discussed on #gentoo-council I think we advocated for a thread on gentoo-project ML if further discussions are needed.
(In reply to Kristian Fiskerstrand from comment #0) > In the Council meeting 10th of December 2017 it was determined that the > gentoo-dev mailing list is to be restricted for posting for gentoo devs and > users that have been whitelisted and monitored by gentoo devs. The > whitelisting is tracked in bug 644070 I have one technical suggestion. Keeping list of whitelisted users in a bug looks like a poor technical design. Therefore I suggest that this list be maintained in a human-readable, machine-parseable file (e.g. JSON or CSV) in a repository writable by all Gentoo developers. This file would be parsed by some part of mailing list software.
And to reduce spam, the list of whitelisted users (regardless of where it is maintained) should not be readable for unauthenticated people.
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #10) > And to reduce spam, the list of whitelisted users (regardless of where it is > maintained) should not be readable for unauthenticated people. ACk, we have a list of addresses in a git repo that devs can RW, but no one (externally) can read. Note that I expect this git repo to be leaked by grumpy developers (many whom have RW access to the whitelist.) There is a challenge with mail deny messages (where a subscriber tries to send a message and is denied) because we will send them a denial. This is used by spammers to send backscatter spam. Its possible its only really bad when anyone can post (so anyone can get the mail) as opposed to only issues denials to subscribers. Will think about this more. -A
(In reply to Alec Warner from comment #11) > ACk, we have a list of addresses in a git repo that devs can RW, but no one > (externally) can read. [...] Thanks a lot for your work on that!
Can you please provide a status update on this including an ETA for implementation?
(In reply to Kristian Fiskerstrand from comment #13) > Can you please provide a status update on this including an ETA for > implementation? I sent mail to council and infra with a draft email for the -dev list to discuss initial whitelist population. -A
Asking for an update (bug popped up in council monthly meeting). Thanks!
(In reply to Sergei Trofimovich from comment #15) > Asking for an update (bug popped up in council monthly meeting). > > Thanks! I sent my (now reviewed) draft to the -dev list. We will allow some time for the whitelist to be populated and then move to enforcement, probably in two weeks (mostly due to upcoming vacation for me.) -A
(In reply to Sergei Trofimovich from comment #17) > Asking for an update (bug popped up in council monthly meeting). > > Thanks! Its enabled now. Enjoy! -A
Could we please indicate this somehow on: 1. https://www.gentoo.org/get-involved/mailing-lists/ 2. https://www.gentoo.org/get-involved/mailing-lists/all-lists.html ? It seems really silly to have 'post to X' links when 'external' people clearly can't post to list.
(In reply to Michał Górny from comment #19) > Could we please indicate this somehow on: > > 1. https://www.gentoo.org/get-involved/mailing-lists/ > 2. https://www.gentoo.org/get-involved/mailing-lists/all-lists.html > > ? It seems really silly to have 'post to X' links when 'external' people > clearly can't post to list. Marked moderated in mailinglists.yaml in 6234b92a4b93b3fa6895363f700b427124c2b165. -A
