My understanding of communication guidelines is that they would apply to project members communicating on any topic. I see this as separate from contributor guidelines which are there to help anybody make a code contribution. My preference would be to start a separate document, although a new section in the code of conduct could also make sense.

@itrharrison the hierarchy you proposed makes sense to me. Should we start a google doc for all members to develop this together, similar to how we worked on the code of conduct?

Comments from @bnord in #138:

Communication guidelines will help us communicate fluidly and transparently. All participants knowing how we communicate is essential for trust pervading and persisting.

• where we talk about different topics
• how often we talk about topics

@itrharrison the hierarchy you proposed makes sense to me. Should we start a google doc for all members to develop this together, similar to how we worked on the code of conduct?

Given the hierarchy above, does it make sense for this to be done through a draft PR? I appreciate it is harder for people to cleanly 'suggest' in that form, and that the discussion may be different if it takes place in public.

Perhaps you're right! I expect the document will be relatively short, simple and uncontroversial so drafting it on GitHub should be fine.

Reviewed on 22/11/22 and should be revised to completion as soon as possible.