Email list hosting service & mailing list manager

Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 09:46 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 16:10 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 16:44 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 16:54 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 17:10 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 18:58 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 21:15 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 17:28 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 21:18 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 21:28 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 21:35 UTC)

Re: Cookbook is now scraped and ready to browse Lassi Kortela 08 May 2019 21:28 UTC

> If we do end up maintaining the cookbook, we should just make the
> license clear on every page.

This is a good idea. In my experience, most sites like this have unclear
licenses.

> Perhaps we could even annotate old code as
> having only the old license, but include a user agreement that licenses
> code under multiple licenses so that users have the most flexibility
> possible.

Also worth considering! This possibility didn't occur to me at all.

>     Here's the Stack Overflow licensing policy:
>     Creative Commons CC-BY-SA
>
> I would trust their approach.  They are such a huge site, with so many
> users, that I assume that they must already have dealt with any possible
> issue that could come up.

It would indeed be reasonable to assume so, but I browsed some of that
discussion once and got the impression that they don't really know what
they are doing (but neither does anyone else necessarily - this is
apparently a very murky area, both the legal interpretation and the
social conventions surrounding re-use).

IIRC they used to have everything under MIT License with some custom
attribution clause added (sounds kind of weird). I got the impression
that there isn't a clear sense of direction there.