[gentoo-dev] gentoo-debuild & incoming: help needed!

[Dan Armak <danarmak@gentoo.org>]

Hi all,

The current gentoo-ebuild/incoming was devised when there were 2-3 ebuilds 
submitted in a week on average, which needed to be organized in a convinient 
location. Now there are often 2-3 ebuilds per day, so we need to reorganize. 
In particular, developers should handle things at the gentoo-ebuild level, 
not the incoming level.

I propose any combination of the following. Tell me what you think and 
propose any other ideas.

0. drobbins, reminder: add the gentoo-ebuild submission rules to the list 
page! (Although the rules will need to be changed based on what we decide 
here).

1. Developers with particular interest in an ebuild, such as an ebuild that 
is the result of a previous discussion with the author, should take it 
themselves from gentoo-ebuild and edit/commit it to portage. In fact, if 
there is are established communications between the developer and the author, 
they needn't go through gentoo-ebuild at all.

2. Authors who want to update their ebuild often (like the mozilla case which 
had at least 5 versions ubmitted on gentoo-ebuild) might get cvs access to 
/usr/portage/incoming/username and do what they want in there, then get a 
developer to move it to portage proper.

3. All developers should scan gentoo-ebuild once in a while, and pick up any 
ebuilds they are interested in. On the same criteria as they would if the 
ebuilds were in incoming.

4. If they see an intersting ebuild which however isn't good enough for 
inclusion in gentoo, i.e. author didn't follow ebuild writing rules, they 
should reply and instruct the author on making the correct changes.

5. As above, they should answer generic ebuild-writing questions on 
gentoo-ebuild.

6. An ebuild that isn't picked up by anyone for say a 2-day limit can be 
placed in incoming as now done.


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel