Action required: help identify API reviewers for your SIG
60 views
Skip to first unread message
Jordan Liggitt
unread,
Apr 12, 2019, 2:31:19 PM4/12/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to kubernetes...@googlegroups.com, kubernetes-api-reviewers
SIG leads / subproject owners:
For 1.15 API reviews we'll be iterating on the shadowing approach we took in 1.14, to develop reviewers in each SIG area to distribute expertise and increase review bandwidth.
To help us do that, please identify a few people in your SIG or subproject (1-3ish) who are willing to be actively involved in performing or shadowing API reviews for that area (especially if you have API-related items planned for 1.15 or already pending review).
Open a PR updating the OWNERS_ALIASES file with their github handles and assign it to me (@liggitt). If there are specific subproject(s) a person should review APIs for, that's helpful to add as a comment in the file as well.
Ideal candidates already have domain expertise in the SIG/subproject, are very familiar with the existing APIs for your area, and have read (or will read) through the API conventions and API changes docs.
As a reminder, agreement from relevant SIG leads and/or subproject owners that a particular change is desired is a prereq for the review process, so your volunteers will only get as many items as your area is willing to take on.