CDK Community PR Reviews

CDK Community Reviews

The CDK Team is introducing Community PR Reviews to improve the contributor experience. We've heard from a group of community members that they would be interested in additional responsibility to help scale our open-source project. Historically, reviewing PRs has always been a bottleneck for the team. Now, with the help of a pool of trusted reviewers, we will be expanding our reviewing power beyond just the team of CDK maintainers.

Priorities

We review Pull Requests in the following order:

• p1 PRs with passing checks (denoted by pr/needs-maintainer-review)
• p2 PRs that are community reviewed (also gets pr/needs-maintainer-review)
• p1 PRs with a failing automated review to see if we can unblock you
• p2 PRs with passing checks (denoted by pr/needs-community-review)

Essentially, getting a community review lets you jump the line slightly. The CDK Maintainers still aim to get to all community PRs that come in but recognize that we are a finite resource and don't manage to get to everyone in a timely manner.

How to get your P2 PR community reviewed

Please do not ping our community members directly, either on GitHub or on cdk.dev!

If your PR is eligible for a community review, the pr/needs-community-review label will be automatically added to the PR. Trusted community members will be able to search for that label and find these PRs organically. If you feel like your PR needs an extra bump, consider posting it on the #contributing channel in cdk.dev. Community members will be on the lookout there as well for possible reviews.

Trusted CDK Reviewers

Github	cdk.dev	Specialization
pahud	Pahud Hsieh
jogold	Jonathan Goldwasser
hoegertn	Thorsten Höger
robertd	Robert Djurasaj
watany-dev	yohei watanabe
jumic	Julian Michel
daschaa	Joshua Weber
yamatatsu	yamatatsu
lpizzinidev	Luca Pizzini
iRoachie	Kyle Roach
kylelaker	Kyle Laker
WinterYukky	WinterYukky
tmokmss	tmokmss
humanzz	Ahmed Kamel
msambol	Michael Sambol
go-to-k	k.goto
nmussy	nmussy