Skip to content

docs: state the contributor-license policy (issues yes, code no) - #70

Merged
tsyma merged 2 commits into
mainfrom
docs/contributor-policy
Sep 13, 2026
Merged

tsyma merged 2 commits into
mainfrom
docs/contributor-policy

Conversation

@AliceLafox

@AliceLafox AliceLafox commented Sep 13, 2026

Copy link
Copy Markdown
Member

This repo had no contributor-license policy, so the default inbound = outbound applied: a single merged outside patch would leave its author holding copyright on those lines permanently, and the project could never change its own licensing terms again — dual-licensing, granting an exception, or shipping the code inside something else — without tracking every past contributor down.

Adopts the policy already in force in felitronics-core: issues and ideas welcome and credited, code PRs closed unmerged, reasoning stated in the file. No code, build or licence change.

The repo had no contributor-license policy, so the default inbound = outbound
applied: a merged outside patch would leave its author holding copyright on
those lines, and the project could never change its own licensing terms again
without tracking every past contributor down. This mirrors the policy already
in force in felitronics-core.
@AliceLafox
AliceLafox force-pushed the docs/contributor-policy branch from 91540c9 to 8b3fb63 Compare September 13, 2026 18:32
…xist

The policy sends a would-be contributor to an issue without saying what to put in
it; a pasted patch carries the same copyright question in through the side door.
And third-party dependencies were said to be recorded "with the project's
notices" — this repo fetches minimp3 and nlohmann/json but keeps no such file, so
the sentence promised a record that is not there.
@tsyma
tsyma merged commit 8e5e6ec into main Sep 13, 2026
10 checks passed
@tsyma
tsyma deleted the docs/contributor-policy branch September 13, 2026 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants