Even something as simple as "I built this for my own needs and have open sourced it for open knowledge and will only fix issues that further my own needs and will not accept anything but simple PRs" goes a long way.
Is it different than someone advertising their FAANG's credentials?
Once again, if you feel every contributor is entitled, don't open source your project or disable issues and make it very clear issues and contributions are not welcome.
It 100% is entitlement, and open source is not a "product" because you don't pay for it. The developers of open source owe you nothing.
For the umpteenth time in this discussion, no one said they did. And please note what I implicitly defined as supported, which is basically that a non-antagonistic conversation can be had about issues and contributions. That is not entitlement.
Actually you did when you said, among other things:
>To me, it just sets an implicit expectation of "this is something I support"
>Again, expecting a product to be supported unless otherwise stated is not entitlement
If you describing something you expect, you are describing something that you feel that you are owed.
Why even participate in open source if everyone seems to hate it and be on edge?
You were given something for free. That doesnt confer any rights, legal, moral or otherwise.
Drive by pull requests are not always welcome for any number of reasons which are the sole prerogative of the project maintainers who owe you nothing.
PRs are even worse when theyre big. If you do a large PR without informing anyone you should expect by default for it to be ignored.
> You were given something for free.
I wasn't given anything. Something was released into the open to be interacted with at some level. If a maintainer wants to complain about any interaction whatsoever, then take it private or disable issues, write a contributing (or non-contributing) guideline, and reject PRs professionally.
> That doesnt confer any rights, legal, moral or otherwise.
That's completely obvious. But like I said, a simple PR or issue filing does not imply a demand of the maintainer by the reporter or contributor. So you're basically showcasing what I'm saying isn't great, in that maintainers have this bias already set in their mind that any communication to them is a demand of their time and effort and a claim of rights, which it's very often not.
This "hill" that has to be gotten over by the contributor is just a reality of the situation. I don't see any way around it.
Maintainers get to decide, and they're not obligated to publish their evaluation criteria.
God forbid people communicate.
At a baseline, you are responsible for the maintainer's communication burden too, such as reading in between the lines and accommodating for their schedule (they may need weeks to respond).
If you don't think it's a burden, then why not fork the project and become the maintainer yourself?
"Before you criticize someone, walk a mile in their shoes"
This is a tiring discussion, because this is exactly what I'm talking about. No one is here talking about how anyone owes one anything. In fact, no one in any part of life owes one anything if you'd like to go that route. But effective communication and expectation setting avoids the vast amount of communication issues. If a maintainer wants to release software and then complain about it every step of the way and claim everyone is demanding how they spend their time and effort and not reading their mind and now bowing at their feet, that's their prerogative. But that isn't some righteous path. It's an annoying one.
If maintainers are such sensitive souls, then they should either: communicate early and stop complaining, or take the project private or disable issues and stop complaining. Why almost go out of your way just to complain and make your job harder?
You were. You were describing what you "expect" from maintainers. That is the same thing as saying what you are owed.
E.g. when I make a contract I expect the other side to honor it. I am owed that because they signed a contract.
I expect people to not spit on me on the street - that's part of an unspoken societal contract.
If somebody makes a commitment, I expect them to follow through on it (even if they are not legally bound to) - again, part of an unspoken societal contract.
If I email somebody, I don't expect a response under all circumstances - again, unspoken societal contract.
What you were describing above were additional expectations you have on people who gave you something for free in exchange for nothing.
You're not owed an explanation just because somebody gave you something for free. The maintainer might have complicated reasons for wanting to accept some PRs and not others and might not want to put the work in to write it down.
They're not obligated to explain this to the all and sundry just in case somebody wants to raise a drive by PR.
If you think they are obligated, that's indicative of a culture of entitlement.
Reading the message is a demand. Reading the code is a demand. Thinking about whether the approach is satisfactory is a demand. Thinking of a response is a demand.
If you want to maximize your chances, you had better put as much effort into making things as easy for the maintainer as possible, such as including alternate approaches you considered and why they were not chosen, written as succinctly yet clearly as possible. Your code should completely match the existing style and formatting of the code; your own style preferences are irrelevant. Of course, you need to be as polite as possible without being condescending. And even then, you are owed nothing.
That is the approach I take when writing my PRs, and my success rate is rather high (but I still get rejected or ignored).