After some discussion in our last ONFIRE meeting it appears that our most basic needs comprise of:

1. A real-time editor for in-the-moment information management
2. A technical platform that allows us to manage immediate incident-related action items as well as any follow-up items post-incident
3. A predictable place for "finished" incident documents to live for later consumption

The rest are "nice-to-have" integrations of varying importance (like notifying people on IRC/Slack).

Our current setup uses Google Docs for 1, Phabricator for 2, and Wikitech for 3. I propose we start with these first three requirements, see what solutions work better than our current one and then work our way down with the integrations/niceties. We've been circling the wagons trying to come up with some sort of integrated approach but tend to just keep coming back to a slightly altered version of the present one.

A recurring pain point is information duplication/transference: Synchronizing the same information between our bug report, our real-time knowledge/graphs, our IRC, and the final Wikitech article is painful.

Already-rejected ideas:

• Remove Wikitech and just have the Google doc be the final resting place of the document (Too easy to lose/change the doc)
• Remove Google docs and just use IRC for the real-time communication (IRC is too primitive to easily collect and maintain all of this info)
• Remove Wikitech and use the ticket description instead (Too difficult to locate the ticket)

The feedback I've heard in the meetings suggests to me that nobody wants to leave the current phab/gdocs/wt setup (and if we did it'd be pretty much just replacing one component with one very similar).