GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
TODO: This is designed to be the ultimate membership management suite for UCC. Signups are electronic and automatic, data is able to be conveniently stored in the member database and some of it is even automatically validated.
Stuff to do
-----------
- Important structural TODO:
- Design database schema for rolling memberships
- Build member-facing initial registration form
- Build door-facing pending membership approval form
- Design database schema for rolling memberships [done]
- Build member-facing initial registration form [done, but really ugly]
- Build door-facing pending membership approval form [done]
- Build member-facing post-approval (or post-email-confirmation) registration form
- Build member-facing renewal form
- Stuff to do after structural bits
- Administrative user authentication via LDAP/AD
- Administrative user authentication via LDAP/AD [done]
- Automatic member account creation (after membership approved)