Meeting minutes
Agenda Review
Action Items
<addison> https://
<addison> #180
<gb> Action 180 publish address formats around the world article for wide review (on xfq) due 2025-08-07
xfq: Done
<addison> close #180
<gb> Closed issue #180
<addison> #178
<gb> Action 178 inquire with tc39 about reviews of specs (on aphillips) due 2025-07-31
addison: Done, got a response from Shane Carr
<addison> close #178
<gb> Closed issue #178
<addison> #162
<gb> Action 162 poll I18N/CSS for new day/time (on aphillips) due 2025-03-25
addison: Got some responses, talka bout it later
<addison> close #162
<gb> Closed issue #162
<addison> #157
<gb> Action 157 write glossary proposal identifying options and next steps for those options (on aphillips) due 2025-02-20
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
<addison> #127
<gb> Action 127 make a list of shared topics of interest between TC2 and W3C-I18N (on aphillips) due 2024-09-30
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #7
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips) due 27 Jul 2023
Info Share
xfq: Published the address formats article for wide review. Got some comments.
Review RADAR Review
<addison> https://
addison: No reviews.
Pending Issue Review
<addison> https://
addison: No incoming panding issus
Write more articles about server configuration
<xfq> w3c/
<gb> Issue 671 Write more articles about server configuration (by xfq)
xfq: I raised this issue ^^
… About how to set up lang negotiation in Apache.
… We have a poorly maintained server techniques page.
… about http-charset, etc.
… There are now more modern frameworks, in addition to traditional servers.
… We could mention them They are useful for developers.
<xfq> w3c/
<gb> Pull Request 672 Add an article on language negotiation in Next.js (by xfq)
<xfq> vercel/
xfq: We should mention some of them. And as an experiment I wrote this ^^
… about next.js
<xfq> https://
<xfq> https://
xfq: Any feedback?
addison: You want to write a bunch of these? Do you want help?
xfq: I want to write more, this is the first one.
addison: And retire the current articles?
xfq: They still apply. I already updated some.
… I want to maintain the page better.
addison: When do you want reviews? In a couple of weeks?
ACTION: addison: schedule topic to review server config articles/materials per 2025-08-07 call
xfq: Maybe one or two weeks. Article is simple.
<gb> Created action #181
addison: I still have a lang neg article I haven't worked on for a while.
r12a: On the next.js article: Where do you store the file and how do you point to it? Seems a different file name fhan in Apache.
addison: It is path-based negotiation.
r12a: We should explain that.
xfq: It says "language path" but I can make that clearer.
… It is usually in the root directory of the project.
r12a: And what if you have other stuff in the URL, e.g., /fr/ab?
xfq: Explaining that may make it very long.
r12a: What would be cool is to have a single example, say with English and French, and see in each article how to do that example, with each method.
… This article would have a link to the other articels that do the same example ina different method.
<xfq> w3c/
<gb> Pull Request 672 Add an article on language negotiation in Next.js (by xfq)
addison: We can invite other people to write articles for their technology, using the same example
discuss next steps with tc39
<addison> https://
addison: Reaction from Shane Carr ^^
… Define tracked repos and labels, similar to how we do with WHATWG.
… Anybody can be a liaison person?
… Their meeting is also on Thursday, later than ours.
JcK: Can we standardize on calling them "ECMA TC 39", because there are other TG 39s.
I18N+CSS
addison: Florian doesn't have time for a i18n+CSS meeting.
<r12a> s/Benticide/Fantasai/
addison: What do we want to do?
<addison> https://
<addison> https://
xfq: Any other people from CSS interested and able to join?
addison: Or do we send somebody to their meeting, who reports back?
addison: More participation in our group would be good. Or we can go back to ad-hoc meetings.
xfq: I won't be able to join the CSS meeting, because of the time.
r12a: And much of their stuff is not relevant to us, if we attend their meeting.
addison: We can try to manage things with labels. And maybe go to their call once a month and arrange with Alan to schedule some issues at the start of the call.
r12a: Seems a useful fallback.
addison: Should I propose that? The existing call on the calendar isn't doing anything.
ACTION: addison: respond to CSS, cancel existing call, propose ideas for future cooperation per today's telecon
<gb> Created action #182
<Bert> s/callback/fallback/
r12a: We should probably monitor their agendas as well.
addison: I use a label on their GitHub issues.
… It would be good if they could also reach out to us if they stumble upon an issue.
… We have to do a lot of polling and there are a lot of groups...
I18N Glossary
addison: We talked about some options. When do you want to talk about it again?
xfq: We didn't have a conclusion, did we?
… Here are the options ^^
… I'm inclined to keep it as a note for now.
… And we could make it a Rec-track when we recharter next time.
… Then aother WGS can link to it without worrying about non-normative references.
addison: There is a bunch of work in there.
… We need to start behaving as if it were normative.
xfq: Make normative and non-normative sections.
addison: I made a list, which could be mnaintained.
xfq: We can use that list as a start.
… I can look into this.
… And start rewriting.
… When we have a normative-like document when we recharter, it will be relatively easyt to republish it.