updated content

Author: chanezon

README.md

@@ -8,6 +8,8 @@ username:ocp-reader@metadocker.onmicrosoft.com
 password: Runc0pen
 ```
 
+Content for the website is in markdown format in the content directory.
+
 In order to preview the website locally, [install Hugo](http://gohugo.io/overview/installing/), then in the directory where you checked out this project:
 ```
 hugo server  -w -v

content/about.md

@@ -3,12 +3,4 @@ date = "2015-06-10T19:03:22-07:00"
 title = "About"
 +++
 
-The Open Container Project is open governance structure for the express purpose of creating an open industry standard for container runtime.
-
-It has been announced June 20th 2015: [Press Release](http://fixme.com), [Blog Post](http://fixme.com).
-
-Projects associated to the Open Container Project can be found at [https://github.com/opencontainers](https://github.com/opencontainers).
-
-Contact the project maintainers on IRC at ...
-
-Contact the Linux Foundation about the OCP at ...
+The Open Container Project is an open governance structure for the express purpose of  creating open industry standards around container formats and runtime. Projects associated to the Open Container Project can be found at [https://github.com/opencontainers](https://github.com/opencontainers). Contact the project maintainers on IRC at [#opencontainers](https://botbot.me/freenode/opencontainers/). Contact the Linux Foundation about the OCP at [info@opencontainers.org](mailto:info@opencontainers.org).

content/charter.md

@@ -3,28 +3,5 @@ date = "2015-06-09T19:03:22-07:00"
 title = "Charter"
 +++
 
-The mission of the OCP is to promote and promulgate a set of common,
-minimal standards around container technology. The OCP’s specific duties include:
-
-1. Creating a formal specification for container image formats and runtime, which will allow a compliant container to be portable across all major, compliant operating systems and platforms without artificial technical barriers, in keeping with the values “Values” articulated below
-2. Accepting, maintaining and advancing the projects associated with these standards, which shall initially be the Container Runtime (runc); It will look to agree on a standard set of container actions (start, exec, pause,....) as well as runtime environment associated with container runtime.
-3. Attempting to harmonize the above-referenced standard with other proposed standards, including, but not limited to, the Appc specification. A number of important ideas and concepts have been developed by the Appc community, and it is an explicit goal to make it possible for those concepts part of this effort.
-4. Ensuring that the scope of technologies promulgated and proposed as standards are those that are sufficiently widespread and sufficiently mature and stable so as to warrant establishment as a standard. The OCP is specifically not intended to seek standardization in areas where there is still rapid innovation and where there are many possible competing standards. We believe that practical code that is broadly adopted should lead, rather than follow, paper specification.
-5. Establishing and enforcing a program of compliance to the OCP trademark, as well as any trademarks associated with OCP standards or Projects
-6. Providing oversight of the technical leadership of the Projects
-7. Ensuring that all Projects under the OCP aegis are licensed under Apache v2.0, and a lightweight contribution mechanism, such as a DCO
-8. If deemed appropriate, seeking the establishment of one or more formal standards via an established standards body, such as the IETF.
-9. Funding the day to day operations of the Projects, provided, however, that the OCP is not intended to pay the salaries of the maintainers and contributors to the Projects
-10. Ensure the standard is practical and meets user’s needs by adding users as active participants in the Project. These needs will include considerations such as usability and backwards compatibility.
-
-### Values guiding specification
-
-A number of these values are explicitly derived from the AppC stated values in order to maximize likelihood of harmonization. Wherever possible, the exact wording from the AppC stated values has been chosen.
-
-1. Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable. Container runtime should not be bound to clients, to higher level frameworks, etc.
-2. Portable: The runtime standard should be usable across different hardware, operating systems, and cloud environments.
-3. Secure. Isolation should be pluggable, and the cryptographic primitives for strong trust, image auditing and application identity should be solid
-4. Decentralized. Discovery of container images should be simple and facilitate a federated namespace and distributed retrieval.
-5. Open. The format and runtime should be well-specified and developed by a community. We want independent implementations of tools to be able to run the same container consistently. Code leads spec, rather than vice-versa. We seek rough consensus and running code.
-6. Minimalist: The spec should aim to do a few things well, be minimal and stable, and enable innovation and experimentation above and around it
-7. Backward compatible: Given the broad adoption of the current Docker container format (500M container downloads to date), the new standard should strive be as backward compatible as possible with that format
+The mission of the OCP is to promote and promulgate a set of common, minimal industry standards around container technology.
+To read more about the organization’s values, guidelines, structure, and duties, please read the [FAQ](/faq). Please note that the OCP foundation documents are a work in progress.

content/faq.md

@@ -0,0 +1,4 @@
++++
+date = "2015-06-10T19:03:22-07:00"
+title = "FAQ"
++++

content/index.md

@@ -3,23 +3,41 @@ date = "2015-06-07T19:03:22-07:00"
 title = "Index"
 page = "index-partial.html"
 +++
-The Open Container Project is open governance structure for the express purpose of creating an open industry standard for container runtime.
 
-It has been announced June 20th 2015: [Press Release](http://fixme.com), [Blog Post](http://fixme.com).
+The Open Container Project is a lightweight, open governance structure, to be formed under the auspices of the Linux Foundation, for the express purpose of creating open industry standards around container formats and runtime.
 
-In the past two years, there has been rapid growth in both interest in and usage of container-based solutions. Almost all major IT vendors and cloud providers have announced container-based solutions, and there has been a proliferation of start-ups founded in this area as well. While the proliferation of ideas in this space is welcome, the promise of containers as a source of application portability requires the establishment of certain standards around format and runtime. While the rapid growth of the Docker project has served to make the Docker image format a de facto standard for many purposes, there is widespread interest in open industry standard container specifications, which are:
+The OCP was launched on June 20th 2015: [Press Release](/pressrelease), [FAQ](/faq).
 
-1. not bound to higher level constructs such as a particular client or orchestration stack, and
-2. not tightly associated with any particular commercial vendor or project, and
-3. portable across a wide variety of operating systems, hardware, CPU architectures, public
-clouds, etc.
+In the past two years, there has been rapid growth in both interest in and usage of container-based solutions. Almost all major IT vendors and cloud providers have announced container-based solutions, and there has been a proliferation of start-ups founded in this area as well. While the proliferation of ideas in this space is welcome, the promise of containers as a source of application portability requires the establishment of certain standards around format and runtime. While the rapid growth of the Docker project has served to make the Docker image format a de facto standard for many purposes, there is widespread interest in a more formal, open, industry specification, which is:
+
+* not bound to higher level constructs such as a particular client or orchestration stack
+* not tightly associated with any particular commercial vendor or project
+* portable across a wide variety of operating systems, hardware, CPU architectures, public clouds, etc.
 
 The specification will be available at [https://github.com/opencontainers/specs](https://github.com/opencontainers/specs). The newly expanded team of maintainers (both original libcontainer maintainers and the appc maintainers) are busy preparing the first draft of the specification, and intend to release it in 2-3 weeks.
 
-Runc, the reference implementation of the OCP specification will be available at [https://github.com/opencontainers/runc](https://github.com/opencontainers/rrunc)
+Docker is donating its container format and runtime, runC, to the OCP to serve as the cornerstone of this new effort. It is available now  at [https://github.com/opencontainers/runc](https://github.com/opencontainers/runc).
 
 The following organizations are sponsors of the Open Container Project:
 
+* Appcera
+* AWS
+* Cisco
+* CoreOS
 * Docker
+* EMC
+* Fujitsu
+* Google
+* Goldman Sachs
+* HP
+* Huawei
+* IBM
+* Intel
+* Joyent
+* Pivotal
+* the Linux Foundation
+* Mesosphere
 * Microsoft
-* full list
+* Rancher
+* Red Hat
+* VMWare

content/pressrelease.md

@@ -0,0 +1,6 @@
++++
+date = "2015-06-10T19:03:22-07:00"
+title = "Press Release"
++++
+
+Today...