Date: Thu, 3 Jun 1999 20:26:07 -0400 (EDT) From: Chuck Robey <chuckr@picnic.mat.net> To: Amancio Hasty <ahasty@mindspring.com> Cc: Vince Vielhaber <vev@michvhf.com>, 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: <Pine.BSF.4.10.9906032003460.82061-100000@picnic.mat.net> In-Reply-To: <37570ED8.A83B82F@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[I rearranged the things since these folks can't be bothered to comment at the bottom] > Vince Vielhaber wrote: > > 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. On Thu, 3 Jun 1999, Amancio Hasty wrote: > 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. I'm sorry, these are both crack-pot ideas, it's been explained again and again, and Amancio, for one, knows this, so I can't see why he went on this way. I will restate the obvious again, please read this before exploding, because I'll make it real clear. I am going to explain reality; if you're complaining about reality, go grab a bottle of bourbon, it will work as well. Reality: FreeBSD is written (not run, not administered, really written) by volunteers. These volunteers work on what they want to. Core can say NO, but they can't say YOU WILL, because the volunteers WON'T. People with no intention (and often no ability) to code keep wanting to tell the folks that DO code what to do. Impossible, this IS NOT a paid organization, the volunteers will just go away and code for another group that is less self-desctructive. Some group you're talking about that doesn't code has no authority whatsoever, and in fact no expertise at all to even pretend they know what they're doing, else they WOULD be coding. You cannot code without real experience, this is not some weird TV show with scifi unreality. The only group that these volunteers will listen to or respect is a group of folks that DO code and DO have the expertise. Trying to get together a group of dilettantes may be a marketing man's idea of how to go, but it will not fit FreeBSD's reality, and you cannot force things like that here. Just realize, IF you're loud enough, and succeed, the programmers will all desert you, and you'll have a nice place to argue, but no more software. Core here does an excellent job, with all the problems they face, most committers will agree to that pretty quickly, and they are the only ones with a vote. Look to reality for the reasons why. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- 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?Pine.BSF.4.10.9906032003460.82061-100000>