public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: reopening gentoo-council
Date: Mon, 1 Aug 2011 23:02:02 +0200	[thread overview]
Message-ID: <20023.5194.711313.587404@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <4E370FE5.80102@gentoo.org>

>>>>> On Mon, 01 Aug 2011, Petteri Räty wrote:

> Your rational is a bit off or can be understood incorrectly in how
> the current rules go. Discussion should happen on the on topic
> mailing list (most of the time gentoo-dev or gentoo-project).
> gentoo-project is only used to submit threads to the agenda
> regardless of where the discussion happens. gentoo-dev-announce can
> be used to draw attention to important things. How do you propose
> people decide if something is gentoo-council material or do we go
> back to the situation where threads get fragmented to multiple
> mailing lists? If actual discussion happens elsewhere than
> gentoo-council then I don't think we need a separate mailing list
> just for handling agendas etc. Finally I think gentoo-project /
> gentoo-dev reach a wider audencience but we should get verified
> numbers from infra.

gentoo-dev, -project, -dev-announce ... this would mean that we split
discussions between three mailing lists at least. (Probably more, for
example PMS/EAPI related stuff should be discussed on gentoo-pms then.)

That's too complicated for my simple mind.

Ulrich



  reply	other threads:[~2011-08-01 21:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 17:55 [gentoo-project] Preparations Council meeting 2011-08-09 Fabian Groffen
2011-07-31 16:51 ` Ulrich Mueller
2011-08-01 20:43   ` [gentoo-project] Re: reopening gentoo-council Petteri Räty
2011-08-01 21:02     ` Ulrich Mueller [this message]
2011-08-01 23:06       ` Jorge Manuel B. S. Vicetto
2011-08-02  0:35         ` Ulrich Mueller
2011-07-31 19:03 ` [gentoo-project] Preparations Council meeting 2011-08-09 Markos Chandras
2011-08-01 18:54   ` Fabian Groffen
2011-08-01 17:57 ` Markos Chandras
2011-08-01 18:59   ` Fabian Groffen
2011-08-01 19:16     ` Markos Chandras
2011-08-01 19:32       ` Fabian Groffen
2011-08-01 20:46         ` Markos Chandras
2011-08-01 23:10           ` Jorge Manuel B. S. Vicetto
2011-08-02  6:28             ` Fabian Groffen
2011-08-02  8:11             ` Markos Chandras
2011-08-01 23:12       ` Jorge Manuel B. S. Vicetto
2011-08-02  8:13         ` Markos Chandras
2011-08-01 21:51 ` Patrick Lauer
2011-08-01 22:57   ` Aaron W. Swenson
2011-08-02  6:24   ` Fabian Groffen
2011-08-04 13:24   ` Dane Smith
2011-08-04 14:33     ` Patrick Lauer
2011-08-04 19:56       ` Donnie Berkholz

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=20023.5194.711313.587404@a1i15.kph.uni-mainz.de \
    --to=ulm@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