in a bunch of cases i've seen, the other maintainer is active and responsive. if they're not, i think i agree its fair to fork/replicate can't think of a good reason to duplicate active, well built packages otherwise!
in a bunch of cases i've seen, the other maintainer is active and responsive. if they're not, i think i agree its fair to fork/replicate can't think of a good reason to duplicate active, well built packages otherwise!
Totally agree. Like qs! 😉
hah, that is a 3rd valid case - when two packages want to follow different paths of implementation. so it makes sense to diverge the ones im talking about are near identical implementations of the same thing. only diff is the owner