You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This group is subject to the governance documented in the [TOB proposal](https://github.com/opencontainers/tob/blob/main/proposals/wg-auth.md#governance).
4
+
5
+
## Code of Conduct
6
+
7
+
Working group members and maintainers shall follow the [OCI code of conduct](https://github.com/opencontainers/.github/blob/master/CODE_OF_CONDUCT.md)
8
+
9
+
## Discussion
10
+
11
+
- Discussions take place in the [GitHub repo](https://github.com/opencontainers/wg-auth) and during [weekly meetings](https://github.com/opencontainers/wg-auth/blob/main/README.md#meetings).
12
+
- Notes taken during the community meetings are recorded in [this hackmd document](https://hackmd.io/bGIxKAxPROi8KlwZMQioXQ), and later migrated to the [minutes](./minutes) folder via pull request.
13
+
14
+
## Maintainer Operations
15
+
16
+
The list of current maintainers shall be recorded in the [CODEOWNERS](https://github.com/opencontainers/wg-auth/blob/main/CODEOWNERS) document.
17
+
18
+
- Maintainers shall be responsible for overseeing documentation of community decisions, consensus, and resolution of conflicts.
19
+
- Maintainers shall provide timely feedback to requests for review and promptly merge approved Pull Requests.
20
+
- Maintainers shall operate in good faith and trust in the community and in each other.
21
+
- Maintainers shall keep the documentation, issues, and discussion topics as up-to-date as possible.
22
+
- In the event a Maintainer cannot perform their duties or have been inactive for a period of time, an interim or permanent replacement shall be nominated from the community.
23
+
- Consensus on unblocking inactivity or deadlock must be reached in a community meeting and recorded in the meeting minutes.
24
+
- Any member from the community may volunteer to be a maintainer as long as they pledge to follow the OCI code of conduct and perform these duties.
25
+
26
+
## Conflict Resolution
27
+
28
+
- Conflicts that cannot be resolved within the group shall be referred to the OCI Technical Oversight Board (TOB) as per [section 5.xv](https://github.com/opencontainers/tob/blob/main/CHARTER.md#5-technical-developer-community) of the TOB Charter.
29
+
- Resolution of the conflict shall be documented on this GitHub repository's issues which can be referred to in a pull request.
Authentication and authorization are a key requirement for registries to control access.
6
+
Implementations of this in registries and clients have roughly followed standards set by Docker and have mostly focused on compatibility with specific implementations of registries or clients.
7
+
This working group will define a standard to be supported by OCI compatible registries and clients when support for authentication and authorization is required.
- WG Meeting: [Tuesdays at 10:00am PT (Pacific Time)](https://zoom.us/j/92128676364) (weekly). [Convert to your timezone](https://dateful.com/convert/pt-pacific-time?t=10am).
20
+
-[Meeting notes and Agenda](https://hackmd.io/YyhWh7X_RuCod0i0mGxVLg).
- Josh: Jon (who isn't here) once shared this image with me and it changed my life <https://raw.githubusercontent.com/google/go-containerregistry/main/images/credhelper-basic.svg>
29
+
- Jason: Consider adding docker authentication docs as a baseline and add to it if thats possibly
30
+
- Jason: document the state of the world is the milestone. And really restrain on improving the state of the world?
0 commit comments