Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add subproject governance #12

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

lukpueh
Copy link
Member

@lukpueh lukpueh commented Apr 8, 2024

Add governance document based on CNCF subproject governance template.

  1. The first commit is an unchanged copy of the original CNCF template from 3 years ago (more recent updates of the template itself are not covered in this PR and can be seen this diff)
  2. The second commit updates the template to fit the TUF org and was contributed by @joshuagl also 3 years ago (see commit message for details)
  3. The third commit was contributed by @JustinCappos based on recent community discussions. Most notably, it adds two new TUF project types and describes a process where the steering committee members are elected by TUF contributors (previously the steering committee was constituted from subproject representatives, TAP editors and the consensus builder without an election)

This PR is meant as discussion starter.

This is a modified version of the proposed CNCF Subprojects template by
Josh Berkus.

Modifications are made based on two significant factors:
1) the heart of TUF is the specification and TAPs, and therefore the
steering committee explicitly includes all TAP editors
(spec + TAPs maintainers)
2) the community around TUF today is small, so some procedure has been
streamlined to ensure governance is not too burdensome (removal of member
representatives feels suboptimal, but we don't have a big community to
draw from yet).

Signed-off-by: Lukas Puehringer <[email protected]>
Co-authored-by: Joshua Lock
Signed-off-by: Lukas Puehringer <[email protected]>
Co-authored-by: Justin Cappos

Contributors who have not actively contributed to the project, through PRs and
Issues, or communicated on project forums (GitHub, Slack, Mailing list) for
longer than 12 months may be involuntarily moved down the contributor ladder,
or asked to move to an emeritus status.
longer than 2 months may be involuntarily moved down the contributor ladder,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 months is a fairly short amount of time, I think we should give folks at least a 3 month/12 week grace period.

* One Maintainer representative from each member subproject
* All of the TAP Editors
* Two of the TAP Editors
* Two elected from the set of TUF contributors
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is TUF defined here? The specification?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants