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 "ApacheProjectMaturityModel" by BertrandDelacretaz
Date Tue, 20 Jan 2015 14:15:33 GMT
Dear Wiki user,

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

The "ApacheProjectMaturityModel" page has been changed by BertrandDelacretaz:
https://wiki.apache.org/incubator/ApacheProjectMaturityModel?action=diff&rev1=18&rev2=19

Comment:
Typos and minor tweaks

  
   CD40:: The full history of the project's code is available via a source code control system,
in a way that allows any released version to be recreated.
  
-  CD50:: The provenance of each line of code is established via the source code control system,
in a reliable way based on strong authentication of the committer. When third-party contributions
are committed, commit messages provide reliable information about the code provenance. <<FootNote(See
also LC40.)>>
+  CD50:: The provenance of each line of code is established via the source code control system,
in a reliable way based on strong authentication of the committer. When third-party contributions
are committed, commit messages provide reliable information about the code provenance.<<FootNote(See
also LC40.)>>
  
  === License and Copyright ===
-  LC10:: The code is released under the Apache License, version 2.0
+  LC10:: The code is released under the Apache License, version 2.0.
  
   LC20:: Libraries and other dependencies that are required to use the compiled code do not
create more restrictions than the Apache License does. '''TODO do we need to define "dependency"?
Footnote?'''
  
@@ -42, +42 @@

  
   LC40:: Committers are bound by an Individual Contributor Agreement ("Apache iCLA") that
defines which code they are allowed to commit and how they need to identify code that is not
their own.
  
-  LC50:: The copyright ownership of everything that the project produces is clearly defined
and documented. <<FootNote(In Apache projects, the ASF owns the copyright for the collective
work, i.e. the project's releases. Contributors retain copyright on their contributions but
grant the ASF a perpetual copyright license for them.)>> 
+  LC50:: The copyright ownership of everything that the project produces is clearly defined
and documented.<<FootNote(In Apache projects, the ASF owns the copyright for the collective
work, i.e. the project's releases. Contributors retain copyright on their contributions but
grant the ASF a perpetual copyright license for them.)>> 
  
  === Releases ===
   RE10:: Releases consist of source code, distributed using standard and open archive formats
that are expected to stay readable in the long term.<<FootNote(See http://www.apache.org/dev/release.html
for more info on Apache releases)>>
@@ -51, +51 @@

  
   RE30:: Releases are signed and/or distributed along with digests that can be reliably used
to validate the downloaded archives.
  
-  RE40:: Convenience binaries can be distributed alongside source code but they are not Apache
Releases - they are just a convenience provided with no guarantee.
+  RE40:: Convenience binaries can be distributed alongside source code but they are not Apache
Releases -- they are just a convenience provided with no guarantee.
  
  === Quality ===
   QU10:: The project is open and honest about the quality of its code. Various levels of
quality and maturity for various modules are natural and acceptable as long as they are clearly
communicated.
  
-  QU20:: The projects puts a very high priority on producing secure software. <<FootNote(The
required level of security depends on the software's intended uses, of course. Expectations
should be clearly documented.)>>
+  QU20:: The project puts a very high priority on producing secure software.<<FootNote(The
required level of security depends on the software's intended uses, of course. Expectations
should be clearly documented.)>>
  
-  QU30:: The project provides a well-documented channel to report security issues, along
with a documented way of responding to them. <<FootNote(Apache projects can just point
to http://www.apache.org/security/ or use their own security contacts page, which should also
point to that.)>>
+  QU30:: The project provides a well-documented channel to report security issues, along
with a documented way of responding to them.<<FootNote(Apache projects can just point
to http://www.apache.org/security/ or use their own security contacts page, which should also
point to that.)>>
  
   QU40:: The project puts a high priority on backwards compatibility and aims to document
any incompatible changes and provide tools and documentation to help users transition to new
features.
  
@@ -79, +79 @@

  
   CO70:: The project strives to answer user questions in a timely manner.
  
- === Consensus building ===
+ === Consensus Building ===
-  CS10:: The project maintains a public list of its contributors who have decision power
- the project's PMC (Project Management Committee) consists of those contributors.
+  CS10:: The project maintains a public list of its contributors who have decision power
-- the project's PMC (Project Management Committee) consists of those contributors.
  
-  CS20:: Decisions are made by consensus among PMC members <<FootNote(In Apache projects,
"consensus" means ''widespread agreement among people who have decision power''. It does not
necessarily mean "unanimity".)>> and are documented on the project's main communications
channel. Community opinions are taken into account but the PMC has the final word if needed.

+  CS20:: Decisions are made by consensus among PMC members<<FootNote(In Apache projects,
"consensus" means ''widespread agreement among people who have decision power''. It does not
necessarily mean "unanimity".)>> and are documented on the project's main communications
channel. Community opinions are taken into account but the PMC has the final word if needed.

  
-  CS30:: Documented voting rules are used to build consensus when discussion is not sufficient.
<<FootNote(For Apache projects, http://www.apache.org/foundation/voting.html defines
the voting rules.)>>
+  CS30:: Documented voting rules are used to build consensus when discussion is not sufficient.<<FootNote(For
Apache projects, http://www.apache.org/foundation/voting.html defines the voting rules.)>>
  
   CS40:: In Apache projects, vetoes are only valid for code commits and are justified by
a technical explanation, as per the Apache voting rules defined in CS30.
  
-  CS50:: All "important" discussions happen asynchronously in written form on the project's
main communications channel. Offline, face-to-face or private discussions <<FootNote(Apache
projects have a private mailing list that their PMC is expected to use only when really needed.
The private list is typically used for discussions about people, for example to discuss and
to vote on PMC candidates privately.)>> that affect the project are also documented
on that channel.
+  CS50:: All "important" discussions happen asynchronously in written form on the project's
main communications channel. Offline, face-to-face or private discussions<<FootNote(Apache
projects have a private mailing list that their PMC is expected to use only when really needed.
The private list is typically used for discussions about people, for example to discuss and
to vote on PMC candidates privately.)>> that affect the project are also documented
on that channel.
  
  === Independence ===
   IN10:: The project is independent from any corporate or organizational influence.<<FootNote(Independence
can be understood as basing the project's decisions on the open discussions that happen on
the project's main communications channel, with no hidden agendas.)>>

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


Mime
View raw message