web-platform-tests / web-platform-tests/rfcs
Contact points for each browser
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 110
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/web-platform-tests/wpt/issues/39309 got filed while @jgraham was OOO; with WebTransport being enabled, Firefox started timing out all the WebTransport infrastructure tests (https://github.com/web-platform-tests/wpt/pull/39345) because it didn't have the server running (https://github.com/web-platform-tests/wpt/pull/39322).
Now, it seems like the ideal solution to this would be to start running with the server and update the expectation, but I loathe to make such a change as I'm not someone who deals with Gecko's CI, which would presumably also be affected by this change.
However, with @jgraham out I don't actually know who to ask about that. Sure, I could ask other admins (especially @zcorpan, who seems to be the only other Mozilla employee in the group), but I'm pretty sure @zcorpan isn't the right person.
I wonder if it makes sense to have some teams in the WPT org, like "web-platform-tests/firefox-ci" or similar with enough people that one person being out doesn't leave me (who frankly knows too many people in the browser space) not knowing who to ask?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue 39309 and pull requests 39345 and 39322 to understand the WebTransport timeout and CI context. Then review the proposal for browser-specific teams or contact points; done would be an agreed, documented ownership structure for questions when a browser contact is unavailable.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100