Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 Jun 1999 16:25:12 -0700
From:      Amancio Hasty <ahasty@mindspring.com>
To:        Vince Vielhaber <vev@michvhf.com>
Cc:        Jaye Mathisen <mrcpu@internetcds.com>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Matthew Dillon <dillon@apollo.backplane.com>, freebsd-hackers@FreeBSD.ORG, Garance A Drosihn <drosih@rpi.edu>
Subject:   Re: Matt's Commit status (was Re: 3.2-stable, panic #12)
Message-ID:  <37570ED8.A83B82F@mindspring.com>
References:  <XFMail.990603191403.vev@michvhf.com>

next in thread | previous in thread | raw e-mail | index | archive | help
It is a nice idea and I have proposed it in the past however most likely
such organization will devolve to the current status-quo with core;however,
if the oversight committee is composed of individuals from companies
using FreeBSD it may actually work for committee  should have a vested
interest in FreeBSD.




Vince Vielhaber wrote:

> On 03-Jun-99 Jaye Mathisen wrote:
> >
> > I second this.  Even if it's a bit painful, somebody who has been working
> > diligently at this needs to be able to be make their work usable quickly.
> > I would guess that not too many things hinder progress, or quash desire
> > more than fixes to problems languishing.
> >
> > There has to be some middle ground somewhere that lets Matt get his fixes
> > in quickly, and still doesn't ruffle too many core feathers.
> >
> > I had the opportunity to hear some of the core side recently, and I
> > certainly sympathize or empathize with the issue, but nobody else has
> > stepped up to fix the NFS problems, and I would like to see this
> > opportunity capitalized on.
>
> Not knowing the FULL story from both sides, I feel it'd be inappropriate
> if I were to comment on it.  However knowing Matt's coding abilities,
> having seen the eruption here a few months ago, and the past splits that
> IIUC were due to core problems, perhaps an oversight board (for lack of
> a better description) consisting of zero core people and zero committers
> may help to stop or solve some of these erruptions before they spill out
> into the public's view.  Who does a coder, committer, core member, etc,
> have to turn to if (s)he feels (s)he's getting the shaft?  Not anything
> aimed at you (Jordan) or David, but let's face it - you two have enough
> to do without having to worry about the petty crap that seeps out as well.
>
> Vince.
> --
> ==========================================================================
> Vince Vielhaber -- KA8CSH   email: vev@michvhf.com   flame-mail: /dev/null
>        # include <std/disclaimers.h>                   TEAM-OS2
>         Online Campground Directory    http://www.camping-usa.com
>        Online Giftshop Superstore    http://www.cloudninegifts.com
> ==========================================================================
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37570ED8.A83B82F>