Email list hosting service & mailing list manager

Scheme registry license Lassi Kortela (07 Aug 2020 10:00 UTC)
Re: Scheme registry license hga@xxxxxx (07 Aug 2020 10:59 UTC)
Re: Scheme registry license Lassi Kortela (07 Aug 2020 11:13 UTC)
Re: Scheme registry license hga@xxxxxx (07 Aug 2020 14:56 UTC)
Scheme.org file server? Lassi Kortela (07 Aug 2020 11:36 UTC)
Re: Scheme.org file server? John Cowan (07 Aug 2020 13:59 UTC)
Re: Scheme.org file server? Lassi Kortela (07 Aug 2020 14:11 UTC)
Re: Scheme.org file server? Lassi Kortela (07 Aug 2020 14:13 UTC)
Brief notes on licensing Lassi Kortela (07 Aug 2020 11:46 UTC)
Re: Brief notes on licensing hga@xxxxxx (07 Aug 2020 15:08 UTC)
Scope of the registry, and impact of scope on licensing Lassi Kortela (07 Aug 2020 15:32 UTC)

Re: Scheme registry license hga@xxxxxx 07 Aug 2020 10:58 UTC

A Creative Commons licences sounds like the right general approach (I
have no informed opinion on which would be appropriate).

What about code in the registry?  Snippets might not pose a problem,
but it should have a policy about fully featured things starting with
a single procedure implementation of something as simple as a CRC
checksum generator.

I'm thinking of a policy of curating such things in one or more
files organizing and indexing "generally useful stuff", with pointers
to repos, tarballs, etc. of the code itself, and behind the scenes
also making backups of them, so if the site rots or the user is banned
the code it contained can be resurrected.

Acceptable software licenses for those should be defined, either
anything https://opensource.org/licenses approved, or we could take
a stand against all or almost all viral licenses.  I certainly do,
the moment I see GPL/LGPL or worse I move it into "perhaps examine
for ideas category.  We are not a popular and big enough community
to allow members of it to try to force copyleft on everyone else.

An exception is the Eclipse license; while the boundary isn't
precisely defined, it's clear enough for me, if you modify the stuff
released under it, it's copyleft, you have an entirely reasonable
reciprocal duty to the community that provided it to you.  But
anything that for example links or uses it remains your own IP.  E.g.
patch the core if Clojure and you have a duty to make this available,
but your independent code written in Clojure is yours.

- Harold

----- Original message -----
From: Lassi Kortela <xxxxxx@lassi.io>
Date: Friday, August 07, 2020 4:59 AM

The registry is a collection of lists. Such a thing probably counts as a
work under copyright, and we should pick a license.

I'm not well versed in this area, but there's some talk that source code
licenses are not well suited to non-code works. The hugely popular
Awesome lists "strongly recommend the CC0 license, but any Creative
Commons license will work" (source:
<https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md>).

CC0 is a public domain equivalent license -- essentially a wordy waiver
of rights granted under copyright intended to also cover countries whose
legislation doesn't let authors voluntarily place works into the public
domain.

Should we go with CC0?