> For your information, bad language is banned in most organizations and, therefore, if you are interested in having adoption of your Open Source, it is good practice to avoid such language.
> If you are not willing to receive contributions from the community, if you are not interested in your Open Source contribution gaining adoption, or if you prefer people to sign special agreements to make contributions, perhaps you are better off closing down your repository, making it private.
How about, if I release something for free, that I made on my own time, anyone can feel free not to use it if they don't like how I've written it.
I don't think I've even sworn in a public repo. I try to keep it professional. But if I did, and someone has a problem with it, they can write their own fucking software. They're not paying me to cater to their whims.
You forgot the “Hope this helps. Ciao!”, which is where I briefly had my vision go red and heard the phantom war cries of my ancestors skirling up from the depths
> For your information, bad language is banned in most organizations and, therefore, if you are interested in having adoption of your Open Source, it is good practice to avoid such language.
> If you are not willing to receive contributions from the community, if you are not interested in your Open Source contribution gaining adoption, or if you prefer people to sign special agreements to make contributions, perhaps you are better off closing down your repository, making it private.
How about, if I release something for free, that I made on my own time, anyone can feel free not to use it if they don't like how I've written it.
I don't think I've even sworn in a public repo. I try to keep it professional. But if I did, and someone has a problem with it, they can write their own fucking software. They're not paying me to cater to their whims.