Open diamondap opened 12 years ago
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: https://github.com/rnewman/clj-apache-http/issues/8
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 < reply@reply.github.com>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: https://github.com/rnewman/clj-apache-http/issues/8
Reply to this email directly or view it on GitHub: https://github.com/rnewman/clj-apache-http/issues/8#issuecomment-1667237
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