-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPL 1.0 not appearing in license lists #449
Comments
The license is at http://choosealicense.com/licenses/epl-1.0/ The license selection drop-down on GitHub eventually (via benbalter/licensee, which vendors github/choosealicense.com) is informed by changes here. The change you noticed is due to #386 See #413 and #427 for similar discussion. I can't promise anything but I'll pass along the desire of people who already know what license they want to have that license available in the license selection UI somehow. Thanks for the feedback! I'm closing this now as I don't think think there's anything to do for this project, but feel free to continue conversation if you have further questions. |
BTW @waynebeaton since I see that you're on the Eclipse Foundation staff, I look forward to adding the next version of the EPL when it is eventually done; made me check the mailing list. Also very nice to see the new contributor agreement utilizing the DCO! |
I cannot figure out how to even navigate to the EPL page on the site. Am I just not seeing it? Is there an actual link on the site? The notion expressed in #386 that the EPL isn't a license that "anyone should choose unless they already know about them because they're in the relevant communities" is incorrect. I just did a quick search to compare hits of the EPL vs the AL and while there are certainly more hits against AL, the numbers are in the same order of magnitude. Lots of people who aren't building Eclipse plug-ins select the Eclipse Public License. How do we appeal this decision? |
Eclipse and Clojure are pretty big communities, so I'm not surprised that EPL gets lots of hits. Why should someone who is just learning about open source licenses and not in one of those communities (and maybe others I don't know about) learn about EPL? It isn't linked prominently but can be gotten to at http://choosealicense.com/appendix/ which is linked from the top of http://choosealicense.com/licenses/ and http://choosealicense.com/about/ Also see just added #413 (comment) we're considering how to make more licenses accessible from the drop-down. |
- document criteria for whether a license is hidden - needed for license spectrum on /licenses OR - on 'popular' list at https://opensource.org/licenses (some other list could be used in the future) - adjust license properties and tests accordingly This gets non-hidden list back close to what it was before #386 and (pending licensee vendoring this change, licensee release, and github.com licensee dependency version bump) some commonly requested licenses (eg #413 #449) will reappear in the github.com license drop-down.
I swear that the EPL used to be an option in the license selection drop-down for a new GitHub repository, but it's not showing up anymore.
AFAICT, the license file meets the criteria outlined on the CONTRIBUTING page.
I don't see how the list of licenses is being fed to GitHub. What do I need to do to make this happen?
The text was updated successfully, but these errors were encountered: