Re: nvidia-driver and no update in /usr/ports/UPDATING

On Wed, 13 Apr 2022 13:29:23 -0700
Dave Hayes <dave@jetcafe.org> wrote:

> On Wed, 13 Apr 2022 21:03:21 +0100
> "Steve O'Hara-Smith" <steve@sohara.org> wrote:
> > 	How else should you be when someone does something for free and
> > gives away the result ? At a free barbecue would you complain that they
> > didn't have your favourite sauce or might you provide a bottle for
> > others to enjoy as well ?
> 
> It's how you complain of course. 
> 
> If I mention in an offhand way "Damn, no hot buffalo sauce, oh well",
> that's not really actionable and a kind host might even say something
> like "Oh I have some of that in the back, let me get you some". 

	Right and if they don't then it ends there.

> What I will always take issue with is: given someone who politely
> (incorrect or not) files a bug or issue and gets ignored anyway; the
> moment they speak up, you call them rude. :) I think this is just a
> difference of opinion between you and me and it's not a big deal, but it
> does come up.

	Did you read the bug report ? It basically said this change needed
a comment in updating, it didn't say why, it didn't suggest what the
comment needed to say and it didn't mention the maintainer let alone cc
them.

	The result of that is that it drops doing all of that on whoever is
triaging the bug queue when it comes in - I know what I'd do in that
position. I'd jot down a note to look up the maintainer and shoot them an
email, then I'd go on to the next bug which might be more serious. I might
never get round to the note, that's what happens to notes. or I might send
the email. The maintainer might compose an entry and commit it or they might
think "I've another update to do in a couple of weeks I'll do it then", or
even "I'll do it tomorrow I have this fiddly bug to fix today" and then
forget it. These things happen.

	Now suppose the reporter had taken the little extra time to
formulate an actionable bug report with a note as to the problems not
having the entry causes, some starting point text for the note and the
email address of the maintainer. This time I'd deal with it immediately
because I have all the information I need - and so does the maintainer, cut
and paste maybe a small edit, commit and done.

	In the second scenario the probability of getting things done is
*much* higher.

> > 	You're only part of a community if you take part in it.
> 
> FreeBSD sets an extremely high bar for "taking part in it". Ignoring

	No it doesn't. Just put yourself in the position of the people you
are asking to do work for you and help them to help you by making it easy
for them and not bitching at them. It really isn't much to ask when you're
talking to people who do this for the fun of it.

-- 
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/