List view
- No due date•29/29 issues closed
- Due by September 30, 2025
- Due by July 31, 2025•11/11 issues closed
- Due by May 31, 2025•5/5 issues closed
- Due by April 30, 2025•14/14 issues closed
Priorities for this release: - A further updated and navigable life cycle diagram with child pages for the different stages and links to associated RSQKit tasks. More Research Software Stories from the different research clusters. - Improvements to task pages - Higher level task pages (compound / task assemblies) - linking to sets of tasks to achieve a higher level quality goal (e.g. the use of continuous integration). - Research quality indicator based index page. - Further roles matching managers and scientists. - Better connection with research cluster training catalogues allowing users to find domain aware guidance around software quality tasks. - Improved community engagement with the EVERSE Network and beyond around input and contribution and incentives - An explanation and link to how TechRadar can help you choose tools based on your research software circumstances to improve quality
Due by October 31, 2025•26/26 issues closed- Describe progress in establishing RSQKit to date Note this used to be called MS2.2 but was updated to MS5
Due by February 26, 2025•23/23 issues closed- Indicators, tools, contributors data schemas - Updated task template page - More task pages - Research community pages for all EVERSE Science clusters - A initial position on what is the equivalent for RSQKit for the 'Tool Assembly' in RDM Kit
Due by March 18, 2025•4/4 issues closedMini sprint to sort out a few infrastructure issues in RDMKit before the end of 2024: - Ensure everyone can install and run RSQKit locally or at least make any PRs on their own fork of the repo so that changes can be tested and verified (update 2024-12-08 we now have Netlify app which helps with rendering each branch in a separate website so that will help massively as we do not need to work much in forks any more) - Provide any help with installing tools locally (for those who want to work like this) - Perform issue triage and assign people responsible for each issue (check if everyone is clear on what needs doing) - Review all remaining PRs and make sure they have been responded to or merged
Due by December 31, 2024•16/16 issues closed