From 7a6484fffaf2b1a728dc0780ead4ac73fdb06afe Mon Sep 17 00:00:00 2001 From: cevheri Date: Tue, 1 Sep 2026 01:06:07 +0300 Subject: [PATCH] docs(readme): the first supporter, and the attribution the site already 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. --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index e1cea8eb..46d768b1 100644 --- a/README.md +++ b/README.md @@ -937,6 +937,21 @@ _Be the first to sponsor libredb-studio!_ --- +## Supporters + +Distinct from the sponsors above: these are open-source programmes that cover a +running cost of the project. A place here cannot be bought, and nothing here is +an endorsement of libredb-studio by the company named. The full list, what each +one covers and what attribution is owed in return are at +[libredb.org/supporters](https://libredb.org/supporters/). + +- **[Tailscale](https://tailscale.com/opensource)** — the Community on GitHub + plan behind the private network maintainers use to reach the database probe + hosts, so testing against real engines does not mean exposing database ports + to the internet. Since 2026-09-01. + +--- + ## Contributing We welcome contributions from the community! Whether it's a bug fix, a new feature, or documentation improvements: