Re: [GNUnet-developers] spdx proposal (aside: public domain licenses)

[ng0]

I think I have to read up more on cc0 and public domain, as well as
the history of FSF position towards it to make a meaningful claim on
the licenses.

Meanwhile I personally find 0bsd / zero-clause BSD easier to be understood by
humans for reasons I wrote before, making it a more obvious choice. Previously
I have just written custom 2 liners where I simply dedicated something to the
public domain.
Of course we will continue to have auto-generated artifacts in the repository
which simply state "... is in the public domain". One can overthink the
simplicity, and as long as we don't end up copying code which wasn't
public domain and putting it in the public domain: either of cc0 or 0bsd
should be good enough, leaving it up to people to chose as long as there's
a SPDX identifier for it.

2019-01-16 16:45 GMT+00:00 Christian Grothoff<address@hidden>:
> I think it should be OK to put the SPDX marker for CC0 and write "in the
> public domain (or CC0)" into the text. After all, we use this for very,
> very trivial "code".  That said, I don't have a strong reason for going
> for CC0 vs 0BSD here, it's just that you say FSF recommends CC0, which
> is generally a good reason for me in the absence of a real argument ;-)
> 
> On 1/14/19 2:16 PM, address@hidden wrote:
>> Reading into general licenses we use, I found that simply stating "public 
>> domain"
>> is considered "controversial" enough for the FSF to recommend CC0 now. I have
>> no strong preference over the presented alternatives (CC0, 0BSD, etc) but 
>> would
>> make files which are not just Makefiles state 0BSD. For myself 0BSD seems 
>> more
>> appropriate for what we have and is more to the point, less "intimidating" 
>> for
>> people who don't use license texts on a daily/regular basis.
>> 
>> Compare https://opensource.org/licenses/0BSD 
>> (https://tldrlegal.com/license/bsd-0-clause-license)
>> with
>> https://creativecommons.org/publicdomain/zero/1.0/legalcode 
>> (https://tldrlegal.com/license/creative-commons-cc0-1.0-universal)
>> 
>> As neither Trademarks nor Patents apply for the files we put in the public 
>> domain and our
>> project, 0BSD seems better because it can be processed easier by humans 
>> (which also
>> relates to this thread intention).
> 
> 
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnunet-developers
>