The one downside of boltdb is that it can only be accessed from one process at a time due to how the file is opened with exclusive file locks.

To be able to expose the database to more then just the bot interface, a proxy layer is needed. This will be done via the REST API (already implemented).

The remaining work is to convert the bot commands from using the direct query interface to using the RESTful API.

A notification cron is missing to present users with the URL to access the days status reports.

Currently quartermaster runs in the foreground. It should run in the background as a daemon

Go's time.Location{} fails to correctly parse AEST and AEDT which causes these when attempted to default to UTC with an error.

Using pure locales parse correctly from the iana tz file there for Austraila/Sydney automatically corrects to AEST/AEDT.

Automation of the build process and storage of build artifacts is needed.

When we get pinged by this thing, we need to know what format we are supposed to provide our status in. Is it just free text or can we use any special formatting or keywords, or tags?

Are we structuring the text in anyway?

Do we have examples of "good" statuses or "bad" statuses? Does the bot ask you questions to help shape a better standup status report?

Where is this being reported to? How do we view other people's reports? How is this being archived so that we can view past reports?

Unit testing is needed to prevent issues and regressions

The REST API is currently exposed over HTTP and should be moved to HTTPS.

This can be done with a self signed cert, but a valid domain hosting the REST API and LetsEncrypt would be better.

Deployment automation is needed.

This will more then likely be done with Ansible, but the use of docker should be investigated.

Currently the REST API cannot be exposed on the public internet due to it not being secure.

A midleware wrapper similar to https://github.com/abbot/go-http-auth. This will allow us to manage user tokens from the boltdb and lock down access to the REST API to authenticated users/processes.