rufuspollock
commented
11 months ago @skreutzer thanks for the fulsome issue 🙏👏
The licensing point is just an oversight - we used to have a license on here i think and it got lost from the README or repo in a refactor. I think we'd be fine with CC-BY or CC-BY-SA. I can confirm and we'll update (PS: I'm the original founder of Open Knowledge Foundation so i'm pretty big around the licensing).
Background of the question is, I/others have observed several similar directory compilation (sometimes + sensemaking) efforts, so the general notion would be to source/extract your data and propagate it to other places/directories as well (and vice versa). Generally, this often only led to opposition/refusal, with the practical consequence that there's now a lot of duplication and incompatibility of course (proprietary silos each, be it for technical, legal and/or administrative reasons).
I hear you and I've seen that over the years in various areas. that said, having been involving in open data and creating data and knowledge commons etc etc for 20y i think this is much harder than we think e.g. merging data ongoingly (with ease) requires similar (or identical) data structures etc etc. However, generally agree that people could at the very least openly license - spent many years advocating for this. (PS: you may like https://github.com/datasets/)
I'm not right now volunteering to parse out your data from Markdown you've put stuff into, just because it's not a clean/proper data project. But someone might do at some point, as you're probably doing that for the Web-site and visualizations already? So would be nice to get the clean data, and not bother with the Markdown much.
I actually specifically prefer markdown with frontmatter now - we used to run off pure csv. More about this in https://github.com/orgs/life-itself/discussions/829
Here's a few similar things:
This is a super-useful list 🙏🙏 - can we add it to https://ecosystem.lifeitself.org/related-efforts?
Hi, I'm just wondering: you're not licensing the content of this repo and the contributions at this time. Is there a particular reason for not doing that, as the legal default then resorts to "all rights reserved" (each contributor retaining veto powers for their parts). At best, there's some implicit, non-transferable permission for the material to be published on/as GitHub only and to go onto your Web-site only? Is the idea to go "pragmatic" about it and ignore it, till/in-case there'll be eventually a problem?
Background of the question is, I/others have observed several similar directory compilation (sometimes + sensemaking) efforts, so the general notion would be to source/extract your data and propagate it to other places/directories as well (and vice versa). Generally, this often only led to opposition/refusal, with the practical consequence that there's now a lot of duplication and incompatibility of course (proprietary silos each, be it for technical, legal and/or administrative reasons).
Are you by any chance in favor of Creative Commons BY-SA 4.0 (which is probably the best libre-free license for content/media/database works, despite a bit weak on anti-DRM and doesn't come with a path-to-upgrade), to not be worse than or incompatible with the Wikipedia/Wikidata? You probably can't retroactively get consent for prior data from some contributors up to this/future point, right? For code (in case there's some reusable tooling, visualizations), that would ideally be the GNU Affero General Public License version 3 + optionally any later version of the license (to also close the SaaS loophole), but my impression is, developing some tooling and building infrastructure may not be the main focus here.
I'm not right now volunteering to parse out your data from Markdown you've put stuff into, just because it's not a clean/proper data project. But someone might do at some point, as you're probably doing that for the Web-site and visualizations already? So would be nice to get the clean data, and not bother with the Markdown much.
Here's a few similar things:
Because I'll soon be locked out from this account, I'll manually check occasionally if a license is later applied (if possible at all, retroactively, for former contributions) to this repo, or to new/other repos/data.