From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.67) (envelope-from ) id 1IDcbD-0006iF-Pr for garchives@archives.gentoo.org; Wed, 25 Jul 2007 08:52:04 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l6P8p6oB029931; Wed, 25 Jul 2007 08:51:06 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l6P8n9Un027524 for ; Wed, 25 Jul 2007 08:49:10 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id A8C7565335 for ; Wed, 25 Jul 2007 08:49:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: 0.882 X-Spam-Level: X-Spam-Status: No, score=0.882 required=5.5 tests=[AWL=-0.619, BAYES_50=0.001, RCVD_NUMERIC_HELO=1.5] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-835m5IhjkA for ; Wed, 25 Jul 2007 08:49:07 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 69771652EB for ; Wed, 25 Jul 2007 08:49:06 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IDcYE-0007lL-Oe for gentoo-dev@gentoo.org; Wed, 25 Jul 2007 10:48:58 +0200 Received: from 82.153.39.13 ([82.153.39.13]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 25 Jul 2007 10:48:58 +0200 Received: from slong by 82.153.39.13 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 25 Jul 2007 10:48:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Steve Long Subject: [gentoo-dev] Re: Re: New lists and their usage Followup-To: gmane.linux.gentoo.project Date: Wed, 25 Jul 2007 09:51:50 +0100 Message-ID: References: <1184970024.8424.22.camel@inertia.twi-31o2.org> <46A3AF4F.9040508@gentoo.org> <1185223269.8799.24.camel@inertia.twi-31o2.org> <1185225609.2494.3.camel@uberpc.marples.name> <1185239460.8799.45.camel@inertia.twi-31o2.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 82.153.39.13 User-Agent: KNode/0.10.4 Sender: news Cc: gentoo-project@lists.gentoo.org X-Archives-Salt: a3fa95ab-6c7e-4397-bed3-1a9c4487bd05 X-Archives-Hash: 52a4c93556c298e0c3e719068f7be60b Chris Gianelloni wrote: >> Yeah, you should take that to -project or some other suitable list :P > > Once some consensus is made and it actually becomes policy, sure. Until > then, I'm going to continue to use this list for the same things it's > been used for up until now. Once we've agreed upon how the lists should > be used, then I see no issue with using them that way, meaning *this* > conversation does belong here, as there's been no consensus amongst our > developer pool, nor a completed Council decision to change the policy. > Well I think there's been a consensus that project is for non-technical discussion. Usage policy for lists would seem to fall under that. > Like I said, the two proposals I had seen were: > > - gentoo-dev-announce > - gentoo-project > > I hadn't seen anyone asking for both, so we've now got to figure out > whether to drop one list or repurpose one of them. Personally, I'm for > repurposing gentoo-dev-announce to be a global "development" announce > list with no reply-to munging/filtering and developer-only posting. I > think doing this would be complimentary to gentoo-project and would be > useful to me, allowing me to know about conversations on other lists and > allowing *me* to *choose* when I want to participate, which is a vast > improvement from what we have had until now. > That sounds like an effective use of dev-announce, although it would make more sense to keep it as pure announcements, which would mean reply-to would be dev. Otherwise, it could become the public dev-only mailing list which was proposed for this list, and there was definitely no consensus established for that move. -- gentoo-dev@gentoo.org mailing list