Skip to content

Latest commit

 

History

History
79 lines (59 loc) · 4.28 KB

CODE_OF_CONDUCT.md

File metadata and controls

79 lines (59 loc) · 4.28 KB

Code of Conduct

Our pledge

We want students, first-time contributors, and experienced maintainers to participate in a welcoming, respectful community. We are committed to participation free from harassment, 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.

Expected behavior

  • Be patient with questions and explain feedback clearly. Someone may be learning Git, English, a programming concept, or open-source collaboration for the first time.
  • Review the contribution and its impact on students. Critique ideas and code respectfully.
  • Give credit, respect copyright, and avoid publishing another person's private information.
  • Accept constructive feedback, take responsibility for mistakes, and help resolve their impact.
  • Respect a request to stop an interaction or move a discussion to an appropriate channel.

Unacceptable behavior includes harassment, threats, stalking, deliberate intimidation, discriminatory or derogatory remarks, sexualized language or imagery, unwelcome sexual attention, personal attacks, and publishing private information without permission. Repeated disruption of discussions or retaliation against someone who raises a concern is also unacceptable.

Where this applies

This Code applies to the project's issues, discussions, pull requests, reviews, learning-content submissions, and other project-managed spaces. It also applies when someone officially represents ProCoderJii, for example through an official project account or an appointed role.

Report a concern

Email procoderji@gmail.com. Project maintainers use this channel to receive conduct reports. Please include the information you are comfortable sharing:

  • What happened and where it happened.
  • Links, dates, or screenshots that help explain the incident.
  • People involved and whether the behavior is ongoing.
  • A way to contact you and any concern about how a response could affect you.

You do not need to investigate the incident yourself. Leave out unrelated personal information, passwords, and private student records. Conduct reports should go through the email channel rather than a public issue or pull-request discussion.

Reports will be handled as privately as practical. Maintainers may need to share relevant information with people who help review or resolve the incident; identifying details should be limited to what is needed. Absolute confidentiality or anonymity cannot be guaranteed, especially when an incident is already public. Reporters should be told about necessary sharing when practical.

Review and response

Maintainers review available information, consider the behavior and its impact, and may ask for clarification. A maintainer who is involved in a report should not decide its outcome. If another reviewer is unavailable, that limitation should be made clear to the reporter.

The response should be proportionate to the severity, context, and recurrence of the behavior. It may include:

  1. Correction: explain the concern, request a change, or remove inappropriate content.
  2. Warning: state the behavior that must stop and any conditions for continued participation.
  3. Temporary restriction: limit participation in project spaces for a stated period.
  4. Permanent restriction: end participation when serious or repeated harm makes it necessary.

These are available responses, not a required sequence. Serious behavior may need an immediate restriction. Maintainers may remove or reject comments, content, or contributions that violate this Code. They should communicate a decision and relevant participation conditions to those affected when appropriate, while limiting disclosure of private report details.

Retaliation against a reporter, witness, or person helping resolve a report is a separate conduct concern. If you believe a decision overlooked relevant information, request a review through procoderji@gmail.com and explain the concern or new information.

Attribution

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