Skip to content

Add SMP eScience Center indicator configurations (low/medium/high) - #105

Open
vuillaut wants to merge 1 commit into
mainfrom
add/smp-escience-center-configurations
Open

Add SMP eScience Center indicator configurations (low/medium/high)#105
vuillaut wants to merge 1 commit into
mainfrom
add/smp-escience-center-configurations

Conversation

@vuillaut

@vuillaut vuillaut commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Fixes #73

Summary

  • Adds configurations/practical-smp-escience-center/readme.md, mapping the Netherlands eScience Center's Practical Guide to Software Management Plans (Table 4 management levels) onto EVERSE catalog indicators and the plugins currently wired up in this repo.
  • Adds three ready-to-run resqui configs derived from that mapping — one per management level, each using every plugin listed as validating that level's core requirements' unambiguous indicator:
    • smp-escience-low.json (9 checks) — Purpose, Version control, User documentation, Software licensing and compatibility, Deployment documentation.
    • smp-escience-medium.json (19 checks) — low + Repository, Citation, Developer documentation, Testing, Packaging, Maintenance.
    • smp-escience-high.json (20 checks) — medium + Risk analysis.

Open questions

  • Two core requirements (Support, Software Engineering quality) are required at medium/high per the guide but have no plugin currently wired up in this repo, so they're intentionally absent from these configs — flagged as an open item in the readme. --> should I open an issue to track these afterwards and in a future improvement?
  • Some indicators can be part of (or participate in validating) a requirement. I have not considered them in the configurations here --> should we? and if yes, how?

Test plan

  • validated using command resqui -c configurations/practical-smp-escience-center/smp-escience-high.json -t "$GITHUB_TOKEN" -o high.json - other configs being subsets of the high one, they are also valid ✔️

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
https://claude.ai/code/session_012KQ4BHoo6AUDDpWa9R4Q1o

Maps the Netherlands eScience Center's Practical Guide to Software
Management Plans (Table 4 management levels) onto EVERSE catalog
indicators and wired-up plugins. Each core requirement's "Validates
without ambiguity" indicator is checked via every plugin listed as
wired up for it in the guide's readme:

- smp-escience-low.json (9 checks): Purpose, Version control, User
  documentation, Software licensing and compatibility, Deployment
  documentation.
- smp-escience-medium.json (19 checks): low + Repository, Citation,
  Developer documentation, Testing, Packaging, Maintenance.
- smp-escience-high.json (20 checks): medium + Risk analysis.
  (Support and Software Engineering quality are required at
  medium/high per the guide but have no wired-up plugin yet, so
  they're not represented in these configs.)

Verified smp-escience-low.json end-to-end with `resqui -c ... -v`
against this repository.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012KQ4BHoo6AUDDpWa9R4Q1o
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implementing Software Management Plan

1 participant