pālana

The license, plainly

pālana is licensed under the GPL-3.0. This page says what that means in practice, in the order the questions come up.

What you can do without asking#

Use pālana for anything. Read every line of the source. Build it yourself — swift build and go. Modify it. Fork it. Redistribute it, including any signed build, as long as the source travels with it under the same license. None of this requires permission; that is what the license is.

No CLA, ever#

Contributions are accepted under GPL-3.0 and contributors keep their copyright. There is no contributor license agreement and there never will be one. The consequence is deliberate: once outside contributions are in the code, nobody—including the author—can relicense pālana closed. Your patches lock it open.

The code is free. The name identifies the author's builds.#

Forks are welcome and must travel under their own name. "pālana" and the leaf mark identify builds signed, notarized, and released by the author—that signature chain is the one thing a fork cannot carry, and the name is how you know which builds carry it.

The beta is free. At 1.0, signed builds become a one-time $29 purchase—no subscription, no license key, all 1.x updates included—and the license does not change: the code stays GPL-3.0, building it yourself stays free, and the purchase pays for the signing certificate, the notarization, and the time. The GPL explicitly permits selling copies—what it forbids is closing the source, and that door is welded shut above.

The beta deal#

File a real issue during the v0.x beta—a bug, a refusal on a host pālana hasn't met, a plan that said something untrue—and your 1.0 license is free. "Real" means reproducible or informative, not a typo report; judged by the author, generously.

If you redistribute#

Keep the license, keep the notices, and provide the source—a link to the repo at the matching version satisfies it. The full text governs where this page simplifies.