tpac-breakout-bot
commented
8 months ago Thank you for proposing a session!
You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.
Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.
Session description
The move to Github for tracking our work - including actions, and various horizontal review tasks - has been a boon for productivity, and transparency. However, it can be hard to keep up to date with all the work that's going on, especially for TF facilitators, WG chairs, people who take part in horizontal review activities, and people who find the command line more accessible.
With a hat tipped to Tracker, our long-time action management tool, APA WG has been exploring the possibilities for presenting the rich and robust GitHub process on the command line. But this isn't just for APA WG; it's intended to be of use to TF facilitators and WG chairs across W3C.
Session goal
Demonstrate our command-line work tracking tool, and seek feedback from potential users
Session type
Breakout (Default)
Additional session chairs (Optional)
No response
IRC channel (Optional)
nu-tracker
Other sessions where we should avoid scheduling conflicts (Optional)
10
Instructions for meeting planners (Optional)
Meeting must start between 0700 and 2100 UTC.
Agenda (link or inline) (Optional)
Link to calendar (Optional)
Calendar entry
Meeting materials (Optional)