I could make a PR, but I'm not sure how that should be conveyed best. I would probably change it from "Open Source and PRO version" to "Non-free Community Edition and Paid PRO version".
Originally created by @TechnologyClassroom on GitHub (Feb 10, 2023).
Original GitHub issue: https://github.com/ligurio/awesome-ci/issues/132
The community edition's [LICENSE](https://github.com/marcinguy/betterscan-ce/blob/master/LICENSE) has the commons clause which is non-commercial. The 1st statement of OSI's open source definition [says that non-commercial restrictions are not open source](https://opensource.org/osd#free-redistribution).
I could make a PR, but I'm not sure how that should be conveyed best. I would probably change it from "Open Source and PRO version" to "Non-free Community Edition and Paid PRO version".
Hi! Thanks for highlighting this! I'm ok to just update a license. Could you make a PR for that?
<!-- gh-comment-id:1426208680 -->
@ligurio commented on GitHub (Feb 10, 2023):
Hi! Thanks for highlighting this! I'm ok to just update a license. Could you make a PR for that?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @TechnologyClassroom on GitHub (Feb 10, 2023).
Original GitHub issue: https://github.com/ligurio/awesome-ci/issues/132
The community edition's LICENSE has the commons clause which is non-commercial. The 1st statement of OSI's open source definition says that non-commercial restrictions are not open source.
I could make a PR, but I'm not sure how that should be conveyed best. I would probably change it from "Open Source and PRO version" to "Non-free Community Edition and Paid PRO version".
@ligurio commented on GitHub (Feb 10, 2023):
Hi! Thanks for highlighting this! I'm ok to just update a license. Could you make a PR for that?