With the current number of authors on the community blog I think it’s a good idea to make sure we all have a clear understanding of what it means to have an account on such visible community asset. I think it would be good for the whole community to have a brief, clear, understandable code of conduct for all existing authors and for the future ones. We discussed on our community team and we came up with the OpenStack Blog Authors Code Of Conduct below. We’ll publish this together with other community policies (like the OpenStack Event policy) in the next days: add your comments below or send them to the community team.
OpenStack.org Blog is the asset owned by the community and a platform where to share thoughts, ideas, reports and news about OpenStack. All the authors of blog posts have the responsibility to respect this common space while being grateful for the opportunity it represents. As a writer you should write articles respecting other’s opinions, even if you disagree. The OpenStack Community will benefit from sharing, debating and reflecting rather than discounting and disparaging others’ thoughts. Remember that as an author of OpenStack.org blog, the community trusts you to give voice to the community as a whole.
Writers accept these simple principles:
- Prefer facts to opinions: be always aware that what you publish will be read by thousands of people and that your opinion is not necessarily that of the whole community. Try to stick to facts, like reporting the result of a meeting, announcing upcoming community events, describing technical achievements.
- Disclose, don’t promote: it’s good to let people know that a company is contributing to OpenStack, sponsoring an event and such but the OpenStack.org Blog is not the place to publish a company’s press release or other type of commercial offering message.
- Contribute to the commons: our blog is licensed under the terms of Creative Commons Attribution Share-alike version 3 unported. Pay attention to the license of any material you add to the blog, make sure it’s released under compatible terms.