I've slowly been moving the various pieces of the ODK infrastructure out of UW into a central location backed by one account and sticking as much as I can in repos and automating with ansible. I'm aware of the following servers for the community...
Domain names and DNS are handled by AWS we use POBox to do our mail routing.
@yanokwa has admin access to all the community machines and @W_Brunette has access to all the passwords to the various services. Nafundi has been picking up the cost of these machines.
UW continues to run https://opendatakit.org and that's going to change eventually. My dream there would be some statically hosted site like the docs site, but more on that later.
Proposed next steps
I love dev ops, but I think it'd be prudent to transition my administration of these machines to a community member who wants to do/learn dev ops. Before I can do that, it'd be good to get some sort of plan of attack and volunteers to take this work on.
My high-level goal is to standardize on our infrastructure and reduce the administrative load so it's mostly automated and easy for newbies to maintain. In the places where we can use a turnkey service, we should because it's easier to get a few hundred dollars a year for hosting than it is to find great dev ops volunteers.
Here's my tentative plan.
- Start an infrastructure repo (or repos) with some sensible structure.
- Move and various server code we have into that repo and secure sensibly.
- Standardize on operating systems, scripts, and add SSL support to all the things.
- Include documentation on the various pieces of infrastructure.
- Reduce the number of servers we use (e.g., xlsform, build, slack might be able to run on one machine)
- Do a little dance, because we are winning!
There is some question about who we trust with the keys to this kingdom, but I think first we should see if there is anyone interested in becoming a contributor to ODK in this way. My gut is that this is a one time push and then it's mostly maintenance...