Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
66 lines (41 loc) · 3.14 KB

CONTRIBUTING.md

File metadata and controls

66 lines (41 loc) · 3.14 KB
Raw

Contributing To ScopeWeaver

Thanks for your interest in contributing to ScopeWeaver.

ScopeWeaver is being prepared for its public open-source release. During this phase, the repository may contain governance, licensing, and project-setup material before the full implementation is published.

Before You Start

  • Open an issue or discussion before starting substantial work.
  • Keep proposed changes narrowly scoped and easy to review.
  • Do not assume undocumented APIs, internal contracts, or file layouts are stable yet.

What Contributions Are Helpful

We expect contributions in areas such as:

  • documentation improvements
  • architecture feedback
  • bug reports and reproduction cases
  • tests
  • implementation work that aligns with the published roadmap

Contribution Workflow

  1. Start by opening an issue or discussion.
  2. Wait for maintainer confirmation before beginning large changes.
  3. Submit a focused pull request with a clear description of what changed and why.
  4. Be prepared to revise the change during review.

If the repository later adds issue templates, pull request templates, or additional project automation, follow those project-level instructions as well.

Licensing Of Contributions

ScopeWeaver Community Edition is licensed under the GNU Affero General Public License v3.0 (AGPLv3).

For this project, contribution rights matter because the maintainers intend to support both:

  • the open-source community edition under AGPLv3
  • separate commercial licensing for users who need rights beyond AGPLv3

For ScopeWeaver, the intended licensing and sublicensing party is URAI. Because registration is not yet finalized, the exact legal counterparty for contributor-rights paperwork must be stated explicitly in the final CLA or equivalent document before signature.

For that reason:

  • by submitting a contribution, you confirm that you have the right to contribute it
  • you must not submit material that you do not have the right to license
  • maintainers may require a signed Contributor License Agreement (CLA) or similar contributor-rights document granting the necessary rights to the then-current URAI legal counterparty before merging non-trivial contributions

If you are contributing on behalf of an employer, client, university, or other organization, make sure you have authority to do so.

Until the project publishes its final CLA workflow, contributors should coordinate with maintainers before submitting substantial code.

Code And Review Expectations

  • Prefer small pull requests over broad, mixed changes.
  • Keep documentation aligned with behavior.
  • Add tests where the change justifies them.
  • Do not include secrets, credentials, or private data in commits, issues, or pull requests.

Community Expectations

Please engage in good faith, keep review discussions technical and respectful, and assume that project conventions may still evolve during the public-release preparation phase.

Questions

For contribution and licensing questions, contact URAI through the repository or the URAI organization or URAI website until dedicated public contact channels are published.