[gentoo-dev] Organizing user ebuild submissions

[gentoo-dev] Organizing user ebuild submissions

[Dan Armak]

Hi all,

In the last few days there has been a edluge of ebuild submission on the 
mailing list. I think we need to organize this process, because some ebuilds 
get lost, and others may get grabbed by more than one developer.

A final solution could be, when we introduce stable/unstable trees into cvs, 
we could add a "user" tree as well. Then ebuilds would move from user and 
unstable into stable as developers find time to test them.

Until that happy time however we should make some temporary provisions. Is 
anyone handling this issue specifically as of now?

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Organizing user ebuild submissions

[Daniel Robbins]

On Mon, Jul 30, 2001 at 10:59:10PM +0300, Dan Armak wrote:
> Hi all,
> 
> In the last few days there has been a edluge of ebuild submission on the 
> mailing list. I think we need to organize this process, because some ebuilds 
> get lost, and others may get grabbed by more than one developer.
> 
> A final solution could be, when we introduce stable/unstable trees into cvs, 
> we could add a "user" tree as well. Then ebuilds would move from user and 
> unstable into stable as developers find time to test them.
> 
> Until that happy time however we should make some temporary provisions. Is 
> anyone handling this issue specifically as of now?

Nope; would you be willing to grab all ebuild submissions from this mailing
list and track their addition to our Portage tree, reporting back to the
original submitter, etc?  This would also include tracking testing and
informing me of people who are creating solid ebuilds so that I can set them up
with developer accounts.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Organizing user ebuild submissions

[Dan Armak]

On Monday 30 July 2001 23:00, you wrote:
> On Mon, Jul 30, 2001 at 10:59:10PM +0300, Dan Armak wrote:
> > Hi all,
> >
> > In the last few days there has been a edluge of ebuild submission on the
> > mailing list. I think we need to organize this process, because some
> > ebuilds get lost, and others may get grabbed by more than one developer.
> >
> > A final solution could be, when we introduce stable/unstable trees into
> > cvs, we could add a "user" tree as well. Then ebuilds would move from
> > user and unstable into stable as developers find time to test them.
> >
> > Until that happy time however we should make some temporary provisions.
> > Is anyone handling this issue specifically as of now?
>
> Nope; would you be willing to grab all ebuild submissions from this mailing
> list and track their addition to our Portage tree, reporting back to the
> original submitter, etc?  This would also include tracking testing and
> informing me of people who are creating solid ebuilds so that I can set
> them up with developer accounts.

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.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Organizing user ebuild submissions

[Mikael Hallendal]

Dan Armak <danarmak@gentoo.org> 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.

Regards,
Mikael Hallendal

-- 
Mikael Hallendal                micke@codefactory.se
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: [gentoo-dev] Organizing user ebuild submissions

[Daniel Robbins]

On Mon, Jul 30, 2001 at 10:26:25PM +0200, Mikael Hallendal wrote:
> Dan Armak <danarmak@gentoo.org> 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.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Organizing user ebuild submissions

[Dan Armak]

On Monday 30 July 2001 23:30, you wrote:
> On Mon, Jul 30, 2001 at 10:26:25PM +0200, Mikael Hallendal wrote:
> > Dan Armak <danarmak@gentoo.org> 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

Re: [gentoo-dev] Organizing user ebuild submissions

[Mikael Hallendal]

Dan Armak <danarmak@gentoo.org> writes:

> 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?

Isn't it better if the team (which should have the best idea of where
it should go) put them in the right directory? That will also make it
easier on the one that puts them in incoming.

Regards,
Mikael Hallendal

-- 
Mikael Hallendal                micke@codefactory.se
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: [gentoo-dev] Organizing user ebuild submissions

[Dan Armak]

On Monday 30 July 2001 23:46, you wrote:
> Dan Armak <danarmak@gentoo.org> writes:
> > 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?
>
> Isn't it better if the team (which should have the best idea of where
> it should go) put them in the right directory? That will also make it
> easier on the one that puts them in incoming.
Who is me. Fine then! I'll collect the ebuilds posted in the last week or so, 
which is what I have of the mailing list locally, and will add them to 
incoming w/ wiki notes if they haven't been added already. Now we need to 
notify all developers. I'll post a message on a new thread with a suitable 
subject.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Organizing user ebuild submissions

[Hendrik Visage]

Perhaps think of a gentoo-ebuild mailing list??
this way the -dev group could discuss development issues rarther than ebuild
troubles/submissions.

On Mon, Jul 30, 2001 at 11:53:34PM +0300, Dan Armak wrote:
> On Monday 30 July 2001 23:46, you wrote:
> > Dan Armak <danarmak@gentoo.org> writes:
> > > 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?
> >
> > Isn't it better if the team (which should have the best idea of where
> > it should go) put them in the right directory? That will also make it
> > easier on the one that puts them in incoming.
> Who is me. Fine then! I'll collect the ebuilds posted in the last week or so, 
> which is what I have of the mailing list locally, and will add them to 
> incoming w/ wiki notes if they haven't been added already. Now we need to 
> notify all developers. I'll post a message on a new thread with a suitable 
> subject.
> 
> -- 
> 
> Dan Armak
> Gentoo Linux Developer, Desktop Team
> Matan, Israel
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 
------------------------
Hendrik Visage
hvisage@envisage.co.za

Re: [gentoo-dev] Organizing user ebuild submissions

[Daniel Robbins]

On Tue, Jul 31, 2001 at 03:32:01AM +0200, Hendrik Visage wrote:
> 
> Perhaps think of a gentoo-ebuild mailing list??
> this way the -dev group could discuss development issues rarther than ebuild
> troubles/submissions.

Yep; will do that soon.

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Organizing user ebuild submissions

[Dan Armak]

On Monday 30 July 2001 23:26, you wrote:
> Dan Armak <danarmak@gentoo.org> 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.
>
So, we come again to the requirement of introducing stable/unstable/user etc. 
development trees into cvs.
-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Organizing user ebuild submissions

[Daniel Robbins]

On Mon, Jul 30, 2001 at 11:32:56PM +0300, Dan Armak wrote:

> So, we come again to the requirement of introducing stable/unstable/user etc. 
> development trees into cvs.

Just add the new ebuilds to /usr/portage/incoming in the current CVS repository.
wiki items should be tagged as "unstable"; forgot to mention that.

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.