2 ms·
This is great, and something we as a community need. I work on CocoaPods the objc dependency manager and we have a strict rule of no-unlicensed code. Meaning fo
by orta 13y ago
This is great, and something we as a community need. I work on CocoaPods the objc dependency manager and we have a strict rule of no-unlicensed code. Meaning for a lot of libraries adding themselves to our toolchain is the first time they've ever had to think of the license.
As this is a github project, I'd definitely like to make it known that it would be really cool to have some integration with the license on github's side on a per-repo basis. Asking people to create a license when creating a public repos at the same time as a README could really help get people thinking about licensing.
- vrdabomb5717 13y agoGithub seems to have done this: https://github.com/blog/1530-choosing-an-open-source-license https://github.com/blog/1530-choosing-an-open-source-license Their new repo page points to choosealicense.com and lets you choose any of the major OSS licenses, though it does show the MIT, GPL3, and Apache ones in bold. I'd definitely like the option to add a license to my repo after creation though, instead of having to manually add a license to the repo and then pushing it. A UI for asking collaborators if it's okay to retroactively open-source their work under a specific license would be useful too.
- orta 13y agoThis is a start to get people more thinking about it!