2023-11-02 Meeting

[lucacasonato]

We're meeting at 14:30 UTC today, as usual. Please add agenda topics below:

• Venue
• Common Minimum API progress
• Clarify scope (Clarify the scope of the community group www#36)

[lucacasonato]

• Clarify scope
  • No opposition, accepted
• Change venue
  • Summary on the background:
    • see Tracking issue: consider ECMA TC / W3C WG to publish standards #58
  • Background on this
    • Intellectual property: we can be sure that our published documents are correctly licensed
    • Allows us to actually publish standard documents from a recognized body
    • may increase trust in the work we do
  • Possible venue change
  • Dan proposes ECMA
    • Andreu: what is the bar for becoming an Invited Expert?
    • Dan: this is generally possible, but it is less inclusive.
    • Andreu: patent policy requires legal names - this can pose inclusivity issues.
    • Dan: this can be worked around, for example in tc39 legal names are only know to a very limited number of people that have to deal with the legal work related to Invited Experts / members. Not known to members in general.
  • Some discussion about WinterCG (community group) vs TC/WG and a standards body
    • Luca: I think there is a place for both, especially because a lot of the work we do is destined to end up in a different standard bodies existing specifications (fetch, crypto, etc). The CG would continue to hold all meetings and incubate ideas. Technical work related to standardization could then happen in the relevant upstream bodies, or our own TC/WG for first-party standards we'd like to publish (e.g Sockets or common minimum).
    • Owen: the Web Components CG at W3C operates in this fashion, and it works well. This is something we should consider too.
• Common minimum api
  • How to get Node.js more actively involved?
  • Some discussion on navigator.userAgent
• Node TSC x WinterCG meeting
  • @legendecas will schedule this, look for an issue with a Doodle on the admin repo soon.