Date: Thu, 03 Jun 1999 18:17:04 -0700 From: Amancio Hasty <ahasty@mindspring.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) Message-ID: <37572910.D15A90D7@mindspring.com> References: <Pine.BSF.4.10.9906032003460.82061-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey wrote:
> [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.
I differ with the above Alice in Wonderland explanation on the
management of "coders" or software projects. In your scenario
I would say it depends upon whether the coders wishes to
impose his own technological point of view and displace others
solely based on political or emotional motivations without
any technological or scientific considerations and what should
be done about it when we reach such crossroads which is
a far cry from dictating what people should code or do.
I do understand that this is a volunteered organization and you don't need to
explain
it . I think that if the current scenario of core just snapping priviliges or
ignoring
developers continues development will actually come to a painfully slow
pace. Just read Matt's email and see who is stepping up to take his
place and he is a *volunteer*. The problem now is who can step up
to support Matt , NFS development, or resolve the current
conflict between core and Matt.
As stated by another user, NFS is a key technology component for a
UNIX server class OS.
Amancio
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?37572910.D15A90D7>