5 ms·
I agree with your sentiment of "Unless that guy specifically says he's going to maintain it for free you are entitled to exactly absolutely nothing" That works
by andsoitis 3y ago
I agree with your sentiment of "Unless that guy specifically says he's going to maintain it for free you are entitled to exactly absolutely nothing"
That works both ways though, a maintainer cannot expect users to not complain (so they have to develop management strategies where they ignore the noise, rather than try to engage/capitulate). A maintainer can also not lament when users do not feel the desire to contribute monetarily.
- bjornsing 3y ago> a maintainer cannot expect users to not complain Eh… Isn’t that fairly close to the definition of entitlement (i.e. you complain when you have no reason to)?
- andsoitis 3y agoAs a maintainer you cannot control how people behave. There’s no point in lamenting that people act entitled. Instead, it is more productive to develop strategies to ignore the noise from entitled voices. You do not need to respond to them. You do not need to convince them. You do not have to keep them happy.
- dom96 3y ago> There’s no point in lamenting that people act entitled. There is: it discourages people from acting entitled.
- yjftsjthsd-h 3y agoDoes it? How much of an impact do you think it has?
- deleted 3y ago[deleted]
- billythemaniam 3y agoI suspect ignoring them is more effective than essentially complaining back.
- mikrl 3y ago>so they have to develop management strategies where they ignore the noise I believe this is called “please use the template when submitting an issue” and we all know how that goes. I’ve honestly found myself laughing like a madman at GitHub issues where the maintainer calmly and repeatedly tries to explain to the increasingly disgruntled reporter to UTFT (use the fine template)
- pydry 3y agoTo be fair the UX on those things is abysmal. Github could improve the experience 10 fold.
- TillE 3y agoUX can help a bit, but fundamentally the problem is people who have an issue or question but are completely unable to communicate it in a way that can be understood and addressed. The garbage bug reports I see on my projects and others are like, either one sentence or rambling nonsense. The templates don't help much, these users will do their best to ignore them. As long as you're not doing that, your bug report is probably very welcome.
- pydry 3y agoUX is partly about how to accommodate that without throwing up hoops to jump through to the people who aren't a waste of space. Most bug reports, especially on complex software should follow something resembling a kind of wizard/state machine (e.g. state: OS has/has not been specified) but instead everything is a text box with a dump of contextual questions, half of which don't even necessarily make sense for the specific bug report you're making. >As long as you're not doing that, your bug report is probably very welcome. When barriers are thrown up to the other kind of person it will often make it seem like they are very unwelcome even when they're not - e.g. the first message you see may be a hostile list of "DON'T DO THESE 5 THINGS" because somebody once did each of those things. I'm pretty sure a lot of good bug reports are lost this way.
- marcosdumay 3y ago
- prmoustache 3y ago> That works both ways though, a maintainer cannot expect users to not complain (so they have to develop management strategies where they ignore the noise, rather than try to engage/capitulate). A maintainer can also not lament when users do not feel the desire to contribute monetarily. The solution is quite simple really. 1) have your repo private and release only tarball files or have a read only repo with no pull/merge request functionnality 2) do not use an issue tracker Basically, do not use a forge such as github/gitlab, at least not publicly. Problem solved.
- sweetjuly 3y agoGitHub also lets you turn off the issue tracker, which is wonderful for projects which are ""incidentally open source"" where I have no plans to maintain it beyond my own personal needs