Re: [gentoo-dev] Maintainership and commit policy

[Mikael Hallendal]

Hi!

> Since we hae the new team system in place, i think the following
> should be the tree structure : under incoming directory there should
> be team directories and under that the new incoming ebuilds from the
> list or from developers who do not maintain the ebuilds they wish to
> commit.  after committing to the corresponding team.
>
> and before that i assume the developers shouldbe aware which
> directories from the portage tree belong to which team ?!  once
> committed to the incoming tree for an ebuild which a developer doesn't
> maintain , he should mail the current developer for either committing
> that ebuild or wait for this comments. if the new maintainer doesn't
> recieve any response from the old maintainer in let's say 3-4 days
> then the new maintainer can reqeust the commit access from the curent
> group leader.

This sounds very good to me, with a little modification :) 
If it's a change in an existing ebuild it's better to submit a patch
against the current becuase with a patch it's much easier to se what
changes has been made. I think this goes when changing the version
number too. 

Regards,
Mikael Hallendal

-- 
Mikael Hallendal                micke@×××××××××××.se
CodeFactory AB                  http://www.codefactory.se/
Office: [phone]     Cell: [phone]