The purpose of the meeting is to discuss core WordPress development. This is a working product team meeting, not an open town hall or Q&A session. The focus is on technical issues and release scheduling, and the players are the people who are working on patches for the active core development cycle. Anyone is welcome to attend to keep up with what’s going on in core, but the agenda is generally limited to discussion by active contributors.
Most dev chats begin with a status update from the lead developers, the ui group, and any contributor who is officially assigned to a development task by the lead developers. When that is complete, we address agenda items that have been suggested on the weekly agenda post, with priority given to issues that are holding back development of approved tasks for the current development cycle.
If you are working on a patch for the current release cycle, you are welcome to request a spot on the agenda if you have a concern or need some group brainstorming that has not been adequately addressed by the Trac ticket. If your suggested item is not relevant/not about something going on in the current dev cycle, it will not make it onto the meeting agenda as there is usually a more suitable venue to discuss it.
Time permitting, the dev chat usually ends with an open floor for anyone to bring up any tickets they are looking for additional feedback on.
The proposed agenda is usually made available 24 hours before the weekly meeting so people can review it and decide if there are topics they are interested in attending to discuss.