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

License #1

Closed
fniekiel opened this issue Nov 22, 2016 · 7 comments
Closed

License #1

fniekiel opened this issue Nov 22, 2016 · 7 comments

Comments

@fniekiel
Copy link
Collaborator

Need to figure out, which license we put this under!

@ercius
Copy link
Owner

ercius commented Nov 22, 2016

Yes definitely. Anyone have a preference or experience with this?

On Mon, Nov 21, 2016, 4:29 PM fniekiel notifications@github.com wrote:

Need to figure out, which license we put this under!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AO7olBgLc4HZNjXZLNCDhsHzS8Piud4Qks5rAjeCgaJpZM4K43nl
.

@tcpekin
Copy link
Collaborator

tcpekin commented Nov 22, 2016

I've seen a lot of projects use one of the GPL licenses. After looking into it a bit, it seems like it's about as open as one can get. Derivatives, even ones that are commercialized, have to be published under the same license and completely open (copyleft is the term apparently). This is also what hyperspy uses (GPL v.3).

@fniekiel
Copy link
Collaborator Author

GNU LGPLv3

@fniekiel fniekiel reopened this Nov 24, 2016
@fniekiel
Copy link
Collaborator Author

Sorry for bringing this up once more.

Turned out that the PySide issue inhibits me from using the GUI tools on any other machine, than that funny broken ubuntu one where you can have the unsupported case of PySide running with python3.5.

The easiest way would be to migrate over to PyQt4, which I just tested. Almost no code changes, BUT it would imply that we have to move to the GPLv3 instead of the LGPLv3 license.

Would this be ok with you?

@tcpekin
Copy link
Collaborator

tcpekin commented Nov 24, 2016 via email

@ercius
Copy link
Owner

ercius commented Nov 25, 2016 via email

@fniekiel
Copy link
Collaborator Author

After talking to Colin, GPLv3 it is.

ercius pushed a commit that referenced this issue Dec 21, 2017
Correction on bug for on_memory read: fid.tell() method was not wrapped
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