Sprint 2, review meeting: notes

[ghost]

Wednesday October 29th, 3:00pm @ BA3200

Allen (issue #21)

As Max or Professor Sara, I want to make groups that can be subsets of users for functions like viewing topics that are private etc. [2] [B]

• Implemented and ready to go.

Izzy (Issue #19)

As Max or Professor Sara, I want to be able to view all the topics on the main messageboard view in a table view or list view. [1] [B]
As Max or Professor Sara, I want to be able to edit or delete messages I have posted so that I can correct any mistakes I’ve made. [2] [C]

• Implemented; raw topic dumps are working correctly, edit and delete work correctly without a seperate page.

Benson (Issue #20)

No user story; email verification for registrations.

• Implemented. Note: the verification email is, at present, printed to the console that the server is running on. You can also bypass this by editing the is_active field for the registering user in the admin panel

Austin (Issue #26)

As Max or Professor Sara, I want to make my topics only viewable by certain groups so that I can keep team discussions private. [1] [A/B]
As Max or Professor Sara, I want to join groups, such as courses or teams, so that I can participate in specific discussions. [1] [B]

• Group privacy NYI - see (Issue Private Topics #28)
• Group creation and joining is implemented correctly.

Alec (Issue #22)

As Max or Professor Sara, I want to create and edit a user profile so that other students and professors can quickly find my contact details and other information. [3] [C] extra for this sprint

• Basic implementation is complete, will be implemented in phase 3

Spencer (Issue #27)

No user story: going to attempt to prevent the need for refreshing when new messages are posted.

• Refresh elimination is not implemented - ran into inter-OS library issues.
• Some CSS implemented instead to make things look nicer.

In all, all but one planned user story was implemented; topic privacy did not make it in due to technical issues. Some extra functionality including email registration, user profiles and some CSS made it in from other members.

Overall, our planned sprint was somewhat light on content, based on the completion of extra features.