Skip to content

I believe this fixes issue 340 by making the period show in the corre… #371

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
pearcej merged 1 commit into from
Jul 24, 2026
Merged

I believe this fixes issue 340 by making the period show in the corre… #371

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
2 changes: 1 addition & 1 deletion source/sec_licensing_existing_communities.ptx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@
Plausible decided to change licenses from the very permissive <url href="https://mit-license.org/" visual="mit-license.org/">MIT License</url> to the <url href="https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-the-agplv3" visual="www.fsf.org/bulletin/2021/fall/the-fundamentals-of-the-agplv3">AGPL license</url>, a GNU copyleft license designed to protect rights when the software is being utilized over a network. Simply stated, the AGPLv3 is basically the GPLv3, but with an additional licensing term that requires that users who interact over a network with modified versions of the program can receive the source code for that program.
</p>
<p>
In their blog, Plausible explained that they made the change their license to protect against corporations that took their code and then used it to create and sell proprietary software that directly competed with their project. They had also been approached by some large corporations that wanted Plausible to help them so they could sell a version of Plausible Analytics to their own clients without wanting to contribute anything back to the Plausible project. For more details, see <url href="https://plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses" visual="plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses">Open source licensing and why we're changing Plausible to the AGPL license</url>.
In their blog, Plausible explained that they made the change their license to protect against corporations that took their code and then used it to create and sell proprietary software that directly competed with their project. They had also been approached by some large corporations that wanted Plausible to help them so they could sell a version of Plausible Analytics to their own clients without wanting to contribute anything back to the Plausible project. For more details, see <url href="https://plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses" visual="plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses">Open source licensing and why we're changing Plausible to the AGPL license. </url>
</p>
<p>
The kind of situation Plausible found themselves in underscores the importance of licensing, and also the importance of the terms of that license.
Expand Down
Loading