Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: Document communication principles #104

Open
it33 opened this issue Jan 20, 2017 · 3 comments
Open

Discussion: Document communication principles #104

it33 opened this issue Jan 20, 2017 · 3 comments

Comments

@it33
Copy link
Contributor

it33 commented Jan 20, 2017

We should document our external communication principles, as a draft:

  • Share the right information, at the right time, in the right context to the right audience
  • Speak clearly, kindly, concisely, internationally
  • Celebrate success, alert appropriately on issues

These principles would guide community communication, RDP, blog and marketing. This ticket is to start a discussion.

@it33 it33 changed the title Document communication principles Discussion: Document communication principles Jan 20, 2017
@justinegeffen justinegeffen transferred this issue from mattermost/docs Mar 30, 2020
@BhaswatiRoy
Copy link

Hello @it33
We can document this information in a separate subsection under the "Contributors" section
image
I can work on this!

@cwarnermm
Copy link
Member

Hello @BhaswatiRoy and thank you for your interest in contributing to the Mattermost Handbook! We welcome your contribution. Please feel free to draft a Handbook PR with your updates and assign @justinegeffen as an editor reviewer on the PR.

The navigation pane is defined by summary.md located in the root of the Handbook GitHub repo. Feel free to raise any questions in this PR directly. Thanks!

@BhaswatiRoy
Copy link

Hello @cwarnermm
Thanks for all the information, I have submitted the pr!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants