Quotes and sources to use when dealing with delicate OSS situations
One of the reasons contributions to open source fail is because they are submitted without the “why”, just the “what”.— Jason McCreary (@gonedark) June 23, 2019
Spend time to craft the PR with why the change is needed. What was the problem before? How does this solve it?
I’m really disappointed that some users spoke so disrespectfully about members of the team responsible for the new Twitter web site. Critcism on our work and decisions is fair game. Personal attacks aren’t. Ask yourself, what would your mom think of your behavior? 🤦♀️ is my guess.— Dantley Davis (@dantley) July 24, 2019
Saw a few tweets today by people annoyed with #Symfony, which is fine, but sometimes reads as hostile. It’s maintained by people, many spending their free time, making it better for everyone - not just you - and you can always join them. There are many ways to contribute.— Denis Brumann (@dbrumann) August 7, 2019
The community management trap:— Conal Pierse (@ConalPierse) August 18, 2019
1: People are acting like assholes
2: You try to calmly explain an issue
3: They ignore you and continue being assholes
4: You ask them to stop being assholes
5: They feign outrage, act like bigger assholes, and call you unprofessional
Please don’t pester maintainers with demands like “FIX THIS” or even worse, threaten to “I’ll have to switch to X if you don’t” which I’ve heard many times. It can even have the opposite affect—them ignoring you.— Jay Phelps (@_jayphelps) October 3, 2019
Unless you pay for a license or have a support agreement. https://t.co/vqRr98S5xL
If you want a maintainer to respond to your issue, here's a list of things NOT to say:— Frank de Jonge (@frankdejonge) March 8, 2020
- Merge please
- Please merge now
- This needs to be fixed asap
- Please fix now
- Fix now please
- Why is this not fixed?
- How come this is not merged?
- Is this project still maintained?
Do you think OSS devs are breaking BC in patch releases intentionally (semver anyone)? Nope, they are humans like you, they make mistakes.— Fabien Potencier (@fabpot) June 9, 2020
It's like saying that you should never deploy bugs in production. Sure. But human beings are not perfect, stop whining and deal with it.
"If you don't drop IE11 you are perpetuating the madness!", "Kill IE11 support!" Having wasted months of my life making WC and Proxy's work on IE11 along with some crazy nasty bugs, I couldn't agree more! However a thread on why is not that simple, especially on enterprise: 👇— Diego Ferreiro Val (@diervo) July 2, 2020
Angry 10x GitHub developer: “I don’t like this default setting!!!”— John O'Nolan 🏴☠️ (@JohnONolan) June 27, 2020
Me: “Good news, it’s open source, so you can just change it to work how you prefer”
Dev: “NO. I want you to change the default based on my usecase”
“We’re not going to do that”
Dev: “WOW I cannot BELIEVE this”
Ce n'est pas parce que toi tu en a besoin que ta PR est forcément dans la continuité de ce que veux faire la core team. Donc faut bien faire attention à distinguer un bugfix d'une feature quand on applique ce raisonnement.tou Quoi qu'il en soit, y'a toujours le fork.— Alexandre 🐿 ❤️👹#onEstLaTech (@pockystar) July 11, 2020