Groot v1.0 / v 1.5

[narendasan]

Considering the amount of stability and scaling issues we are running into I consider what we have something like a v0.x. I think we need to spend a bit of time hardening services and in general introduce a tick/tock development cycle between new features and services and hardening what we have (so vX.5 is at the end of the feature cycle and v(X+1).0 is the hardening cycle). General operation question I would like input on is what the cadence of this cycle should be? Also planning for hardening and feature cycles should happen at the same time after the end of the last feature cycle.

What should be included in the next hardening cycle:

Devops:

• Dockerize all components
• Finish arbor groot separation
• At least some CI for each repo Add CI for each Groot v1 repo #41
• Add licenses to all repos
• Make any private repos public (that should be public)
• Full setup of the beta. dev. and acm. servers
• https://github.com/acm-uiuc/groot-nginx-config/issues/1
• Create a list of services List of services #38
• Method to rebuild code in docker containers Update dockerfiles to use volumes to manage source #42
• Unified secrets file

Bugs / Revisions:

• Credits exchange rate groot-desktop-frontend#89
• Better 502 page A better 502 page #17
• Update references to Caffeine to merch groot-desktop-frontend#93
• Increase padding between intranet services  groot-desktop-frontend#84

What should be include in the next feature cycle:

Features

• Improve the usage of the quotes database groot-quotes-service#4
• Better 404 Page groot-desktop-frontend#56
• Better solution for Sponsors groot-desktop-frontend#16
• Add links to groups to join in the intranet groot-desktop-frontend#96
• Edit Gigs groot-gigs-service#2
• https://github.com/orgs/acm-uiuc/projects/1#card-2328731

New Services

What needs to be added/removed?

• Unified sponsor store Unified sponsor service for display and desktop #27

[narendasan]

Things from the backlog to discuss:
iCard service?
Hardware service (may want to wait until merch and jetson ready)
Better handling of mailman (I don't want to migrate but I want something with less spam and a bit easier configuration)

[narendasan]

Another that might be interesting is having a server that auto deploys pull requests before merge (kind of like CI)

This would let us fiddle with the site with out having to spinup a local instance

[narendasan]

Note go will not rebuild (pushing that back until arbor support)