Document project roadmap and contribution stance about inviso HOT 3 OPEN

@adamkennedy We've been running Inviso internally at Netflix since well before the release and it is largely unchanged from the initial release.

The only feature we recently added that hasn't made it back into the OSS version is the ability to see pending app/user/queue container requests in addition to the existing running ones that inviso shows now. If there's interest in that, I can push those changes as well.

Most of the known issues are related to getting Inviso setup in certain environments and you can see some of that in the current open issues. Probably the biggest issue is that Inviso won't work out-of-the-box with ElasticSearch 2.x due to the incompatibility of the mapping property names, but it appears one user found a workaround for that.

As with almost all OSS projects, we're happy to receive contributions. If the change is substantial, it might be good open an issue to discuss it first.

from inviso.

It would be nice to have that, we tend to burst a lot.
It would also mean any branches we worked on would be less likely to clash with internal work there when the time comes to merge.

from inviso.

Sounds good. I'll try to get the changes pushed in the next few days and an update to the docker file, so you can test it out.

from inviso.