Status Updates

[rpghawke]

20220213 attendees: bakhtawar macdugrpg lukeskyjogger trevorstroxel First part of meeting discussing various job application and status updates, then reviewing their launch menu layouts, and making suggestions.

Then discussed github README.md and markdown, trevorstroxel will be updating that to be more in sync with bcirpg.com front page as he learns Markdown. bakhtawar macdugrpg trevorstroxel will be working on their menu updates from review and suggestions made.

Then discussed basic Waterfall and Agile project management concepts and Gantt chart versus Kanban board, aslo Scrum and Scrummaster, and Standup meetings do's and don'ts. Then discussed getting used to using the Project Kanban here https://github.com/RPG-Research/bcirpg/projects/1 and also how to convert a Kanban task into an "Issue" so it can be assigned, tracked, commented. Each week we'll review the Kanban and Issues boards and make sure each has the correctly updated status. Will practice what "Standup" meetings before going into more full meeting each week to help everyone get practice with the "right way" to do a standup meeting, versus the all the common "wrong way".

Next week will be the final revision of each person's separate incarnation of the front menu. We will then discuss what we like from each and merge the ideas into tasks for a single main menu, then assign subtasks for each person to work on that front menu toward completion, and learning how to work on code cooperatively rather than in separate silos.

Then once we're all happy with the main menu and sign off as completed, we'll assign tasks to each developer, their choice, for the next sections when you click that main menu, and onward from there, using the Kanban and Issues boards heavily.

We also discussed how critically important it is to leave prolific comments, not be afraid to share your coding struggles, because the will help others to help you if you are currently struggling, or help others in the future when they are struggling and see your detailed explanation of the struggle, attempts made, results from each attempt, and the final results that worked and any thoughts about what to do next time.

This helps everyone grow more quickly and well-rounded as developers, and makes for a much strong team connection as well. Sent everyone on physical break at end of hour, then have everyone resume their work on their main menu coding (And Trevor on the README.md https://github.com/RPG-Research/bcirpg ) as assigned issue #24 24. Happy Coding!