Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
107 lines (76 loc) · 4.93 KB

CODE_OF_CONDUCT.md

File metadata and controls

107 lines (76 loc) · 4.93 KB

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, caste, color, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to a positive environment:

  • 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
  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior:

  • 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 without their explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening a GitHub Discussion or contacting the project maintainer directly. All complaints will be reviewed and investigated promptly and fairly.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1.

GSSoC Contributor Procedures

This section supplements the Contributor Covenant above with procedures specific to GirlScript Summer of Code (GSSoC) 2026 contributors. Both the Contributor Covenant and these GSSoC procedures apply; in case of conflict, the Contributor Covenant prevails for non-GSSoC contributions.

Scope

These procedures apply to:

  • All participants registered for GSSoC 2026 (mentors, contributors, maintainers)
  • All DevTrack contribution channels: GitHub Issues, Pull Requests, Discussions, and the project Discord (if applicable) during the GSSoC program window
  • All GSSoC-related work, including issue selection, claims, reviews, and evaluations

Reporting Procedure

If you experience or witness behavior that violates the Contributor Covenant during GSSoC participation:

  1. Open a private GitHub Security Advisory at https://github.com/Priyanshu-byte-coder/devtrack/security/advisories/new with the gsoc-coc label in the title. This keeps the report visible only to the maintainer.
  2. If the advisory form is unavailable, email doshipriyanshu3@gmail.com with subject line GSSoC CoC Report.
  3. Include the following:
    • Your GitHub handle and GSSoC participant ID (if registered)
    • The GitHub handle of the person whose behavior is being reported
    • A factual description of the incident(s) with dates and links to public evidence (issues, PRs, comments) when possible
    • The specific section of the Contributor Covenant that you believe was violated

Response Timeline

  • Acknowledgement: within 48 hours of receiving a report
  • Initial review outcome: within 5 business days
  • Resolution and any corrective action: communicated privately to the reporter and, where appropriate, to the GSSoC program admins

Confidentiality and Anonymity

  • Reports are kept confidential. Details are shared only with maintainers who need to know to investigate or take action.
  • Reporter identity is not disclosed publicly or to the reported person beyond what is necessary to convey the report.
  • If the reporter wishes to remain anonymous to the reported person, the maintainer will honor that request to the extent possible.

Appeals

If you disagree with a CoC enforcement decision made under these procedures, you may appeal by replying to the original advisory thread within 14 days of the decision. An uninvolved maintainer (or, if none is available, a GSSoC program admin) will review the appeal and respond within 7 business days.

After a Report

Once a report is filed:

  1. The maintainer acknowledges receipt within 48 hours.
  2. The maintainer investigates by reviewing the linked evidence and may request additional context from the reporter.
  3. The maintainer decides on a resolution (no action, warning, temporary restriction, or permanent ban) and communicates it privately.
  4. The reporter is informed of the resolution and, if applicable, the appeal window.

Out of Scope

  • Disputes over technical decisions (architecture, code style, merge timing) are handled through normal PR review and Discussion channels, not CoC procedures.
  • Issues with the GSSoC platform itself (points, leaderboard, certificate eligibility) should be directed to the GSSoC program admins, not the project maintainer.