openstack-community team mailing list archive

[Tim Bell <Tim.Bell@xxxxxxx>]

Fully supportive of the new wording. It covers exactly what I was trying to 
convey, i.e. express what you think but respect that others may feel 
differently.

Tim

> -----Original Message-----
> From: Stefano Maffulli [mailto:stefano@xxxxxxxxxxxxx]
> Sent: 07 June 2012 19:02
> To: Tim Bell
> Cc: User Groups Community, OpenStack
> Subject: Re: [Openstack-community] DRAFT OpenStack.org Blog Authors
> Code of Conduct
>
> Thank you Tim, I've incorporated your thoughts in the preamble. I'm
> publishing this now on the blog itself and if no further comments are
> received, I'll assume the policy is in place (until we need to change it, of
> course).
>
> 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.
>     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.
>
> On Sat 02 Jun 2012 11:24:47 AM PDT, Tim Bell wrote:
> >
> > 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'
> > thoughts.
> >
> > Tim
> >
> >> -----Original Message-----
> >> From:
> >> openstack-community-bounces+tim.bell=cern.ch@xxxxxxxxxxxxxxxxxxx
> >> [mailto:openstack-community-
> bounces+tim.bell=cern.ch@lists.launchpad.
> >> net]
> >> 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 Conduct
> >>
> >> Hello all,
> >>
> >> 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.
> >>
> >> Below is a draft: please review it and give your opinion. Add your
> > comments
> >> and if there are no clear oppositions, we'll remove the draft from
> >> http://wiki.openstack.org/Website/AuthorsCodeOfConduct.
> >>
> >> thanks,
> >> stef
> >>
> >>
> ==========================================================
> ======
> >> ==========
> >> DRAFT OpenStack.org Blog Authors Code of Conduct
> >>
> >> 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.
> >>
> >> If you are an author of OpenStack.org blog it means that 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.  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.
> >>
> >> * 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.
> >>
> >>
> ==========================================================
> ======
> >> ==========
> >>
> >> --
> >> 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

Attachment: smime.p7s
Description: S/MIME cryptographic signature