Found this old post that is worth adding here for reference I believe it stemed from that one day back in the day where enforcement got stuck on after a spork and nobody could get a hold of evan to disable it and we didn't have a block accepted for like 5 hours or something...?
https://dashtalk.org/threads/todays-issues-and-future-handling-of-crises.893/#post-5472
I agree that we need better communication for the future.
I couldn't get a complete hold of what was happening yesterday because I was travelling when the price alarms started buzzing on my phone. I'm quite calmed and just waited to get some info, but for some people it must have been tough... You can't imagine how frustrating is being a train with a bad connection and 30 pages of bitcointalk to read
Some thoughts:
-I'm also ok with giving all my data to the group for this kind of days.
-A map of the team's time zones and languages would be nice to have.
-We need an internal channel. A dedicated IRC channel is ok, but I think I would prefer something with more prevalent notifications. There are many apps we can use that can be installed on phones without the need to disclose the number to the others if someone prefers to keep it private.
-We should distribute responsibilities over the different communication channels. It is impossible to be at the same time on bitcointalk, darkcointalk, twitter, irc... We need to think on some way to identify us as sources of reliable semiofficial information.
-A support ticker system would be nice, but we need to be sure that we can handle it. The workload can be quite high. Maybe in a first phase something only open to those running darkcoin services (Evan has a mailing list, we could get to them easily).
-For planned events like this hard fork we need to plan ahead and reach out proactively. We can make a list on Asana and coordinate there easily draging items from one group to another and assigning them to team members(I've made an example project there for this).