-
Notifications
You must be signed in to change notification settings - Fork 57
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
Update editors for v2 #246
Milestone
Comments
Current information is that it will just be @mwatson2 and myself as co-editors for the V2 MSE spec. |
8844c2e#diff-3d8aef5368ad0d78966832e7189732dc fixed this issue already. |
Matt,
Although I have been very absent from discussions these recent
months (years!), I am still able to help with editing. You can assign
things to me if you like.
...Mark
…On Tue, Sep 8, 2020 at 2:07 PM wolenetz ***@***.***> wrote:
Current information is that it will just be @mwatson2
<https://github.com/mwatson2> and myself as co-editors for the V2 MSE
spec.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#246 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZ57CZSW2FF3VAJ6DHPMCTSE2MKBANCNFSM4JVNW6LA>
.
|
@mwatson2 - excellent. I've sent a request to setup a triage session for V2 in email. Let's get the ball rolling together (it's been moving, but just on MSE-in-Workers experimental implementation in Chromium, not spec, recently). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I will continue editing. @mwatson2 will continue editing.
We still need to know from MSFT who they will have as their new editor.
The text was updated successfully, but these errors were encountered: