Being a bit curious to try out the current best practice of how to structure
Go projects I reshuffled the stuff to closer match the advice from:

https://peter.bourgon.org/go-for-industrial-programming/#structuring-your-code-and-repository

This CL contains the basic datatypes for the rotang project together with
functions to convert the legacy JSON rota configurations into the new
configuration type.

Bug: 845549
Change-Id: I61544c7da49aeb3096cdbe289d52fb766b3fdac2
Reviewed-on: https://chromium-review.googlesource.com/1126695
Reviewed-by: Tiffany Zhang <zhangtiff@chromium.org>
Commit-Queue: Ola Karlsson <olakar@chromium.org>
8 files changed
tree: 25e274c5dc1e8144273b64203a9e620fb4b5a8b9
  1. pkg/
  2. Makefile
  3. OWNERS
  4. README.md
README.md

Rota-NG

This is the home of the Rotation Manager-NG Design Doc.

The goal is replace the current Python script generating the Sheriff rota with this Go AppeEngine service. This to have a better base for running/managing the service and future developments