Skip to content

EVERSE-ResearchSoftware/tools-feedback

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

24 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Feedback EVERSE Services

Welcome to the central feedback repository for the EVERSE (European Virtual Institute for Research Software Excellence) tool suite. This space is dedicated to gathering insights, requirements, and technical reviews to ensure our tools meet the needs of the diverse research software community.

πŸ›  Our Services

We are currently collecting feedback for the following core components:

Tool Description Service Repository
RSQKit Research Software Quality Toolkit View service View Repo
Quality Dimensions and Indicators List of Software Quality Dimensions and Indicators used in EVERSE View service View Repo
TechRadar Visualizing the research software landscape View Service View Repo
QualityPipelines CI/CD templates for quality assurance View Repo
DashVERSE Analytics dashboard for the EVERSE ecosystem View Repo
** EVERSE Training** Educational resources for research software engineering View Service

πŸ“₯ How to Provide Feedback

We value input from both users (researchers, developers) and domain experts (community leads, RSE managers).

1. Structured Issues (Preferred)

Please use our Issue Templates to ensure your feedback is routed correctly:

  • πŸ› Bug Report: Encountered a technical problem? Let us know.
  • πŸ’‘ Feature Request: Have a requirement for a new functionality?
  • πŸŽ“ Expert Community Review: Deep-dive technical or domain-specific assessments.
  • πŸ’¬ General Remarks: Anything that doesn't fit the above.

2. Workshop & External Data

We collect feedback at the GAM and during dedicated sessions. To add the outcome of such feedback rounds to the repository

  1. Navigate to the /data directory.
  2. Open a Pull Request to upload your export (PDF, CSV, or Markdown summary).
  3. Name your file or folder using the format: YYYY-MM-DD-Workshop-Name or similar.

Here, you can also add "random feedback" that does not fit the issue format.


πŸ“Š Feedback Organization

To keep the community informed on how their feedback is being used, we organize all input into a global dashboard:

πŸ‘‰ Kanban board will follow

We use labels to categorize feedback:

  • project:[tool-name] β€” Which tool the feedback belongs to.
  • persona:expert β€” Insights from community experts.
  • status:planned β€” Feedback that has been accepted into the roadmap.
  • type:bug β€” Type of issue as indicated above.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •