Date: Tue, 16 Mar 1999 16:19:41 +0100 From: Eivind Eklund <eivind@FreeBSD.ORG> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: freebsd-chat@FreeBSD.ORG Subject: Re: 1998 Bugs Message-ID: <19990316161941.E4774@bitbox.follo.net> In-Reply-To: <36EE651B.D7EFAD7A@newsguy.com>; from Daniel C. Sobral on Tue, Mar 16, 1999 at 11:05:15PM %2B0900 References: <36EE651B.D7EFAD7A@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 16, 1999 at 11:05:15PM +0900, Daniel C. Sobral wrote: > I notice that we had almost as much bugs reported through send-pr on > 1998 as we had on all previous years together... > > I can think of a few explantions... > > * 3.0-RELEASE with the kld and elf move? > * number of users has been increasing at a very fast rate? > * more committers -> more new committers -> more bugs? > * quality has decreased? > * size has increased? > * someone managed to get the users to user send-pr at last? > * all of the above? > * none of the above? > * others? More people running -current and submitting PRs against that instead of mailing current@FreeBSD.org, because current@FreeBSD.org has become a pit, just like -hackers used to be. > So, I guess the question is... will we have as much new PRs this > year (~5000)? Will we actually double again? Probably the latter. > On a more serious note (yup, the above was not quite serious), this > vast increase in the number of new PRs will be straining us. Should > we have a new type of contributor, in addition to our regular doc's > people, ports' people and src's people (did I miss anyone?), the > PR's people? 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. 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. Eivind. 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?19990316161941.E4774>