# Code of Conduct

<!-- 
============================================================================
TEMPLATE INSTRUCTIONS (delete this block before publishing)
============================================================================
Replace all {{PLACEHOLDER}} values:
  anvomidaviser     - Your project name
  hyperpolymath            - GitHub/GitLab username or org
  anvomidaviser             - Repository name
  j.d.a.jewell@open.ac.uk    - Email for conduct reports
  hyperpolymath     - Name of conduct team/committee
  48 hours    - Initial response SLA (e.g., 48 hours)
  2026     - Current year

Review and customise:
- Adjust enforcement ladder for your community size
- Add/remove examples based on your context
- Ensure contact methods work for your team
============================================================================
-->

## Our Pledge

We as members, contributors, and leaders pledge to make participation in anvomidaviser 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, caste, colour, 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.

We recognise that a thriving open source community requires **psychological safety** — an environment where people can contribute, ask questions, make mistakes, and learn without fear of ridicule or retaliation.

---

## Our Standards

### Expected Behaviour

The following behaviours contribute to a positive environment:

**Communication**
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Giving and gracefully accepting constructive feedback
- Assuming good intent while addressing impact
- Communicating clearly and patiently, especially with newcomers

**Collaboration**
- Focusing on what is best for the community
- Showing empathy and kindness toward other community members
- Being collaborative rather than competitive
- Mentoring and supporting less experienced contributors
- Celebrating others' contributions and successes

**Professionalism**
- Accepting responsibility and apologising to those affected by our mistakes
- Learning from the experience and avoiding repetition
- Respecting others' time and attention
- Staying on topic in project spaces
- Following project guidelines and conventions

**Accessibility**
- Using plain language and avoiding unnecessary jargon
- Providing alt text for images and transcripts for audio/video
- Being patient with those using assistive technologies
- Accommodating different communication styles and needs
- Recognising that not everyone communicates the same way

### Unacceptable Behaviour

The following behaviours are considered harassment and are unacceptable:

**Harassment**
- The use of sexualised 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
- Deliberate intimidation, stalking, or following (online or in-person)
- Unwelcome physical contact or simulated physical contact (e.g., emoji)
- Sustained disruption of talks, events, or online discussions

**Discrimination**
- Discriminatory jokes and language
- Posting or threatening to post others' personally identifying information ("doxing")
- Advocating for, or encouraging, any of the above behaviour
- Microaggressions — subtle, often unintentional, discriminatory comments or actions

**Professional Misconduct**
- Publishing others' private information without explicit permission
- Misrepresenting affiliation or contributions
- Plagiarism or claiming credit for others' work
- Retaliating against anyone who reports a Code of Conduct violation
- Other conduct which could reasonably be considered inappropriate in a professional setting

### Grey Areas

Some situations require judgement. When uncertain:

- **Intent vs Impact**: Good intentions do not excuse harmful impact. Focus on making things right.
- **Power Dynamics**: Those with more power (maintainers, employers, experienced contributors) must be especially mindful of their impact.
- **Cultural Differences**: What's acceptable varies by culture. When in doubt, err on the side of caution and ask.
- **Humour**: Jokes at others' expense are rarely funny to everyone. Punch up, not down.

---

## Scope

This Code of Conduct applies within all community spaces, including:

**Online Spaces**
- Repository discussions, issues, and pull/merge requests
- Project chat channels (Matrix, Discord, Slack, IRC)
- Mailing lists and forums
- Social media when representing the project
- Video calls and virtual meetings

**In-Person Spaces**
- Conferences, meetups, and events
- Workshops and training sessions
- Any gathering where you represent the project

**Representation**
This Code of Conduct also applies when an individual is officially representing the community in public spaces. Examples include:

- Using an official project email address
- Posting via an official social media account
- Acting as an appointed representative at an event
- Speaking on behalf of the project

---

## Enforcement

### Reporting

If you experience or witness unacceptable behaviour, or have any other concerns, please report it as soon as possible.

**How to Report**

| Method | Details | Best For |
|--------|---------|----------|
| **Email** | j.d.a.jewell@open.ac.uk | Detailed reports, sensitive matters |
| **Private Message** | Contact any maintainer directly | Quick questions, minor issues |
| **Anonymous Form** | [Link to form if available] | When you need anonymity |

**What to Include**

- Your contact information (unless anonymous)
- Names/usernames of those involved
- Description of what happened
- When and where it occurred
- Any witnesses
- Any supporting evidence (screenshots, links)
- How you would like us to respond (if you have a preference)

**What Happens Next**

1. You will receive acknowledgment within **48 hours**
2. The hyperpolymath will review the report
3. We may ask for additional information
4. We will determine appropriate action
5. We will inform you of the outcome (respecting others' privacy)

### Confidentiality

All reports will be handled with discretion:

- Reporter identity is protected by default
- Details are shared only with those who need to know
- We will ask before naming you in any communication
- Anonymous reports are accepted and investigated

### Conflicts of Interest

If a hyperpolymath member is involved in an incident:

- They will recuse themselves from the process
- Another maintainer or external party will handle the report
- We will disclose any potential conflicts

---

## Enforcement Guidelines

The hyperpolymath will follow these guidelines in determining consequences:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome.

**Consequence**: A private, written warning providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested.

**Duration**: Immediate

### 2. Warning

**Community Impact**: A violation through a single incident or series of actions.

**Consequence**: A warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period. 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.

**Duration**: 1-4 weeks

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including sustained inappropriate behaviour.

**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period. 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.

**Duration**: 1-6 months

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, 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.

**Duration**: Permanent (with appeal rights after 12 months)

### Enforcement Across Perimeters

For contributors with elevated access (Perimeter 2 or 1):

| Level | Additional Consequence |
|-------|----------------------|
| Correction | Noted in contributor record |
| Warning | Access privileges may be temporarily reduced |
| Temporary Ban | Access reduced to Perimeter 3 for ban duration |
| Permanent Ban | All access revoked |

---

## Appeals

If you believe an enforcement decision was made in error:

1. **Wait 7 days** after the decision (cooling-off period)
2. **Email** j.d.a.jewell@open.ac.uk with subject line "Appeal: [Original Report ID]"
3. **Explain** why you believe the decision should be reconsidered
4. **Provide** any new information not previously available

**Appeals Process**

- Appeals are reviewed by a different hyperpolymath member than the original
- You will receive a response within 14 days
- The appeals decision is final
- You may only appeal once per incident

**Grounds for Appeal**

- Procedural errors in the original investigation
- New evidence not previously available
- Disproportionate response to the violation
- Misunderstanding of facts

---

## Supporting Those Who Report

We are committed to supporting those who report violations:

**We Will**
- Believe and take all reports seriously
- Respect your privacy and confidentiality preferences
- Keep you informed of progress (if you wish)
- Take steps to protect you from retaliation
- Provide resources if you need support

**We Will Not**
- Require you to confront the person directly
- Dismiss reports without investigation
- Reveal your identity without consent
- Tolerate retaliation against reporters
- Rush you to make decisions

---

## Prevention

Beyond enforcement, we actively work to prevent issues:

**Onboarding**
- All contributors are expected to read this Code of Conduct
- Perimeter 2 applicants must confirm they've read and understood it
- Maintainers receive additional training on enforcement

**Culture**
- We model the behaviour we expect
- We intervene early when we see potential issues
- We thank people for positive contributions
- We create opportunities for diverse voices

**Review**
- This Code of Conduct is reviewed annually
- Community feedback is welcomed
- Changes are communicated clearly

---

## Acknowledgments

This Code of Conduct is adapted from:

- [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1
- [Django Code of Conduct](https://www.djangoproject.com/conduct/)
- [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct)
- [Python Community Code of Conduct](https://www.python.org/psf/conduct/)

We thank these communities for their leadership in creating welcoming spaces.

---

## Questions?

If you have questions about this Code of Conduct:

- Open a [Discussion](https://github.com/hyperpolymath/anvomidaviser/discussions) (for general questions)
- Email j.d.a.jewell@open.ac.uk (for private questions)
- Contact any maintainer directly

---

## Summary

**Be kind. Be respectful. Be collaborative.**

We're all here because we care about this project. Let's make it a place where everyone can do their best work.

---

<sub>Last updated: 2026 · Based on Contributor Covenant 2.1</sub>
