search

epiverse-trace / blueprints

Software development blueprints for epiverse-trace
https://epiverse-trace.github.io/blueprints
Other
2 stars 3 forks source link

Document current situation in new sustainability chapter #77

Closed Bisaloo closed 3 months ago

Bisaloo commented 4 months ago

Fix #37. Also relates to https://github.com/orgs/epiverse-trace/discussions/86 but without providing many answers yet.

This PR focuses on documenting the current situation, but does not add new processes and standards.

netlify[bot] commented 4 months ago

Deploy Preview for playful-gelato-7892ba ready!

Name Link
Latest commit b7bea400643fc4747d0b9b0556566df86c33e3fa
Latest deploy log https://app.netlify.com/sites/playful-gelato-7892ba/deploys/65cdca714c74d70008660451
Deploy Preview https://deploy-preview-77--playful-gelato-7892ba.netlify.app/sustainability
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Bisaloo commented 4 months ago

Just a few thoughts:

  • A core Epiverse value (the top one iirc) is inclusivity. What could we do, or what are we doing, to ensure that new and existing team members have the skills to be included in the development of all packages? E.g. improving epi, maths, or programming knowledge? @avallecam is running some courses in the coming weeks - is that something worth mentioning?

  • Let's say we have a lottery-win event - how could we communicate temporarily reduced support for, or development on the affected packages? Would it help to use a status badge?

  • More broadly, I noticed that there wasn't a concrete committment to project or software sustainability. Is it worth thinking of fallback maintenance options/rules, as e.g., Pharmaverse do?

Thanks, I agree all of these are really good point but probably outside the scope of this specific PR. The goal is to document processes that are already in place but not explicitly described anywhere. I have updated the original PR comment to reflect this more clearly.

I completely agree we have a lot more to discuss on this topic, and probably clearer steps to implement, but a PR is not the best forum to do it. @pratikunterwegs, could you copy this comment to https://github.com/orgs/epiverse-trace/discussions/86 so that it's preserved in a place where we can more easily find it again? Thanks!