Skip to content

Maintenance Wish-List #43

@steffilazerte

Description

@steffilazerte

Hi @thibautjombart (CC @CyGei)

👋🏼 I'm @steffilazerte (with rOpenSci, we chatted a couple of weeks ago), and I've been tasked with helping to organize the maintenance needs of RECON packages. The first thing we want to do is figure out what packages need, maintenance-wise.

So that's what brings me here. I'm hoping you can provide me with a wish-list of what you'd like for your package and what support you might need to achieve this. I've outlined some ideas you may want to consider, but feel free to expand or include things I haven't thought of

(You're also my guinea pig for this request, so I'd really like to hear of general questions you think should be included on this list for when I approach more maintainers, or if this list is overwhelming and needs to be paired down 😅).

Things to consider on your wish-list

What the package needs

  • General Code Review - check that code follows best practices, works as intended, etc.
  • Testing - add, fix, or improve the testing suite
  • Address existing GitHub issues - generally address outstanding issues
  • Fix show-stopping bugs - Are there any specific, critical bugs that need to be fixed?
  • Desired functionality - Do you need to add functionality to meet current (scientific) standards in your field?
  • Compatibility - Do you need to improve/fix compatibility with other RECON packages?
  • Documentation - Do you need to improve/fix documentation (i.e. man pages, examples, vignettes, etc.)?

Help needed to achieve this

(feel free to be specific about the needs for different tasks)

  • Do you need developers to help?
  • Do you need specialized help? (e.g., developers with epidemiology experience)?
  • Do you have people to help, but just need the funds?
  • Would you like to pass on maintainer-ship of this package, or find co-maintainer to help lighten the load?
    (Maintaining a package can be a lot of work and depending on other commitments you might have, it's not always feasible)

General details which might help

  • Is this package meant to work with other RECON packages (e.g., part of a workflow, data input/output, function dependencies, etc.)? Which ones and how?
  • Are there anything specifically urgent about maintenance for this package? (e.g., upcoming workshops, bugs in this package causing problems in another package, etc.)

Feel free to open or link to issues specific to these wish-list items, or simply itemize them for me here (I may open issues on your behalf for better tracking).

Let me know if you have any questions, of if I've missed something important. Thank you! 🙏🏼

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions