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 Fri, 06 Feb 2015 14:41:19 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=23&rev2=24

  = A Maturity Model for Apache Projects (EARLY 2015 DRAFT) =
  
- '''Status''': incorporated all comments from the comdev thread, looks like this is ready
to move to http://apache.org/dev or wherever we want to have it.
+ This has moved to http://community.apache.org/apache-way/apache-project-maturity-model.html
  
- This is being discussed on the [[http://mail-archives.apache.org/mod_mbox/community-dev/|dev@community.a.o]]
list, starting at the http://s.apache.org/apache_maturity_model thread.
- 
- Feel free to join the discussion and contribute to this!
- 
- == Overview ==
- The goal of this maturity model is to describe how Apache projects operate, in a concise
and high-level way.
- 
- It is meant to be usable outside of Apache as well, for projects that might want to adopt
some or all of these principles. Projects that envision moving to Apache at some point might
start working towards this to prepare for their move.
- 
- It does not describe all the details of how our projects operate, but aims to capture the
invariants of Apache projects and point to additional information where needed. To keep the
main model as concise as possible we use footnotes for anything that's not part of the core
model.
- 
- Contrary to other maturity models, we do not define staged partial compliance levels. A
mature Apache project complies with all the elements of this model, and other projects are
welcome to pick and choose the elements that suit their goals.
- 
- Note that we try to avoid using the word "must" below. The model describes the state of
a mature project, as opposed to a set of rules.
- 
- == The Apache Project Maturity Model ==
- Each item in the model has a unique ID to allow them to be easily referenced elsewhere.
- 
- === Code ===
-  CD10:: The project produces Open Source software, for distribution to the public at no
charge.<<FootNote("For distribution to the public at no charge" is straight from the
from the ASF Bylaws at http://apache.org/foundation/bylaws.html.)>>
- 
-  CD20:: The project's code is easily discoverable and publicly accessible.
- 
-  CD30:: The code can be built in a reproducible way using widely available standard tools.
- 
-  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.)>>
- 
- === License and Copyright ===
-  LC10:: The code is released under the Apache License, version 2.0.
- 
-  LC20:: Libraries that are mandatory dependencies of the project's code do not create more
restrictions than the Apache License does.<<FootNote(It's ok for platforms (like a runtime
used to execute our code) to have different licenses as long as they don't impose reciprocal
licensing on what we are distributing.)>> <<FootNote(http://apache.org/legal/resolved.html
has information about acceptable licenses for third-party dependencies)>>
- 
-  LC30:: The libraries mentioned in LC20 are available as Open Source software.
- 
-  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.)>> 
- 
- === 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)>>
- 
-  RE20:: Releases are approved by the project's PMC (see CS10), in order to make them an
act of the Foundation.
- 
-  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.
- 
- === 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 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.)>>
- 
-  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.
- 
-  QU50:: The project strives to respond to documented bug reports in a timely manner.
- 
- === Community ===
-  CO10:: The project has a well-known homepage that points to all the information required
to operate according to this maturity model.
- 
-  CO20:: The community welcomes contributions from anyone who acts in good faith and in a
respectful manner and adds value to the project.
- 
-  CO30:: Contributions include not only source code, but also documentation, constructive
bug reports, constructive discussions, marketing and generally anything that adds value to
the project.
- 
-  CO40:: The community is meritocratic and over time aims to give more rights and responsibilities
to contributors who add value to the project.
- 
-  CO50:: The way in which contributors can be granted more rights such as commit access or
decision power is clearly documented and is the same for all contributors.
- 
-  CO60:: The community operates based on consensus of its members (see CS10) who have decision
power. Dictators, benevolent or not, are not welcome in Apache projects.
- 
-  CO70:: The project strives to answer user questions in a timely manner.
- 
- === 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.
- 
-  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.)>>
- 
-  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.
- 
- === 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.)>>
- 
-  IN20:: Contributors act as themselves as opposed to representatives of a corporation or
organization.
- 
- == Related efforts, inspiration ==
-  * http://oss-watch.ac.uk/resources/ssmm
-  * http://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/
-  * https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
-  * http://rfc.zeromq.org/spec:16
-  * http://oss-watch.ac.uk/resources/reusereadinessrating
-  * http://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration
-  * https://www.apache.org/dev/project-requirements
- 
- == Footnotes ==
- 

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


Mime
View raw message