Including some non-Googler Chromium experts in Blink bug triage rotation

[Rick Byers]

Hey,

@Mike Jackson asked me at BlinkOn if there are any Chromium rotations that Edge engineers could help with. Unfortunately for logistical reasons a lot of our rotations require Google-internal tools, but that's not true for the blink bug triage rotation. Also I think the blink bug triage rotation is actually helpful for experienced Chromium engineers looking to increase their breadth of experience across all of chromium web platform areas (eg. sometimes digging into repros a bit in order to route correctly, etc.). So we agreed we'd test it out and just coordinate with y'all here on this public list, sound good?

Mike, you asked about logistics. We have a tool for sending calendar invites to people for their rotation. So if you give me addresses of one or two people I can propose some slots (2-business-days each) for their first shift and also ensure one of us is available on standby to help answer any questions. Logistically we let the tool just do round-robin scheduling and then find someone on this list to swap with when a scheduled date doesn't work for us. I can also help with this (feel free to ping me on slack for faster response times).

In terms of components, the (pretty light) instructions are here. The main priority is just to look for things in the generic uncatagorized web platform bucket which is just marked 'Blink' and drive them down to zero. We also found that sometimes platform bugs are miscategorized as UI bugs and so we do a pass over those too to get them routed to the right platform area or UI sub-component. There's a pretty wide spectrum of acceptable level of engagement on any given issue, but I think a good rule of thumb is probably that effective triage takes 2-3 hours a day during your shift (though that's just my personal experience - others here may disagree).

Any other questions?

Thank you so much for your offer of assistance! In general we all care a lot about web developers having a great experience when they make the effort to report an issue to us, and so appreciate your willingness to bring your team's expertise to help!

Thanks,

   Rick

[Mike Jackson]

Thanks Rick. This all sounds great! Could we start out by included dan...@microsoft.com, and kbab...@microsoft.com on the rotation?

[TAMURA, Kent]

On Thu, Nov 7, 2024 at 10:12 AM 'Mike Jackson' via Component:Blink bug rotation <crblink-...@chromium.org> wrote:

Thanks Rick. This all sounds great! Could we start out by included dan...@microsoft.com, and kbab...@microsoft.com on the rotation?

On Tuesday, November 5, 2024 at 2:47:36 PM UTC-8 Rick Byers wrote:

Hey,

@Mike Jackson asked me at BlinkOn if there are any Chromium rotations that Edge engineers could help with. Unfortunately for logistical reasons a lot of our rotations require Google-internal tools, but that's not true for the blink bug triage rotation. Also I think the blink bug triage rotation is actually helpful for experienced Chromium engineers looking to increase their breadth of experience across all of chromium web platform areas (eg. sometimes digging into repros a bit in order to route correctly, etc.). So we agreed we'd test it out and just coordinate with y'all here on this public list, sound good?

It sounds like a very good idea!

The only concern is that the internal rotation tool may not support non-Alphabet users. We might need to find an alternative tool.

 

Mike, you asked about logistics. We have a tool for sending calendar invites to people for their rotation. So if you give me addresses of one or two people I can propose some slots (2-business-days each) for their first shift and also ensure one of us is available on standby to help answer any questions. Logistically we let the tool just do round-robin scheduling and then find someone on this list to swap with when a scheduled date doesn't work for us. I can also help with this (feel free to ping me on slack for faster response times).

In terms of components, the (pretty light) instructions are here. The main priority is just to look for things in the generic uncatagorized web platform bucket which is just marked 'Blink' and drive them down to zero. We also found that sometimes platform bugs are miscategorized as UI bugs and so we do a pass over those too to get them routed to the right platform area or UI sub-component. There's a pretty wide spectrum of acceptable level of engagement on any given issue, but I think a good rule of thumb is probably that effective triage takes 2-3 hours a day during your shift (though that's just my personal experience - others here may disagree).

Any other questions?

Thank you so much for your offer of assistance! In general we all care a lot about web developers having a great experience when they make the effort to report an issue to us, and so appreciate your willingness to bring your team's expertise to help!

Thanks,

   Rick

--
You received this message because you are subscribed to the Google Groups "Component:Blink bug rotation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crblink-rotati...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/crblink-rotation/dfd620b0-ad65-4e6c-8542-359f3df1a79cn%40chromium.org.

--

TAMURA Kent
Software Engineer, Google

[Rick Byers]

On Thu, Nov 7, 2024 at 2:30 AM TAMURA, Kent <tk...@chromium.org> wrote:

On Thu, Nov 7, 2024 at 10:12 AM 'Mike Jackson' via Component:Blink bug rotation <crblink-...@chromium.org> wrote:

Thanks Rick. This all sounds great! Could we start out by included dan...@microsoft.com, and kbab...@microsoft.com on the rotation?

Great, thank you Daniel and Kevin! I've added you both and the system assigned you 12/4-5 and 12/6-8 respectively - you should have a calendar invite. Let me know if you'd like to swap for different dates. Eg. I'm next scheduled for 11/26 but could take 12/4 instead (but travelling on 12/8 so can't take that one). I know you both have been around Chromium for quite some time so I have no concerns, but don't hesitate to ping me on slack if you want to chat (or I could hop on a quick video chat too if that's better).

On Tuesday, November 5, 2024 at 2:47:36 PM UTC-8 Rick Byers wrote:

Hey,

@Mike Jackson asked me at BlinkOn if there are any Chromium rotations that Edge engineers could help with. Unfortunately for logistical reasons a lot of our rotations require Google-internal tools, but that's not true for the blink bug triage rotation. Also I think the blink bug triage rotation is actually helpful for experienced Chromium engineers looking to increase their breadth of experience across all of chromium web platform areas (eg. sometimes digging into repros a bit in order to route correctly, etc.). So we agreed we'd test it out and just coordinate with y'all here on this public list, sound good?

It sounds like a very good idea!

The only concern is that the internal rotation tool may not support non-Alphabet users. We might need to find an alternative tool.

It seems to support external addresses with calendar invites too - I did a quick test with my personal GMail account. But the management interface is internal only so we'll still have to handle additions / removals / swaps. Should be OK I think? But yeah  

[Kevin Babbitt]

Thanks Rick, I have the Google calendar invite and the slot I got assigned works for me.

 

Kevin

[Daniel Clark]

Confirming that I also received the calendar invite and can do the assigned slot.

 

Thanks!

Dan

[Johnny Stenback]

This is great to see, I'm very excited to have Microsoft contributing in this way as well! I'm happy that our tooling supports this use case. One idea I had that might help with swaps if your slots don't work at some point is that if it happens to work for y'all you should feel free to swap internally amongst yourselves w/o needing to involve anyone at Google. If you do that we won't know, but that's ok, what matters is that the triage happens, not who does it when. If that doesn't work out though, we're of course always happy to help move stuff around in the internal tool.

Cheers,

Johnny

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/crblink-rotation/MW4PR00MB1453CE95BB2E11AF85F4E313C55C2%40MW4PR00MB1453.namprd00.prod.outlook.com.

[TAMURA, Kent]

On Thu, Nov 7, 2024 at 11:49 PM Rick Byers <rby...@chromium.org> wrote:

On Thu, Nov 7, 2024 at 2:30 AM TAMURA, Kent <tk...@chromium.org> wrote:

On Thu, Nov 7, 2024 at 10:12 AM 'Mike Jackson' via Component:Blink bug rotation <crblink-...@chromium.org> wrote:

Thanks Rick. This all sounds great! Could we start out by included dan...@microsoft.com, and kbab...@microsoft.com on the rotation?

Great, thank you Daniel and Kevin! I've added you both and the system assigned you 12/4-5 and 12/6-8 respectively - you should have a calendar invite. Let me know if you'd like to swap for different dates. Eg. I'm next scheduled for 11/26 but could take 12/4 instead (but travelling on 12/8 so can't take that one). I know you both have been around Chromium for quite some time so I have no concerns, but don't hesitate to ping me on slack if you want to chat (or I could hop on a quick video chat too if that's better).

On Tuesday, November 5, 2024 at 2:47:36 PM UTC-8 Rick Byers wrote:

Hey,

@Mike Jackson asked me at BlinkOn if there are any Chromium rotations that Edge engineers could help with. Unfortunately for logistical reasons a lot of our rotations require Google-internal tools, but that's not true for the blink bug triage rotation. Also I think the blink bug triage rotation is actually helpful for experienced Chromium engineers looking to increase their breadth of experience across all of chromium web platform areas (eg. sometimes digging into repros a bit in order to route correctly, etc.). So we agreed we'd test it out and just coordinate with y'all here on this public list, sound good?

It sounds like a very good idea!

The only concern is that the internal rotation tool may not support non-Alphabet users. We might need to find an alternative tool.

It seems to support external addresses with calendar invites too - I did a quick test with my personal GMail account. But the management interface is internal only so we'll still have to handle additions / removals / swaps. Should be OK I think? But yeah  

Oh, that's nice!  Yeah, Googleers can help to operate the tool.

 

 

Mike, you asked about logistics. We have a tool for sending calendar invites to people for their rotation. So if you give me addresses of one or two people I can propose some slots (2-business-days each) for their first shift and also ensure one of us is available on standby to help answer any questions. Logistically we let the tool just do round-robin scheduling and then find someone on this list to swap with when a scheduled date doesn't work for us. I can also help with this (feel free to ping me on slack for faster response times).

In terms of components, the (pretty light) instructions are here. The main priority is just to look for things in the generic uncatagorized web platform bucket which is just marked 'Blink' and drive them down to zero. We also found that sometimes platform bugs are miscategorized as UI bugs and so we do a pass over those too to get them routed to the right platform area or UI sub-component. There's a pretty wide spectrum of acceptable level of engagement on any given issue, but I think a good rule of thumb is probably that effective triage takes 2-3 hours a day during your shift (though that's just my personal experience - others here may disagree).

Any other questions?

Thank you so much for your offer of assistance! In general we all care a lot about web developers having a great experience when they make the effort to report an issue to us, and so appreciate your willingness to bring your team's expertise to help!

Thanks,

   Rick

--
You received this message because you are subscribed to the Google Groups "Component:Blink bug rotation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crblink-rotati...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/crblink-rotation/dfd620b0-ad65-4e6c-8542-359f3df1a79cn%40chromium.org.

--

TAMURA Kent
Software Engineer, Google