Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 03 Feb 2007 19:01:58 +0100
From:      "Julian H. Stacey" <jhs@flat.berklix.net>
To:        Dan Lukes <dan@obluda.cz>
Cc:        freebsd-security@freebsd.org, Deb Goodkin <deb@freebsd.org>
Subject:   Re: Support for 5.x (Was: Re: What about BIND 9.3.4 in FreeBSD in base system ?) 
Message-ID:  <200702031801.l13I1w2p096068@fire.jhs.private>
In-Reply-To: <45C46EE5.4060404@obluda.cz> 
References:  <200702012319.l11NJJ7r065204@drugs.dv.isc.org> <45C2E612.5080002@FreeBSD.org> <45C3B56E.3060706@rxsec.com> <45C3DCA5.3070908@FreeBSD.org> <45C46EE5.4060404@obluda.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
> 	It seems to me, the one reason for limited resources is - project has 
> no resources to accept resources. I can't tell why the project lack 
> volunteers processing community inputs. May be, there are no such 

> 	As I don't know what's wrong nor how to correct it, this message is not 
> complaint in any way. It's just a note related to Doug's notice ...

[ I wonder if for the thread, per
	http://docs.freebsd.org/mail/archive/2007/
  bugs@ or bugbusters@ might be better ?  Not on those though .. ]

Nice definition: "No resources to accept resources"  :-)

Handling other people's send-pr bug input would be boring
compared with writing own code, or debugging.  Hence unactioned send-prs.

I've filed some send-pr diffs years back & not seen action, others
have been actioned occasionaly & I've been guilty of not responding
in time (Mea Culpa, even own bug reports are boring, especially
since once my auto diff applier works for me, there's less incentive
to persuade send-pr team to apply diff). Probably a common phenomena.

Dealing with boring bugs surely approaches paid work in needing
motivation, so if the FreeBSD Foundation (a member cc'd) ever has spare
money, it may be wise to have a few people paid something to action the
oldest=most boring send-prs ?

Oldest often would mean "So boring no one has touched it, (Or so
intractable/ insoluble/ major dev. effort required)".  If we used
any other criteria than oldest first, it would need someone to spend
time judging what should be paid as most boring & what not, & then
we'd be in a recursive "Woulndn't that be a boring job too?" so who
would do That ? So oldest bug first, unless reason to skip, eg
intractables.

If companies ever want to sponsor a little, we could suggest to
companies: please sponsor one of you own staff members (or some
freelance FreeBSD commiter), perhaps eg one day a week or just
Friday afternoons or whenever panic requirements are lesss likely),
to work the oldest = most boring send-prs that have been _so_ boring
for years no one has processed them.

The method of oldest most boring first would not destroy the incentive
of the code bug-a-thon people to periodically attack the parts of
the send-pr backlog they consider newer & interesting enough to
work on unpaid.

Disclaimer: Yes I'm a freelance. But no commit privs, so not eligable.
-- 
Julian Stacey.  BSD Unix C Net Consultancy, Munich/Muenchen  http://berklix.com
Mail Ascii, not HTML.		Ihr Rauch = mein allergischer Kopfschmerz.
Vista of a Bill from Redmond ?  http://berklix.com/free-talk-on-free-software/



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