opencontainers / opencontainers/tob

CHARTER: OCI Project Removal and Archival

Open
#83 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
91
Forks
58
PR merge metrics
No merged PRs in 30d

Description

We currently do not have a process for OCI Project removal and archival. It's unclear whether these should even be considered two separate processes. The TOB does have the right to remove projects under Section 2 (b) of the Charter, but it seems like this is something which should be slightly more formalised (such as requiring a 30 day notice with a comment period before archival of the project -- and likely we would never want to outright remove a project from the OCI).

Are there any strong opinions about what the process should be? In keeping with the apparent consensus on the TOB calls, we should probably make this as minimal as possible.

I am writing this as a separate issue, because it won't be included in my first round of charter refactoring but it is something that I wanted to open a discussion about.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading Section 2 (b) of the Charter and the existing charter-refactoring context mentioned in the issue. Determine whether removal and archival need separate processes, then document a minimal agreed process with a clear notice and comment period if the project decides one is required.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.