After running a local version, I thought I would add some notes about my experience: - This seemed really cool since we have various processes and this would l

After running a local version, I thought I would add some notes about my experience: - This seemed really cool since we have various processes and this would let us both document and operationalize the processes. Things like: add/change user permissions or create a new vm/container, etc. We could make it easy to show where documentation is and what should be updated. - Installation is simple, but it is hardcoded to authenticate against Github and look and see if you are a member of the 18F group. If not, you are refused access. Changing the group is just a simple edit to the app.js file, but changing authentication from Github to another source would require adding another passport config file into api/ (as far as I can tell), and possibly additional dev. - The checklists are all json files, there's no UI for creating the checklist. In fact, there's no CRUD for checklists at all, they are flatfile managed with a text editor. This is not ideal, but building an editor might not be too rough. The main thing is that checklist creation is a developer operation. - There is no UI for associating checklists with role/users or grouping the checklists. Everyone sees all of the checklists and then self-selects which checklist they want to add to their plate. It looks like the tasks are all user-specific, so you couldn't have a checklist that was divided up amongst a team, it is all single-user focused. I suppose you could create a dummy team user that multiple people had access to, but that seems icky. Similarly, while you can see other user's tasks, you can't take one of their tasks and help them out by doing it. - There's no context for the tasks. If you had two new employees or two VMs to provision, you would have to do them one at a time. Adding a second checklist while you have a first in progress just gives you a pile of duplicated tasks that have no context as to which initial action they are related to. You can add a note to the initial checklist assignment like "SE3: Jane Doe" which will give some context for that assignment, but I don't see where that is related to the tasks. If the tasklist showed "Checklist Name - Checklist Note" in the table, then at least you could keep them separate. Otherwise, I would love for this to work. I am in academia where we have two problems that this impacts: 1) we have lots of bureaucracy 2) we have lots of turnover in IT staff because we pay poorly. For both of these reasons, having a checklist tool would be fantastic. Devs: please comment!