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? #8

Open
diamondap opened this issue Jul 27, 2011 · 2 comments
Open

License? #8

diamondap opened this issue Jul 27, 2011 · 2 comments

Comments

@diamondap
Copy link

I forked your clj-apache-http library ( https://github.com/diamondap/clj-apache-http ) and I've gotten inquiries about what license the library is under. Since I forked from you, I can't very well attach a license to it without knowing what license, if any, you're using.

Can you help? Does wrapping the Apache code automatically put it under the Apache license?

By the way, I added support for client certificates and the new Apache async http client. If you want to pull in the changes I added, please do.

--Andrew

@rnewman
Copy link
Owner

rnewman commented Jul 27, 2011

BSD is fine by me; if you'd prefer something else, I'm flexible. There's no compile-time dependency on the Apache code, AFAIK, so the Apache license shouldn't apply, but IANAL.

Will happily pull in changes when I get a few free hours -- been stupidly busy for months :/

Thanks for checking in.

On 27 Jul 2011, at 12:24 PM, diamondap wrote:

I forked your clj-apache-http library ( https://github.com/diamondap/clj-apache-http ) and I've gotten inquiries about what license the library is under. Since I forked from you, I can't very well attach a license to it without knowing what license, if any, you're using.

Can you help? Does wrapping the Apache code automatically put it under the Apache license?

By the way, I added support for client certificates and the new Apache async http client. If you want to pull in the changes I added, please do.

--Andrew

Reply to this email directly or view it on GitHub:
#8

@diamondap
Copy link
Author

Thanks for taking the time to respond.

I like the BSD license, so if you want to go with that, please do.

I understand about being busy!

--Andrew

On Wed, Jul 27, 2011 at 4:24 PM, rnewman <
[email protected]>wrote:

BSD is fine by me; if you'd prefer something else, I'm flexible. There's no
compile-time dependency on the Apache code, AFAIK, so the Apache license
shouldn't apply, but IANAL.

Will happily pull in changes when I get a few free hours -- been stupidly
busy for months :/

Thanks for checking in.

On 27 Jul 2011, at 12:24 PM, diamondap wrote:

I forked your clj-apache-http library (
https://github.com/diamondap/clj-apache-http ) and I've gotten inquiries
about what license the library is under. Since I forked from you, I can't
very well attach a license to it without knowing what license, if any,
you're using.

Can you help? Does wrapping the Apache code automatically put it under
the Apache license?

By the way, I added support for client certificates and the new Apache
async http client. If you want to pull in the changes I added, please do.

--Andrew

Reply to this email directly or view it on GitHub:
#8

Reply to this email directly or view it on GitHub:
#8 (comment)

@S11001001 S11001001 mentioned this issue Jul 3, 2013
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