From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-council+bounces-600-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1MT8fg-0006Hn-OO
	for garchives@archives.gentoo.org; Tue, 21 Jul 2009 06:17:52 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 4DC8AE02E6;
	Tue, 21 Jul 2009 06:17:52 +0000 (UTC)
Received: from petteriraty.eu (petteriraty.eu [78.47.27.97])
	by pigeon.gentoo.org (Postfix) with ESMTP id F104DE02E6
	for <gentoo-council@lists.gentoo.org>; Tue, 21 Jul 2009 06:17:51 +0000 (UTC)
Received: from [82.130.46.217] (qiz1.kyla.fi [82.130.46.217])
	by petteriraty.eu (Postfix) with ESMTPSA id 93A957B90059
	for <gentoo-council@lists.gentoo.org>; Tue, 21 Jul 2009 06:17:50 +0000 (UTC)
Message-ID: <4A655D48.6040903@gentoo.org>
Date: Tue, 21 Jul 2009 09:16:40 +0300
From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= <betelgeuse@gentoo.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8.1.22) Gecko/20090720 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
Precedence: bulk
List-Post: <mailto:gentoo-council@lists.gentoo.org>
List-Help: <mailto:gentoo-council+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-council+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-council+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-council.gentoo.org>
X-BeenThere: gentoo-council@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-council <gentoo-council@lists.gentoo.org>
Subject: [gentoo-council] Nuking this mailing lists
X-Enigmail-Version: 0.95.7
OpenPGP: url=http://users.tkk.fi/~praty/public.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 3489454d-d751-4477-8725-c48c09f21d9d
X-Archives-Hash: e0dcb0d0bd0cd735eea02b9cef27ffac

What we currently have now:
1. gentoo-dev: technical issues
2. gentoo-project: non technical cross project issues
3. gentoo-council: supposedly council related things

Problems I see with this:
1. People are unsure where to post to and cross post to mailing lists in
order to reach more devs. The right way here is a single mailing list
and gentoo-dev-announce.
2. We have two relative low traffic mailing lists gentoo-project and
gentoo-council.
3. If we truly use gentoo-council for all council related matters it
splits cross project technical talk between gentoo-dev and gentoo-council=
.
4. The original point in creating gentoo-project / gentoo-dev-announce
was that people wouldn't have to receive discussion about technical
items if they wanted to. So technical items should stay on gentoo-dev
instead of floating elsewhere.
5. -council is probably not reaching as many developers as -dev so
technical issues might not get input. Granted this point can be helped
by using gentoo-dev-announce but then devs who only want to see the
decisions would see the initial discussion too.
6. A user not familiar with our mailing list setup might not find
-council to follow up important threads if they want to.

What I propose:
1. Use gentoo-dev for technical council related matters
2. Use gentoo-project for non technical council related matters
3. Use gentoo-dev-announce to start threads if deemed necessary but
moderators should be alert in order to not have too much of these
through -dev-announce.

Regards,
Petteri