I agree to this exception.

El mar, 5 jul 2022 a la(s) 03:35, Oswald Buddenhagen (
oswald.buddenha...@gmx.de) escribió:

> moin jesse,
>
> you're receiving this mail because you contributed to the isync project
> (https://isync.sourceforge.io/) a while ago.
>
> please see the two enclosed mails, and reply directly to the second one
> on-list (no need to subscribe; i'll approve your mail).
>
> thanks
>
>
>
> ---------- Forwarded message ----------
> From: Oswald Buddenhagen <oswald.buddenha...@gmx.de>
> To: isync-devel@lists.sourceforge.net
> Cc:
> Bcc:
> Date: Sun, 26 Jun 2022 14:07:01 +0200
> Subject: isync GPL incompatibility due to Cyrus SASL
> moin,
>
> debian bug #1012636 has brought to my attention that the SASL support
> introduced in isync v1.2 (commit eb100515) makes isync binaries built
> with it not legally distributable (unless SASL is a system library).
>
> to address this issue, i intend to generalize the GPL exception as per
> the attached patch.
>
> i just updated the AUTHORS file to accurately reflect the copyright
> holders and other contributors, as can be determined from the CVS/git
> history. every contributor is invited to verify their classification.
>
> ideally, every copyright holder will reply to this message on-list to
> express their agreement to the license change. in a while, i'll send out
> individual mails for missing confirmations.
>
> because
> - isync already contains an exception for OpenSSL,
> - every contributor implicitly agreed to that exception, and
> - that exception exists specifically because of the advertising clause
>    in OpenSSL < v3's license,
> i'm assuming that everyone will be fine with the proposed change.
> i'll rely on that assumption in case some copyright holder(s) cannot be
> reached.
>
> thanks
> _______________________________________________
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
>
>
> ---------- Forwarded message ----------
> From: Oswald Buddenhagen <oswald.buddenha...@gmx.de>
> To: isync-devel@lists.sourceforge.net
> Cc:
> Bcc:
> Date: Mon, 27 Jun 2022 11:51:01 +0200
> Subject: Re: isync GPL incompatibility due to Cyrus SASL
> On Sun, Jun 26, 2022 at 02:07:01PM +0200, Oswald Buddenhagen wrote:
> >to address this issue, i intend to generalize the GPL exception as per
> >the attached patch.
> >
> >>As a special exception, mbsync may be linked with libraries whose
> >>license contains advertising clauses.
> >
> come to think of it, this is ambiguous and may be used to completely
> subvert the gpl. let's try this instead:
>
> As a special exception, mbsync may be linked with libraries with a more
> restrictive license if the only incompatibility are advertising clauses.
>
>
> _______________________________________________
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>


-- 
Jesse Weaver
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Reply via email to