Posting Etiquette (Where to Ask)

All deputies are added as authors on make.wordpress.org/community. In general, posting etiquette can be described simply as, “Post to the blog if it is something all the deputies should know (or if you are asking a question that would benefit all deputies to know the answer), and if it is a sensitive situation, be thoughtful with your language.” Some people wonder if they are allowed to post certain things, or what things are appropriate, or which things belong on the blog vs. in Slack or SupportPress. This page is intended to answer these questions.

 

There is a policy I’m not sure about.

First, pop into Slack to see if anyone can answer the question. If not, post your question as a new blog post on make/community. If yes, and there is not documentation on the policy, post to make/community and summarize the policy in question as you know it and suggest we confirm this is correct and add it to the handbook. If yes, and there is already documentation that you just overlooked, no need to post about it.

There’s something odd/awkward/unpleasant going on with a specific WordCamp or meetup.

When weird stuff is going on, it is a good idea for all the deputies to know about it so no one talks at cross-purposes. These things should be included in the daily updates comments on days when you volunteer, but if it is something big that needs a decision with group backing, go ahead and write a new post about it. Be respectful but specific in the language you use to describe the issue — vague allusions will not help anyone understand what is  going on.

I want to know if a bill got paid.

Superdeputies have access to the payments dashboard, and can check the status there. If you have access, go ahead and check. If you do not, ping a superdeputy in Slack and one of them can check for you. If no one is in Slack, send an email to support@wordcamp.org.

Deputies: What other situations might have you wondering if you should post or not? Leave a comment on this page and we will continually update with more scenarios as requested.