docs(readme): the first supporter, and the attribution the site already promised - #535
Merged
Conversation
…dy promised libredb.org/supporters states the commitment in its own words - "The same entry in the repository: the README carries it too, so the attribution survives someone reading the project on GitHub and never opening this site" - and until now there was nothing to carry, so the README had no place to put one. Tailscale granted the Community on GitHub plan on 2026-09-01, which makes that promise due. Kept separate from `## Sponsors` on purpose. That block sits between sponsors-start/sponsors-end markers that update-sponsors.yml rewrites from GitHub Sponsors, so an entry placed there would be erased by the next bot run and would also conflate two different things: individuals donating, versus a programme covering a specific running cost. The section states what it is not, because the supporters page does: placement is not for sale and naming a company is not that company endorsing this project.
|
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.
What
Adds a
## Supporterssection to the README with its first entry: Tailscale, which granted the Community on GitHub plan to thelibredborganization on 2026-09-01 (support ticket TSS-100364, confirmed in the admin console: plan "GitHub Community plan", next invoice 2027-09-01, $0.00).Why this is a debt, not a marketing addition
libredb.org/supporterspublishes what a supporter is promised, and one of the four promises is stated in these words:That page is cited on the application forms so a reviewer can hold the page against the form. Until now the promise had never come due, because no programme had accepted the project. One has, so the README owes the entry the same day the site got it.
Why not inside
## SponsorsThat block sits between
<!-- sponsors-start -->/<!-- sponsors-end -->, which.github/workflows/update-sponsors.ymlrewrites from GitHub Sponsors. An entry placed there would be erased by the next bot run, and it would conflate individual donations with a programme covering a specific running cost. The new section says which of the two it is.Verification
bun run readme:check— OK, 16 engines and the install commands still matchREADME_zh.md/README_ja.md. The guard covers engine names and install commands, so an English-only section is legal abridgement and needs no translation.format·lint·typecheck·knip·build— all clean.bun run test— 10474 pass, 1 fail. The failure isbacklog-structure.test.ts > every cited entry exists, and it is local-only and pre-existing: all five dangling citations are insidedocs/superpowers/, which is gitignored and therefore invisible to CI. Reproduced on a cleanorigin/maintree with this change stashed, so it is not from this PR.Documentation only. No executable lines added, so the coverage gate is unaffected.