The Apache Software Foundation
The Apache Software Foundation Incubator

Tuweni Project Incubation Status

This page tracks the project status, incubator-wise. For more general project status, look on the project website.


Tuweni is a set of libraries and other tools to aid development of blockchain and other decentralized software in Java and other JVM languages.

The Tuweni project retired from Apache Incubation on 2023-07-29


  • 2022-10-20 Tuweni starts discussing graduating.
  • 2022-05-12 New Committer, Stefan Pingel
  • 2022-05-12 New Committer, Sally MacFarlane
  • 2021-12-21 New Committer, Adrian Sutton
  • 2021-05-06 New Committer, Nicolas Melendez
  • 2020-06-08 New Committer, Danno Ferrin
  • 2019-08-01 New Committer, Gordon Martin
  • 2019-02-25 Tuweni enters incubation.

Project info

item type reference
Website www
. wiki
Mailing list dev
. commits
Bug tracking Github
Source code git
Mentors toulmean Antoine Toulme
. wave Dave Fisher
. jbonofre Jean-Baptiste Onofre
. kamaci Furkan Kamaci
Committers/PPMC toulmean Antoine Toulme
. ddutta Debo
. jon Jon Scott Stevens
. jrhea Jonny Rhea
. lmccay Larry McCay
. mkalinin Mikhail Kalinin
. pierresmits Pierre Smits
. sneethir Selvamohan Neethiraj
. vinayakumarb Vinayakumar B
. pinges Stefan Pingel
. macfarla Sally MacFarlane
. adrian Adrian Sutton
. nfmelendez Fernando Nicolas Melendez
. gmartin Gordon Martin

Incubation status reports

Incubation work items

Project Setup

This is the first phase on incubation, needed to start the project at Apache.

Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the project to be incubated

date item
2019-05-01 Make sure that the requested project name does not already exist. Please follow the guide to ensure a suitable project/product name.
2019-05-01 If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names.
2019-05-01 If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
2019-05-01 If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.


date item
2019-05-01 Request DNS (first step after creating podling status page)
2019-05-01 Request Mailing Lists
2019-05-01 Request git repositories
2019-05-01 Ask infrastructure to create source repository modules and grant the committers karma (if using SVN)
2019-05-01 Ask infrastructure to set up issue tracker (JIRA, Bugzilla).
2019-05-01 Ask infrastructure to set up wiki (Confluence).
2019-05-01 Migrate the project to our infrastructure.

Mentor-related responsibility/oversight

date item
2019-05-01 Subscribe all Mentors on the pmc and general lists.
2019-05-01 Give all Mentors access to the incubator SVN repository. (to be done by the Incubator PMC chair or an Incubator PMC Member wih karma for the authorizations file)
2019-05-01 Tell Mentors to track progress in the file 'incubator/projects/{}.html'
date item
2019-05-01 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2019-05-01. Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Verify distribution rights

date item
2019-05-01 Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
2019-06-19 Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Establish a list of active committers

date item
2019-05-01 Check that all active committers have submitted a contributors agreement.
2019-05-01 Add all active committers in the relevant section above.
2019-05-01 Ask root for the creation of committers' accounts in LDAP.

Project specific

Add project specific tasks here.


These action items have to be checked for during the whole incubation process.

These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.

Collaborative Development

  • Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
  • Are there three or more independent committers? (The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.)
  • Are project decisions being made in public by the committers?
  • Are the decision-making guidelines published and agreed to by all of the committers?

Licensing awareness

  • Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?

Project Specific

Add project specific tasks here.


Things to check for before voting the project out.

Organizational acceptance of responsibility for the project

  • If graduating to an existing PMC, has the PMC voted to accept it?
  • If graduating to a new PMC, has the board voted to accept it?

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks?