Skip to content

Latest commit

 

History

History
92 lines (55 loc) · 8.19 KB

File metadata and controls

92 lines (55 loc) · 8.19 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.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

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

Examples of unacceptable behavior include:

  • 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, such as a physical or email address, without their explicit permission
  • Plagiarism — copying another contributor's pull request, diff, or work and submitting it as your own (including duplicated or lightly reworded copies filed under a different account), and attempts to game contribution scoring or farm Gittensor rewards through copied submissions
  • Manipulating the review bot or automated gate — embedding hidden or misleading instructions in code, comments, PR titles/bodies, file contents, or commit messages to influence the AI review or pass the gate (prompt injection)
  • Circumventing CI or the gate — disabling or weakening tests, faking or gaming validation, or editing CI to skip required checks
  • Submitting malicious or destructive code — malware, backdoors, secret exfiltration, malicious dependencies, or anything intended to damage the codebase, its data, or production systems
  • Abusing system resources — webhook floods, deliberately triggering expensive re-reviews or CI runs, or attempts to exhaust the review bot's compute or credits
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement is proportional and escalates with intent and repetition. A linked, currently-open issue is required on every PR — issue creation is maintainer-only, so pick an existing open issue to link rather than opening your own; a PR with no linked issue, or one linked to an issue that's already closed, is automatically closed before its content is even scored. Off-scope or low-effort work is closed or relabeled, with no further penalty. Reward-farming is against policy: using more than one account under the same person's control (alt / sock-puppet accounts) to inflate contribution credit, or manufacturing low-value/slop PRs and bulk point-chasing surface PRs; linked issues from farming are closed so the work earns no bonus credit and a warning is issued, with continued or any confirmed multi-account farming closed on sight and blocked. Plagiarism and ban-evasion — copying another contributor's work, or returning under a new account after a block — result in an immediate permanent block from contributing across all of our repositories (JSONbored/gittensory, JSONbored/metagraphed, JSONbored/awesome-claude).

Contribution terms. By submitting, you affirm the work is your own original work and that you have the right to contribute it under this repository's license. Contributing is not an entitlement: contribution scoring and any Gittensor rewards are set by the subnet's on-chain hyperparameters and validators, not by us, and all decisions — merge, close, scope, policy, timing, labels, and blocks — are at maintainer discretion and final. Report security issues privately rather than exploiting or weaponizing them in a PR; good-faith research is welcome through that channel.

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the maintainers privately via the repository's confidential reporting channel — open a GitHub security advisory or contact the maintainer @JSONbored. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

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

2. Warning

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

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

3. Temporary Ban

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

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

4. Permanent Ban

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

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.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.