From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE, INVALID_DATE,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from mailgw2.netvision.net.il ([194.90.1.9]) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15RJnN-0003OQ-00 for gentoo-dev@cvs.gentoo.org; Mon, 30 Jul 2001 14:37:46 -0600 Received: from localhost (ras9-p11.rlz.netvision.net.il [62.0.91.11]) by mailgw2.netvision.net.il (8.9.3/8.9.3) with SMTP id XAA29919 for ; Mon, 30 Jul 2001 23:40:16 +0300 (IDT) Content-Type: text/plain; charset="iso-8859-1" From: Dan Armak To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] Organizing user ebuild submissions X-Mailer: KMail [version 1.2] References: <0107302259100D.00612@localhost> <87d76i9n9q.fsf@codefactory.se> <20010730143027.S14345@cvs.gentoo.org> In-Reply-To: <20010730143027.S14345@cvs.gentoo.org> MIME-Version: 1.0 Message-Id: <0107302339040J.00612@localhost> Content-Transfer-Encoding: 8bit Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Mon Jul 30 14:38:02 2001 X-Original-Date: Mon, 30 Jul 2001 23:39:04 +0300 X-Archives-Salt: 0438b104-6e15-4d97-834a-622332f13f5a X-Archives-Hash: d8072520224166d7286c29b0587e128e On Monday 30 July 2001 23:30, you wrote: > On Mon, Jul 30, 2001 at 10:26:25PM +0200, Mikael Hallendal wrote: > > Dan Armak writes: > > > I wouldn't mind handling the mailing-list side of the story - grabbing > > > all ebuilds and putting them wherever and informing whoever. But many > > > ebuilds come through for packages I don't use and in many cases can't > > > test. I don't think any one developer could or should handle the > > > testing, that's why we have teams. We can have an "incoming" ebuild > > > tree (in cvs or elsewhere) and developers could grab ebuilds that fall > > > under their area of interest, test them and put them either in the > > > stable or unstable cvs trees. > > > > I also think this is the way of doing it. Perhaps, when you find an > > ebuild in the mailinglist you can commit it to some place in cvs and > > add a wiki todo about it giving it to the correct team. This way it > > will be easy to track what "your" team has to test. > > Good idea. Dan, go ahead and create and add a /usr/portage/incoming > directory to CVS and check all new ebuilds in there. Then, post a wiki > item for each new ebuild (or batch of related ebuilds) and assign the wiki > item to the appropriate team, priority "low". Thanks for doing this. > OK. Should I classify the ebuilds as well and have e.g. /usr/portage/incoming/app-text? -- Dan Armak Gentoo Linux Developer, Desktop Team Matan, Israel