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

Add proprietary-license URL type? #107

Closed
jbicha opened this issue Mar 17, 2017 · 5 comments
Closed

Add proprietary-license URL type? #107

jbicha opened this issue Mar 17, 2017 · 5 comments
Assignees

Comments

@jbicha
Copy link
Contributor

jbicha commented Mar 17, 2017

I wrote an appstream file for Steam. I added <project_license>LicenseRef-proprietary</project_license> but I'd like to point to the actual license too.

What do you think about adding a proprietary-license URL type? GNOME Software could then use that URL to override the default License Proprietary > More information popup link.

On the other hand, it doesn't have to be a URL if there was a way I could include the license text directly.

@hughsie
Copy link
Collaborator

hughsie commented Mar 17, 2017

I think the idea here was to use LicenseRef-free=http://some-url.com -- does that work in gnome-software?

@jbicha
Copy link
Contributor Author

jbicha commented Mar 17, 2017

Ok, I see that should work for Free Software, but what about Proprietary Software?

The GNOME Software solution is nice, but maybe this should really be done officially in appstream itself.

If there's enough of a demand for custom Free licenses, then maybe my proposed URL type could be custom-license with a note in the documentation that it's strongly discouraged for Free Software to use custom licenses.

@hughsie
Copy link
Collaborator

hughsie commented Mar 17, 2017

I think providing yet another way to specify a license is going to make it confusing for free software. I'd certainly accept a patch to add support for LicenseRef-Proprietary= making the URL a hyperlink in GNOME Software.

@ximion
Copy link
Owner

ximion commented Mar 17, 2017

@hughsie Looks like SPDX doesn't have an explicit solution for this... But LicenseRef-Proprietary= would make sense to me.

Including the license text directly or having some kind of directive to include an external COPYING file into the data is opening a whole new can of worms, which I would like to avoid at least for now.

@cassidyjames
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants