Skip to content

Profile: no claim that every fork change is one upstream would merge #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
closer-claudio merged 1 commit into from
Oct 18, 2026
Merged

Profile: no claim that every fork change is one upstream would merge #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion profile/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,9 @@ Friendly forks of upstream projects.
When an upstream project we depend on is unmaintained, slow to move, or simply missing
something we need, we fork it here rather than vendoring a patch and forgetting about it.
The fork stays honest about what it is: upstream keeps the credit, the licence stays
upstream's, and every change is one we would happily see merged back.
upstream's, and what differs from upstream is written down, change by change. Not every
change is upstream's to take: some align a fork with our own lint baseline or replace a
library, and those are ours to carry.

**If you can get a fix upstream, do that first.** These forks exist because that was not
possible or not timely — not because we think we own the code.
Expand Down
Loading