Content OWNERS Nomination

513 views
Skip to first unread message

Dave Tapuska

unread,
Oct 6, 2020, 10:58:04 AM10/6/20
to content-owners
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.

Nasko Oskov

unread,
Oct 15, 2020, 11:01:44 AM10/15/20
to Dave Tapuska, content-owners
The current content/OWNERS have discussed and decided not to offer Dave content/ ownership at this time, and we've responded privately with more details.

Thank you for your offer, and we do appreciate your contributions!
content/OWNERS

--
You received this message because you are subscribed to the Google Groups "content-owners" group.
To unsubscribe from this group and stop receiving emails from it, send an email to content-owner...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/content-owners/07ead92b-dc64-468b-b2fd-37e40384ea11n%40chromium.org.

Nasko Oskov

unread,
Jan 5, 2024, 2:10:28 PM1/5/24
to content-owners, Nasko Oskov, content-owners, Dave Tapuska
Happy New (calendar) Year everyone.

I wanted to follow up on this thread and announce that Dave was just added to content/OWNERS in recognition of his contributions since the initial discussion. Congrats Dave!

To unsubscribe from this group and stop receiving emails from it, send an email to content-owners+unsubscribe@chromium.org.

Dana Jansens

unread,
Jan 5, 2024, 2:11:31 PM1/5/24
to Nasko Oskov, content-owners, Dave Tapuska
Congrats Dave :) And thanks for taking on this responsibility!

To unsubscribe from this group and stop receiving emails from it, send an email to content-owner...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "content-owners" group.
To unsubscribe from this group and stop receiving emails from it, send an email to content-owner...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/content-owners/6c07fdc5-4089-4d19-9882-8e01304ee12bn%40chromium.org.

Kentaro Hara

unread,
Jan 5, 2024, 3:35:36 PM1/5/24
to Dana Jansens, Nasko Oskov, content-owners, Dave Tapuska
Congrats, Dave!!


2024年1月6日(土) 4:11 Dana Jansens <dan...@chromium.org>:
Reply all
Reply to author
Forward
0 new messages