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: v...@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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
