Bugzilla – Full Text Bug Listing
| Summary: | [proposal] ee4j.jakartaee-stable | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bill.shannon, cydnie.smith, david.blevins, dmitry.kornilov, frederic.gurr, ivar.grimstad, kwsutter, sharon.corbett, starksm, steve.millidge, webmaster, yamini.k.b |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-project-stable-jakarta-ee-apis/edit | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
We’ve received all of the project requirements and have scheduled the creation review to conclude on May 16/2018. Please continue to monitor communication channels. Following the creation review, we will initiate the provisioning process. As part of this process, we will bring committers on board. To gain committer status, some paperwork [1] must be completed. The exact nature of that paperwork depends on several factors, including the employment status of the individual and the Eclipse Foundation membership status of the employer. If you can be ready with the paperwork in time for the completion of the creation review, then we can move quickly through the provisioning process. When we initiate provisioning, committers will be sent an email with instructions; please don't send any paperwork in until after you receive those instructions. Please encourage all future project committers to join the incubation mailing list [2]. We use this list to connect committers from new projects to their peers in other projects in the incubation phase and to mentors who can help answer questions and discuss issues related to the project onboarding process. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://dev.eclipse.org/mailman/listinfo/incubation I've removed Suma Sri Uppala from the list of committers because they have not created an Eclipse Foundation account. I declare the Creaton Review successful! We will initiate the project resources provisioning process shortly. Please tell your project committers to carefully monitor their email for a message from The Eclipse Foundation with instructions for providing committer paperwork [1]. Our IT team cannot allocate project resources until after we have processed the paperwork for at least one committer, so your attention in this matter will keep the process moving forward. Be advised that the paperwork process will time out after 120 days; any committers who are unable to complete their paperwork requirements in this timeframe will have to be elected to the project (your project mentors can provide assistance with this). [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management: As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization and flatten any previous history. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=jakartaee-stable Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/jakartaee-stable-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/ee4j/jakartaee-stable.git Commits will be published to www.eclipse.org/jakartaee-stable within 5 minutes Downloads: http://download.eclipse.org/jakartaee-stable Archives: http://archive.eclipse.org/jakartaee-stable Builds: You can upload releases to ~committer_id/downloads/jakartaee-stable via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org Older builds should be moved to the archives area when they are no longer required. -M. Your next step is to submit an initial contribution [1] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. IP requests are referred to as Contribution Questionnaires (CQs). When the initial CQ receives “check in” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution The initial contribution for Enterprise Deployment API project has been cleared: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16371 Can we have the repository created please? eclipse-ee4j/enterprise-deployment Ok I've created the repo and updated the PMI. The Jakartaee-stable team will get access the next time the sync tools run. -M. The initial contribution for JAX-R API project has been cleared: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=16386 Can we have the repository created please? eclipse-ee4j/jaxr-api The initial contribution for JAX-RPC API project has been cleared: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16388 Can we have the repository created please? eclipse-ee4j/jax-rpc-api Done, the Jakartaee-stable Github team will get access to these repos in the next hour or so when the sync tool runs. -M. The initial contribution for Enterprise Management project has been cleared: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=16836 Can we have the repository created please? eclipse-ee4j/management-api Done. The Jakartaee-stable Github team will get access to these repos when the sync tool runs. Project is fully operational. This bug is now closed! |