As the number of contributions grow, reviewer bandwidth becomes a bottleneck; and maintainers are always asking for more help. However, ultimately maintainers must at least Ack every patch that goes in; so if you're not a maintainer, how can you contribute? Why should anyone care about your opinion?
This talk will try to lay out some advice and guidelines for non-maintainers, for how they can do code review in a way which will effectively reduce the load on maintainers when they do come to review a patch.
Software Engineer in Arm Open Source Software team. Mainly focus on Virtualization, Containers and Security. Currently focus on Unikraft/gVisor/Firecracker/Nabla /Solo5 opensource projects support on arm64 platform.
