QT4 CG Meeting 080 Agenda 2024-06-04/05
Agenda index / QT4CG.org / Dashboard / GH Issues / GH Pull Requests
Agenda
This meeting will be a face-to-face meeting hosted by XML Prague in Prague, CZ. We will meet from 09:00CEST (07:00GMT, 08:00BST, 03:00EDT) to 18:00CEST on Tuesday 4 June and Wednesday 5 June.
The meeting will be in the room NB 468. This room is in the same building (the so called "Nová budova"/"New Building") as the main conference sessions. There are lifts and stairs in front of the cloak room. Use lift to go to the floor 4. Then use corridor on your right side, room is almost at the end of the corridor.
(We have used this room in past for XSLT and XProc meetings, so it may be familiar to some of you.)
XML Prague has generously agreed to provide refreshments, including lunch.
At 17:00CEST (15:00GMT, 16:00BST, 11:00EDT) each day, we will attempt to join a Zoom session using the usual call-in details. If anyone unable to attend the face-to-face joins the call, we’ll attempt to summarize the decisions made during the day and solicit feedback.
See the meeting logistics page for details about the Zoom session.
1. Administrivia
1.1. Roll call
1.2. Approve the agenda
1.3. Approve minutes of previous meeting
Minutes of the previous meeting.
1.4. Next meeting
This meeting is planned for 4-5 June in Prague, CZ. The following meeting is scheduled for 11 June.
Or do we want to skip a week after the face-to-face?
1.5. Review of open action items [0/6]
(Items marked [X] are believed to have been closed via email before this agenda was posted.)
[ ]
QT4CG-063-06: MK to consider refactoring the declare item type syntax to something like declare record[ ]
QT4CG-077-03: MK to add a note about document order across documents[ ]
QT4CG-077-04: MK to review inconsistencies discovered in review of #1117[ ]
QT4CG-078-01: MK to make the default for normalize-newlines backwards compatible.[ ]
QT4CG-078-02: MK to update the prose oftransient{}
to use the word “should”.[ ]
QT4CG-079-01: WP to seek expert advice on hashing functions.
2. Technical Agenda
Rather than attempt to construct an agenda in advance, the chairs propose that we begin the meeting Tuesday by reviewing our status, who is actually attending, and constructing an appropriate agenda by reviewing the issues, pull requests, and other sources.