The goal of this template is to make the process of communication easier and smoother in the event of an Emergency.
Include a brief statement of the identified issue at hand, a clear detailed statement of the objective and/or the key message.
Include a detailed description of key stakeholders and user groups involved. Break down users into sub-categories and highlight existing stakeholders:
Example:
- (a) Client teams
- (b) Mining Pools
- (c) Exchange
- (d) Node operators
- (e) dApps
- (f) Users
- (g) etc.
Include a detailed message explaining the purpose of this communication, the plan, and answers to some potential FAQs such as if there is an immediate plan of action. If there is not an immediate action plan, make sure to communicate when a plan will be developed, and who will be developing it, etc.
- Yes or No
- (a) Immediate Actions to Take
- (b) Establishing Partnerships (Audit/Security, Comms, etc.)
- (c) Mid-Course Evaluation and Correction
- (d) Constant Updates
- Provide an FAQ list or a link to an FAQ page
- Provide an estimated time for when the next update will occur:
- <tentative date / time>
Examples:
- The best way to communicate regarding Ethereum announcements is using the Ethereum Blog.
- The quickest way to communicate an issue or announcement is via Twitter or the Ethereum Cat Herders Medium.
- Ethereum Magicians - for discussion. It is a key source and hub for the discussion of major changes / process improvements happening within Ethereum for contributors (developers) and also an easy place to reference the conversation at a later date.
- AllCoreDevs Gitter - Good for immediate response and discussion about emergency issues at hand as well as changes/improvements but has a limited user base (catered to core devs only and does not reach the broader community).
- Ethereum Reddit - A great resource for reaching active users and the broader community memebers within Ethereum.