Introduction

This code of conduct outlines expectations for participation in Talegen’s open source initiatives as well as methods for reporting unacceptable behavior.

This community is a welcoming and open community for all.

Anyone violating the code of conduct may be banned from the community.

Our open source initiatives strive to:

  1. Provide a welcoming community to support people of all backgrounds, roles, and levels of expertise. This includes but is not limited to members of any race, ethnicity, culture, national origin, color, education level, sex, orientation, age, size, or other status.
  2. Provide an environment of respect. Whether you are a professional or not, we conduct ourselves professionally. Any disagreement is not an excuse for poor behavior and/or manners. Disrespectful behavior includes but is not limited to:
    • Threats of violence
    • Discriminatory or derogatory language.
    • Posting sexually explicit or violent material.
    • Posting, or threatening to post, people’s personally identifying information (PII) a.k.a. “doxing”.
    • Insults, discriminatory terms, and/or slurs.
    • Behavior that could be perceived as harassment.
    • Advocating or encouraging the above behaviors.
  3. Provide an environment of understanding and patience. You may not be communicating in someone else’s primary spoken or programming language, and others may not have your level of understanding or communication skills.
  4. Disagreements both social and technical are opportunities to learn. Seek to understand the other viewpoints and resolve your differences constructively.
  5. This code is neither exhaustive nor complete. It serves to capture only our common understanding of a productive, collaborative environment. We expect the code to be followed in spirit as much as in the letter.

Scope

This code of conduct applies to all repositories and communities for Talegen-managed open source projects regardless of whether or not the repository explicitly calls out the specific use of this code of conduct.

The code also applies in public spaces where an individual is representing a project or its community. Examples include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online and/or offline event. Representation of a project may futher be defined and clarified by project maintainers.

Reporting Code of Conduct Issues

We encourage all of our communities to resolve issues on their own whenever possible. In the event that an issue cannot be resolved locally, please fee free to report your concerns by contacting [email protected] Your report will be handled in accordance with the issue resolution process described in the Code of Conduct FAQ.

In your report please include:

  • Your contact information
  • Names (real, user names, or pseudonyms) of any individuals involved. If there are additional witnesses, please include them as well.
  • Your account of what occurred and if you believe the incident is ongoing. If there is a publically available record (e.g. a list archive or chat log) please include a link to or attachment.
  • Any additional information that may be helpful.

All reports will be reviewed by a multi-person team and will result in a response that is deemed necessary and appropriate to the circumstances. Where additional perspectives are needed, the team may seek insight from others with relevant expertise or experience. The confidentiality of the person reporting the incident will be kept at all times. Involved parties are never part of the review team.

Anyone asked to stop unacceptable behavior is expected to comply immediately. If an individual engages in unacceptable behavior, the review team may take any action they deem appropriate, including a permanent ban from the community.

This code of conduct is based on the template established by the TODO Group and used by numerous other large communities (e.g., Microsoft, Facebook, Twitter, GitHub and the Scope section from the Contributor Covenant version 1.4.