-
Notifications
You must be signed in to change notification settings - Fork 3
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
2025-01-09 meeting agenda #80
Comments
Unfortunately unable to attend today. No recent updates on the Sockets API but planning to circle back around on it in a couple of weeks. The tl;dr is that we need to define the roadmap for next steps on moving it forward. |
We should talk about onboarding delegates and invited experts to TC55, including some of the non-Ecma regulars in these calls. |
Why is there any concern with winterTC hosting runtime keys? |
There is no concern - it just doesn't fall cleanly into the TC55 scope we discussed with Ecma. A registry is not a spec, and Ecma does not have a template for registries as of yet, so we all concluded it would be easier to do this in the OpenJSF package manfiest space. |
TCs aren’t limited to hosting specs or registries, they can also have “any document you want”. |
Please add topics as comments
The text was updated successfully, but these errors were encountered: