Blog/firecms open source #681
Merged
Conversation
This file contains 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
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.
This pull request includes updates to the licensing information in the
README.mdfile and a new blog post detailing FireCMS's commitment to open source. The most important changes are:Updates to licensing information:
README.md: Updated the license section to specify that the core of FireCMS is licensed under the MIT license, while some packages used in FireCMS Pro and Cloud are licensed under the Business Source License 1.1 (BSL).New blog post:
website/blog/2024-12-04-firecms_open_source.md: Added a new blog post titled "FireCMS, Our Commitment to Open Source" by Marian Moldovan, which discusses the different versions of FireCMS (Community, Cloud, Pro), their respective licenses, and the company's dedication to open source.