[Mplayer-cvslog] CVS: main/DOCS/tech MAINTAINERS,1.38,1.39

[Diego Biurrun]

Attila Kinali writes:
> On Mon, Aug 30, 2004 at 03:38:08PM +0000, Diego Biurrun wrote:
> > Ivan Kalvachev writes:
> > > I don't think an maintainer could be somebody that cannot maintain
> > > the code directly. So I think that he must have cvs write access
> > > after he send him next patch and before the patch get commited.
> > 
> > Having CVS write access sure helps, but as long as he sticks around,
> > reviews EDL patches, takes care of that part of the code and gets
> > somebody to commit things for him he can have the title maintainer
> > IMHO.
> 
> IMHO this is a policy question and IMHO Ivan is right.

Yes, it is a policy question.

> Currently i use the MAINTAINERS file as a list on who has cvs write
> access and whos patches i dont need to check as deeply as others.

Well, that list is badly out of sync in this regard.  There are quite
a few people with write access that are not listed there.

> So if we get people without cvs write access into MAINTAINERS we
> (ok, i) will need another list with people who have cvs write
> access.

I use /etc/passwd on mphq ;-)

> So, to sumarise this: IMHO only people with cvs write access should be
> listed in MAINTAINERS. IMHO people like Reynaldo whould be given cvs
> write access if they are willing to maintain a part of MPlayers code
> base.

I'm fine with giving Reynaldo CVS access.  Nevertheless I think that
we could have maintainers that take care of small parts of MPlayer
without having write access.  They should just find somebody to apply
their patches and since they are the maintainers you should be able to
trust them.  I'm neutral on this subject, but I agree with extending
CVS access to people willing to do maintenance of some part of
MPlayer.

Diego