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

clarify license #2

Closed
rgerhards opened this issue Jan 28, 2014 · 3 comments

Comments

Projects
None yet
1 participant
@rgerhards
Copy link
Member

commented Jan 28, 2014

select most liberal one, given the restrictions of the existing code

@ghost ghost assigned rgerhards Jan 28, 2014

@rgerhards

This comment has been minimized.

Copy link
Member Author

commented Jan 28, 2014

I have contacted the other authors asking for permission to change the license of the original part of liblogging. One of them, Devin Kowatch, is no longer reachable under the recorded email address. I hope to be able to contact him via some search results. If not, that's becoming a problem because he has done one quite important commit: 46ecb98

@rgerhards

This comment has been minimized.

Copy link
Member Author

commented Jan 28, 2014

If this is legally OK:

ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change

we could probably do a similar thing. However, I am a bit hesitant, as the other contributors are also affected, and IMHO this would require their agreement. Obviously, this wasn't the case with BSD either...

@rgerhards

This comment has been minimized.

Copy link
Member Author

commented Feb 3, 2014

I got permission to change the original liblogging license to 2-clause BSD via mail. So this now can be done (and needs to be done ;)).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.