Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Mar 1999 02:39:28 +0900
From:      "Daniel C. Sobral" <dcs@newsguy.com>
To:        Eivind Eklund <eivind@FreeBSD.ORG>
Cc:        freebsd-chat@FreeBSD.ORG
Subject:   Re: 1998 Bugs
Message-ID:  <36EE9750.AB88915E@newsguy.com>
References:  <36EE651B.D7EFAD7A@newsguy.com> <19990316161941.E4774@bitbox.follo.net>

next in thread | previous in thread | raw e-mail | index | archive | help

Eivind Eklund wrote:
> 
> I think that would be a good idea.  My take on this is that we should
> have a team of people that take responsibility for handling PRs, and
> that each incoming PR should be assigned to one of the people on the
> team.  That person has the responsibility for handling the PR *in some
> fashion*.  This could be
> * To commit a patch
> * To track down the correct person for fixing this PR and transferring
>   the responsibility
> * To reply to the person that originally sent the PR, attempting to
>   get hold of more information
> * To decline a suggestion for change
> * To identify this is a correct PR, stamp it with 'correct problem
>   report', and put it on active status.
> 
> The clue is just that the person does _something_ about the PR,
> instead of leaving both the PR and the person sending it high 'n dry,
> with no response at all from FreeBSD.

That was my general feeling.

> Technically, I would implement the above scheme as a two-part system:
> 1. A cronjob that goes through all new PRs every night, and assigns
>    them to people from a list of PR tag team members.  (Round-robin
>    fashion, of course).
> 2. A small setuid program for adding and removing people from said
>    list.
> 
> I'm willing to be on such a team if 10 other committers also are - if
> I get 10 volunteers, I'll write up the code.

I'd volunteer, too. There is a few problems we have to plan for,
though.

* How do we deal with "disappearing" volunteers?

* How do we deal with volunteers that lagged too much and then
discover they won't be able to deal with the problems assigned to
them?

* Life happens; people should belong to this list if they have *the
time* to handle it. That means people should be relatively free to
bug out when they feel they won't be able to handle the load. And
that means there will be times when there are too few volunteers,
which would be swamped with PRs. 

I suggest "hard limits" on the number of PRs per volunteer to be
handed out each day. When the limit is reached, the PRs get queued
until the next day.

Or any number or variants on the above.

Anyway, we have to deal with the general problem of having the
person to which a PR was assigned not handle it.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	"What happened?"
	"It moved, sir!"




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36EE9750.AB88915E>