incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "CodeOfConduct" by CraigRussell
Date Fri, 29 Jun 2007 01:54:48 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by CraigRussell:
http://wiki.apache.org/incubator/CodeOfConduct

The comment on the change is:
typographic and/or grammatical changes (mostly)

------------------------------------------------------------------------------
  
  THIS IS A DRAFT DOCUMENT FOR DISCUSSION PURPOSES ONLY. 
  
- The Apache Software Foundation creates and maintains open source software products for the
public benefit utilizing a collaborative, meritocractic approach to software development.
Our products are developed by a diverse community of volunteers, most of whom use our software
products in the course of their own daily lives. Our development discussions are held over
public mailing lists. Everyone is invited to join the discussion so long as the usual courtesies
of [http://en.wikipedia.org/wiki/Netiquette email netiquette] are observed. 
+ The Apache Software Foundation creates and maintains open source software products for the
public benefit utilizing a collaborative, meritocractic approach to software development.
Our products are developed by a diverse community of volunteers, a large number of whom use
our software products in the course of their own daily lives. Our development discussions
are held on public mailing lists. Everyone is invited to join the discussion so long as the
usual courtesies of [http://en.wikipedia.org/wiki/Netiquette email netiquette] are observed.

  
  In addition, we wish to emphasize that while the foundation embraces the spirit of civil
disagreement, we do not sanction personal attacks or the posting of off-topic content. 
  
   * As an organization devoted to creating software of the highest quality, we agree to agree
and to disagree -- as strongly as need be -- without crossing the boundary into personal attacks
or the posting of off-topic content.
  
-  * The foundation defines personal attacks as "criticizing the coder rather than the code".
It is acceptable to criticize an idea, it is not acceptable to criticize the person suggesting
the idea. The foundation lists must be a safe place where developers can brainstorm without
fear of being insulted or flamed. 
+  * The foundation defines personal attacks as "criticizing the coder rather than the code".
While it is acceptable (indeed, encouraged) to criticize an idea, it is not acceptable to
criticize the person suggesting the idea. The foundation lists must be a safe place where
developers can brainstorm without fear of being insulted or flamed. 
  
-  * The foundation defines off-topic content as anything included or linked that is:
+  * The foundation defines off-topic content as anything included or linked that:
-    * Being used to abuse, harass, stalk or threaten a person or persons
+    * Is used to abuse, harass, stalk or threaten a person or persons;
-    * Libelous, defamatory, knowingly false or misrepresents another person
+    * Is libelous, defamatory, knowingly false or misrepresents another person;
-    * Infringes upon any copyright, trademark, trade secret or patent of any third party.
+    * Infringes upon any copyright, trademark, trade secret or patent of any third party;
-    * Violates any obligation of confidentiality
+    * Violates any obligation of confidentiality;
-    * Violates the privacy, publicity, moral or any other right of any third party
+    * Violates the privacy, publicity, moral, or any other right of any third party; or
     * Contains editorial content that has been commissioned and paid for by a third party.
  
- Since most of the foundation's mailing lists are unmoderated lists open to the public, we
ask all of our subscribers to help us observe these guidelines. First, by following the guidelines
in your own posts. Second, by bringing the guidelines to the attention of anyone who violates
one of them. And, third, by ignoring or deleting the posts of subscribers who refuse to observe
the guidelines ("Don't feed the trolls"). 
+ Since most of the foundation's mailing lists are unmoderated lists open to the public, we
ask all of our subscribers to help us observe these guidelines. First, by following the guidelines
in their own posts. Second, by bringing the guidelines to the attention of anyone who violates
one of them. And, third, by ignoring or deleting the posts of subscribers who refuse to observe
the guidelines ("Don't feed the trolls"). 
  
  These guidelines were adapted from the [http://blogher.org/community-guidelines BlogHer
Community Guidelines].
  
@@ -42, +42 @@

  || 5 || A project's primary web site and mailing lists must be maintained on ASF hardware.
Resources maintained elsewhere are not ASF resources, even if maintained by individuals who
happen to be ASF committers. ||
  || 6 || Project source code and documentation must be donated to the ASF under a [http://apache.org/licenses/index.html#clas
Contributor's License Agreement]. Donated source code and documentation must carry the ASF
copyright and be placed under the Apache License. Code and documentation donated to the ASF
must be maintained on ASF hardware. Obtaining a non-exclusive ASF copyright on all material
in the ASF repository is encouraged. ||
  || 7 || A PMC member can veto a product change with a technical or legal justification.
||
- || 8 || A release must include the ASF source code being released, binaries are optional.
A release vote must be on the actual bits that comprise the release, preferably already digitally
signed by a release manager. An ASF release must be approved by at least three members of
the PMC and by a majority of the PMC members voting. Approving a release is a development
decision. A release cannot be vetoed. ||
+ || 8 || A release must include the ASF source code being released; binaries are optional.
A release vote must be on the actual bits that comprise the release, preferably already digitally
signed by a release manager. An ASF release must be approved by at least three members of
the PMC and by a majority of the PMC members voting. Approving a release is a development
decision. A release cannot be vetoed. ||
  || 9 || Other libraries included with a distribution may be under a different license but
must be redistributable under the Apache license.||
  || A || The PMC chair/Project VP must submit regular status reports to the ASF board. The
PMC chair is not the project's "leader". ASF projects do not have "lead" developers. Decisions
are made jointly by the PMC. ||
  || B || [http://tinyurl.com/mw7t6 Author tags] in source code are discouraged but permitted
if a PMC so prefers. ||
@@ -90, +90 @@

  
  || '''Motto''' || '''Core Value''' ||
  || Put community before code. || collaboration ||
- || Let them that do the work make the decisions. || self-determination ||
+ || Let they that do the work make the decisions. || self-determination ||
  || If it didn't happen on a mailing list, it didn't happen. || transparency ||
  || Merit never expires. || sustained interest ||
  || Critique our code, not our coders. || netiquette ||

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message