docs: add CLA infrastructure and modernize GitHub templates#1521
Merged
docs: add CLA infrastructure and modernize GitHub templates#1521
Conversation
Add Apache ICLA-style CLA (license grant, not copyright assignment), GitHub Action enforcement via contributor-assistant/github-action@v2, and CODEOWNERS gating for commercially relevant sync server paths. - CLA.md: 7-section Apache ICLA adapted for EpicenterHQ - ci.cla.yml: enforces CLA signing on PRs, allowlists bots - CODEOWNERS: gates apps/api/, packages/sync/, packages/sync-client/ - CONTRIBUTING.md: added Licensing and CLA section - HOW_TO_MONETIZE.md: updated to reflect CLA is now in place - Workflow README: documented ci.cla.yml in CI table
Add Sync, CLI, Workspace, and Landing Page to the Affected Component dropdown. Existing Whispering-centric options kept since they're still the primary bug surface.
…plate Conventional commit prefixes in the PR title already encode the change type. The checkboxes added friction without new signal.
Contributors touching the sync server or API paths now get a heads-up that those directories require explicit owner review.
… link Contributors can now open blank issues or jump straight to Discord from the template chooser.
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
1 participant
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.
Adds CLA infrastructure—Apache ICLA-style license grant, GitHub Action enforcement, CODEOWNERS gating for commercially relevant paths—and updates GitHub templates to reflect the Epicenter rebrand.
FINANCIAL_SUSTAINABILITY.md lays out how we hope to become financially sustainable: AGPL stays, we sell commercial licenses to enterprises that can't accept it. Grafana, Bitwarden, MinIO, AppFlowy, and Logseq all use this same model, and every one of them requires a CLA.
CLA infrastructure
The CLA bot comments on first-time PRs with signing instructions. Contributors reply with the signing phrase and they're set—takes about ten seconds. Bots (dependabot, renovate, github-actions) are allowlisted.
Template updates
The GitHub templates were still referencing "Whispering" in places and missing ecosystem-wide components. This PR:
Documentation updates
CONTRIBUTING.md gets a new "Licensing and CLA" section explaining the requirement. FINANCIAL_SUSTAINABILITY.md is updated to reflect that the CLA is now in place (previously it said "we don't need one yet") and acknowledges that all listed comps use CLAs. A new section clarifies AGPL-compatible license options for downstream developers.
Lays groundwork for #792