Missing license

[evertrol]

This repository appears to be missing a license. A form of a creative-commons license is probably what is needed.

Perhaps a Citation File Format CFF is also a good idea. Happy to create one with a PR.

[libcce]

For the moment, here is the license https://github.com/LibraryCarpentry/Top-10-FAIR/blob/master/LICENSE.md. But I believe links need to be updated. In the file itself but also adding the license in the navigation, other places. And if you want to start the CFF in the meantime that would be great. Thanks!

[evertrol]

Apologies, it seems that I stupidly overlooked the license file.

But I'll leave this issue open if you feel it requires an update. And I'll get work on the PR for a CFF file.

[evertrol]

Related, but perhaps worth a new issue: what about contributing? There is a Contribution section in the README that covers it, so looks like no CONTRIBUTING file needed.

But what about someone who files one or more PRs with significant additions (complete paragraphs, new or revised resources, ...); does such a person become a co-author? Or is that left to actual sprinters, and any contribution through e.g. PRs is maintained in the commit history? What if the contribution is just a few spelling corrections or rewordings?
Could help if this is somehow clarified.

(unless I missed the essential section or file again...)

[evertrol]

CFF file will not work: it's for software only. So just keep the Zenodo reference, that should be enough.

[libcce]

HI @evertrol up to this point there hasn't bee too much contributor activity outside of the sprinters that are all listed in Zenodo. Contributorship has meant participating in the sprint, listing your name as a sprinter on one of the Things, and then being listed in the Zenodo release. It's a good question about how we might integrate contributions from GitHub and not via a lesson sprint. I don't know when the next release will be but best option seems to be moving everyone over to GitHub so that when there is a next release all contributions are recorded. But I'm sure that won't be easy as most of the Things were developed in Google docs, less people were familiar with GitHub. So the other way is to scan the contributions and then add the contributors to the Things they have contributed to as sprinters during the next release. Reminds me of all the fun I had entering our ORCIDs and affiliations 😄 But we can consider a modified version of this contributing file https://github.com/LibraryCarpentry/lc-xml/blob/gh-pages/CONTRIBUTING.md.

[evertrol]

I guessed most things were done through Google docs, since that's where my contribution has been edited in as well. But now that it lives on GitHub, and assuming all these top-10 lists are living documents, keeping them up-to-date via GitHub issues (possibly, hopefully), seems like a practical and convenient thing.

An adjusted version of that CONTRIBUTING file sounds great.

Also:

Reminds me of all the fun I had entering our ORCIDs and affiliations

Maybe this isn't that much work a next time, but, while a CFF file doesn't work, perhaps there could an AUTHORS file (that can easily be sorted if so wanted), e.g. in JSON format. That might make it more straightforward to add new authors and upload to/enter for a newer version (I actually don't know what formats can be handled when entering authors; perhaps only plain text?).

[libcce]

Instead of AUTHORS I created https://github.com/LibraryCarpentry/Top-10-FAIR/blob/master/CITATION.jsonld which I thought was better because it included all the metadata for context purposes.

Do you want to close this issue and open a new issue that describes the task above, create a modfiied CONTRIBUTING file base on https://github.com/LibraryCarpentry/lc-xml/blob/gh-pages/CONTRIBUTING.md and that accommodates Top 10 FAIR's workflows?