Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/ljedrz/nac

Not A Community: a code of conduct aiming to avoid community issues by minimizing the community aspect itself.
https://github.com/ljedrz/nac

code-of-conduct

Last synced: 25 days ago
JSON representation

Not A Community: a code of conduct aiming to avoid community issues by minimizing the community aspect itself.

Awesome Lists containing this project

README

        

# FAQ

#### 1. How to use it in my project?

Just copy the `CODE_OF_CONDUCT.md` file into the root directory of your repository. Feel free to modify it as you see fit.

#### 2. Why another code of conduct? There are so many already.

While most codes of conduct attempt to regulate contributor behavior, this one targets the community aspect itself, which makes it very concise and no-nonsense. Its main assertion is that code repositories are **not** communities at all - just venues where useful tools and products are created. Anything that can be considered personal is off-topic.

#### 3. Do I have to strip my profile from personal details in order to participate?

Not at all; it is only considered irrelevant, and expect to be treated as if you were a `user#1234` with a blank pfp and bio regardless of its contents.

#### 4. But I **want** to express my personal identity.

This is not the place for it - it's a code repository only; there are a lot of _actual_ communities where this is encouraged, feel free to do it there.

#### 5. What if I don't like a contributor's name, pfp, or what they do/say outside of the repository?

You're thinking in terms of personal identity again; feel free to use something like [Greasemonkey](https://en.wikipedia.org/wiki/Greasemonkey) to erase/change it locally, but don't expect the repository owners to do anything about it.

#### 6. Why is there no list of violations?

Everyone has a different level of sensitivity, so it would be impractical to try to create an exhaustive one. If it can be considered personal, it's discouraged.

#### 7. Why are there no details of penalties/enforcement?

As with the previous point, there is no "one size fits all" measurement of severity of violations. This is at the repository owners' discretion.

#### 8. Why is there no contact information?

Since a code repository is not a community, there are no dedicated moderators; just tag one of the owners and they will address it when they have the time.

#### 9. But doesn't all this mean we're at the mercy of the owners of the repository?

You're _always_ at the mercy of the owners of the repository, regardless of how verbose and precise the code of conduct is. This one just doesn't suggest otherwise.

#### 10. Isn't this just a variant of [NCoC](https://github.com/domgetter/NCoC)?

While there are some similarities between NAC and NCoC in terms of observations and recommendations, NAC is tailored to code repositories, and was created in order to promote the idea that they are not really communities and that they shouldn't be treated as such. It is also technically _a_ code of conduct.