During the conference, an attendee can ask to have a comment recorded in the devlog. Just say "comment box", and mfiano will log it here. If it is something that should be discussed and addressed in the future, mention for it to be added to the Backlog instead.
These items will carry over to the next meeting's log, unless discussed and expunged or deferred as appropriate. Items marked as resolved this meeting will not be carried over.
[IN-PROGRESS] #2 Lift utilities (mfiano)
[IN-PROGRESS] #3 Write a "Getting Started" guide for the manual (psilord)
[IN-PROGRESS] #4 Construct GitHub Pages website and repo for automatic docs building/deployment (mfiano)
[IN-PROGRESS] #5 Create a new project skeleton generator (psilord)
[DEFERRED] #1 Game time shift (mfiano)
[DEFERRED] #6 Go over some comments from a new user (psvennson)
Schedule the date and time of the next meeting.
[NEW] items at the top of the list in the Backlog section, either marking them as
[DEFERRED] if we will not work on them, or marking them as
[IN-PROGRESS] if we will be working on them this stream or independently offline before the next meeting.
Review and respond to any issues or PRs on GitHub for the Virality repository.
Discuss status of backlog item #3, #4, and #5, which were expected to be worked on offline.
Resume work on item #2 (a small amount each meeting, and possibly in between meetings).
Begin new work
Work on a
[NEW] item in the backlog.
Determine if any
[DEFERRED] item should be addressed for the remainder of this meeting.