Hey all,
The KubeVirt community keeps growing, and it's amazing to see. More and more contributors from a diverse range of companies and organizations are joining forces to make KubeVirt better for a wide variety of use-cases and business needs. Just at yesterday's community meeting, about 5 new people introduced themselves!
We've worked hard to get here - driving community changes toward greater transparency, diversity and inclusivity. It's fulfilling to see the results of that long-standing effort.
But more contributors also means more PRs, more VEPs and more ideas to discuss - which calls for more people participating in reviews. Since the number of approvers and reviewers today is relatively low, we need to increase review efforts to avoid it becoming a bottleneck for introducing great ideas or welcoming new contributors.
Since I've seen many repeated questions in this area, here's a quick FAQ:
Q: Can anyone participate in reviews?
A: Absolutely! As an open source community, we invite everyone to express their thoughts, questions and comments on every issue or PR. Don't hesitate to ask "newbie" questions and get involved!
Q: Why should I help review?
A: There are multiple reasons. First, being a good citizen in an open source community is simply the right thing to do. Second, your review contributions will be recognized and reciprocated when you need reviews for your own PRs and VEPs. Third, being honest - we're near the threshold of what we can review as a community, which means that without more reviewers we risk having to limit the number of VEPs we can track per release. This is really crucial - we don't want review capacity to become a bottleneck for accepting great new enhancements.
Q: What does it mean to become an official "reviewer"?
A: Our bot auto-assigns two reviewers to each new PR. These reviewers get notified when assigned and are expected to review it. A reviewer should be willing to dedicate enough time for these reviews.
Q: How can I become a reviewer?
A: You need to open a PR that adds your GitHub handle to the OWNERS_ALIASES [1] file. Before doing so, please ensure the nominated reviewer meets the requirements in our membership policy [2]. You can refer to previous nomination PRs [3] for an example.
Q: I'm confident to be a reviewer only for a specific area of the project, not all areas. What should I do?
A: You can become a reviewer for a specific SIG, as can be seen in the OWNERS_ALIASES file.
If you have any further questions, feel free to either respond to this mail, reach to me privately or posting a question in the kubevirt-dev Slack channel [4].
Thanks a lot for your help!