Octaryn Engine
Contributor intake required

Contributor Intake

Before your first substantive pull request, start the verified contributor intake flow. You will sign in with GitHub first and then complete the private intake form. Your request then goes to maintainer review before any private repo access is granted. That is the record maintainers check before reviewing a first substantive PR.

Start Verified Intake Read Public Terms Read Assignment Summary
GitHub identity is verified first. Intake details stay private in the private intake repo, and access is only granted after maintainer approval.

Before you open a PR

  1. Read the public summaries for the license, contribution rules, and assignment terms below.
  2. Start the verified intake flow and sign in with the GitHub account you will use for contributions.
  3. Complete the private intake form with your legal name, email address, and required acknowledgments.
  4. Wait for maintainer approval. If approved, GitHub will send collaborator invites for `octaryn-core` and `octaryn-editor`.
  5. Do not include unauthorized third-party code or assets.

Maintainer checks

  • Check that the contributor completed the verified intake flow before a first substantive PR is merged.
  • Use the approval email link to approve access before any collaborator invite is sent.
  • Use the verified GitHub login stored by the intake app as the access record.
  • Confirm collaborator access was granted to `octaryn-core` and `octaryn-editor` only after approval.
  • Use the private intake repo records and the approval email flow for contributor details and access decisions.
  • Only merge substantive first-time PRs after confirmation.

Key restrictions

  • The private code repos are access-controlled and they are not open source.
  • Contributors may not redistribute forks, mirrors, or binaries.
  • Only Zachary David Rose may publish or commercialize the project.
  • Accepted contributions are governed by the assignment agreement.

Public Reading Summaries

LICENSE.md summary

Octaryn Engine is access-controlled, source-available, and proprietary. Approved contributors may review, build, modify, and submit changes through the official workflow, but may not redistribute source, publish mirrors, distribute builds, or use the project commercially without written authorization.

CONTRIBUTING.md summary

Approved contributors may work in the private code repos, push branches, and open pull requests. Nothing should be pushed directly into the protected main branch, and all substantive work is reviewed at maintainer discretion before merge.

CONTRIBUTOR_ASSIGNMENT.md summary

Intentional submissions are governed by contributor assignment terms that transfer contribution rights to Zachary David Rose, with an exclusive fallback license where assignment is not available. The verified intake flow is the project's access and acceptance checkpoint before substantive pull requests are reviewed.