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 14:55 UTC

> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Friday, August 07, 2020 6:13 AM
>
>> [ We'll use the Creative Commons CC0 licence. ]
>
>> 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.
>>
>> [ Stuff that's more than "snippets", especially licensing, see
>>   a following message on that. ]
>
> What kinds of code snippets would the registry need to contain? I
> thought it would just be some simple lists, and link to external sources
> for anything complicated.

Trying to anticipate things we might want to put in the registry that
we aren't yet thinking about.  "Snippets" being artifacts too small
for their own repo or tarball, the latter the registry can just point
to.  As mentioned above, perhaps simple stuff like one procedure
implementations of CRCs.  Or smaller things that are truly "snippets".

- Harold