The "My Team" tab is available when the user is not logged in, so on production when a user goes to it, it indicates that a client-side error occurred.

Expected Behavior: The My Team tab only appears when the user is logged in AND the user is in the competition

Competition Teams

Users can create and join teams for a competition, and the submission is attached to this team.

Requirements

• A logged in user can join a competition, becoming a participant
• A teams page lists all teams
• Teams have a max of 4 people
• A participant may switch from a one-participant team to a new team by fulfilling the above conditions
• A participant may leave a competition, but this action is irreversible to enforce commitments to teams
• To switch teams, one of the following must happen:
  • a participant must submit a join request and (a member of) the team must accept the request
  • the team (member) must invite the participant and the participant must accept the invite
• Currently joined competitions show up at top of home page for a user

Software Design

Schema Changes

• submissions table -> teams table as an object property:

• New table: participants:

Indexes: by_user, by_team

With this normalized database design, switching and joining teams is simple and efficient.

Competition Participation.pdf

Subtasks

• #12
• #15
• #16

Competition Hosting and Management

Description

Requirements

Software Design

Schema Changes

State Diagram.pdf

Subtasks

Create Posts
Read beethovons list
Update Beethovons
Delete Beethovons (after clicking)

Submissions in Gallery

Description

Requirements

Software Design

Schema Changes

State Diagram.pdf

Subtasks

Team Collaboration

Allow users who have entered the competition to find and collaborate with teammates. (Front-end team commitment enforcement)

Requirements

• A competition participant can view possible teammates: formed teams and participants
• The team list allows a competition participant to switch teams as described in #10
  • The teams list is sorted in ascending order of team size (one-person teams appear first)
• When making a join request, the requestor may put a message that will be viewed in the team's dashboard
• Each competition participant can view a dashboard only visible to his teammates containing
  • team chat
  • join requests
  • invitations, the status, and the people involved (who invited and who is being invited)
• Teammates can chat with each other in a chat only visible to his teammates
  • Chats are plaintext messages and links
• Any teammate can invite a participant from the teams list
  • Invitations can be made with a message that is viewable by the team and the potential joiner
• When making both join requests and invitations, the user is reminded visually to include contact information. This is a temporary requirement until join request chats are implemented

Software Design

Schema Changes

New table: messages

Indexes: by_team

The _creationTime built-in column should be used for this table.

[12] Team Collaboration State Diagram

Cross Chats

Ability for teammates to chat with someone they invited or who requested to join (each a "team switcher") the team.

Requirements

• Two participants in the same competition on different teams may send private messages ("direct chat") to each other in a chat window for the purpose of deciding whether to switch teams
  • To initiate a private chat, one participant invites and the other must accept.
• All participants of a team and a participant in the same competition but on a different team may send messages in a group chat window for the purpose of deciding whether to join the team ("group chat")
• These chat windows are accessible from a list of all of the team switcher chats, which appear under the Find Teammates tab

Software Design

Schema Changes

New table: direct_chats

New table: group_chats

New table: direct_messages

New table: group_messages

Rename table: messages --> team_messages