List of use cases

[mirdaki]

This should be an inclusive list of all the use cases we need to meet. Please feel free to suggest more (and I will create an issue for each respective feature).

• Sign in an existing member, have it correlate with the closest meeting
• Add a new member, and sign them into the current meeting
• A student can sign in as a guest
• Let project leads update the project description, URL, and active status
• Submit an expense to be processed
• Allow treasurer to approve and reimburse an expense
• Allow officers to create a new event with time, location, event picture, etc
• Allow officers to modify any part of an existing event
• Let project leads add members to their project
• Let officers get data on sign-ins
• The events should be kept in sync with the Google Calendar and vice-versa
• Project members should be automatically kept updated based of commits/GitHub teams information
• Generate some text about upcoming events for email or Facebook announcements (or actually be able to send out announcements via the List-serve and Facebook)
• Officer should be able to store weekly announcements anyone can access
• Once approved by an officer, a member should have a user created for them on the server
• Resource text should be kept up-to-date with the Club's resources repository (maybe vice-versa)
• Allow officers to remove members (which would affect them signing into GitHub and the server)
• The database should be easily backup-able and redeploy-able by an admin
• Allow Secretary to add meeting notes to events
• Sync meeting notes between the Club Documents repository and vice-versa
• Support self-hosted documentation such as (MKDocs)[https://www.mkdocs.org/] for officer documents, general club resources, and projects documentation

We will need some sort of authentication that works for both human sign-ins (e.g. via a web portal) and for bots that we will use on Discord, for GitHub, etc. All CRUD operations should be supported for the right officers. Regular members should be able to sign in and read most data.