Skip to content

Commit ce087c8

Browse files
authored
Merge pull request #22 from opencontainers/digest-proposal
Add OCI digest project proposal
2 parents 8997b1a + f4deef8 commit ce087c8

1 file changed

Lines changed: 47 additions & 0 deletions

File tree

proposals/digest.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
# OCI go-digest project proposal
2+
3+
## Abstract
4+
[image-spec#486][image-spec-486] introduces a dependency on a stable upstream implementation of https://github.com/docker/go-digest, which was recently broken out of the https://github.com/docker/distribution project.
5+
6+
This package has been instrumental in providing a strong hash-identity implementation in Go and we will extend this to OCI. This will be supported by moving https://github.com/opencontainers/go-digest to OCI. While this package does support opencontainers/image-spec, it is broadly useful in other image formats or outside image formats.
7+
8+
Having a solid, battle-proven, common digest implementation in OCI for use in and outside the image-spec will ensure long lasting security and interoperability throughout the container ecosystem.
9+
10+
## Proposal
11+
With repositories under the https://github.com/opencontainers organization:
12+
13+
Rename (transfer) https://github.com/docker/go-digest would become https://github.com/opencontainers/go-digest.
14+
15+
### Initial Maintainers
16+
Initial maintainers of the go-digest project would be seeded from the image-spec project:
17+
* Brandon Philips <brandon.philips@coreos.com> (@philips)
18+
* Brendan Burns <bburns@microsoft.com> (@brendandburns)
19+
* Jason Bouzane <jbouzane@google.com> (@jbouzane)
20+
* John Starks <jostarks@microsoft.com> (@jstarks)
21+
* Jonathan Boulle <jon.boulle@coreos.com> (@jonboulle)
22+
* Stephen Day <stephen.day@docker.com> (@stevvooe)
23+
* Vincent Batts <vbatts@redhat.com> (@vbatts)
24+
25+
### Code of Conduct
26+
This project would incorporate (by reference) the OCI Code of Conduct.
27+
28+
### Governance and Releases
29+
This project would incorporate the Governance and Releases processes from the OCI project template: https://github.com/opencontainers/project-template.
30+
31+
### Project Communications
32+
Both of the proposed projects would continue to use existing channels in use by the OCI developer community for communication including:
33+
* GitHub for issues and pull requests
34+
* The dev@opencontainers.org email list
35+
* The weekly OCI developer community conference call
36+
* The #OpenContainers IRC channel
37+
38+
### Versioning / Roadmap
39+
We will probably minimize the releases of this project.
40+
41+
It will provide digesting functionality for all present and future versions of the specification.
42+
43+
## Frequenty Asked Questions (FAQ)
44+
Q: Does this change the OCI Charter or Scope Table?
45+
A: No. Nothing in this proposal is intended to amend the OCI Charter (https://www.opencontainers.org/about/governance) or OCI Scope Table (https://www.opencontainers.org/about/oci-scope-table).
46+
47+
[image-spec-486]: https://github.com/opencontainers/image-spec/pull/486

0 commit comments

Comments
 (0)