-
Notifications
You must be signed in to change notification settings - Fork 21
Chair Notes Templates
Inbal Levi edited this page Aug 31, 2024
·
34 revisions
These templates use syntax that is compatible with both TWiki and GitHub Markdown, so you can paste them to both the meeting wiki and the Github for paper tracking:
* Lists that start with 3 spaces and use `*` to start items are recognized by both TWiki and GitHub.
__Double underscores denote bold italics text in TWiki and bold text in GitHub Markdown.__
Usage with GitHub issues and the TWiki minutes template:
- Copy everything below the line
## PNNNNRM: DESCRIPTION
into GitHub issues, prepending## YYYY-MM-DD Library Evolution Telecon
. - Copy everything below the line
__Chair:__
into the "Chair Notes" section of the TWiki minutes template.
For simultaneous discussion of multiple papers or subjects without a specific paper:
- Include links for all relevant papers and their GitHub issues.
- Either name the wiki page after one key paper or give it a descriptive name for the topic.
### Summary
should be a few sentences summarizing the discussion.
### Next Steps
should be a summary of the consensus of the room: decisions, guidance, feedback, etc. See templates below.
# ISO C++ Library Evolution Telecon
*Date:* YYYY-MM-DD
*Attendance:*
*
## Agenda
* Administrative:
* Find minute taker.
* Code of Conduct reminder.
* Patent and IP policy reminder.
* Recording policy reminder.
* Zoom name reminder.
* Polling tutorial.
* Electronic polling reminder.
* Mailing list review reminder.
* Meeting reminder.
* PNNNNRM: DESCRIPTION.
## PNNNNRM: DESCRIPTION
[PNNNNRM](https://wg21.link/PNNNNRM): DESCRIPTION
[YYYY-MM-DD Library Evolution Telecon Minutes](http://wiki.edg.com/bin/view/Wg21telecons2024/PNNNN#Library-Evolution-YYYY-MM-DD)
__Champion:__
__Chair:__
__Minute Taker:__
__Start:__ YYYY-MM-DD HH:MM TIMEZONE
Does this paper have:
* Why this facility should go into the standard library?
* Examples?
* Field experience?
* Implementation experience?
* Usage experience?
* Deployment experience?
* Performance considerations (compile time, runtime)?
* constexpr?
* Discussion of prior art?
* Changes Library Evolution previously requested?
* Support for "std::format", "hash", and allocators (if required)?
* Wording?
* Feature test macro?
* Freestanding?
Pros:
Cons:
Open Questions:
Key Insights:
Poll Ideas:
Action Items:
__End:__ HH:MM
### Summary
### Next Steps
LEWG Telecons
LEWGI Telecons
Mailing List Reviews
Chair Guide
- Theory
- Polls
- Checklists
- Templates
- Prioritization
Tracking