Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kata Containers Mission Statement #47

Closed
annabellegoth2boss opened this issue Jul 16, 2018 · 19 comments
Closed

Kata Containers Mission Statement #47

annabellegoth2boss opened this issue Jul 16, 2018 · 19 comments

Comments

@annabellegoth2boss
Copy link

It's a good time for us to create a mission statement for the Kata Containers project! This statement should be fairly brief and tell people what this project aims to do and how we do it.

This issue is for open discussion of what should be included in the mission statement and if anyone wants to suggest drafts.

Examples can be found from OpenStack and Zuul

@raravena80
Copy link
Member

Suggesting something like this:

Enable infrastructure providers to run containers in a painless, secure and isolated way via open community collaboration

Embodies Kata Containers and the OpenStack community together.

@grahamwhaley
Copy link
Contributor

Maybe we can start with a list of key items we might want to touch on? Off the top of my head, in no particular order:

  • Virtual Machines
  • Containers
  • Small / Fast / Efficient
  • Secure
  • Open Source
  • Open Community
  • Multi-stack, neutral, independant
  • Scaleable
  • De-facto / reference implementation

My first stab then:

Define and implement the de-facto Open Source and Community implementation for
Virtual Machine Container enablement and runtimes.

I think we can do better though :-)

@ttx
Copy link
Member

ttx commented Jul 19, 2018

I think we should touch on the secure/isolation properties while being able to run classic unmodified images. To build on both suggestions above, something like:

Openly collaborate to define and implement the de-facto open source virtual machine container solution, enabling infrastructure providers to run any container in more secure and isolated way.

@egernst
Copy link
Member

egernst commented Jul 19, 2018

I like it @ttx. Only thing I would consider changing is replacing infrastructure providers to users?

@ttx
Copy link
Member

ttx commented Jul 19, 2018

@egernst Feel free to tear it apart and iterate on it !

I borrowed "infrastructure providers" from Ricardo's version as it's good to call those out as a primary target (in an open infrastructure story arc), but I agree it might be reductive... Maybe "...enabling infrastructure providers and other users to run..." ?

@brecky777
Copy link

brecky777 commented Aug 10, 2018

I'd like to see messages around adoption / use and community. Not sure how I feel about Kata being the "defacto" because in truth, I think the road Kata has paved will likely lead to a wellspring of solutions representing a continuum of container virtualization solutions which address different use cases and levels of user sophistication. Maybe we'd like to broaden the Kata Container umbrella to encompass more than just what we refer to a "Kata Containers" today?
But rather than being philosophical and creating more questions than answers, I'll build upon what's been proposed:

Engage and nurture a robust, global community of active contributors and users to define and implement more secure and versatile container solutions that marry the benefits of virtual machines with the speed and ease-of-use of containers.

@jodh-intel
Copy link
Contributor

I like it. My only comments would be to:

  • Replace "marry" with "combine" (or maybe replacing "that marry" with "combining").

    Either would be clearer for non-native English speakers I think.

  • Change "ease-of-use" to "ease of use"

    Although what you've written is perfectly correct, I think the doc team prefers us to drop dashes for visual clarity and again as an aid for non-native speakers.

@raravena80
Copy link
Member

I like it too.

Engage and nurture a robust, global community of active contributors and users to define and implement more secure and versatile container solutions combining the benefits of virtual machines with the speed and ease of use of containers.

@grahamwhaley
Copy link
Contributor

Personally, I'd drop the 'more' - other than that, +1 from me :-)
@annabellebertooch , how's this looking to you?

@ttx
Copy link
Member

ttx commented Aug 14, 2018

LGTM! I think "active" could be dropped too, as I feel like that meaning is already conveyed in "robust". If we want another adjective, I'd pick "diverse", since that has multiple desirable dimensions. As in "...a robust, diverse, and global community of contributors and users".

@jbryce
Copy link
Member

jbryce commented Aug 17, 2018

I really like the direction this went. Thanks for the input from everyone!

@annabellegoth2boss
Copy link
Author

Some word-smithing for your consideration:
"Openly collaborate across a diverse, global community of contributors and users to define and implement secure, versatile containers solutions that combine the benefits of virtual machines with the performance and ease of containers."

@annabellegoth2boss
Copy link
Author

annabellegoth2boss commented Sep 19, 2018

With some wordsmith assistance, I'd like to propose:
"Openly collaborate across a diverse, global community to define and implement secure, versatile container solutions that combine the benefits of virtual machines with the performance and ease of containers”

@grahamwhaley
Copy link
Contributor

Only thing I'd change is s/containers solutions/container solutions/ - but, maybe that is just a niggle happening in my head :-)

@raravena80
Copy link
Member

Sounds good to me!

@ttx
Copy link
Member

ttx commented Sep 20, 2018

I like it! I'll let the choice between "container solutions" and "containers solutions" to native speakers.

@jodh-intel
Copy link
Contributor

that combine the benefits of virtual machines with the performance and ease of containers."

Since our project name includes the term "containers", this reference to the ease of containers is somewhat confusing I think. It might be better described as,

that combine the benefits of virtual machines with the performance and ease of Linux containers."

Or maybe,

that combine the benefits of virtual machines with the performance and ease of traditional Linux containers."

However, that makes what is already a very long sentence slightly longer. In fact, it's instructive to say it out loud. I timed it a few times and speaking at a "natural" rate, it takes me ~12 seconds. That suggests it's too long and complex. If so, that could prove challenging to understand for non-native English readers.

In summary, can we break this into multiple sentences? Or -- stepping back a long way -- could we even shorten it to something super succinct like:

Kata Containers: Working together to make containers better. 😄

/cc @klynnrif, @intelkevinputnam.

@gnawux
Copy link
Member

gnawux commented Sep 20, 2018

I prefer to use virtualization or virtualization technology instead of virtual machines. In my opinion, we are working to leverage the capabilities of VT, and get rid of the overhead of emulating a real machine.

@annabellegoth2boss
Copy link
Author

The change from "virtual machines" to "virtualization" makes sense to me. Beyond that, I'd propose we accept the below, and can always edit in the future.

Openly collaborate across a diverse, global community to define and implement secure, versatile container solutions that combine the benefits of virtualization with the performance and ease of containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants