Prepare repository for open-source release#64
Merged
Conversation
…and README updates - LICENSE-MIT: MIT license text - LICENSE-APACHE: placeholder (to be updated by maintainer) - LICENSE-AGPL: placeholder for AGPL-3.0 (calendar/relayer, to be updated) - CODE_OF_CONDUCT.md: Contributor Covenant v2.1 - CONTRIBUTING.md: development guide and contributor guidelines - SECURITY.md: vulnerability reporting policy - .github/FUNDING.yml: links to calendar/relayer for ETH donations - .github/ISSUE_TEMPLATE/bug_report.yml: structured bug report form - .github/ISSUE_TEMPLATE/feature_request.yml: feature request form - .github/ISSUE_TEMPLATE/config.yml: issue template config with docs link - .github/PULL_REQUEST_TEMPLATE.md: PR description template - Update crates/calendar and crates/relayer Cargo.toml to AGPL-3.0-only - Update README.md with badges, license section, contributing link, funding info - Add license field to root package.json Co-authored-by: lightsing <15951701+lightsing@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add documentation for open source readiness
Prepare repository for open-source release
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add standard OSS governance files, GitHub templates, and split licensing (MIT/Apache-2.0 for libraries, AGPL-3.0 for server components).
Licensing
LICENSE-MIT— full text;LICENSE-APACHE,LICENSE-AGPL— placeholders, need full text before going publicuts-calendaranduts-relayerCargo.toml overridden toAGPL-3.0-only; all other crates remainMIT OR Apache-2.0via workspacepackage.jsongetslicensefieldCommunity docs
CODE_OF_CONDUCT.md— Contributor Covenant v2.1CONTRIBUTING.md— dev setup, build/test/lint commands, project structure, licensing terms for contributionsSECURITY.md— private vulnerability reporting via GitHub Security Advisories or email, 48h ack SLAGitHub config
.github/ISSUE_TEMPLATE/bug_report.yml/feature_request.yml— structured forms with component dropdown.github/ISSUE_TEMPLATE/config.yml— blank issues enabled, link to docs.github/PULL_REQUEST_TEMPLATE.md— description + checklist.github/FUNDING.yml— custom links to calendar/relayer homepages (ETH to operator address)README
CONTRIBUTING.md, funding section, license section explaining the split modelOpen questions
uts-stamper,uts-journal,uts-beacon-injectoralso be AGPL? They're runtime dependencies of the server crates.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.