(Full resolution will be available to all later)
This means that our community is part of an experiment to create Top Level Projects directly, without going through the Incubator. Apache Zest is one of a very small number of projects where this has happened, and recently it is only Apache Steve. But Apache Steve's codebase came from within ASF, and we will carve a new path in that respect.
The initial steps will be quite burdensome on primarily myself, to setup, and/or request for, the various resources necessary. And it will take a while.
This is especially true for those who has contributed large amounts of code, such as myself, Rickard, Paul, Stan and many others. For the parts, where no Software Grant is obtained, we might need to cut that out. I will come back on this issue quite soon.
The two most urgent tasks for the project (the above paragraph is for us personally) are a) create mailing lists and b) get the JIRA project created to track all the things needed to be done.
Once those are done, the initial PMC can start to invite people to the PMC and hand out commit privileges to our contributors. In that process, each of you will be asked to sign and send in a so called ICLA. You can do that ahead of time. It is basically saying that you have the right to contribute, what you will contribute, to the ASF. As the Software Grant is about all the contributions that have already occurred, the ICLA is about all the contributions in the future. Some of you already have ICLA on file with ASF.
https://www.apache.org/licenses/icla.txt or in PDF
https://www.apache.org/licenses/icla.pdfPaul also asked me privately whether Qi4j 2.1 release must be renamed. The short answer is "sort of".
a. Any public announcement SHOULD be using Apache Zest.
b. Qi4j will be a sub-project within Apache Zest, so the Qi4j name (I suggest) remains. So relatively little in the documentation will change, just adding Apache Zest references here and there.
c. Package names in Java can remain org.qi4j, for compatibility reasons if no other. We can decide later about whether to keep org.qi4j for the API, in which case we need to request that ASF takes ownership of the domain name, or change to org.apache.qi4j for the compatibility break in Qi4j 3.0
Exciting times ahead.
Cheers