Agreement with ICQ

[Paul Aurich]

And Evan Schoenberg, M.D. spoke on 05/21/2011 07:13 AM, saying:
> 
> On May 21, 2011, at 9:05 AM, Ivan Komarov wrote:
> 
>>> Agreed. I don't think _any_ of these limitations can be imposed on
>>> Pidgin/libpurple.
>>
>> Good point. I expressed our concerns to them (for the record, by
>> "them" I mean Andrey Krylov, ICQ Marketing Manager in Russia:
>> http://ru.linkedin.com/pub/andrey-krylov/31/937/2b8). They agree these
>> limitations are impossible to impose on an open-source product, but
>> this is the standard agreement which can't be changed. On the other
>> hand, Andrey said the agreement is a pure formality and they don't
>> really care about whether we satisfy these provisions or not. He
>> confirmed we don't have to change *any* code in libpurple/Pidgin, all
>> we have to do is sign the agreement.
> 
> 
> That's not how contact work.  You don't sign an agreement, the provisions of which are unacceptable, based on a verbal agreement that the "contact is just a formality; it's okay if you violate it."
> 
> Under no circumstance should this agreement be signed.  If they don't care about whether we satisfy these provisions or not, they should provide us with a new contract themselves, or we should mark out the unacceptable provisions, initial the changes, and send it back to them for review.
> 
> -Evan

+1.

One thing I've not seen discussed, but that Kevin reminded me of: did the
agreement signed with AOL cover ICQ as well?

~Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20110522/e8ac003a/attachment.sig>