Development

To contribute, please fork the repository and create pull requests.

The master branch should contain stable releases, tagged with the release number (1.0.0, etc).

The develop branch is where active development should take place.

Please use pull requests for new features.

Available at PERM.

TODO

• Fix login buttons dropdown
• Deploy to Heroku EC2
• Add testing framework
• Get dynamic attendance data from user object
• Attendance chart should be simple values removed if window is too small
• Connect to Mailchimp Mailgun
• Ensure all datetimes are generated for Mountain Time
• Should use Bootstrap grid system on /shifts so it collapses on mobile
• Add unit, integration, and regression tests!!

Minimum Viable Product

• Users should be able to sign in with email and password
• Users should be able to sign out
• Users should be able to see their upcoming shifts
• Users should be able to see their past shifts
• Users should be able to see the shifts for the current week
• Users should be able to drop a shift
• Users should be able to pick-up a shift
• Users should be able to see their attendance stats
• Users should be able to email other users when dropping a shift
• Administrators should be able to create new users
• Administrators should be able to create shifts for a student

Version 1.1

• Users should be able to see a calendar view of all shifts

• Users should be categorized as [student, command, nurse, admin]

• Shifts should be categorized as [student, command, nurse, admin]

• Users should be able to pick up shifts that match their role

• Users should be able to reset their password

• Users should be able to upload a profile picture

• /users/:id and /shifts should be unified, with functionality based on current user

• Administrators should be able to change a user's role(s)

• Users should have to confirm that they attended a shift

• There should be a Study resource for study info

• Persistent chat log

• Administrators can specify user starting dates

• Fix time difference calculation of the calendar

• Admins should confirm deleting a shift (could mis-click)

• Users must have at least a first and last name

• User email login should be case insensitive

• Changing user start date breaks user stat counts

• Users should be able to reset their password without logging in

• When an admin drops a user from a shift, the shift can't be picked up

• Command users should be able to pick up regular student shifts

• Should be able to correct and reverify an email address