Shall extend the scope with FAIR code/software management? Process is the same as for FAIR data policies.
or maybe a follow up lesson about open source policy?? I don't know how broad this should be, maybe a follow up lesson so that everything is not stuffed into one? What do you think?
I agree that we might need another lesson plan for code/software management policies - even though the process is similar.
[...] could you expand this to software & code? :)
I think that software policies are documents in their own right and shouldn't be thoroughly covered in this particular lesson plan. However, institutional data policies should usually describe the expectations around research software. As mentioned in https://doi.org/10.5281/zenodo.6225774, "The policy should make clear that research software required for reproducibility is deposited with a suitable code repository. "
Transferred comment 1
Link to relevant text: https://elixir-europe-training.github.io/ELIXIR-TrP-FAIR-Converge/units/FAIR-generics/topics/4-FAIR-in-data-policies/
General comment:
Shall extend the scope with FAIR code/software management? Process is the same as for FAIR data policies.
or maybe a follow up lesson about open source policy?? I don't know how broad this should be, maybe a follow up lesson so that everything is not stuffed into one? What do you think?
I agree that we might need another lesson plan for code/software management policies - even though the process is similar.
[...] could you expand this to software & code? :)
I think that software policies are documents in their own right and shouldn't be thoroughly covered in this particular lesson plan. However, institutional data policies should usually describe the expectations around research software. As mentioned in https://doi.org/10.5281/zenodo.6225774, "The policy should make clear that research software required for reproducibility is deposited with a suitable code repository. "