Yes that is a common problem. I could see GitHub creating tools to help you select a license and inform you how to use it properly, as well as having systems that show you how the license affects your project.
It's not under the github.com domain, but they did create it. IIRC they link to it somewhere when you go to create a new repo, along with a drop down to select what license you want (Assuming you're not just pushing an already created repo).
I don't think Microsoft/GitHub would have any issue with doing a wizard-y license picker/builder (well, boiler plate existing licenses with fill in the blank for attribution, project name, and the like). They did add that little table at the top of LICENSE pages that checks off what rights and responsibilities the consumer has under the license so it seems they're fans of making the various licenses understandable.
I think it is a good request though. I'm fond of MIT, but with the right wizard, I may also find that GPL or something else may be a better fit for what I'm working on.
DSMan195276|6 years ago
It's not under the github.com domain, but they did create it. IIRC they link to it somewhere when you go to create a new repo, along with a drop down to select what license you want (Assuming you're not just pushing an already created repo).
jsgo|6 years ago
I think it is a good request though. I'm fond of MIT, but with the right wizard, I may also find that GPL or something else may be a better fit for what I'm working on.