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 TedHusted
Date Sat, 02 Jun 2007 12:39:18 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 TedHusted:
http://wiki.apache.org/incubator/CodeOfConduct

The comment on the change is:
Grammar changes to community guidelines. Other changes to project guidelines. 

------------------------------------------------------------------------------
- Some ASF Members have indicated a wish to draft a [http://en.wikipedia.org/wiki/Code_of_conduct
code of conduct]. This area is intended to help volunteer collobarate on an ASF Code of Conduct
and related documents. Whether or not the foundation should have such a code has not been
determined.
+ Some ASF Members have indicated a wish to draft a [http://en.wikipedia.org/wiki/Code_of_conduct
code of conduct]. This area is intended to help volunteers collaborate on an ASF Code of Conduct
and related documents. Whether or not the foundation should have such a code has not been
determined.
  
  THESE ARE DRAFT DOCUMENTS FOR DISCUSSION PURPOSES ONLY. 
  
@@ -8, +8 @@

  
  THIS IS A DRAFT DOCUMENT FOR DISCUSSION PURPOSES ONLY. 
  
- The Apache Software Foundation creates and maintains open source products for the public
benefit utilizing an open, collaborate 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 [http://en.wikipedia.org/wiki/Netiquette
email netiquette] are observed. 
+ The Apache Software Foundation creates and maintains open source products for the public
benefit utilizing an open, collaborative 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. 
  
- In addition, we wish to emphasize that while the the foundation embraces the spirit of civil
disagreement, we do not sanction personal attacks or the posting of off-topic content. 
+ 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. 
  
-  * The foundation embraces the spirit of civil disagreement. 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 boundaries into personal attacks or the posting of off-topic
content.
+  * The foundation embraces the spirit of civil disagreement. 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. 
  
@@ -24, +24 @@

     * Violates the privacy, publicity, moral or any other right of any third party
     * Contains editorial content that has been commissioned and paid for by a third party.
  
- Since the foundation mailing lists are 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 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"). 
  
- These guidelines were adopted and adapted from the [http://blogher.org/community-guidelines
BlogHer Community Guidelines].
+ These guidelines were adapted from the [http://blogher.org/community-guidelines BlogHer
Community Guidelines].
  
  = Project Guidelines =
  
- Each ASF project is entitled to develop and post their own guidelines. As an aid to developing
individual project guidelines, here is a set of general project guidelines and practices.

+ Each ASF project is entitled to develop and post their own guidelines. As an aid to developing
individual project guidelines, here is a set of general project guidelines and ASF practices.

  
- || 0 || Individuals compose the ASF. Projects must be managed in a collaborative, meritocratic
way, so that new volunteers are encouraged to join the project group, and so that the volunteers
doing the work are the individuals who make the decisions. PMC members are encouraged to nominate
qualified contributors as new committers. ASF Members are encouraged to nominate qualified
committers as new members. Given sufficient time and sustained interest, the set of committers
should equal the set of PMC members, and the set of PMC members should equal the set of ASF
members. ||
- || 1 || Merit never expires.||
+ || 0 || Individuals compose the ASF. Our projects must be managed in a collaborative, meritocratic
way, so that new volunteers are encouraged to join the project group, and so that the volunteers
doing the work are the individuals who make the decisions. ||
+ || 1 || PMC members are encouraged to nominate qualified contributors as new committers.
ASF members are also encouraged to nominate qualified contributors as new members. Given sufficient
time and sustained interest, the set of committers should equal the set of PMC members, and
the set of all PMC members should equal the set of ASF members, which together constitute
the ASF Community. ||
+ || 2 || Merit never expires. "Emeritus" members and committers are welcome to become active
participants again, with all prior rights and privileges intact. ||
- || 2 || The mailing lists are a project's only venue for the conduct of business. All development
discussions must occur on the project's public mailing lists, or be summarized to the lists,
and the lists must be archived. Development support products, like version control systems,
issue trackers, and wikis, should log changes to a public mailing list. Comments posted to
a list through development support products are a normal component of development discussions.
||
+ || 3 || The mailing lists are a project's only venue for the conduct of business. All development
discussions must occur on the project's public mailing lists, or be summarized to the lists,
and the project lists must be archived. Development support products, like version control
systems, issue trackers, and wikis, should log changes to a public mailing list. Comments
posted to a list through development support products are a normal component of development
discussions. ||
- || 3 || The project's private list may only be used to discuss pre-disclosure security problems,
pre-agreement discussions with third parties that require confidentiality, nominees for project,
project committee or Foundation membership, or personal conflicts among project personnel,
and nothing else. Posts to a private list are considered confidential and must not be quoted
on public lists without the permission of the author. ||
+ || 4 || The project's private list may only be used to discuss pre-disclosure security problems,
pre-agreement discussions with third parties that require confidentiality, nominee candidates,
or personal conflicts among project personnel, and little else. Discussing development issues
on a private list is taboo. Posts to a private list are considered confidential and must not
be quoted on public lists without the permission of the author. ||
- || 4 || 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. ||
+ || 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. ||
- || 5 || Project source code and documentation must be donated to the ASF under a 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. ||
+ || 6 || Project source code and documentation must be donated to the ASF under a 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. ||
- || 6 || A PMC member can veto a product change with a technical or legal justification.
||
+ || 7 || A PMC member can veto a product change with a technical or legal justification.
||
- || 7 || 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 members voting. 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. ||
- || 8 || Other libraries included with a distribution may be under a different license but
must be redistributable under the Apache license.||
+ || 9 || Other libraries included with a distribution may be under a different license but
must be redistributable under the Apache license.||
- || 9 || The PMC chair/Project VP must submit regular status reports to the ASF board. ||
+ || 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. ||
- || A || Author tags in source code are discouraged but permitted. ||
+ || B || Author tags in source code are discouraged but permitted. ||
  
  
- = Apache Mottos =
+ = ASF Mottos =
  
  THIS IS A DRAFT DOCUMENT FOR DISCUSSION PURPOSES ONLY. 
  
- This is a list of various Apache mottos, classic and contrived, designed to express the
essential principles and practices of the Apache Culture. This is an initial draft, and in
its final form, each motto would include a paragraph or three of explanation. 
+ This is a list of various ASF mottos, classic and contrived, designed to express the essential
principles and practices of ASF Culture. This is an initial draft. Ideally, each motto would
include a paragraph or three of explanation. 
  
   * Let them that do the work make the decisions.
   * Merit never expires.
@@ -59, +60 @@

   * Give karma where karma is due.
   * Sometimes it's easier to ask for forgiveness than permission.
   * If it didn't happen on a mailing list, it didn't happen.
-  * Don't cross post from a private list to a public list.
   * Don't feed the trolls.
   * Thanks for volunteering.
  

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


Mime
View raw message