Reboot Jakarta Contexts and Dependency Injection

The EMO is using this issue to track the progress of project recreation.

Project

This single review combines a Termination Review with a Creation Review in order to reconstitute this specification project under the Implementation Patent License. All other aspects of the project, including the scope will remain unchanged. That is, we're going to simultaneously terminate and re-create the project in place. This way we can, for example, use the same project id and existing project records in the PMI, avoid engaging in the initial contribution process, etc.

To be clear, the review is atomic: upon success, the existing project will be terminated and the new project will be created in its place (specifically, the creation part cannot succeed unless the termination part also succeeds). We'll meet all of the requirements of the EDP and EFSP, but will skip the part where we engage the webmaster to archive any resources as part of a termination or provision any resources as part of a creation (thereby avoiding the need for us to retire and then re-provision every committer).

The EMO will engage with the project team to get all existing committers to make a public statement that specifically authorizes the EMO to transfer their existing committer status to the reconstituted project. We’ll start a thread on the tracking issue to capture this. The committer status of all committers who authorize the EMO to transfer their committer status will automatically be transferred to the reconstituted project. Any existing committers who do not provide authorisation before the conclusion of the review will be removed from the reconstituted project and their commit rights will be revoked.

Note that, within three months of the conclusion of the review, any committers who are retired as part of this will be reinstated by the EMO upon their request (send a note to emo@eclipse.org). After three months, the standard processes must be followed to reinstate committers (i.e., committer election or appointment as a Participant Representative).

Basic Information

• License: Apache License, Version 2.0
• Patent License: Implementation Patent License

Pre-creation Checklist

To be completed by the EMO

• Project scope is well-defined
• Top-level Project selected
• PMC accepts the project (PMC has replied with +1)
• License(s) approved
• Project name trademark approved
• Project lead(s) identified
• Committers identified
• Committers have Eclipse Foundation Accounts
• Eclipse Architecture Council mentor identified
• Two weeks of community review completed

Being this a specification project, a Spec Committee ballot to approve the project creation must run for at least one week

• Specification Committee ballot initiated
• Specification Committee ballot concluded successfully