openstack-community team mailing list archive
Mailing list archive
Re: DRAFT OpenStack.org Blog Authors Code of Conduct
I'd propose to add an additional one regarding respect of other's opinions
Articles should be written on the basis of mutual respect of other's
opinions. There are always many different perspectives on how technology can
be used. Blog should accept that different views are to be considered even
if the author does not share them. Communities benefit from sharing,
debating and reflecting rather than discounting and disparaging others'
> -----Original Message-----
> From: openstack-community-bounces+tim.bell=cern.ch@xxxxxxxxxxxxxxxxxxx
> On Behalf Of Stefano Maffulli
> Sent: 01 June 2012 21:50
> To: User Groups Community, OpenStack
> Subject: [Openstack-community] DRAFT OpenStack.org Blog Authors Code of
> Hello all,
> with the current number of authors on the community blog I think it's a
> idea to make sure we all have a clear understanding of what it means to
> 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
> Below is a draft: please review it and give your opinion. Add your
> and if there are no clear oppositions, we'll remove the draft from
> DRAFT OpenStack.org Blog Authors Code of Conduct
> OpenStack.org Blog is the asset owned by the community and a platform
> to share thoughts, ideas, reports and news about OpenStack. All the
> blog posts have the responsibility to respect this common space while
> grateful for the opportunity it represents.
> If you are an author of OpenStack.org blog it means that the community
> you to give voice to the community as a whole. Writers accept these simple
> * Prefer facts to opinions: be always aware that what you publish will be
> by thousands of people and that your opinion is not necessarily that of
> whole community. 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
> Blog is not the place to publish a company's press release.
> * Contribute to the commons: our blog is licensed under the terms of
> 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.
> Mailing list: https://launchpad.net/~openstack-community
> Post to : openstack-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-community
> More help : https://help.launchpad.net/ListHelp
Description: S/MIME cryptographic signature