[Practitioner Guide]: Research Software Impact

[germonprez]

Practitioner Guide Topic (1 - 3 words)

Research Software Impact

Primary Metrics (2 - 4 metrics)

Project Engagement
New Contributors
Technical Forks
Stars - To be built

Why is this topic important? How will this help people improve their open source project and / or community? Who will benefit from this guide?

This guide is aimed at helping university affiliated people better understand their contributor and user communities associated with research-related open source projects.

How would you like to see this guide developed?

I have the experience and time available to write the first draft

Additional Notes

No response

[geekygirldawn]

Un-assigning myself since I haven't started working on this one in case someone else wants to pick it up and work on it.

[geekygirldawn]

I've created the doc based on the expert guide template that you can use to collaborate on this guide: https://docs.google.com/document/d/1a1cEW5_BvBni40gWgd0Cirj1r2gmzchmB3KZZrRPqx4/edit?tab=t.0

[geekygirldawn]

We've published a general version of a sunsetting guide (not specific to research projects):
https://chaoss.community/practitioner-guide-sunset

It also looks like this guide has evolved a bit ... which happens with these types of guides :) Looking at the doc, I think this has evolved into a Research Software Impact guide, so I'm going to adjust the title of this issue to reflect what's in the guide. cc: @claredillon and @germonprez

As always, let me know if you'd like any help with this guide!