QUIC Team Meeting
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
@nodejs/quic @pimterry @martenrichter @Ethan-Arrowood
There are some details of the QUIC/HTTP3 API surface that we need to work through, and details of finishing up the implementation that could benefit from us having a regular call.
I've created a poll for us to use to figure out the best times. I got tired of using doodle with the ads and limits, so I created an alternative (https://github.com/jasnell/quando) ...
It requires github auth to respond... Please provide your availability. It's set for a specific week but the idea is to fill in the date/time slot that works best for you for a meeting every two weeks (for now)
https://quando.jasnell.me/p/8756cd92-e81b-478c-a562-12fd348febaf
Contributor guide
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
This issue names no source files, tests, or implementation entry points. Start by reviewing the QUIC/HTTP3 API-surface and implementation work referenced in the issue, then use the linked quando poll to provide availability; done means the meeting schedule and follow-up work are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100