replace nlesc.github.io software list with new RSD #275
Conversation
bouweandela
left a comment
bouweandela
left a comment
There was a problem hiding this comment.
Thank you for taking the time to update the guide!
| * Project based GitHub organizations | ||
| * MUST have at least two owners that are Netherlands eScience center employees | ||
| * MUST be [registered](https://github.com/NLeSC/nlesc.github.io#adding-an-github-organization) at [https://nlesc.github.io/](https://nlesc.github.io/), to keep track of all the project organizations | ||
| * MUST be registered at the [Research Software Directory](https://research-software-directory.org/projects/), to keep track of all the project organizations |
There was a problem hiding this comment.
It would be nice to add link with some information on how to do this. Would you be able to add that?
There was a problem hiding this comment.
Is that as simple as filling in the short form for New Project/Software, or are there further requirements for that?
There was a problem hiding this comment.
Thinking about this some more, I'm not sure GitHub organizations need to be registered in the RSD. When you publish a software package it should be entered into the RSD, but the GitHub organization where that software is hosted is not really relevant (even if it will be visible in the RSD from the software package site) so maybe this entire sentence could be removed? @jmaassen @nielsdrost Any opinions?
There was a problem hiding this comment.
It is relevant to keep track of all we're doing, because projects do not always have software packages as output. Sometimes the project works on existing packages, for instance, and it is not appropriate to "claim" the whole package as our own by putting it in the RSD as if it were our package. Then a project organization can contain the development fork, and then that is listed in the RSD project page so that the work can still be easily traced.
There was a problem hiding this comment.
Thanks for explaining! I've never seen that before, do you have an example?
There was a problem hiding this comment.
There was a problem hiding this comment.
Please note that the software in the RSD does not claim it to be "ours" in any way, just like adding your software to github does not make it the property of Microsoft or archiving it in Zenodo makes it the property of CERN.
The RSD is an open platform to share metadata and context about software. We develop it together with Helmholtz, who also use it extensively. There are already 8 different organizations adding their software packages, and some 20 or so independent researchers and RSEs (more join every day). Our goal is that in a year from now, the "eScience Software" in the RSD will be a small minority, just like it is in github.
So please go ahead and convince you project partners that it is a good idea to put the software in the RSD. We'll be happy to make them maintainers of these entries right away. Note that in some organisations, like Utrecht University, Leiden University and (soon) Amsterdam UMC, all researchers already have access to the RSD using their institute credentials. For people working in other organization we can provide a login via their ORCID.
There was a problem hiding this comment.
Good to know, that's different from the situation when I started working on ROOT. If this is now the way we do things, then perhaps you should still respond to the original question by @bouweandela, because then my explanation no longer makes sense.
There was a problem hiding this comment.
The github organizations should be registered on the project pages in the RSD. Every project we fund should have such a page on the RSD and a github organization shared with the project partners. In some cases it makes sense to do this differently, but this should be discussed on a case by case basis.
There was a problem hiding this comment.
Thanks for explaining, I'll merge this.
Replaces a reference to where new projects should be registered in the chapter on version control, and updates a reference to the Noodles package from the old to the new directory in Python#Parallelisation
closes #274