Skip to content

Communications & editorial member service guide

Publication thresholds & channels, supports internal content releases and external content publishing.\

#Ops_editorial in Zulip

Internal document release process

Every internal and external document version must include a change log and list of contributors.

  • Change log
  • Contributors

Guiding policy

  • Two or more people ought to own responsibility for a document.
  • Accountable (primary)
  • Responsible (secondary, etc.)
  • While everyone’s feedback is welcome, our goal isn’t that we need every single person involved to give a go or no-go. What might a number of people to determine a stop vs a go may be important
  • Traffic lights: green yellow red
  • Provide deadline at least [X] business days to review/approve object, share/boost in a Zulip channel (see decisions agreement)
  • Those accountable and responsible should seek feedback.
  • Everyone can give feedback, authoritative votes falls to whom (plural) is responsible
  • How do we ratify that this is done and official (see decisions agreement)

Storing final versions of policy documents

  • Publishing workflow
  • Track in a versioned environment
  • We want to be able to track change history, who’s involved/attribution

Informal docs

All EAR members are encouraged to create and circulate internal documents, RFCs, etc.

External document release process

Editorial

Material for external release (separate process)

  • External EAR comms need to be reviewed and approved by the EAR steering group and project committee.

Out of scope

Internal iteration

  • Anyone can propose new things within the group.
  • Suggestion: Draft a quick proposal outlining the problem, opportunity, audience voice/tone and purpose/rough outline of why a policy document may provide value. Circulate it for informal review. If you’d like, reach out to a colleague(s) for private review before sharing in a public channel.

Editorial is subject to the operations agreement.