Commons RDF Project Maturity Report

This is a report of Commons RDF following the Maturity Model for Apache Projects (2016-10).

NOTE: Commons RDF graduated on 2016-11-28 from the Apache Incubator to become a sub-project (component) of Apache Commons. The links below may not have been updated following graduation.



The project produces Open Source software, for distribution to the public at no charge.

All outputs of Apache Commons RDF is open source, covered by Apache License 2.0 and distributed at no charge.


The project's code is easily discoverable and publicly accessible.

Menu on links to Source (git), Source (GitHub mirror), as well as source releases under Download


The code can be built in a reproducible way using widely available standard tools.

See build instructions, requires only Apache Maven 3.2 and Java JDK 8. Build independently verified by Jenkins and Travis CI.

Build Status


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.

Full history in Each release has a corresponding tag

The git commits includes pre-Apache history imported from through software grant.


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.

Only users have commit access. Pull requests are acknowledged in pom.xml.

No contributions have been received so far from developers who have not signed an ICLA with ASF.

Licenses and Copyright


The code is released under the Apache License, version 2.0.

Apache License 2.0 only.


Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.

Dependencies are ASF-compatible open source licenses like Apache License 2.0, BSD, MIT, Eclipse Distribution License.

For details see each module:


The libraries mentioned in LC20 are available as Open Source software.

Yes, see LC20.


Committers are bound by an Individual Contributor Agreement (the “Apache iCLA”) that defines which code they are allowed to commit and how they need to identify code that is not their own.

All Commons RDF committers have ASF ICLAs on file and are Apache committers.


The copyright ownership of everything that the project produces is clearly defined and documented.

ASF copyright asserted in NOTICE and in ASF file headers.

For details, see RAT report for each module:



Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.

Releases archives are in .tar.gz and .zip formats.

All releases are made to and archived on


Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.

All ASF releases of Commons RDF are subject to a vote on dev@ following the ASF voting policy.


Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.

All releases have corresponding PGP asc files with a corresponding key listed in KEYS.

Releases also have .md5 and .sha1 hashes, which corresponds to the hashes in the vote emails and in Maven Central.


Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee.

Convenience binaries are deployed to Maven Central under the org.apache.commons group ID, which include the source release corresponding to the the dist files. (see RE30 )


The release process is documented and repeatable to the extent that someone new to the project is able to independently generate the complete set of artifacts required for a release.

Documented as however this must be updated to align with Apache Commons release process with regards to site publication.



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.

Commons RDF use semantic versioning.

Experimental features are clearly documented as such.


The project puts a very high priority on producing secure software.

Following Apache Commons procedures, Commons RDF uses reports like Findbugs, PMD, JDepend and JaCoCo.


The project provides a well-documented channel to report security issues, along with a documented way of responding to them.

Menu links to Commons Security - security reports are reported to private@commons Commons PMC which include several of the Commons RDF committers.


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.

Even during 0.x development the project has strived for backwards compatibility between releases, see for instance this japicmp report and the use of @Deprecated.

(Note that the first 1.0 release is likely to remove those deprecated methods/classes from the 0.x series)


The project strives to respond to documented bug reports in a timely manner.

Jira is used both for feature suggestions and bug reports.



The project has a well-known homepage that points to all the information required to operate according to this maturity model.

Home page is

The pre-ASF website redirects to the above.

NOTE: As the project is proposing to graduate to Apache Commons PMC, the URL will change (with HTTP redirection) to


The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.

Commons RDF welcome contributions through mailing list and pull requests.


Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project.

Commons RDF recognize all contributions, in particular new features from committers are raised as pull requests and discussed on dev@commonsrdf.

NOTE: As the project is proposing to graduate to Apache Commons, the mailing list will change to dev@commons using the subject tag [RDF].

Commons RDF also recognize non-code contributions, for instance this review meant Adam Soraka was listed as a reviewer


The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.

Commons RDF recognizes contributors, but has not elected any new committers during incubation.

Most of the people involved with Apache Commons are already ASF committers; note that any ASF committer have write-access to Apache Commons code which Commons RDF will honour after graduation.


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.

TODO: This documentation should be covered by Apache Commons PMC, but don't currently have a good page for it beyond Volunteering and Contributing patches.


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.

As this project was to form an API across existing RDF frameworks, the quest for consensus has actually been a bit too strong in this project, which caused several committers to retire from the project.

It has been agreed to aim for Apache Commons PMC as home, which already operates on strong consensus model.


The project strives to answer user questions in a timely manner.

User engagement is currently done via dev@commonsrdf but will transition to user@commons.

Consensus Building


The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors.

All contributors listed on Team page with their role indicated (e.g. PPMC Member).


Decisions are made by consensus among PMC members 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.

All decisions are made on dev@commonsrdf without much consideration about who is in PMC or not.

Note that some discussions happen in GitHub pull requests or Jira issues, which are mirrored to the mailing list.


Documented voting rules are used to build consensus when discussion is not sufficient.

This only happened once which caused disagreements.


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.

No vetoes so far, except soft vetoes during pull request reviews.


All “important” discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions 11 that affect the project are also documented on that channel.

All discussions are on list, see CS20.



The project is independent from any corporate or organizational influence.

No particular influence has been noted from the corporations who employ the committers, however the project communities Commons RDF is integrating with have obviously had an influence on its development.


Contributors act as themselves as opposed to representatives of a corporation or organization.

Commons RDF contributors have very much acted as themselves.