ardc-fair-checklist / ardc-fair-checklist.github.io

Self-assessment checklist for FAIR software
https://fairsoftwarechecklist.net
Apache License 2.0
1 stars 1 forks source link

Revisit scoping of the checklist #75

Closed jspaaks closed 1 year ago

jspaaks commented 1 year ago

code state: d447c22d3bf175dea68f0cf917c53f743d9efe1b

image

FWIW, here's some more phrases we had:

Tom: I’ve been thinking a gap in this approach is filtering out types of software that are not in scope. For instance, deployed or live services. Software not used for research (maybe).

“This tool is intended for …” focus on the middle type (prototypes) Maybe some wording about how it is available excluding commercial software Code you’ve written, not the code you’ve used

“About you: you’re an creator of software…”

After we make changes, it's probably a good idea to revisit the questions and check that they make sense given the scope definition.

jspaaks commented 1 year ago

I think I'm happy with the scoping for the moment.

If you agree @tom-h, I would like to close this issue.

tom-h commented 1 year ago

In the interests of getting this out there, I basically agree. I like the benefits and "calls to action" you've included. I think that is a great way to frame it.

I had imagined making the scope narrower, but it's implied. For instance, we assume openly available software... but then where else would they put their badge? So I think we can leave it as is.