Attendees need to be able to submit their projects. We will support project submissions as a link to a git repository.
The project "description" will be extracted from the repo's README and cached on the server. This file must be named README or README.md or README.txt and must be a plain text file.

The file will be cached on the server and then loaded whenever it is requested. The content of the README will be periodically updated afterwards.

The database will need to associate the following:

• A project name
• The project git repo
• The cached project README (as a file)
• (future) The project image banner

Watershed needs a CI/CD pipeline, using GitHub Actions. Refer to the setup for the main website and Atlas.

We need unit/integration tests for the back end. There are two possible approaches (at least one, could be both):

• Unit tests with Mocha
• Integration tests with Postman

A user's Discord username should be saved to their profile for display. This should be the username#xxxx one.

• Save their username on sign up/link
• Provide some mechanism for people who have already linked a Discord account. Perhaps check it on each login and provide an endpoint that can be called to trigger the update.

• Users should be able to create an account with Discord.
• Users should be able to sign in with their Discord account (and this should behave the same as username/password sign-in).
• Users should be able to link their Discord account with their cuHacking account after creation.

Users must be able to submit registration details for the event.

The registration must collect the following fields:

• First Name
• Last Name
• Pronouns
• Email (which could differ from the email the user registered with)
• Level of Study (High School, College, etc.)
• Program
• Short answer questions (3 max)
• Resumes
• # of hackathons attended
• Type of hacker (Front end, Mobile, Eng, etc.)
• Personal site URL

A user can only register once (need some way to check if user has already registered). A user must be authenticated to submit a registration.

Export CSV of submissions for judging.
The CSV should include:

• Project ID
• The project name
• Project URL (in the submissions gallery)
• Video demo link

Do a build of all services to ensure everything compiles.

Run tests (if any).

Add endpoints to receive announcement content from an admin console (must be appropriately authenticated) and then dispatch them where necessary.

Primarily, they will be dispatched to the cuHacking discord bot (via a webhook), but could also consider sending them out over the browser notification API.

Access the watershed-discord service and assign users their roles after they link their discord accounts.
The role(s) to be assigned should be configured by the configuration file.

This should be a separate endpoint from auth/discord/link, the reason being that users will need to accept the code of conduct prior to being assigned a role(s) so the process can't be entirely automatic. This also saves us the trouble of handling the problem where a user wasn't a member of the guild when trying to link initially.

• [] CRUD endpoints for Challenges (for sponsor and organizer use)
• [] Link Sponsor Challenges to submissions

• Hook up Mailgun on prod
• Add code to send email on complete registration
• Create email template

STORE: active question for each track

4 tracks

POST
Start

{
   userId: string,
}

Return 200 / 400 if has linked account

POST
Switching tracks

{
  userId: string,
  track: 0-3,
}

POST
submit question

{
  answer: string
  userId: string,
}

return 400/200 if the answer is correct, also return name of the part of the snowman

GET
Current question

{
  userId: boolean
}

return 400/200 if they have an active question. Return if they are complete all questions in the track, or all questions in the game.

{
   imageUrl: string,
   questionContent: string
}

Testing the discord bot

Users will need to be able to form teams for the event.

Constraints:

• Teams can have a maximum size of 4 members (and only 3 member invites at a time)
• A user can only be part of one team
• Users must be able to join and leave teams.
• Teams can be named
• Team members should be invited to the team
• Invites should be cancellable
• A user can not remove another team member
• All members of a team have the same level of privilege in managing the team.
• Teams can not be explicitly deleted. They should only be deleted if all members have left the team.

The User entity needs better email validation. Class-validator probably offers this somewhere. If not, a custom validator can be built with some library or a regex.

Add a column to the submissions table that relates to the challenges to indicate that a submission has won that challenge.

The API needs to have mailing support built in:

• Endpoints for sending mail
• Password reset hooked up with emailing
• Email on registration?

Attendees should be able to add a "banner" image with their project submission (#12) that will be displayed on the submissions/judging pages.

We can either use a standard filename pattern to search for images to extract from the repo (e.g. banner.xyz) or extract images from within the repo README file.

• CRUD operations for Hacker Profiles on Users (e.g. socials, bio, etc...)

Socials

• Filter and validate links?
• Linkedin
• GitHub / GitLab?
• Personal Website
• Figma / Dribbble / Behance
• Twitter?
• Email? (opted-in)

Other

• Basic bio (280 character max)
• List of interests?
• Discord (separate from socials)
• School
• Name
• Pronouns
• Team

• Users should be able to create an account with GitHub.
• Users should be able to sign in with their GitHub account (and this should behave the same as username/password sign-in).
• Users should be able to link their GitHub account with their cuHacking account after creation.

• The API needs endpoints for users to login with a username and password.
• The existing Users implementation should be altered to hash passwords.
• These accounts should also be used to authenticate the endpoints.

GET:

• Hackathon end time
• User's details
• Points
• Teams
• Announcements
• Schedule (N latest)

• Basic CRUD
• Get next n events
• Users can favourite events

Add server side validation of max file size for uploads. Allow this to be configurable via the .env file.