add coc inspo

li0ns-resources/GNU-Kind-Communication-Guidelines.txt

@@ -0,0 +1,35 @@
+GNU Kind Communications Guidelines
+
+by Richard Stallman
+
+Purpose
+The GNU Project encourages contributions from anyone who wishes to advance the development of the GNU system, regardless of gender, race, ethnic group, physical appearance, religion, cultural background, and any other demographic characteristics, as well as personal political views.
+
+People are sometimes discouraged from participating in GNU development because of certain patterns of communication that strike them as unfriendly, unwelcoming, rejecting, or harsh. This discouragement particularly affects members of disprivileged demographics, but it is not limited to them. Therefore, we ask all contributors to make a conscious effort, in GNU Project discussions, to communicate in ways that avoid that outcome—to avoid practices that will predictably and unnecessarily risk putting some contributors off.
+
+These guidelines suggest specific ways to accomplish that goal.
+
+Guidelines
+*Please assume other participants are posting in good faith, even if you disagree with what they say. When people present code or text as their own work, please accept it as their work. Please do not criticize people for wrongs that you only speculate they may have done; stick to what they actually say and actually do.
+*Please think about how to treat other participants with respect, especially when you disagree with them. For instance, call them by the names they use, and refer to them using words whose meanings (as you understand them) cover those participants' stated gender identities. Please also show tolerance and respect for people who do that using different words from the words you use.
+*Please do not take a harsh tone towards other participants, and especially don't make personal attacks against them. Go out of your way to show that you are criticizing a statement, not a person.
+*Please recognize that criticism of your statements is not a personal attack on you. If you feel that someone has attacked you, or offended your personal dignity, please don't “hit back” with another personal attack. That tends to start a vicious circle of escalating verbal aggression. A private response, politely stating your feelings as feelings, and asking for peace, may calm things down. Write it, set it aside for hours or a day, revise it to remove the anger, and only then send it.
+*Please avoid statements about the presumed typical desires, capabilities or actions of some demographic group. They can offend people in that group, and they are always off-topic in GNU Project discussions.
+*Please be especially kind to other contributors when saying they made a mistake. Programming means making lots of mistakes, and we all do so—this is why regression tests are useful. Conscientious programmers make mistakes, and then fix them. It is helpful to show contributors that being imperfect is normal, so we don't hold it against them, and that we appreciate their imperfect contributions though we hope they follow through by fixing any problems in them.
+*Likewise, be kind when pointing out to other contributors that they should stop using certain nonfree software. For their own sake, they ought to free themselves, but we welcome their contributions to our software packages even if they don't do that. So these reminders should be gentle and not too frequent—don't nag.
+
+By contrast, to suggest that others run a nonfree program opposes the basic principles of GNU, so it is not allowed in GNU Project discussions.
+
+*Please respond to what people actually said, not to exaggerations of their views. Your criticism will not be constructive if it is aimed at a target other than their real views.
+*If in a discussion someone brings up a tangent to the topic at hand, please keep the discussion on track by focusing on the current topic rather than the tangent. *This is not to say that the tangent is bad, or not interesting to discuss—only that it shouldn't interfere with discussion of the issue at hand. In most cases, it is also off-topic, so those interested ought to discuss it somewhere else.
+
+If you think the tangent is an important and pertinent issue, please bring it up as a separate discussion, with a Subject field to fit, and consider waiting for the end of the current discussion.
+
+*Rather than trying to have the last word, look for the times when there is no need to reply, perhaps because you already made the relevant point clear enough. If you know something about the game of Go, this analogy might clarify that: when the other player's move is not strong enough to require a direct response, it is advantageous to give it none and instead move elsewhere.
+*Please don't argue unceasingly for your preferred course of action when a decision for some other course has already been made. That tends to block the activity's progress.
+*If others have irritated you, perhaps by disregarding these guidelines, please don't excoriate them, and especially please don't hold a grudge against them. The constructive approach is to encourage and help other people to do better. When they are trying to learn to do better, please give them plenty of chances.
+*If other participants complain about the way you express your ideas, please make an effort to cater to them. You can find ways to express the same points while making others more comfortable. You are more likely to persuade others if you don't arouse ire about secondary things.
+*Please don't raise unrelated political issues in GNU Project discussions, because they are off-topic. The only political positions that the GNU Project endorses are (1) that users should have control of their own computing (for instance, through free software) and (2) supporting basic human rights in computing. We don't require you as a contributor to agree with these two points, but you do need to accept that our decisions will be based on them.
+
+By making an effort to follow these guidelines, we will encourage more contribution to our projects, and our discussions will be friendlier and reach conclusions more easily.
+

li0ns-resources/contributor-covenant-CoC.txt

@@ -0,0 +1,78 @@
+= Contributor Covenant Code of Conduct
+
+== Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+== Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+== Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+== Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+== Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+== Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+=== 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+=== 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+=== 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+=== 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+== Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by  Mozilla's code of conduct enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available  at https://www.contributor-covenant.org/translations.

li0ns-resources/contributor-coventant-FaQ.txt

@@ -0,0 +1,54 @@
+Frequently Asked Questions
+We recognize that the adoption of a code of conduct can be a source of confusion or even anger for some people in an open source community. This FAQ is intended to address some of the common concerns that we see raised by people whose reaction to adoption is a negative one, and we hope it will help alleviate some of their concerns.
+
+Are codes of conduct a mechanism for turning project governance over to “social justice warriors”?
+Project maintainers are responsible for tailoring and enforcing the codes of conduct that they adopt. A code of conduct does not grant any authority or power to anyone outside of this group. Even if pressure is applied from a third party, such as on social media, the project maintainers alone have the authority to enforce the code of conduct and are under no obligation to bow to external pressure.
+
+What should I do if I have been accused of violating the code of conduct?
+The first step when dealing with accusations of violation of the code of conduct is to deal with it in a professional manner. Do not respond with sarcasm, attack the code of conduct or its enforcement, or the accuser. Calmly focus on the evidence of what happened, work to understand any damage you may have caused, and examine how your intentions may have inadvertently caused harm. The more you stick to the facts of what happened, and demonstrate your willingness to work with the enforcement team as they evaluate the claim, the better. Most importantly, trust the project maintainers to act in a fair and just manner.
+
+Won’t a code of conduct have a negative effect on the end product?
+There is no evidence that adopting a code of conduct has a negative effect on code quality. But it will affect the experience of those who participate in communities where the CoC is enforced. Ensuring that more people feel safe contributing to the project can significantly improve the quality of the codebase.
+
+Won’t this just promote participation for the sake of participation and an end of meritocracy?
+The code of conduct is not a positive discrimination policy, and it does not include any recommendation on how to recruit or select project participants. It also does not state or imply that any and all contributions should be accepted, regardless of quality or adequacy, based on any personal characteristic of the submitter. By fostering a more cooperative and civil environment, the code of conduct actually creates the opportunity for more people to participate, learn, grow, and improve the quality of their contributions in a positive and supportive environment.
+
+Why should my community have to change to accommodate marginalized people?
+The level of accommodation that the code of conduct implies is not higher than the one that is expected when dealing with peers in other professional settings. It is not about being accommodating to one group, it’s about making all potential contributors feel welcome and safe.
+
+When I code, I just see the code, not the person, so why should I care about this code of conduct? Can’t minorities keep their minority-status to themselves and focus on the code?
+Research shows that the two most important factors in successful teams are diversity ("Why Diverse Teams Are Smarter”, Harvard Business Review) and psychological safety ("Foster Psychological Safety”, re:Work). If a potential contributor has to hide some portion of their identity in order to avoid explicit or implicit bias, they may not feel safe contributing to the project. Each person should feel welcomed and accepted and free to bring their whole selves to their work. What’s more, hiding behind an anonymous account, a gender- or racial-neutral pseudonym, or otherwise hiding one’s true identity can have a materially negative effect on building the kind of reputation and open source track record that many employers look for in potential hires.
+
+Isn’t this just a way for progressive/left-wing people to push their agenda?
+“Everything is politics”, but the code of conduct is not about an advance of progressive/left-wing politics. It’s about establishing a minimal level of civil and professional collaboration. Civil, non-discriminatory, and professional behavior should be a baseline and shared value held by people of all ideologies, regardless of political affiliation (with the obvious exception of hate groups).
+
+Doesn’t adopting a code of conduct make a contributor subject to removal from a project for a simple mistake, holding an unpopular belief, or sharing an opinion on their Twitter account?
+Contributor Covenant specifically states that behavior, actions, and communications outside the scope of the project cannot be considered violations of the code of conduct, unless the person in question is representing the project in an official capacity.
+
+In the case of a confirmed violation, project maintainers are expected to meet the violation with a consequence that is proportional to the offense and to work with the offender to prevent future violations. Maintainers want a safe, collaborative community of bright, kind, compassionate contributors with solid technical and communication skills. It is not in their best interest to be hostile or overly punitive to members of their community.
+
+Doesn’t this code of conduct just promote political correctness?
+Only if you define political correctness as the belief that women, non-binary people, gay, lesbian, queer, and/or transgender people, people of color, and people of different religious backgrounds should be afforded the same rights and privileges as everyone else.
+
+What is so wrong that white males dominate a certain profession?
+Women and men of all backgrounds, ethnicities, and races can have competence and interest in software development and deserve equal access to opportunities in open source and tech. But the low rate at which marginalized people are recruited, and the high rate at which they leave the industry, point to a larger cultural and systemic problem. Codes of conduct attempt to address this in part by reducing the potential for discrimination, explicit and implicit bias, and the negative impact of homogeneous teams.
+
+I don’t agree with Coraline Ada Ehmke’s politics. Should I avoid this code of conduct?
+If you’re a meritocracy fan, you already abide by the principle of separating the person from the contribution. And even if you’re not, adopting Contributor Covenant does not imply any political or social orientation aside from the (unfortunately politicized) goal of making your project welcoming and inclusive to people of all backgrounds.
+
+Doesn’t a code of conduct give too much power to project maintainers?
+Project maintainers are the arbiters of code of conduct violations and are the unquestioned leaders of the projects they own. Without a code of conduct, a project maintainer has the power to eject any contributor from a project for any (or no) reason at all. A properly enforced code of conduct creates a social contract between and among contributors and maintainers that make such abuses of power less acceptable and common. If you don’t trust a project maintainer to act in a just and fair way, you probably should consider not participating in their community.
+
+Can I be cited for a code of conduct violation for something that I say on Twitter or other social media site?
+Contributor Covenant only applies in project spaces and when an individual is representing a project. Your conduct outside of these situations is not governed by the code of conduct.
+
+Does the prohibition on publishing private information include email addresses sent to a public list?
+No. Information that has voluntarily been published to a public location does not fall under the category of private information. Such public information may be used within the context of the project according to project norms (such as in commit metadata in code repositories), without that constituting a breach of the code of conduct.
+
+Why are ‘ethnicity’ and ‘race’ called out as two separate pivots? Aren’t these terms interchangeable?
+Ethnicity (or ethnic group) is a category of people who identify with each other based on similarities such as common ancestry, language, history, society, culture or nation.
+Race is the grouping of humans based on shared physical or social qualities into categories generally viewed as distinct by society and usually resulting from genetic ancestry.
+We recognize different cultures and the process of translation might make the differences between these terms less apparent. Violence and discrimination can occur based on the perception of either and sometimes both at the same time which is why it is important to call them out as two separate concepts.
+
+Contributor Covenant explicitly lists a set of protected classes; does this make it acceptable to discriminate or make others feel unwelcome based on other factors?
+No. Contributor Covenant explicitly lists protected classes for many reasons, such as reminding people to give them appropriate consideration, and assuring people in those protected classes that they are welcome. However, this is not an invitation for rules lawyers to seek loopholes, or to discriminate against others or make people feel unwelcome based on criteria not listed here. (With the notable caveat that those who discriminate or make others feel unwelcome are themselves not welcome.)

li0ns-resources/links.txt

@@ -0,0 +1,8 @@
+links to the sources for the text files in this folder
+
+https://www.contributor-covenant.org/version/2/0/code_of_conduct/
+https://www.contributor-covenant.org/faq/
+by Coraline Ada Ehmke
+
+https://www.gnu.org/philosophy/kind-communication
+by Richard Stallman (controversial)