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

Re-license under BSD? #5

Open
olebole opened this issue Nov 1, 2019 · 5 comments
Open

Re-license under BSD? #5

olebole opened this issue Nov 1, 2019 · 5 comments

Comments

@olebole
Copy link

olebole commented Nov 1, 2019

Hi,

I found jsofa in use of the upcoming CDS Aladin version, which I intend to package for Debian (the old version is already there). I am however a bit in worry about the license, since its restrictions (rename the prefix in case of changes) are difficult for our Debian Free Software Guidelines.

The astropy community solved this by changing the name to "erfa" and then applying (with permission of IAU) a BSD license; see their repository https://github.com/liberfa/erfa.

Maybe the same could be done for jsofa? This would ease packaging for us (and other distributions that are picky with licenses) a lot.

Thanks!

@pahjbo
Copy link
Member

pahjbo commented Nov 4, 2019

I have no objection in principle to doing this - I think that I have already complied with the restrictions on copies of SOFA - i.e changing the name and prefix (though perhaps more minimally than ERFA!)

My unease/uncertainly is whether I can just change the license again for jsofa as it has already been released - surely it makes a mockery of licensing if this is possible?

@olebole
Copy link
Author

olebole commented Nov 4, 2019

I think relicensing is not the problem; at least you could create a new version for it.
More important would be to ask IAU for permission (since they hold the copyright).
Cc to @eteq who went through this for ERFA -- could you share the experiences here?

@olebole
Copy link
Author

olebole commented May 4, 2020

@pahjbo would you mind if I contact the people at IAU to check about a license change similar to ERFA, or whether your name change (iau --> jau) is not considered a "trivial" modification according to their license?

[…]
c) The names of all routines in your derived work shall not include the prefix "iau" or "sofa" or trivial modifications thereof such as changes of case.

@pahjbo
Copy link
Member

pahjbo commented May 5, 2020

@pahjbo would you mind if I contact the people at IAU to check about a license change similar to ERFA, or whether your name change (iau --> jau) is not considered a "trivial" modification according to their license?

[…]
c) The names of all routines in your derived work shall not include the prefix "iau" or "sofa" or trivial modifications thereof such as changes of case.

sorry, I had rather forgotten about this - I do not mind if you want to try contact them - As for the prefix, I had that approved when I originally made the translation - the real idea behind that clause is that there is no linkage ambiguity, and clearly even my small change is sufficient for that.

@olebole
Copy link
Author

olebole commented May 5, 2020

If they approved it, there is no need to contact them. I then just can refer to this issue. Thank you for the explanation.

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

2 participants