choosealicense.com
choosealicense.com copied to clipboard
github
A site to provide non-judgmental guidance on choosing a license for your open source project
Feedback received: choosealicense.com is fine for clear-cut situations, but hard to understand implications if chooser wants to do something else later. Examples given: - make a proprietary version - offer...
As GitHub obviously encourages, some projects will include code from other projects. What is the best thing to do in that situation? Should the originator's copyright info in their license...
As noted in #462 our license texts don't all match precisely the texts their `source:` fields point to. I'd like to fix that eventually, probably by treating license texts curated...
When trying to open a license pull request on projects that I don’t own, I have encountered the following error. > You’re making changes in a project you don’t have...
The problem with Open Software License 3.0 license document is that it does not explain important terminologies, so one has to also refer to[ Lawrence Rosen's website](https://rosenlaw.com/OSL3.0-explained.htm) to fully understand...
https://geth.ethereum.org/docs/install-and-build/installing-geth
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/67bca857eedf99bf44a4b6a0fc5b5ed553135316/contracts/access/Roles.sol
Commits to this repository have been made in 2024, but present copyright date range ends at 2023. This PR updates the date range to include the current year. Should the...
First of all I really want to apologize for all of those commits with horrific messages, but I needed them to run the GitHub-Actions. The deployment to GitHub Pages now...
