I've been asked by Kentaro to put my name forward for nomination as a content/OWNER. As a blink [core|public|common|platform] OWNER for a number of years I've participated and guided a number of decisions in this area of code and feel I am well versed on the content code, specifically around the IPC between browser and renderer, and the content/blink relationship.
Having more owners in content that are common to the blink code can decrease the reliance on the current content/OWNERS to review patches that have already been reviewed by blink owners. (This is more prevalent now with the implementation of the renderer side of the mojo APIs inside blink rather than in content/renderer)
My most recent work removing RenderWidget from content/renderer is coming to fruition (with only a few things remaining inside content/renderer/RenderWidget). I've also been driving the legacy IPC conversion where Igalia engineers have contributing the majority of the patches.
I believe the CLs below demonstrate my ability to question the merits of a CL (whether it is the right decision), whether it fits correctly in the API scope, and my analysis techniques (possibly identifying issues that other content owners did not catch). This is just a few of the
~475 CLs I've reviewed/commented on in the past year.
If the group decides not at this time, please let me know what development actions I can take so I will be able to resubmit my nomination in the future sometime.
Thanks,
Dave.