Maintenance Wish-List

[steffilazerte]

Hi @finlaycampbell (CC @CyGei, @noamross)

Based on the conversations we've had and the issues currently open in the repository, below I've listed what I think are the maintenance needs for epicontacts. I've also included some suggested issues (without a link). If you agree with this outline, I'll create these issues in epicontacts, and then the next step will be to decide what the priorities are and what kind of support you need to get started (i.e. funds to hire a developer, you or other, or help from a developer from rOpenSci, etc.).

Some of these issues may be a bit stale.

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

---

Bugs/Problems

• Use of deprecated igraph functions #140
• Faulty handling of NA in get_clusters #118
• Bug in subset(x cs_min = ...) #97

Functionality

• export as.igraph #117 and add conversion to igraph #98
• Request manual colour nodes #90

Housekeeping

• create pathological data set #115
• Code review of epicontacts #114 and Is it necessary to have dplyr as a dependency? #83 (and an updated Code Review would be good too)
• refactor tests that rely on saved data #96
• Question: why is print.epicontacts skipped on travis? #88
• Review and update Documentation
• Clean up the stale branches

Done?

• Update website #89

[finlaycampbell]

Thanks so much for looking into this, Steffi!

As with outbreaker, there is a seperate timeline branch with quite significant functionality that also indirectly addresses a number of the bugs (#97 and #118) and feature requests (#90). I would say the top priority would be merging this while maintaining backwards compatibility.

Some of the other issues may be out of date, I'll have a look and close any that are no longer relevant.