PlanetUbuntuEditorialPolicy

Differences between revisions 1 and 21 (spanning 20 versions)
Revision 1 as of 2007-05-02 03:20:04
Size: 2747
Editor: S010600502c03205f
Comment: create spec
Revision 21 as of 2007-05-29 07:12:52
Size: 3471
Editor: 80-47-141-162
Comment: rewriting for clarity
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
 * '''Launchpad Entry''': UbuntuSpec:foo
 * '''Created''': [[Date(2005-10-25T15:45:54Z)]]
 * '''Contributors''': CoreyBurger
 * '''Launchpad Entry''': UbuntuSpec:ubuntu-planet-editorial-policy
 * '''Created''': 2007-05-01
 * '''Contributors''': CoreyBurger, MatthewEast
Line 9: Line 9:
Planet Ubuntu, an aggregate of community and Canonical employee blogs about Ubuntu, needs a clear editorial policy, to deal with issues of Canonical to community interactions, content disputes and the like. This spec attempts to create such a policy, for eventual approval by the Community Council. Planet Ubuntu, an aggregate of blogs by Ubuntu members, needs a set of loose guidelines to resolve content disputes and to help with clear communication after an issue has arisen. This spec attempts to create such a policy, for eventual approval by the Community Council.
Line 13: Line 13:
With the early May censorship of Planet Ubuntu by Canonical to prevent early disclosure of the Dell deal, it was made apparent that the current laise-faire method of Planet editorial policy was not working. In that incident, Canonical removed two blogs by community members, as well as one by an employee. In addition, future content disputes or other company to community interactions might require action, issues which should have a clear policy for dealing with. Occasionally issues arise in relation to posts syndicated on Planet Ubuntu. There are two types of such issues:

 1. Confidential information is leaked (generally unintentionally) by a Canonical employee or subsequently a community member which could give rise to difficulties in Canonical's relationship with a business partner.
 1. Material is posted which (generally unintentionally) offends another community member.

In each case it is necessary to have clear processes for resolving the issue as appropriate.
Line 21: Line 26:
Larry runs an Ubuntu business and one of his employees whose blog is syndicated on Planet Ubuntu bas, either accidentally or not, leaked confidential information. He wants to be able to remove that blog from Planet Ubuntu in a confidential manner. Larry runs an Ubuntu business and one of his employees whose blog is syndicated on Planet Ubuntu was, either accidentally or not, leaked confidential information. He wants to be able to remove that blog from Planet Ubuntu in a confidential manner.
Line 29: Line 34:
Covers planet.ubuntu.com Covers [http://planet.ubuntu.com Planet Ubuntu].
Line 33: Line 38:
Policies need to be created for the following situations: === Confidential Information ===
Line 35: Line 40:
* A Canonical employee posts confidential information
* A community member blogs about a rumour based on outside information
* A community member blogs about a rumour based on an employee blog
* Another companies employee posts confidential information on their blog and thus planet
* Somebody objects to the contents of a blog post
Internally, Canonical should develop policies that ensure that all employees are aware of what information is confidential, and what is not.

Where a legal issue arises in relation to confidential information, the [https://launchpad.net/~canonical-sysadmins Canonical sysadmins] may be contacted for an emergency removal of a post. It is imperative that where a post is removed, the relevant user is contacted and respectfully explained the reason why - miscommunication is the main problem in such situations.

=== Inappropriate Posts ===

The Code of Conduct applies to all actions by Ubuntu members, including posting to their blogs. Guidance should be added to the PlanetUbuntu page to ensure that this is clear.

Where a community member is offended by content on another member's blog, the best approach will generally be to attempt to resolve the issue peacefully through respectful discussion. In the event that it is not possible to resolve the issue, the CommunityCouncil can mediate the problem.
Line 43: Line 52:
== BoF agenda and discussion == == Comments ==

See ["/talk"]

Summary

Planet Ubuntu, an aggregate of blogs by Ubuntu members, needs a set of loose guidelines to resolve content disputes and to help with clear communication after an issue has arisen. This spec attempts to create such a policy, for eventual approval by the Community Council.

Rationale

Occasionally issues arise in relation to posts syndicated on Planet Ubuntu. There are two types of such issues:

  1. Confidential information is leaked (generally unintentionally) by a Canonical employee or subsequently a community member which could give rise to difficulties in Canonical's relationship with a business partner.
  2. Material is posted which (generally unintentionally) offends another community member.

In each case it is necessary to have clear processes for resolving the issue as appropriate.

Use Cases

Jane is a community member and wishes to write about rumours of a pending Canonical announcement. She is concerned about being censored, given the previous experience with the Dell deal. She wants reassurance that provided her information comes from outside sources, she is free to post about such deals.

Mark runs Canonical and wants to make certain that future deals are not jeopardized by accidental release of information by his employees. He wants to be able to remove his employees blogs without concerns of censorship

Larry runs an Ubuntu business and one of his employees whose blog is syndicated on Planet Ubuntu was, either accidentally or not, leaked confidential information. He wants to be able to remove that blog from Planet Ubuntu in a confidential manner.

Sally has posted a followup to another blog post by an employee who leaked information. She wants to know what is going to happen to her blog post, now that the employees blog post has been pulled.

Eric objects to some content on their blog, content which does not violate the Code of Conduct. He wishes to know if there is a way and a venue to have a discussion about this content.

Scope

Covers [http://planet.ubuntu.com Planet Ubuntu].

Implementation

Confidential Information

Internally, Canonical should develop policies that ensure that all employees are aware of what information is confidential, and what is not.

Where a legal issue arises in relation to confidential information, the [https://launchpad.net/~canonical-sysadmins Canonical sysadmins] may be contacted for an emergency removal of a post. It is imperative that where a post is removed, the relevant user is contacted and respectfully explained the reason why - miscommunication is the main problem in such situations.

Inappropriate Posts

The Code of Conduct applies to all actions by Ubuntu members, including posting to their blogs. Guidance should be added to the PlanetUbuntu page to ensure that this is clear.

Where a community member is offended by content on another member's blog, the best approach will generally be to attempt to resolve the issue peacefully through respectful discussion. In the event that it is not possible to resolve the issue, the CommunityCouncil can mediate the problem.

Outstanding Issues

Comments

See ["/talk"]


CategorySpec

PlanetUbuntuEditorialPolicy (last edited 2008-08-06 16:27:05 by localhost)