openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r827283 - in /websites/staging/openofficeorg/trunk/content: ./ openofficeorg/list-conduct.html
Date Sat, 28 Jul 2012 14:09:41 GMT
Author: buildbot
Date: Sat Jul 28 14:09:41 2012
New Revision: 827283

Staging update by buildbot for openofficeorg

    websites/staging/openofficeorg/trunk/content/   (props changed)

Propchange: websites/staging/openofficeorg/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Sat Jul 28 14:09:41 2012
@@ -1 +1 @@

Added: websites/staging/openofficeorg/trunk/content/openofficeorg/list-conduct.html
--- websites/staging/openofficeorg/trunk/content/openofficeorg/list-conduct.html (added)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/list-conduct.html Sat Jul 28
14:09:41 2012
@@ -0,0 +1,208 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+ 2.0
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+<meta name="google-site-verification" content="wIHUbgA-JO5PaJHpR5jeI8N9E2y2iF94o4oUwpaAdk8"
+<link href="/openofficeorg/css/ooo.css" rel="stylesheet" type="text/css">
+<title>List Conduct Guidelines</title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<script type="text/javascript">
+  var _gaq = _gaq || [];
+  _gaq.push(['_setAccount', 'UA-30193653-3']);
+  _gaq.push(['_trackPageview']);
+  (function() {
+    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '';
+    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+  })();
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache (incubating)" href="">
+      <img id="logo" alt="Apache (Incubating)" src="/openofficeorg/images/300x100_dj_trans.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="">
+      <img id="asf-logo" alt="Apache Incubator" src="/openofficeorg/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  <div id="sidenav">
+    <h1 id="general">General</h1>
+<li><a href="/openofficeorg/index.html">About</a></li>
+<li><a href="/openofficeorg/downloads.html">Downloads</a></li>
+<li><a href="/openofficeorg/license.html">License</a></li>
+<li><a href="/openofficeorg/trademarks.html">Trademarks</a></li>
+<li><a href="/openofficeorg/press.html">Press</a></li>
+<h1 id="community">Community</h1>
+<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
+<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/openofficeorg/social.html">Social Networking</a></li>
+<li><a href="">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language</a></li>
+<li><a href="">Planning
+<li><a href="/openofficeorg/people.html">People</a></li>
+<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
+<h1 id="development">Development</h1>
+<li><a href="/openofficeorg/source.html">Source Code</a></li>
+<li><a href="/openofficeorg/bug-tracking.html">Bug Tracking</a></li>
+<li><a href="/openofficeorg/qa.html">Quality Assurance</a></li>
+<li><a href="/openofficeorg/translate.html">Translation</a></li>
+<li><a href="/openofficeorg/website-local.html">Website</a></li>
+<li><a href="/openofficeorg/security.html">Security Reports</a></li>
+<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
+<li><a href="">Project Blog</a></li>
+<li><a href="">Incubation
+<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<li><a href="">Website</a></li>
+<li><a href="">Donations</a></li>
+<li><a href="">Sponsorship</a></li>
+<li><a href="">Thanks</a></li>
+  </div>
+  <div id="contenta">
+    <h1 class="title">List Conduct Guidelines</h1>
+    <h1 id="1-respect-one-another">1. Respect one another</h1>
+<p>Discussion is the cornerstone of a project like this and the sharing of viewpoints

+is crucial, as is understanding and accepting that many views will differ from 
+your own. By all means debate rigorously and defend your view point stoutly, but 
+avoid abrasive dialogue and personal attacks. </p>
+<p>Give leeway to people who do not have English as a first language. Pause before

+taking insult, and pause before responding. There is a difference between 
+robust discussion and steamrollering. Civility is paramount. 
+Manners cost nothing; we are all capable of self-moderation, and of being aware
+of our conduct.</p>
+<h1 id="2-remember-the-apache-openoffice-mission">2. Remember the Apache OpenOffice
+<p>“To create, as a community, the leading international office suite that will
+on all major platforms and provide access to all functionality and data through open-component
based APIs and an XML-based file format.”</p>
+<p>The AOO project is a place for finding open-source solutions to document creation

+and consumption. We believe in making AOO freely available because we are the sort
+ of people who welcome diversity in others, creativity of all sorts and who enjoy 
+finding the best in all situations.</p>
+<h1 id="3-be-nice">3. Be Nice</h1>
+<p>Not only are there lots of people on this list whose first language is not English

+there are some busy readers who, by necessity, have to read things quickly. If 
+other list members are telling you they do not understand what you wrote, or take 
+your innocent phrasing in a poor light, take it as a signal that your writing 
+style is too idiomatic or too technical (unlikely but possible) for others to 
+follow easily. This does not necessarily indicate that you are mean, wrong and 
+bad, so just be nice and reword the passage. Assume people are not in 
+"attack mode." We are all on the same team here.</p>
+<h1 id="4-dont-respond-when-you-are-angry">4. Don't Respond When You are Angry</h1>
+<p>Assuming people are not in attack mode means that if you think they are, just now,

+then probably you are just misunderstanding their point. Ad hominem attacks,
+ e.g., "You are too dumb to get this," are a sign that you yourself may not have
+ a good-enough handle on the issue to explain your point clearly.</p>
+<h1 id="5-relax">5. Relax</h1>
+<p>Always remember that unless there is a <em>darn</em> good reason, nothing
gets decided 
+at the ASF in less than 72 elapsed hours, so your reply can wait until morning. 
+You might even get lucky, and when you check back somebody else will have posted 
+either what you wanted to say, or something close enough that you can work with it.</p>
+<p>Remember that the members of a community mailing list will get to the list when

+they can. Most of us do this in our spare time, and in different time zones. 
+Perhaps the rule of thumb could be to respond no more than once per hour, or 
+once per day, to any given thread. The highest frequency of responses does not 
+necessarily “Win” in a community of equals. The most concise and useful post 
+tends to win, because furthering the dialog and advancing the community's goals
+ is what we all desire.<br />
+<p>Of course, not all threads are decision-making threads.  Some are debugging or 
+problem solving.  In those cases, the opposite advice applies.  If you know the
+ answer, and can state it briefly, then do so.</p>
+<h1 id="6-get-to-the-point">6. Get to the point</h1>
+<p>Write as tersely as possible and edit down as much possible so that other people

+who are just as busy as you may quickly get your point without ending up 
+defensive. Of course, balance is needed. Do not let brevity get in the way of 
+providing enough information. Remember that people must understand your post in 
+order to understand your point.</p>
+<h1 id="7-consider-trimming-the-post-to-which-you-are-responding">7. Consider trimming
the post to which you are responding</h1>
+<p>People who read emails on small screens are not the only ones who are frustrated
+ by picking important new information out of tons of stuff they have already read.
+ To trim a post, one simply remove any parts of the post to which one is replying 
+that are not important to understand ones reply. If the response to one of these 
+posts is, “What? I do not understand,” then it may be that too much of the context
+ may have been removed.</p>
+<h1 id="8-respect-the-private-lists">8. Respect the private lists</h1>
+<p>What happens on a private list, stays on that list.  There are only a few private

+lists on the project, e.g., the PMC list and the Security Team.  But you might on 
+occasion interact with other private lists, like legal-internal or 
+infrastructure-private.  Anything you read in a private list is confidential and
+ not to be spoken of, or copied to people who are not members of that private 
+list.<br />
+<p>Note:  the other side of respecting the private lists is to use them only when 
+necessary, and for for topics that require confidentiality, such as information 
+that deals with security vulnerabilities, personnel matters, user private 
+information, etc. </p>
+<h1 id="9-there-are-going-to-be-exceptions-to-the-rule">9. There are going to be exceptions
to the rule</h1>
+<p>All of these guidelines are subject to sanity-testing. A person posting illegal

+material on any or Apache OpenOffice list will be reported to the 
+appropriate authorities and will not be able to complain that their list privacy 
+has been violated. Ramping up to a release, there are a lot of postings at high 
+frequency. Sometimes it unavoidably requires a long post to say what needs to be 
+<h1 id="more-useful-stuff">More Useful Stuff</h1>
+<li><a href="">Apache Tips for
Email Contributors</a></li>
+  </div>
+  <div id="footera">
+    <div id="poweredby">
+      <p><img src="/openofficeorg/images/feather-small.gif"/></p>
+    </div>
+    <div id="copyrighta">
+      <p>
+  Copyright &copy; 2011-2012 The Apache Software Foundation Licensed under the <a
href="">Apache License, Version 2.0</a>
| <a href="/openofficeorg/contact.html">Contact Us</a> | <a href="/openofficeorg/terms.html">Terms
of Use</a>
+      </p>
+      <p>
+  Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ and the seagull logo are registered trademarks of The Apache Software Foundation.
+  Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+      <p>
+  Apache OpenOffice is an effort undergoing incubation at The Apache Software Foundation
(ASF), sponsored by the Apache Incubator.
+  Incubation is required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and
+  decision making process  have stabilized in a manner consistent with other successful ASF
projects. While incubation status is
+  not necessarily a reflection of the completeness or stability of the code, it does indicate
that the project has
+  yet to be fully endorsed by the ASF.</p>
+    </div>
+  </div>

View raw message