Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While nobody is required to like the copy, or "brand" of any project, commercial or otherwise, I do feel like the rhetoric of your comment is largely grounded in a kind of "maximum appeasement" strategy that belongs in for-profit corporate marketing & isn't really appropriate in the open source community.

For example: there's very reasonable arguments that COCs are needed to protect against actual material harm/bullying/abuse targeting individual contributors on projects but this copy specifically does none of that.

In that context, it's just a matter of taste - there's no real reason to police tone that isn't harmful (to anything other than a bottom line).



> I do feel like the rhetoric of your comment is largely grounded in a kind of "maximum appeasement" strategy that belongs in for-profit corporate marketing & isn't really appropriate in the open source community.

I’m not asking for corporate speak. I’m suggesting simple communication that explains the information without insulting the reader and calling them a “motherfucker” every other sentence would be less alienating

> In that context, it's just a matter of taste - there's no real reason to police tone that isn't harmful (to anything other than a bottom line)

I’m not here to police anything or anyone. They’re free to write as they please. I’m just pointing out that writing this way is a big red flag to a lot of people this project’s target audience is the edgelord crowd. If that’s what they’re aiming for then there’s nothing wrong with that, but I don’t think they realize how making strong appeals to that narrow target audience is a fast track to pigeon holing your project as an edgelord thing. Just taking one look at the low brow insults and trash talking in the GitHub issues confirms it.


No need to police! But may make you despise. Or at least doubt.

Emotions going way overboard are usually not good for engineering, or for open-source project governance. Aggressive negative emotions, doubly so.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: