[Container-tools] Naming the "Container App Spec and Libraries" project

[Tomas Radej]

Hi, all.

On 14/04/15 19:02, John Mark Walker wrote:
> Hey gang,
>
> Because there's an obvious namespace collision between CoreOS' appc efforts and our own container app spec, I've been wondering what to name our thing. Here are some potential names. Vote on 1 or submit your own:
>
> - supernetes - I originally liked this, but then realized it doesn't send a realistic message. Connotes some type of orchestration that sits "above" k8s. I don't think that's what we're creating. I include it here for completeness.
>
> - intercon - short for "inter-container" - because what we're doing is about defining multi-container applications that can utilize a number of "providers" and host environments.
>
> All the other names I'm thinking about are variations on this theme:
>
> - interpod - same as above, except adopting the term "pod" from the k8s universe
>
> - hyperpod, hypercon - same theme as above, just using a different term of art to connote "more than one pod"
>
>
> I kind of like intercon, although I could see arguments for something else.
>
> Once we have a name, we need to figure out where it lives. I don't think it belongs under the Project Atomic org on github.

What about these?

* micado - for Multiple Interconnected Container App DefinitiOn
* appic (read as epic) - for APPlication of Interconnected Containers

The downside is that both of these are squatted on GitHub.

Tomas Radej