Basis to accept someone as a maintainer

[Alexander Nicolaysen Sørnes]

On Thursday 24 January 2008 03:21:45 Jeff Zaroyko wrote:
> Vitaliy Margolen <wine-devel <at> kievinfo.com> writes:
> > Recently I've noticed number of random people being accepted as
> > maintainers of few apps I'm being a super-maintainer for. First, can the
> > appDB send notifications that some one became a maintainer? Second, what
> > are the basis that appDB admins accept some one as one? I've tried to
> > search for a single message, test results, anything from the people in
> > question and found none.
> >
> > Should we just make everyone a maintainer? If not, then could anyone
> > spellout why we have some random people there?
> >
> > Vitaliy.
>

There are no standard guidelines for processing maintainer requests.  
Personally, I usually accept all entries if they look decent; ie. not garbage 
characters, non-English language or they expect to get a free copy of the 
program by becoming a maintainer (and quite a few people seem to expect 
that!).

We are quite short of maintainers; the test result queue contians some 500 
entries, for instance.  I guess we could list some additional info about the 
applicant, and reject his application if he has not submitted any data and 
the app contains up-to-date info.


> I'm also curious, I think that there should be code of conduct or similar,
> some app entries don't have objective descriptions and give out of date
> information
>
> perhaps this appdb bug I filed might be relevant too:
>
> http://bugs.winehq.com/show_bug.cgi?id=11144