good morning;
i have released a library, de.setf.amqp[1], which incorporates work of yours. the combined license is the gnu affero. please see the readme[2] for more information. this is to verify the contact information for your library's license. yours is the last respective contact. in some cases, there was none and i have substituted a mailing list as an immediate place-holder, even though, as subscription-only lists, it is not well suited to this purpose. please advise me, should an alternative contact be available.
[1] : http://github.com/lisp/de.setf.amqp [2] : http://github.com/lisp/de.setf.amqp/blob/master/README.md
Hi,
In principle, what I see is fine, but I have two things:
+ Please use http://p-cos.net as a reference for Closer to MOP, not my email address.
+ Your wording states the following: "The required components are included as per the respective licenses and covered, in this combined form, under the GAL as well."
What does this mean? Does this mean that if somebody wants to use de.setf.amqp, that they cannot make 'secret' modifications of Closer to MOP anymore, even if they are unrelated to the functionality of de.setf.amqp? If that's the case, I don't find this acceptable and would ask you to reword this sentence.
Thanks, Pascal
On 15 Feb 2010, at 13:44, james anderson wrote:
good morning;
i have released a library, de.setf.amqp[1], which incorporates work of yours. the combined license is the gnu affero. please see the readme[2] for more information. this is to verify the contact information for your library's license. yours is the last respective contact. in some cases, there was none and i have substituted a mailing list as an immediate place-holder, even though, as subscription-only lists, it is not well suited to this purpose. please advise me, should an alternative contact be available.
[1] : http://github.com/lisp/de.setf.amqp [2] : http://github.com/lisp/de.setf.amqp/blob/master/README.md
Dear James,
As the usocket library is available under the MIT license, you're basically free to do with it what you want. You can use the mailing list address on common-lisp.net because I expect it to be more of a constant than anything else.
Maintainers change; e-mail addresses even more often.
It's not the answer you're looking for, but, well, with this license, you may just not need a contact address other than the current one...
Bye,
Erik.
On Mon, Feb 15, 2010 at 1:44 PM, james anderson james.anderson@setf.de wrote:
good morning;
i have released a library, de.setf.amqp[1], which incorporates work of yours. the combined license is the gnu affero. please see the readme[2] for more information. this is to verify the contact information for your library's license. yours is the last respective contact. in some cases, there was none and i have substituted a mailing list as an immediate place-holder, even though, as subscription-only lists, it is not well suited to this purpose. please advise me, should an alternative contact be available.
[1] : http://github.com/lisp/de.setf.amqp [2] : http://github.com/lisp/de.setf.amqp/blob/master/README.md
usocket-devel mailing list usocket-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel
-
Erik Huelsmann -
james anderson -
Pascal Costanza