Skip to content

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in the AIDDDMAP project and our community a harassment-free experience for everyone, regardless of age, body size, 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.

Our Standards

Examples of Behavior that Contributes to a Positive Environment

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members
  • Supporting and mentoring new contributors

Examples of Unacceptable Behavior

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject:

  • Comments, commits, code, wiki edits, issues, and other contributions
  • Any content that is not aligned with this Code of Conduct
  • Any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include:

  • Using an official project email address
  • Posting via an official social media account
  • Acting as an appointed representative at an online or offline event
  • Participating in project-related forums or discussions

Enforcement

Reporting

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at:

conduct@aidddmap.com

All complaints will be:

  • Reviewed and investigated promptly and fairly
  • Kept confidential to protect the reporter
  • Handled with discretion and respect

Enforcement Process

  1. First Occurrence: A private, written warning, explaining why the behavior was inappropriate.
  2. Second Occurrence: A public warning, documenting the violation.
  3. Third Occurrence: Temporary ban from project communication channels and contribution.
  4. Fourth Occurrence: Permanent removal from the project community.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

Additional Guidelines

Technical Discussions

  1. Be Constructive

  2. Focus on the code, not the person

  3. Explain your reasoning

  4. Provide examples when possible

  5. Documentation

  6. Keep documentation up to date

  7. Document your changes clearly

  8. Help others learn from your work

  9. Code Reviews

  10. Be timely in your reviews
  11. Be thorough but fair
  12. Explain your suggestions
  13. Be open to discussion

Community Interaction

  1. Communication Channels

  2. Use appropriate channels for different types of discussions

  3. Keep technical discussions in technical channels

  4. Respect others' time zones

  5. Language and Tone

  6. Use clear, professional language

  7. Avoid jargon when possible
  8. Be patient with non-native speakers

  9. Use inclusive terminology

  10. Conflict Resolution

  11. Address conflicts privately first
  12. Seek mediation when needed
  13. Focus on solutions, not blame
  14. Take breaks when discussions get heated

Amendments

This Code of Conduct may be amended as needed. Proposed changes will:

  1. Be announced to the community
  2. Have a comment period of at least 14 days
  3. Require approval from the project leadership team
  4. Be clearly versioned and dated

Contact Information

Project Leadership

Community Channels