From owner-freebsd-chat Thu Feb 5 20:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27052 for chat-outgoing; Thu, 5 Feb 1998 20:59:54 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27045 for ; Thu, 5 Feb 1998 20:59:50 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id EAA12041; Fri, 6 Feb 1998 04:59:45 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id FAA01146; Fri, 6 Feb 1998 05:59:44 +0100 (MET) Message-ID: <19980206055944.59391@follo.net> Date: Fri, 6 Feb 1998 05:59:44 +0100 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: chat@FreeBSD.ORG, "Daniel O'Connor" Subject: Re: cvs commit: src/sys/conf files References: <19980206044551.64694@follo.net> <793.886738588@gringo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <793.886738588@gringo.cdrom.com>; from Jordan K. Hubbard on Thu, Feb 05, 1998 at 08:16:28PM -0800 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe chat" On Thu, Feb 05, 1998 at 08:16:28PM -0800, Jordan K. Hubbard wrote: > > No, he couldn't. Not as easy, anyway. In mailing -current, not > > handling a patch drops down to being Somebody Elses Problem - nobody > > is responsible. For personal mail, things end up as the > > Which is why send-pr(1) exists. Which again only let things set around and bitrot. Not always, but at least for major patches, fairly often. It is hard to allocate time to review/test a major patch, especially when 'hey, anybody else can do it'. send-pr isn't a replacement for somebody's personal attention - it is just a way to keep reminders around ;-) And don't get me wrong - I'm not saying that we shouldn't have GNATS or something similar around. I'm just pointing out solutions that I believe scale better, because it seems to me that we're reaching some of the limits for the present organization. Integration by 'whoever picks it up' is one of the places where I think we could benefit by changes. I believe one of the reasons for Linux' success is that external authors get their changes integrated/reject more quickly. We have ports that sit in Gnats for months before being committed. And I'm as guilty as anybody here - I haven't committed them, either. However, if I had gotten 1/10 or 1/20 of those ports as mail to me, with the knowledge that I was expected to take first-line action on them - I'd easily have been able to handle the extra workload. I would have felt a much more specific pressure to take care of the stuff, too. So, I'm throwing the ideas around, in an attempt at at least making people aware of the alternatives. And if somebody suddenly says 'Yeah, that sounds great!' on something, I just might prioritize to get the time to actually implement the necessary infrastructure. It usually isn't more than a couple of evenings worth of work. Eivind.