I've seen a couple of references to modules that no longer work; it's
inevitable with a new language.
There is a balance between having respect for / protecting the original
developer, and also keeping a useful module up to date when the original
developer moves on / gets bored / dies / falls in love with someone else.
Developers see a protocol for adding a module to the ecosystem. I think
it would be effective for the perl6 community to have a visible protocol
for dealing with 'abandoned' modules. If it's visible at the start, it
is difficult to complain about arbitrary decisions later.
I came across the following, which I thought made the balance in a
reasonable way:
https://learn.getgrav.org/advanced/grav-development#abandoned-resource-protocol
Richard Hainsworth
