We now have a workflow for releasing citable versions of our lessons (with DOIs) every 6 months via Zenodo. This makes our more discoverable and sustainable and ensures that everyone involved gets the credit they deserve. For more on this work see https://github.com/data-lessons/librarycarpentry/issues/5
In order to make this happen we need to make one crucial change: all AUTHORS files need to change so that they list names of contributors in the following format:
James AllenJames BakerPiotr BanaszkiewiczErin Becker
@jt14den will run a script that that strips names from lesson logs and edit AUTHORS across all Library Carpentry repos.
When this is actioned (hopefully, soon!), lesson maintainers are asked to eyeball the AUTHORS file to see if anyone obvious is missing (for example, people who contributed to discussions but didn't edit any lessons). Note: template developers are credited in this process; this is in line with Software Carpentry best practice.
In the future, lesson maintainers are encouraged to ensure that those who contribute to lessons are added manually to AUTHORS files (encourage contributors to do it so they see where and how we give credit!)
We now have a workflow for releasing citable versions of our lessons (with DOIs) every 6 months via Zenodo. This makes our more discoverable and sustainable and ensures that everyone involved gets the credit they deserve. For more on this work see https://github.com/data-lessons/librarycarpentry/issues/5
In order to make this happen we need to make one crucial change: all AUTHORS files need to change so that they list names of contributors in the following format:
James AllenJames BakerPiotr BanaszkiewiczErin Becker@jt14den will run a script that that strips names from lesson logs and edit AUTHORS across all Library Carpentry repos.
When this is actioned (hopefully, soon!), lesson maintainers are asked to eyeball the AUTHORS file to see if anyone obvious is missing (for example, people who contributed to discussions but didn't edit any lessons). Note: template developers are credited in this process; this is in line with Software Carpentry best practice.
In the future, lesson maintainers are encouraged to ensure that those who contribute to lessons are added manually to AUTHORS files (encourage contributors to do it so they see where and how we give credit!)