Servo TSC Meeting June 2023 (2023-06-26)

[mrego]

Date

Monday 26th June 2023 at 15:00 UTC

Agenda

• Status update
• WPT pass rate dashboard
• Sync strategy for Stylo, Web Render and SpiderMonkey
• Embedding API
• Linear commit history
• Linux Foundation
• Outreach
• AOB

[mrobinson]

I think it would be good to add an agenda item about linear git history / enforcing squash squash + rebase merge and experimenting with the GitHub merge queue.

[CYBAI]

Possibly related to merge queue; I wonder maybe it's also worth considering making @bors-servo retry (or GitHub merge queue) to only re-run failed jobs.

(corresponding API at https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#re-run-failed-jobs-from-a-workflow-run)

[sagudev]

I think it would be good to add an agenda item about linear git history / enforcing squash squash + rebase merge and experimenting with the GitHub merge queue.

My two cents on this topic:

I believe linear git history is already implemented in bors https://github.com/servo/homu/blob/d6b918f45b4aadfb43ae4cba5b9b80a4f9c00638/cfg.sample.toml#L73-L74, not sure if it works though.

Now about the merge queue, what would happen to our dear bors. I believe it would be pretty easy to make bors as an alias bot that dispatches merge queue events, to keep old workflow for those who were used to it and provide additional features like try/retry that merge queue does not offer. Rust-Lang is working on RIIR of bors that would be as lightweight as possible and I believe if we switch to GitHub merge queue it could be made as a stateless bot (with some stateful cache).

[Manishearth]

Can this first be discussed on Zulip? I'm not sure if this needs to be discussed at the TSC per se

[emilio]

Sync strategy for Stylo, Web Render and SpiderMonkey

FWIW I'll be a bit late (conflict) but I'm interested in this topic.