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 LICENSE #1

Closed
serisman opened this issue Jul 13, 2020 · 9 comments
Closed

Add LICENSE #1

serisman opened this issue Jul 13, 2020 · 9 comments
Assignees

Comments

@serisman
Copy link
Collaborator

This repo need a clearly identified LICENSE so people know what can and cannot be done with it.

@freepdk, my preference for this is MIT, but these files have their roots from easy-pdk-programmer-software which is GPL v3. Are you ok with (re-)licensing these include files as MIT, or should we keep this one as GPL v3?

@spth
Copy link

spth commented Jul 13, 2020

SDCC uses GPL2+LE (i.e, GPL 2 or later with liking exception) for its library.
Whatever is chosen should be compatible with that, at least for the part that is supposed to go into SDCC later.

@serisman
Copy link
Collaborator Author

SDCC uses GPL2+LE (i.e, GPL 2 or later with liking exception) for its library.
Whatever is chosen should be compatible with that, at least for the part that is supposed to go into SDCC later.

This repo is the programmer specific include files (i.e. calibration routines) and is not currently intended to be included with SDCC. But, your comment would apply to the pdk-includes repo: free-pdk/pdk-includes#5

@serisman serisman self-assigned this Jul 13, 2020
@serisman
Copy link
Collaborator Author

Pull Request adding Copyright and LICENSE information: #2

@freepdk
Copy link

freepdk commented Jul 13, 2020

I'm not sure if the old LGPL is the right choice for headers which are included in a linked program.

I think GPL + LinkException is a better choice for this.

@serisman
Copy link
Collaborator Author

serisman commented Jul 13, 2020

I'm not sure if the old LGPL is the right choice for headers which are included in a linked program.

I think GPL + LinkException is a better choice for this.

Do you have a link that shows that as being a real thing?

I couldn't find it on http://www.gnu.org/licenses, and it isn't directly listed on their exceptions page either: https://www.gnu.org/licenses/exceptions.html

GitHub doesn't know about it: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository

SPDX doesn't directly list it (unless it is one of the deprecated ones): https://spdx.org/licenses/

Wikipedia isn't really all that clear, although they do list LGPL as being related: https://en.wikipedia.org/wiki/GPL_linking_exception

Or, do we just list this as GPL 2.0 and include our own exception text (similar to what SDCC uses)? That feels a bit dirty to not use an 'official' license, but maybe it is ok?

@freepdk
Copy link

freepdk commented Jul 13, 2020

https://en.wikipedia.org/wiki/GPL_linking_exception

In SDCC I only found this:
https://sourceforge.net/p/sdcc/code/HEAD/tree/trunk/sdcc/doc/README.txt
https://sourceforge.net/p/sdcc/code/HEAD/tree/trunk/sdcc/COPYING

=> we need to ask @spth

Linking Excpetion:
You might put the repo under GPL LICENSE and then add a "LICENSE-ADDITIONAL" containing the linking exception.

@freepdk
Copy link

freepdk commented Jul 13, 2020

Or, do we just list this as GPL 2.0 and include our own exception text (similar to what SDCC uses)? That feels a bit dirty to not use an 'official' license, but maybe it is ok?

But you use an official license. You just add an additional exception.

@serisman
Copy link
Collaborator Author

Ok, here is a different PR with GPL v2 with Linking Exception: #3

@serisman
Copy link
Collaborator Author

Copyright and LICENSE information was merged via pull request #3

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

No branches or pull requests

3 participants