How to completely ruin an open-source project and anger an entire community
No, no, no! It’s not another article on how to contribute to open-source projects and be really appreciated by the community! In fact, the opposite of that. If you want to know how to make enemies in an open-source project and never get a pull request merged again, just read this article!
Don’t lead by example.
When it comes to open-source projects, it’s important to remember that you are not the only one involved. There are other people who have contributed their time and effort to make the project what it is today. So, when you’re thinking about how to change things, don’t just go ahead and do whatever you want without consulting others first. This will only lead to frustration and resentment from those who have put in the work to get the project to where it is now. Remember, there are more ways than one way to accomplish something. In order for a successful project to happen, everyone needs to be on board with the changes being made.
Don’t take responsibility.
Hey, it’s not your fault if things go wrong. You’re just trying to help, right? And besides, the community should be grateful for all the work you’ve put in. They’ll get over it. Sure, they might make a few snarky comments here and there. But as long as you keep taking credit for other people’s contributions, this is something they’ll have to deal with. Eventually, though, they will get tired of fighting so hard and will quit trying to fix anything that breaks. If that happens, then you can either stop working on the project or move on to something else. Maybe start your own project from scratch and find some new developers who are willing to clean up after you. Either way works out pretty well for you!
Don’t show respect.
If you’re looking to really wreck an open-source project and make a lot of people angry, the best way to do it is by showing a complete lack of respect. This can be done in a number of ways, but some of the most effective include refusing to adhere to established code formatting standards, refusing contributions from anyone other than yourself or close friends, publicly humiliating other contributors (especially on social media), making promises that are never kept, and being generally unapproachable. Once you’ve alienated all potential future contributors, the project will eventually die. Congratulations!
Do nothing, always.
Doing nothing is the best way to always anger a community. If you’re constantly causing problems and not doing anything to fix them, people will get annoyed. Plus, if you’re never around to help out or lend a hand, people will start to resent you. And finally, if you’re always making things worse instead of better, people will give up on you entirely. So if you want to wreck an open-source project and anger a community, just do nothing. Sit back and watch as your legacy crumbles into dust before your very eyes.
You’ll also see a change in the tone of posts about you on social media; there will be less positivity and more negativity, with members increasingly disliking what you’ve done to their once beloved program. For example, some might say that There’s been so much drama over this project, while others might say He/she was so helpful at first but now they don’t even care. Eventually, people might stop following you altogether because all they see are complaints about how terrible everything has become since your arrival. You can also make it really easy for users to quit by implementing complicated features nobody understands or supports (unless they happen to be one of your friends).