Skip to main content
3ngram is open source (Apache 2.0) and accepts contributions under the Developer Certificate of Origin. This page is the map; the canonical documents live in the repository and are linked below.

​
Before you start

3ngram is maintained by a single person, so contributions are managed deliberately:
  • Open an issue before starting a non-trivial PR so scope and approach are agreed up front. Unsolicited large PRs may be closed without a full review.
  • Small, obvious fixes (typos, clear bugs) are welcome directly.
  • Questions and setup help belong in GitHub Discussions, not Issues.
The full workflow — development setup, branch naming, PR checklist, and every CI gate your change must pass — is in CONTRIBUTING.md.

​
DCO sign-off

Every commit needs a Signed-off-by trailer (Developer Certificate of Origin); there is no CLA. Sign off with the -s flag: 
git commit -s -m "feat(scope): add the thing"
CI enforces the trailer on external (fork) PRs. All contributions are made under Apache 2.0, and every new source file carries an SPDX header — see LICENSING.md.

​
Project policies

Contributing guide

Local setup, branch and PR workflow, CI gates, and the PR checklist.

Code of conduct

The Contributor Covenant applies to all project spaces.

Security policy

Report vulnerabilities through a private security advisory — never a public issue.

Support

Where questions, bug reports, and feature requests go, and what response to expect.

​
Where things go

You want to…Go to
Ask a question or discuss an ideaGitHub Discussions
Report a reproducible bugBug issue
Request a featureFeature issue
Report a security vulnerabilityPrivate security advisory
Issues are reserved for actionable, reproducible bugs and concrete feature requests; question-style issues may be converted to a Discussion. There is no commercial support tier and no SLA — well-scoped, reproducible reports get attention soonest.