public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2019-07-21
Date: Fri, 12 Jul 2019 21:56:28 +0200	[thread overview]
Message-ID: <1840792.kWEk0IjtYx@pinacolada> (raw)
In-Reply-To: <d37cea218723a5ea280100d9d9c42c99579315f7.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

Am Montag, 8. Juli 2019, 07:36:03 CEST schrieb Michał Górny:
> On Mon, 2019-07-08 at 06:43 +0200, Ulrich Mueller wrote:
> > > > > > > On Sun, 07 Jul 2019, Michał Górny wrote:
> > > My second agenda item is: removing posting restrictions from gentoo-dev
> > > mailing list.
> 
> As for the attacks, I believe having active Proctors team is
> the
> solution.  After all, they provide more proactive approach
> and better
> response times than ComRel used to.

^ This. (That was the precise intention behind re-forming proctors.)
So now that we have the proctors we can give things a try again.
Attacks and hostile environment were the most critical part.

> As for the off-topics, I don't think we really solved it.  After all:
> 
> a. some of the problematic traffic has shifted to -project or other
> mailing lists,
> b. frequently *developers* are the source of the problem.

Shrug. Off-topic is not so critical. ["Mark all read."] Also, if we manage to 
keep the -dev list at least "off-topic but technical", that's nearly "on-
topic" again.

> The third problem mentioned is a minor one and I think we can live with
> it.

If a "support request" is technically challenging and interesting, why not. 
After all, we might learn something from it and improve Gentoo as a result. 
Also, it *is* interesting to learn what people are using Gentoo for. So this 
is something I can live with too.

> I would also like to remind that the initial proposal made sense because
> it restricted both -dev and -project, so the split between mailing lists
> was preserved.  The decision to restrict one but not the other has
> resulted in switching the split to 'devs only' and 'everyone', without
> matching change of rules.

Yes, and that specific decision was rather idi^H^H^H... never mind.
It was a horrible meeting.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2019-07-12 19:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 19:30 [gentoo-project] Call for agenda items - Council meeting 2019-07-21 Ulrich Mueller
2019-07-07 20:51 ` Michał Górny
2019-07-07 21:00 ` Michał Górny
2019-07-08  4:43   ` Ulrich Mueller
2019-07-08  5:36     ` Michał Górny
2019-07-08 13:50       ` Rich Freeman
2019-07-09  9:58         ` Ulrich Mueller
2019-07-12 19:56       ` Andreas K. Huettel [this message]
2019-07-21  0:22         ` Andrew Savchenko
2019-07-09  9:28   ` Lars Wendler
2019-07-10 13:55     ` William Hubbs
2019-07-10 14:07       ` Michael Everitt
2019-07-10 15:48         ` William Hubbs
2019-07-20 23:57       ` Andrew Savchenko
2019-07-20 23:48   ` Andrew Savchenko
2019-07-21  1:11     ` Raymond Jennings
2019-07-21  6:28     ` Michał Górny
2019-07-21 11:25       ` Andrew Savchenko
2019-07-21 11:52         ` Raymond Jennings
2019-07-21 13:33         ` Michael Orlitzky
2019-07-09  9:02 ` Haelwenn (lanodan) Monnier
2019-07-13  7:39   ` Ulrich Mueller
2019-07-13 10:53     ` Haelwenn (lanodan) Monnier
2019-07-13  3:28 ` desultory
2019-07-13  4:11   ` Matthew Thode
2019-07-13  6:56   ` Michał Górny
2019-07-13  7:09     ` Ulrich Mueller

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=1840792.kWEk0IjtYx@pinacolada \
    --to=dilfridge@gentoo.org \
    --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