public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Call for agenda items - Council meeting 2018-02-11
Date: Wed, 11 Apr 2018 06:46:18 -0700	[thread overview]
Message-ID: <CAGDaZ_pNhfH1g84quhare2WA5xJ-OXoZkUm3pDk=Eq_MDgHvYQ@mail.gmail.com> (raw)
In-Reply-To: <f09550a2-9b21-978d-c1e1-a4d611b9469d@gentoo.org>

I second the motion.

That said however I would personally not be against having individuals
personally banned or blacklisted or restricted or whatnot at the
discretion of the proper authorities should they engage in misconduct.

Such as proctors for example.

I also would be ok with people being sanctioned on a separate basis if
they should evade such a restriction.

Blatant spammers are an obvious example of being worthy of restriction.

All of the above said, however...I would not be against requiring
messages posted to the list (or any list for that example) to be
required to pass anti-spam measures, such as SPF or DKIM.

In that note, I would also like to suggest that SPF/DKIM be used as a
filter for messages being posted to the lists if they aren't already.

On Tue, Jan 30, 2018 at 2:02 AM, Michael Palimaka <kensington@gentoo.org> wrote:
> On 01/30/2018 04:32 AM, Michał Górny wrote:
>>
>> 2. Continuation on mailing list posting restrictions
>> ====================================================
>>
>> We haven't enforced the gentoo-dev posting restrictions so far. I have
>> been approached by a user yesterday who wrongly thought he couldn't post
>> to the list. I think this situation is at least confusing.
>>
>> I believe we should either withdraw the earlier decision and explicitly
>> announce that posting to gentoo-dev will not be restricted to avoid
>> further confusion, or enforce it (how?).
>>
>> That said, I think the list has improved for now, so maybe we don't need
>> to do that after all. Especially given the upcoming possibility of
>> Proctors revival and/or moderation via mailman.
>>
>
> I'd just like to voice my support for withdrawing the earlier decision
> and keeping the mailing list open to all. Open communication channels
> are critical for maintaining an open community.
>


      reply	other threads:[~2018-04-11 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 13:05 [gentoo-project] Call for agenda items - Council meeting 2018-02-11 Ulrich Mueller
2018-01-29 17:32 ` Michał Górny
2018-01-30 10:02   ` [gentoo-project] " Michael Palimaka
2018-04-11 13:46     ` Raymond Jennings [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGDaZ_pNhfH1g84quhare2WA5xJ-OXoZkUm3pDk=Eq_MDgHvYQ@mail.gmail.com' \
    --to=shentino@gmail.com \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox