opencontainers / opencontainers/runc

[org] RFC: ways to move PRs forward

Open
#3,052 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
13.5k
Forks
2.3k
Avg merge
2d 8h
Merged PRs (30d)
30

Description

Currently all the cooperation between maintainers is almost exclusively limited to whatever means github offers. It seems to be working, except some PRs are stalling for months, causing fixes and features to not be merged, as well as, I guess, some contributor frustration, which may result in losing interest to the project.

I propose to

  1. Set up a weekly call, or a chat, for all available maintainers to go through existing PRs (and, if needed, issues). We can pre-select a few PRs to review, and go over them in half an hour or so, weekly. I can take a burden to pre-select PRs (and/or we can use Projects kanban board for that, similar to what happens in Moby).

The alternatives are:

  1. Have an IRC / Slack / Matrix / whatever channel where maintainers can poke each other (if such channel exists and is specific to runc, I am not aware of it).

  2. Lower the bar for PR acceptance/merge to a single LGTM from a maintainer (perhaps even allowing the PR author themselves to LGTM their own work).

Please share your opinions @opencontainers/runc-maintainers

Contributor guide

Open the contributing guide

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 with the issue discussion and the repository's existing pull-request workflow; no specific files, tests, or entry points are named. Review the proposed maintainer coordination options and the stalled-PR problem, then document an agreed process and its ownership as the completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.