Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
67 lines (45 loc) · 2.44 KB

CONTRIBUTING.md

File metadata and controls

67 lines (45 loc) · 2.44 KB
Raw

Contributing to Challenge Run Community (CRC)

Thank you for your interest in contributing to CRC. This document outlines the terms and expectations for anyone contributing to this project.

Permission to Contribute

CRC is a proprietary project. Contributions are accepted by invitation only at the sole discretion of the project owner. Access to this repository does not grant permission to contribute.

If you have been invited to contribute, the following terms apply to all contributions you submit.

Intellectual Property Assignment

By submitting a contribution (including but not limited to code, documentation, design, configuration, translations, or any other materials) to this repository, you agree to the following:

  1. You assign all rights, title, and interest in your contribution to Challenge Run Community (CRC) and its project owner. This includes all intellectual property rights worldwide.

  2. You waive any moral rights to your contribution to the fullest extent permitted by law.

  3. You confirm that your contribution is your own original work, that you have the right to assign it, and that it does not infringe on any third-party rights.

  4. You understand that your contribution may be modified, redistributed, relicensed, or removed at any time without notice or compensation.

If you are unable or unwilling to agree to these terms, do not submit a contribution.

Contribution Guidelines

  • Branching: Work on a feature branch. Do not push directly to main.
  • Commits: Write clear, concise commit messages describing what changed and why.
  • Scope: Only work on tasks you have been assigned or have discussed with the project owner. Do not make unsolicited changes to unrelated areas of the codebase.
  • Code style: Follow the conventions documented in CLAUDE.md (Svelte 5 runes, TypeScript, SCSS, existing CSS variables, mobile-first).
  • Testing: Verify your changes work locally before submitting. Test on both desktop and mobile viewports.
  • Communication: If you are unsure about an approach, ask before writing code.

No Guarantee of Inclusion

The project owner reserves the right to accept, reject, modify, or remove any contribution for any reason. Being invited to contribute does not guarantee that your work will be merged or retained.

Questions

If you have questions about these terms or about contributing, contact the project owner directly.