CodeNomad/GOVERNANCE.md
Pascal André 5509bf668e
docs: name the CodeNomad contributors in the license's copyright notice (#1254)
## Summary

The license's copyright notice read "Copyright (c) 2026 Neural Nomads".
The name could be read as a company of the same name, while no
assignment exists: each contributor keeps the copyright of what they
wrote. The year also missed the project's start (first commit
2025-10-22).

- **`LICENSE`:** "Copyright (c) 2025-2026 CodeNomad contributors". The
license itself (MIT) and its terms are unchanged; released versions keep
their notice.
- **`GOVERNANCE.md`:** one sentence: each contributor keeps the
copyright of their contributions and publishes them under the MIT
license, and the notice names them together as the CodeNomad
contributors.

- **Desktop installers:** the Electron build (`build.copyright`, which
electron-builder otherwise derives from the package author) and the
Tauri bundle (`bundle.copyright`) set "Copyright © 2025-2026 CodeNomad
contributors", which Windows shows as the file's copyright and macOS in
the app's About information.

Neural Nomads stays the name of the GitHub organization and the
publisher shown by the apps and the README.

Both maintainers agreed to this change (`GOVERNANCE.md` requires it for
license changes): @pascalandr through this pull request, @shantur in a
private conversation in which he left the license wording to Pascal.
@shantur, a comment confirming here completes the record.

## Validation

- `git diff --check`; both configuration files parse and
`bundle.copyright` is part of the Tauri 2 schema. No other file carries
the project's copyright notice (third-party notices unchanged).
2026-11-01 11:01:24 +01:00

2.5 KiB

CodeNomad Governance

CodeNomad is an open-source project of the NeuralNomadsAI GitHub organization, released under the MIT license. Each contributor keeps the copyright of their contributions and publishes them under that license; the license's copyright notice names them together as the CodeNomad contributors.

Maintainers

Maintainer GitHub Role
Shantur Rathore @shantur Maintainer and administrator of the repository; owner of the NeuralNomadsAI organization
Pascal André @pascalandr Maintainer and administrator of the repository

The maintainers have the same rights and responsibilities for the project. Either of them can change the repository's settings, manage its access, and act for the project with the services it uses, such as code signing, package registries and funding platforms.

Maintainers review and merge pull requests, publish releases and moderate the project's spaces under the code of conduct.

Decisions

  • Day-to-day changes are proposed and discussed in pull requests to dev, as described in CONTRIBUTING.md. Either maintainer can merge a pull request.
  • Significant decisions need the agreement of both maintainers, recorded in a GitHub issue or pull request: changes to the license, this document or the code of conduct; adding or removing a maintainer; releases that break compatibility; and funding policy.
  • When the maintainers disagree, the current state is kept until they agree.

Becoming a maintainer

A contributor with a sustained record of quality contributions can be invited to become a maintainer with the agreement of all current maintainers. A maintainer can step down at any time by saying so in an issue.

Funding

Contributions are received through the channels listed on the help site's Support CodeNomad page and in .github/FUNDING.yml; today this is Pascal André's GitHub Sponsors. Each channel names who receives the money. A contribution buys no features, roadmap influence, support priority or license rights.

Any shared project fund requires the agreement of both maintainers, and no one approves their own expenses from it.

Succession

If a maintainer becomes unavailable, the remaining maintainer continues the project. If no maintainer can continue, the maintainers hand the project over to new maintainers chosen in a public issue.