As for maintaining software: if you can be more specific where you're running into issues, we can figure out what's going on. Generally, we don't have too much software that isn't maintained at all, but we also do reimplement components from time to time, and you might have run into an issue on a component that is being replaced -- but my apologies if or where we weren't upfront about that...
Also, lots of little things on GitHub like the examples of using Prometheus and others have PRs (some of them by me) which have never had any comments, no acknowledgement that they've been seen, but also no indication that the project isn't maintained or is just an example and that we shouldn't submit PRs.
All that being said, in general thanks for a great product.
In most cases, you can just make a base-64 image and `pkgin in` whatever package you wanted and it's pretty much the same thing.
The Prometheus stuff is heavily used by us internally, and while it's usable, it's pretty experimental (i.e., changing quickly). I don't see any pull requests or issues that are obviously from you, so if you point me at something I can take a look at it.
Have you sent that feedback, possibly pinged bcantrill on the issue (being Joyent's CTO I'd expect devdocs would fall under his purview)?
When it comes down to it though I prefer Triton to the other big cloud providers just because the firewall product is fantastic, bare-metal machines running SmartOS are fantastic, and best of all it's not Amazon (which is all I really want, if I'm honest).