Also if you run into issues like this please make sure to send to firstname.lastname@example.org so we're sure to know about them as well.
The short version is, we'd like to release it and hope to do so again someday.
The issues that make that hard now are we used to maintain multiple sites & themes running Slash. Over time we stopped maintaining & updating the code on those sites (Slashcode.com, and use.perl.org) so some parts of the code have now become a little too Slashdot-specific from a theming and code perspective, making it harder for Slash to be useful as a general product.
Given time we'd like to clean that up, and make the code accessible and useful to everyone again, however finding the time to devote to clean-up and segmentation of the code so far has been difficult. We still hope to see that happen someday in the future though.
There's certainly more I'd like to take on as we're given the engineering bandwidth to get them done. If you have specific suggestions I'd love to hear them as a reply or sent to email@example.com. We certainly have our list but I want to make sure your most pressing concerns are part of it. Thanks for being a longtime Slashdot reader!
I'm not 100% sure what our decision will be but it's a problem I was considering before delving into reader comments much, and it's certainly something that's been voiced by many community members too. There's certainly improvements which could be made, and one of those on the table is going back to the old way of doing things.
We have some things we intend to fix or improve on the core comment navigation experience first, but we should eventually get to giving metamod some attention.
It is much harder to find a job than to keep one.