Skip to content

Commit 750d7ad

Browse files
authored
Merge pull request #604 from vbatts/update_faq
README: trim faq and point to the main site
2 parents 8d87da9 + 49cc57a commit 750d7ad

File tree

1 file changed

+2
-11
lines changed

1 file changed

+2
-11
lines changed

README.md

+2-11
Original file line numberDiff line numberDiff line change
@@ -42,22 +42,13 @@ To support this UX the OCI Image Format contains sufficient information to launc
4242
A: Distribution, for example using HTTP as both Docker v2.2 and AppC do today, is currently out of scope on the [OCI Scope Table](https://www.opencontainers.org/about/oci-scope-table).
4343
There has been [some discussion on the TOB mailing list](https://groups.google.com/a/opencontainers.org/d/msg/tob/A3JnmI-D-6Y/tLuptPDHAgAJ) to make distribution an optional layer, but this topic is a work in progress.
4444

45-
**Q: Why a new project?**
46-
47-
A: The [first OCI spec](https://github.com/opencontainers/runtime-spec) centered around defining the run side of a container.
48-
This is generally seen to be an orthogonal concern to the shipping container component.
49-
As practical examples of this separation you see many organizations separating these concerns into different teams and organizations: the Docker Distribution project and the Docker containerd project; Amazon ECS and Amazon EC2 Container Registry, etc.
50-
51-
**Q: Why work on this?**
52-
53-
A: We are seeing many independent implementations of container image handling including build systems, registries, and image analysis tools.
54-
As an organization we would like to encourage this growth and bring people together to ensure a technically correct and open specification continues to evolve reflecting the OCI values.
55-
5645
**Q: What happens to AppC or Docker Image Formats?**
5746

5847
A: Existing formats can continue to be a proving ground for technologies, as needed.
5948
The OCI Image Format project strives to provide a dependable open specification that can be shared between different tools and be evolved for years or decades of compatibility; as the deb and rpm format have.
6049

50+
Find more [FAQ on the OCI site](https://www.opencontainers.org/faq).
51+
6152
## Roadmap
6253

6354
The [GitHub milestones](https://github.com/opencontainers/image-spec/milestones) lay out the path to the OCI v1.0.0 release in late 2016.

0 commit comments

Comments
 (0)