No, there is no obligation. But there’s a thing called courtesy. And as humans there are certain social norms.
If someone spams me, I will ignore or retaliate by reporting as spam. If someone sends a low effort question, I might politely tell them to rtfm. If someone makes an effort to articulate a problem, even if I disagree, I’ll try to give them a reasoned response.
And if I genuinely have no interest in any interaction I’ll make sure to disable issues/comments or otherwise communicate this intent.
I’m not saying this to be pedantic. And I’m not denying that there is some social expectations when living in society.
If you say that there is no obligations, but also that you should follow some social expectations, then you’re contradicting yourself. It’s just a nicer way to say that people should behave according to what you consider to be acceptable.
Btw, which society rules do you mean? Because you have a lot of differences in different places regarding politeness and other social obligations.
Ok, so the problem here is that “obligation” has two meanings, and they’re being conflated here. One is pretty close to “being courteous to others” and the other is “you must do this”. When people say “maintainers have no obligation to anyone”, the point to the license where it usually says something like “THIS SOFTWARE IS PROVIDED AS-IS WITH NO WARRANTY” and you can tell that it’s the legal “must” definition because it’s in all caps and written in a way that nobody actually would write. So that means that nobody can sue the maintainer when they don’t do something or the other. All good, right? Well, now the question being posed above is “does this mean that the maintainer can also be rid of their obligations in the sense of courtesy, not legality?” And now since there is a difference in the definitions it is not contradictory to want to say “yes” to the second question. And yes, you are correct to say that these differ based on circumstances and location: that’s OK, we don’t judge them in a court of law. We do, however, judge people for their failings to meet societal obligations, based on our personal judgements.
> There is no reason to discuss legal obligations because that part is covered by licenses.
Correct, I think we agree on that.
> The entire discussion is at the level of social expectations.
No, this statement:
> No, there is no obligation. But there’s a thing called courtesy.
Is actually “No, there is no legal obligation. But there’s a thing called courtesy.“ And here the contradiction falls away and the discussion turns to whether there is a social expectation to be courteous. On that point my (and the above commenter, I suspect) would say that yes, of course there is an expectation of social courtesy. There’s one in every other setting too, so why not here?
You are not "gingerlime" who said that, I understand the original as "moral/social obligation" and not "legal obligation" but you seem to be putting the word "legal" on the users' mouth by saying what they "actually" mean?
As a Spaniard living in Japan, what social rules should I use to apply my social courtesy on Github?
I am gingerlime. I simply meant obligation as MUST and social norms / courtesy as SHOULD. So I guess technically you’re correct that it’s not a legal obligation, but I think the GP’s point is valid.
> No, there is no obligation. But there’s a thing called courtesy. And as humans there are certain social norms.
In my experience, there are no objective social norms or definition of "courtesy". What's polite in one culture might not be in another. Projecting your own values onto others isn't helpful.
Most cultures share some general social norms, such as courtesy to others. I would say it’s actually more unhelpful to dismiss norms entirely just because they have variance.
I think they mean they disabled issues altogether on the two github projects. I would give the benefit of doubt and assume they went through and responded to all open issues beforehand. Maybe even put things in a "known issues" section of the readme.
> Of course some people are low effort issuers, but some people put time and effort into opening an issue on a project. When the maintainer closes it without even taking 60 seconds to type a quick message why, it shows me that the maintainer is the entitled dick, not the user.
So what you're saying is that if a person puts a lot of time and effort into opening an issue, they're entitled to a response?
The maintainer has to justify themselves to noone, and only the maintainer knows their aims, contexts and ambitions for the project. That long, detailed issue that someone submits could have been the 50th one they saw that week about the same thing, which they'd already decided they won't fix.
I recently opened a couple of PRs on a small project, one of which looks like it'll be rejected and the other hasn't visibly been reviewed. This is fine. If I need these things badly enough or soon enough, I'll fork the project - I'm certainly not entitled to anyone giving up their time reviewing my code or agreeing with me.
When I see someone expects/demands something of me, I point them to the permissive MIT license. I am also a Spaniard living in Japan, so the concept of "social norms/expectations/etc" (whatever that even is) is totally meaningless to me.
If you put some effort and need help with the project, I'll try my best to help you. If you come demanding free support for your project, I'll just close the issue saying this is not the place.
It sounds like you and I are in agreement then. This is the same way I manage my projects as well. I think this is the best way to handle it. It gives respect to others without accepting disrespect from them.
> I make a point to fix typos and such in documentation when I find them
This is amazing, thank you so much. Typos are very troublesome and they slip through the cracks too easily. A typo PR or issue will get merged 100% of the times in my case.
I meant that I closed the issue section, not individual issues. For individual issues I don't recall closing a single non-rude one without at least a short explanation.
