Thanks Matthew. It makes sense that sample code is often licensed
under more permissive licenses.

Working out the date on which this documentation was published is
going to be tricky. I followed a GitHub link [1] from the page
referenced in groups.js and the file history is pretty garbled due to
file renames and eventually runs into a dead end.

We may have to include both the CC0 and MIT licenses, just in case.

[1] 
https://github.com/mdn/content/blob/main/files/en-us/web/api/document/cookie/index.md

On Thu, 13 Jul 2023 at 08:42, Matthew de Detrich
<matthew.dedetr...@aiven.io.invalid> wrote:
>
> I just had a quick look into this and according to
> https://github.com/mdn/content/blob/main/LICENSE.md#licenses-for-code-examples-and-snippets
> the licensed code snippet (which is what the source file in question is
> referring to) it should be CC0 license if the code snippet was added after
> August 20, 2010 and if it was added before its MIT license (see
> https://github.com/mdn/content/blob/main/LICENSE.md#added-before-august-20-2010
> ).
>
> MIT is compatible with Apache 2 license and CCO is also compatible with
> Apache 2 license since its effectively public domain (see
> https://creativecommons.org/share-your-work/public-domain/cc0/ and
> https://wiki.creativecommons.org/wiki/CC0_FAQ#Can_anyone_use_a_work_that_is_distributed_under_CC0.3F).
> It would be quite shocking if we couldn't use CCO source code as the whole
> point of the license is to waive all copyright, ip and related rights and
> this is why CCO is typically used for code samples/configuration (it's to
> avoid problems like this) and Apache seems to agree as well, see
> https://www.apache.org/legal/resolved.html#handling-public-domain-licensed-works,
> specifically
>
> > You can include works in the public domain (or covered by a license
> treated similarly) within Apache products. You must provide attribution (in
> a similar fashion to the Category A list).
>
> > Licenses that we treat as similar to public domain:
> > Creative Commons CC0 “No Rights Reserved”
> > Creative Commons Public Domain Certification
>
> Kind regards,
> Matthew
>
>
> On Thu, Jul 13, 2023 at 3:08 AM Justin Mclean <jus...@classsoftware.com>
> wrote:
>
> >
> > Hi,
> >
> > > There is no license header on the file we copied and slightly modified.
> > >
> > >
> > https://github.com/lightbend/paradox/blob/8e30c341f1f8351a19b71599219d2f636ba68eb4/themes/generic/src/main/assets/js/groups.js
> >
> > That contains code from [1] which I thought was licensed under the MPL
> > [2], but it looks like this situation may have changed and depends on the
> > date that code was submitted. [3] So either, depending on the license, the
> > code can’t be included in a source release OR it can but you n need to add
> > the license information to LICENSE.
> >
> > > Its project license is the Apache License.
> >
> > That may be but parts of that file are not under the terms of the Apache
> > License.
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie
> > 2. https://www.mozilla.org/en-US/about/legal/terms/mozilla/
> > 3. https://github.com/mdn/content/blob/main/LICENSE.md
>
>
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to