Hacker News Reader

Comment by anothergoogler | Hacker News Reader

Off topic, is it normal now to include a "Code of Conduct" in new, single-contributor projects? I thought it was more of a reactive thing.

View on HN

See https://opensource.guide/starting-a-project/ for GitHub's latest advice on starting an open source project, which includes adding a Code of Conduct. I think single-person projects just starting out can get away with just a LICENSE and README, but it's best to have CONTRIBUTING and CODE_OF_CONDUCT if you expect any contributions.

Hopefully it's rare that it's needed, but it's really easy to add and a nice thing to have proactively instead of reactively, and plenty of people feel more welcome when things like that are explicit.

I don't know what's "normal", but I believe very strongly in specifying acceptable behaviors from the jump when trying to build a community.

Thanks for taking a look.

@eropple Sort of a nitpick, but you might want to replace "[INSERT EMAIL ADDRESS]" with your actual email address. :-)

https://github.com/eropple/taskbotjs/blob/master/CODE-OF-CON...

I just hit my forehead hard enough to wake the dog.

Thanks. :)

"YAGNI" is the first thing that pops into my head. d:o)

The Rust programming language had a Code of Conduct from the get-go. In general, having one gives a reasonable idea of the type of community you'd like to build around the project, and avoids the mess of trying to add one once you have a pile of vehemently anti-CoC community members.

simple copy paste job, avoids "changing the contract" later. i agree it doesnt make sense as a standalone thing but it takes 2 seconds to copy

It's virtue signalling.

Yup. And apparently that really does generate valuable social currency.

Calling out virtue signalling is arguably itself a flavor of virtue signalling, just for (some) other virtues ;)

Agreed. Lets just skip the whole thing next time. :)

Reply on news.ycombinator.com