[okfn-discuss] GNU GPL non-conformant with Open Definition?

[Aaron Wolf]

Yes, commits and such were done on the (non-Open!) Github website:
https://github.com/okfn/opendefinition/

And the (Open!) mailman discussion list:
https://lists.okfn.org/pipermail/od-discuss/ the thread you want is:
https://lists.okfn.org/pipermail/od-discuss/2014-July/000905.html
There, Herb asks "why these new clauses" and the answer "we're not adding
extra rigor, we're just explicitly stating that stuff that the GPL does is
ok"

Cheers,
Aaron

--
Aaron Wolf
wolftune.com

On Mon, Oct 13, 2014 at 9:13 AM, stef <s at ctrlc.hu> wrote:

> On Mon, Oct 13, 2014 at 08:46:24AM -0700, Aaron Wolf wrote:
> > It is a known fact that the point behind the OD text was to *include* the
> > GPL, so the fact that the text seems problematic is *absolutely* an issue
> > of being out of line with the intention. There is no question about this.
> > There is no need to check about whether there's some special intention
> > behind the particular wording. *Nobody* who worked on the OD *intended*
> to
> > exclude the GPL's requirement that unmodified redistributions include the
> > modifiable source.
>
> maybe so. but for me it's unclear: 1/ who the authors are, 2/ what their
> reasoning behind each change is. 3/ confirmation that this is indeed a bug,
> and the authors will fix it.
>
> i guess the idea of bundesgit applied to self would make a lot of sense, in
> regards of answering 1/ and 2/ (from reasonable commit messages). possibly
> also answering /3.
>
> is there a gitrepo of the OD where this is tracked? and i just missed this?
>
> --
> otr fp: https://www.ctrlc.hu/~stef/otr.txt
> _______________________________________________
> okfn-discuss mailing list
> okfn-discuss at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/okfn-discuss
> Unsubscribe: https://lists.okfn.org/mailman/options/okfn-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/okfn-discuss/attachments/20141013/80f89af4/attachment-0002.html>