-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce concept of "communities" #616
Comments
Maybe we should leave out this issue from the V2? as it adds a new functionality when the v2 it is a general overall UI revamp and usability fixes |
We moved it to the nice to have milestone because it needs more discussion. It is related to issues #741 that Helmholtz is working on, see above. As discussed in the RSD weekly of 8 May we could take this approach. |
We had a brainstorm in this topic. These are the notes: At the moment we have 4 projects who are interested in communities:
Main idea of communities feature:
To add software to a community, a user would need to:
Next, the community maintainer needs to be notified of the pending software, check if it adheres to requirements, and accept or reject it (with message?) Communities may potentially have a source to harvest information from:
This may require some extra thinking. How to we define custom scrapers? How do you ensure the scraped metadata and mandatory categories match? etc. |
Also allow automatic accept to community? This would allow all helmholtz software to automatically be added to this community. |
The categories should be finished end-april. |
During the discussions with the TDDC NES, the idea was suggested for the RSD to support "communities".
A community would be a "virtual organization" where are group of people can curate the set of software and project that are interesting to them. By directly linking to a community (for example: research-software-directory/community/ocean-modelling) it would become easier for user groups to find the software and projects they are interested in.
The text was updated successfully, but these errors were encountered: