From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Wed, 29 Oct 2008 21:07:00 -0700 (PDT) Received: from relay.sgi.com (relay1.corp.sgi.com [192.26.58.214]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m9U46XT6028034 for ; Wed, 29 Oct 2008 21:06:33 -0700 Message-ID: <490932BB.9020804@sgi.com> Date: Thu, 30 Oct 2008 15:06:19 +1100 From: Mark Goodwin Reply-To: markgw@sgi.com MIME-Version: 1.0 Subject: Re: oss.sgi.com and mailman, looking for volunteers. References: <490720DD.2050502@thebarn.com> In-Reply-To: <490720DD.2050502@thebarn.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Russell Cattelan Cc: xfs-oss Russell Cattelan wrote: > If everything works out then I will move the entire list over to using > mailman. Or over to vger, as we've been discussing. I'd like to delay any significant change until (a) after we have git'ified our patch flow and tree management processes (shortly after the .28 pull req goes out), and (b) the new oss.sgi.com has been set up and all content rsync'd across. This machine exists but Trev is currently occupied on other tasks. We're going to want more than just a new mailing list or handler. We also need a wiki for docs (news, arch, blogs, training, papers, etc), something like patchwork for tracking submissions, and more, etc. It doesn't make much sense to start setting this up on the current oss and then do it all again on the new oss. So can we please hobble along for another week or two? Thanks -- Mark