What is the problem with ports PR reaction delays?

Big Lebowski spankthespam at gmail.com
Sun Jan 26 13:06:57 UTC 2014

On Sat, Jan 25, 2014 at 11:59 AM, Matthew Seaman <matthew at freebsd.org>wrote:

> On 25/01/2014 10:35, Big Lebowski wrote:
> >> Thus, are you volunteering for this role?  It's not my call, but if you
> >> > really want to do clean out and triage the all PRs on an ongoing
> basis,
> >> > my guess is that would be very welcome and we'd figure out a way to
> set
> >> > that up.  It would definitely help, especially for those maintainer
> that
> >> > "approve" patches but the PRs never get opened (or set to a better
> state
> >> > than "open").
> > If I wouldnt care about FreeBSD and ports state and I wouldnt want to
> help
> > with that, I would have not wrote this message in first place. Yes, I
> would
> > love to help.
> There are a lot of people who would love to help with FreeBSD, and there
> is a lot of help that FreeBSD needs.  The problem is that anyone
> volunteering probably only has a limited amount of time they can donate
> to the project, and there exists at the moment no simple mechanism for
> dividing up the workload into small, easily digestible chunks.
> Take the case of PR triage, often cited as a suitable track for people
> to start getting involved.  Say we get about 300 new PRs in a week.
> What we need is 20--50 people looking at 6--15 PRs a week, rather than
> 2--5 people trying to look at 60--150 PRs a week.  Trouble is, the first
> few people to volunteer will find themselves drinking from the PR
> firehose, and will probably give up long before enough additional people
> can be drummed up to share the load.

Does it have to be all-or-nothing situation, where we can do something only
if we have 20-50 people looking at 6-15 PR's a week, and we cant do
anything if we dont? Cant we start with 2-3 people (3 people so far
volunteered to do so, and I belive a 'call to arms' via this
list/announcements/bsdnow.tv/reddit would result in may others willing to
help) doing as much as they can?

Also, what about some kind of 'junior commiter' role, where solid port
maintainers get rights to commit to their ports only? If that would be
doable, we could offload a lot of work from current commiters to work on
other things.


>         Cheers,
>         Matthew
> --
> Dr Matthew J Seaman MA, D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey

More information about the freebsd-ports mailing list