Description
Checklist before submitting an issue
- I have checked the existing issues and couldn't find an issue about this bug.
Issue details
During the research software templates session in RSECon24, there were several comments in the mentimeter which I have interpreted as related to outreach of the template.
We should make sure the template is easy to find, that people finding it can easily see that it is what they need, and see some examples of others using the template.
Some of these comments (Good SEO) might already be in place?.
Others (good use cases, list of projects using the template (Make template used more visible)), may require a bit of continuous effort, but are possible to measure over time.
Other aspects (Awareness) might be difficult to measure, but still require attention.
Mentimeter comments were along the lines:
Discovery might be difficult for newer coders unfamiliar with templates? Good SEO (Search Engine Optimisation);
Good, short, motivating use case;
Some kind of footprint in repos using it, so I can follow breadcrumbs from well built trips;
Make the template used more visible (e.g., in the README, CITATION.cff...);
Awareness, e.g. an "Awesome" list of possible tempaltes to use with clear categorisation;
Have a well organised/documented library of templates, easy to find right one;
Awareness;
Sell the benefits - what is for, etc;
proved to reduce time :);
Tailored for use with popular repos (e.g. pypi)
Also related to adoption, were some comments on when people find a template useful:
- For CI pipelines
- For automated publication
- When Making packages to redistribute
- When Following good practices/reproducible/FAIR