To get a sense of what's going on, I'd read this: http://rhelblog.redhat.com/2015/05/05/rkt-appc-and-docker-a-take-on-the-linux-container-upstream/
Yes, saw that the other day. It also highlights a general issue that this is a fast moving confusing space to begin with.
It's cold comfort to tell you that TOP MEN are working on it
Who?
Top. Men. (obligatory Indiana Jones reference completion)
In all seriousness, getting these sorts of things into the list faster is always better. I'd like to get the quick start / getting started docs into a better state that follows an actual workflow. Knowing where and how things relate even at an early state is good. For example, I'm working on a quick start version focuses on getting a single host and single container up using the new atomic command, instead of it stopping where it does now. I'm fairly sure that's not a dead end that will require major rework or set out a bad use case.
But addressing the other issue about including the kubernetes guestbook example in the getting started guide is a bigger issue if we have other plans for what a clustered Atomic presence entails. Or I could be conflating something here, and just pick another kubernetes example to fork and make stable for Atomic...
I'm also a bit of a squirrel so each new project gives me something new to chase instead of finishing the quickstart for review. That's not a community issue :)
- Matt M