incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "CodeOfConduct" by AaronFarr
Date Sat, 30 Jun 2007 04:57:14 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 AaronFarr:

The comment on the change is:
changed wording of the licensing guidelines  -- farra

  || 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. ||
  || 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. ||
  || 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 [
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 || Individuals who provide source code and documentation to the ASF should submit a
[ Contributor's License Agreement]. Source code
and documentation must be under the Apache License and include the necessary [
notifications and headers].  ASF project resources, such as code and documentation, must be
maintained on ASF hardware. ||
  || 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. ||
  || 9 || Other libraries included with a distribution may be under a different license but
must be redistributable under the Apache license.||

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message