-
Notifications
You must be signed in to change notification settings - Fork 22
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
Becoming a TC39 delegate #211
Comments
I won't be in the standards meeting next week, but I obv vote yes on this. If it's approved, and @gibson042 files the onboarding issue, I can onboard Lea very quickly. |
Sure thing. @LeaVerou, can you provide the requested information?
|
@gibson042 Sure, thanks! |
Thanks. I also vote yes, and opened an issue for TC39 marked pending until the OpenJSF meeting. |
+1! |
+1 |
That's |
+1 |
1 similar comment
+1 |
Sweet, we're good! @ljharb @LeaVerou @gibson042 |
Thanks everyone! 🙏🏼 Should I be added here? https://github.com/openjs-foundation/standards/blob/main/MEMBER_REPRESENTATION.md |
Hello,
After some recent discussions, @ljharb suggested it would help if I became a TC39 delegate so I could have better access to TC39 internal channels. This came up recently as we wanted to solicit TC39 input in a couple TAG discussions, but I did not have access in certain private repos that would be best for that. Beyond that, I do have personal interest in participating in TC39 discussions and have filed a couple proposals around ESM recently, so I'd love to be able to participate properly as an OpenJS delegate.
(I became a Standards WG participant in #199 )
The text was updated successfully, but these errors were encountered: