-
Notifications
You must be signed in to change notification settings - Fork 101
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
Make licenses displayed in sensible order in interactive mode #90
Comments
I think alphabetical is the way to go. Ideally, the menu can start on MIT but that depends on JuliaLang/julia#30043. |
Could we have MIT twice? Once at the top, and once alphabtrically? |
Definitely I think we should strongly encourage MIT as the license choice. |
#61 sorts licenses alphabetically and pre-selects MIT, so that should solve this. |
I am hesitant on pushing for a particular license, but if we were, I think ISC would be a better candidate these days than MIT Expat (both being in the MIT family). It would also be nice to have the licenses support a language option. For example, for EUPL-2 (https://joinup.ec.europa.eu/collection/eupl/eupl-text-11-12). |
I think the MIT expat license is the best option because it is the license used by (most components of) the Julia language itself |
I do like the language option idea, that would be easy to implement but just tedious to go find licenses in various languages. |
For the language formats, I think it might depends on the licenses, but would be cool for some communities that are not English-only (e.g., Europe, Asia, Latin America). As for the MIT Expat/ISC... They are both MIT family so there is no difference at all in the terms. I don't see any reason as for why current most common text flavor would be an argument. The only difference is in the flavor of the text (e.g., using the OSI approved text, the Expat flavor, the Choosealicense flavor, or ISC text with now redundant text removed). For instance, Julia is MIT licensed, but doesn't use the MIT Expat flavor text which most of the community uses and the difference has zero consequence. |
Right now they show up in an arbitary order as we keep them in a
Dict
I this is clearly not the right order.
There is some bikeshedding to be done on the correct order.
(Alphabetical, vs Most commonly used, vs Most/Least restrictive)
but clearly we do not want this order.
The text was updated successfully, but these errors were encountered: