Subject: port-master role (was: Re: Relevance of ARM merge (was: ...))
To: Stephen Borrill <netbsd@brio.precedence.co.uk>
From: Chris Gilbert <chris@paradox.demon.co.uk>
List: port-arm32
Date: 02/20/2001 00:56:37
On Thursday 15 February 2001 10:22 am, Stephen Borrill wrote:
> On Wed, 14 Feb 2001, Ben Harris wrote:
> > Personally, I think we should give developer accounts to anyone around
> > here with something worthwhile to contribute, wait a month or two and see
> > if an obvious new leader emerges.  If I'm lucky, it won't be me.
>
> Seconded.

Agreed, however might be hard to find anyone with enough time to take it on, 
I find time hard enough to find for the bits I do, and a port-master does a 
lot.

Out of curiosity what does the role of port-master actually entail?  I'm just 
thinking it's worth making sure that the person (or persons, I believe some 
ports have more than one port-master, we may have to do that) selected is 
aware up front what they might have to do?  (although some of these things 
are currently being done by others already, and maybe happy to keep doing so)

My current list is (note that I don't really know for sure):
deal with PR's (which we have some that are over 2 years old, and may not be 
of interest/applicable anymore)
general maintenance work
Likely to be overseeing the splitting of the port up, unless that happens 
before then.
merging of new ports in (eg sa11x0 and hpcarm, unless those people get 
developer accounts)
sorting out developer accounts for people
does the official releases on ftp site.
keeps the port up to date with the rest of happenings in the tree.
drives the port to new things (eg upcoming hardware etc)
organise stands at shows
keeps docs up to date

Perhaps I'm just being ignorant and there's a webpage somewhere that says 
what they do?

Cheers,
Chris