Date/Location: 31-Mar-2020 at 16:30 in Collaborate Ultra Attendees: Josh F, Jake S, Hayden F, Reinaldy M Start time: 4:30pm End time: 6:00pm

Information Updates/Reminders

1. The next two weeks are going to be about understanding the legacy Battleship code base so that we can plan for the work to fix and improve it.
2. Everyone should be able to use git, github wiki and Trello. Ask for help if that is a problem.
3. We’ll be using toggl.com to keep track of time.
4. The Programming Help Desk ATC620 is available to help us with programming for this unit.

Decisions Needed

(D1) Which team member will create Trello board and invite other team members? Jacob

(D2) Which team member will create Toggl team project and invite other team members (using email addresses)? Josh

(D3) Which team member is responsible for adding the VB.Net code base to the project github? Jacob

(D4) Which team members (can be one or two) are responsible for researching tools that can be used to convert VB code to C# code? Jacob or Aldy

(D5) Which team member is responsible for researching a suitable coding standard to be used for the project?Aldy

(D6) Which team members (can be one or two) are responsible for making a complete list of files with detailed descriptions of what each file is for?Hayden Jacob can help if need

(D7) Which team member is responsible for going through the entire code base to identify obvious TODO, BUG or FIXME comments and put them down in a list? Josh

(D8) Which team member is responsible for going through the entire code base to determine how much existing documentation is available and how useful it is? Hayden

General Items

1. Everyone needs to download the old code and make sure they can run it.

2. Need a Trello board created for this project and team. Actions and other details will be posted there. Columns used need to be decided. See (D1)

3. Need a Toggl team project to track the time the team uses. We need to decide what activities to track. See (D2)

4. Need a github account for this project. (Project from Activity 3.1 can be used if suitable.) Existing code base can be added.

5. Need github wiki pages to document project details. See (D3)

6. Need to find and list functional issues. What works the way it should and what does not? Every team member is responsible for doing this and adding to the list on wiki.

7. Need a list of all the files, and what each file is for (description). Decide where this is stored. Put on wiki. See (D6)

8. Are some files (code or resources) not being used or not needed? Create a list and share on wiki. See (D6)

9. What tools we can use to convert VB code to C# code? See (D4)

10. What coding standards should we use for the project? See (D5)

11. Are there any obvious TODO, BUG or FIXME comments in the code base that we should know about? See (D7)

12. How much of the code has been documented, and once converted what needs to be done. See (D8)

13. A list (on wiki) should be created to keep track of extensions ideas and new features that could be added (not bugs to fix). Do not work on these extensions/features at this stage yet. Every team member is responsible for doing this and adding to the list on wiki.

All the above actions have to be done before next week lab.