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

docs: add maintainer guidelines #306

Closed
rdimitrov opened this issue Jun 8, 2022 · 0 comments
Closed

docs: add maintainer guidelines #306

rdimitrov opened this issue Jun 8, 2022 · 0 comments
Assignees

Comments

@rdimitrov
Copy link
Contributor

Define and document the maintainer review policy we'd like to follow in go-tuf.

Things like a review checklist, recommended response time, minimum number of approvers before PR can be merged, issues that people are working on should be part of the roadmap plan and have owners assigned which indicate their commitment, define and promote the use of labels, avoid having stalled PRs and Issues, etc.

@rdimitrov rdimitrov changed the title Add maintainer guidelines docs: add maintainer guidelines Jun 8, 2022
@znewman01 znewman01 self-assigned this Jun 8, 2022
znewman01 added a commit to znewman01/go-tuf that referenced this issue Jun 8, 2022
Follow-up from theupdateframework#190 (thanks @asraa!).

I did not add a DCO requirement at this point, as that was controversial
in theupdateframework#190. I filed theupdateframework#308 to track that.

I tried to address all *other* feedback in theupdateframework#190.

Fixes theupdateframework#212.

Fixes theupdateframework#306.
@asraa asraa closed this as completed in 1684c68 Jun 9, 2022
Repository owner moved this from 🆕 New to 🏗 In progress in [go-tuf] Project planning - v0.6.0 (Target: 2022-11-30) Jun 9, 2022
@rdimitrov rdimitrov moved this from 🏗 In progress to ✅ Done in [go-tuf] Project planning - v0.6.0 (Target: 2022-11-30) Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants