Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Dec 2017 05:24:14 -0500 (EST)
From:      Mike Remski <mremski@comcast.net>
To:        freebsd-hackers@freebsd.org, Dieter BSD <dieterbsd@gmail.com>
Cc:        freebsd-arch@freebsd.org
Subject:   Re: Getting PRs fixed [ was: Re: The future of fortune(6) ]
Message-ID:  <1306478885.37537.1512123855297@connect.xfinity.com>
In-Reply-To: <CAA3ZYrCCQPeSk4EvL=VN06R8C_FHkXmj%2BSor46t2sWPjzJTbJg@mail.gmail.com>
References:  <CAA3ZYrCCQPeSk4EvL=VN06R8C_FHkXmj%2BSor46t2sWPjzJTbJg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

> On November 30, 2017 at 6:13 PM Dieter BSD <dieterbsd@gmail.com> wrote:
> 
> 
> ( Does this need to be cc-ed to arch, or is hackers sufficient? )
> 
> Dieter> Ignoring PRs for years and years and years and years...
> 
> Mark> Please suggest a constructive solution.  (This is a serious request.)
> 
> Given the discussion this has come out of, (demands for censorship
> due to someone claiming to be offended at something) I suppose I should
> state that this is not intended to be offensive.  Offense, like beauty,
> is in the eye of the beholder.  I have intentionally left out a few
> details/specifics in an attempt to avoid or at least reduce offense.
> 
> Damn it Jim, I'm an engineer, not a motivational speaker!
> 
> D> Status reports that do not report progress (or lack thereof)
> D> reducing the number of open PRs.
> 
> There used to be periodic reports sent to various mailing lists
> listing open PRs.  At some point these stopped coming.  Perhaps
> due to:
> 
> D> Replacing a working PR system with bugzilla
> 
> Perhaps these reports could be resurrected?  Or made part of the
> quarterly status reports?  Or something?  Many PRs were ignored
> even with the reports, but it shouldn't hurt and might help a little.
> 
> Recruiting additional developers might help.  How to do that?
> Well, I don't know, but I have noticed that a half-baked
> attempt at cloning Unix has become very popular despite being
> very buggy and brain damaged.  I tried it a few times with
> horrible results.  I have completely given up on it after it
> scrambled my data.  :-(  Anyway it seems to have a lot of
> developers and corporate support, so they must be doing *something*
> right.  Perhaps someone could study that project and figure out
> how they are attracting all these developers and corporate support.
> Perhaps the person we should be recruiting is a recruiter?
> (Catch 22?)
> 
> I have observed the foundation receiving significant donations,
> (like US$1M) and spending money on things that seem unlikely to result
> in improvements to the system.  Perhaps some of this bounty could
> instead be used to pay developers to fix bugs.
> 
> I observe a lot of new features being developed, and yet PRs continue
> to be ignored.  I realize that many people consider developing new
> features to be more fun that fixing old PRs, but the old PRs do need
> to be fixed.  Some of these PRs cause data to be lost, or other
> hardships.  :-(  It is especially annoying when a developer cannot be
> bothered to maintain even their own code, much less anyone else's.
> Are FreeBSD's developers mature adults or just children?
> Perhaps there should be a requirement to fix x old PRs to receive a
> commit bit, and to fix y bugs/year to retain it.  I don't especially
> like this idea, but offer it mainly  in hopes that it might inspire
> someone to think of a way to improve it.
> 
> I shouldn't have to say this, but when I say fixing a PR I mean just that.
> Fixing it, not just closing it with some absurd excuse.
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


Bug databases need to be scrubbbed periodically.  Even if it's just to close ones that can't be reproduced or have been fixed by other changes (after due diligence in verifying it so there is no absurd excuse).

There are a lot of foks with the ability and desire to help, fixing PRs and sending in patches should be a good way to involved, but that still depends on the owner of a piece to look at a patch, ask questions, get revisions and commit it.  If that never happens or the submitter never gets any feedback, it winds up discouraging the new people.

Fixing bugs, espeically on !CURRENT, is not glamorous, but necessary.  Often actually root causing the bug and patching it gives one a better understanding of the overall system and a sense of satisfaction.

Yes, I realize that everyone is a volunteer and has a real life, but at least acknowledging a submission should be done, even if it is automated.  This goes both ways:  originator of a bug (or patch) needs to be responsive to the FreeBSD committer if they request more data or clarification.

My 2 cents as a long time user of FreeBSD as my primary desktop at home.

mike



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