On 8/31/2021 5:45 AM, Enrico Zini wrote:
Hello,
I would like to be able to license my code with one of the *GPL family
licenses, and to add OSI as an extra entity that can guarantee for what
"or later" might mean in the future.
I'd like something similar to what KDE Foundation is doing:
https:/
On 27.10.21 09:26, Enrico Zini wrote:
On Wed, Sep 08, 2021 at 04:53:09PM +0200, Enrico Zini wrote:
Yes the idea is interesting.
So you avoid giving a "blank check" to the FSF by giving another to OSI...
I assume that both organisations are safe :-)
My intention is actually to avoid giving a b
On 28/10/21 06:21, Enrico Zini wrote:
On Wed, Oct 27, 2021 at 06:15:42PM -0400, Andrew DeMarsh wrote:
> In truth I'm not even really sure where you would send this kind of request
> to the OSI other than maybe it's Legal representative.
Yes, quite. I tried that first, and they told me to write
On Wed, Oct 27, 2021 at 06:15:42PM -0400, Andrew DeMarsh wrote:
> In truth I'm not even really sure where you would send this kind of request
> to the OSI other than maybe it's Legal representative.
Yes, quite. I tried that first, and they told me to write here.
Enrico
--
GPG key: 4096R/634F4
Let me first state that I am merely a bystander and have no standing beyond
mere membership with the OSI or FSF. What you are asking for is a bit
difficult to deliver on for a couple reasons, not the least being that you
are asking on a public mailing list for something only the executive/staff
can
On Wed, Sep 08, 2021 at 04:53:09PM +0200, Enrico Zini wrote:
> > Yes the idea is interesting.
> > So you avoid giving a "blank check" to the FSF by giving another to OSI...
> > I assume that both organisations are safe :-)
>
> My intention is actually to avoid giving a blank check to any
> organi
On Wed, Sep 08, 2021 at 04:27:48PM +0200, Patrice-Emmanuel Schmitz via
License-discuss wrote:
> Yes the idea is interesting.
> So you avoid giving a "blank check" to the FSF by giving another to OSI...
> I assume that both organisations are safe :-)
My intention is actually to avoid giving a bla
Yes the idea is interesting.
So you avoid giving a "blank check" to the FSF by giving another to OSI...
I assume that both organisations are safe :-)
For its EUPL compatibility, the European Commission avoided references to
external entities by specifying:
" later versions of the licence as long as
Hello,
I would like to be able to license my code with one of the *GPL family
licenses, and to add OSI as an extra entity that can guarantee for what
"or later" might mean in the future.
I'd like something similar to what KDE Foundation is doing:
https://community.kde.org/Policies/Licensing_Polic
