Skip to content
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

Better license shields #1093

Closed
KOLANICH opened this issue Sep 25, 2017 · 9 comments
Closed

Better license shields #1093

KOLANICH opened this issue Sep 25, 2017 · 9 comments
Labels
service-badge Accepted and actionable changes, features, and bugs

Comments

@KOLANICH
Copy link

KOLANICH commented Sep 25, 2017

1 Open https://tldrlegal.com/license/apache-license-2.0-(apache-2.0) .
Look at the page.
You see 3 columns of different colors. Each column has clauses describing license in short, each clause has own pictogram.
2 GitHub has an API returning the similar information.

So, how should the license shield look like?
0 Background color:

  • red for proprietary or missing (which makes the work automatically proprietary)
  • orange for unrecognized (the license doesn't look like proprietary, but it is not in the database)
  • yellow for viral (aka copyleft, like GPL and MPL)
  • cyan for permissive (Apache, MIT, BSD)
  • bright green for public-domain like (Unlicense, CC-0, WTFPL)
    1 a logo: License logos #1219
    2 a SPDX identifier
    3 areas of pictograms, each area has own background color, and contains pictogramms matching the corresponding column of tldrlegal. Of course you'll have to find own source of icons since tldrlegal's ones are copyrighted and not in svg.
@paulmelnikow
Copy link
Member

I like the idea of colors! Probably I would make the unrecognized license either gray, which we usually use for unknown, or red, since some rando license is not so safe, and might even be proprietary.

@KOLANICH
Copy link
Author

KOLANICH commented Sep 26, 2017

unrecognized license may be proprietary, but it is probably not proprietary, since it is not detected as proprietary (proprietary licenses have some special wording and lack other wording specific for free software/culture licenses, so this heuristics can be used to detect explicitly proprietary licenses not in the DB) , so orange

@paulmelnikow paulmelnikow added the service-badge Accepted and actionable changes, features, and bugs label Oct 2, 2017
@ritwickdey
Copy link
Contributor

I like the idea too 👍 . I think we have to sort the all licence -- but is it not huge? -- I don't know.

@KOLANICH
Copy link
Author

KOLANICH commented Oct 7, 2017

sort all the license

tldrlegal and github have done the work for us. We only need to get the data through API and draw a shield

@ritwickdey
Copy link
Contributor

from github, i can find only these -

  "agpl-3.0",
  "lgpl-3.0",
  "bsd-2-clause",
  "epl-1.0",
  "bsd-3-clause",
  "gpl-2.0",
  "mpl-2.0",
  "mit",
  "gpl-3.0",
  "lgpl-2.1",
  "unlicense",
  "apache-2.0"

@platan
Copy link
Member

platan commented Oct 20, 2017

I will implement this improvement.

@paulmelnikow
Copy link
Member

Addressed in #1190! Though perhaps we should leave this open until we apply these changes to the rest of the license badges.

@KOLANICH
Copy link
Author

The rest of thingsm like icons for clauses are still not implemented.

@paulmelnikow
Copy link
Member

There's been some discussion of license colors in #2026 so let's finish that discussion there.

By default, we don't show icons on badges; that's something users can opt into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

4 participants