Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upcoming Servo issue triage meeting on August 5 2024 #95

Closed
2 of 6 tasks
gterzian opened this issue Jul 22, 2024 · 2 comments
Closed
2 of 6 tasks

Upcoming Servo issue triage meeting on August 5 2024 #95

gterzian opened this issue Jul 22, 2024 · 2 comments
Labels
triage-meeting Issue triage meeting

Comments

@gterzian
Copy link
Member

gterzian commented Jul 22, 2024

Where: https://meet.jit.si/ServoTriage.

When: 10:00 AM GMT, August 5 2024 (Europe and Asia friendly, we can later alternate with a US friendly time if needed).

What: any issue one wishes to triage.

Who: anyone is welcome, but if there are no issues to discuss the meeting will be canceled.

Please express your interest to attend and note the issue(s) you would like to triage(which can be one someone else already brought up).

Actions points:

  • @Taym95 to continue working on Speedometer integration(hand-over from @CYBAI for now)
  • @wusyong to look further into embedder -> window messaging, also how it relates with creating new windows, and looking into using webdriver for messaging.
  • @gterzian and @Taym95 to look at Fix ordering of documents servo#32574
  • @wusyong to start work on readablestream bytes reader and controller(or hand-off to someone prior to holiday).
  • @Taym95 to start work on TODOs for readablestream default reader controller.
  • @wusyong on holiday

New issues we can discuss:

@Taym95
Copy link
Member

Taym95 commented Aug 5, 2024

@gterzian
Copy link
Member Author

gterzian commented Aug 5, 2024

Action points:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-meeting Issue triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants