Bugzilla – Full Text Bug Listing
| Summary: | [proposal] ee4j.cdi | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Cydnie Smith <cydnie.smith> | ||||||
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | antoine, ivar.grimstad, manovotn, sharon.corbett, sstark, starksm64, wayne.beaton, webmaster | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 10 | ||||||||
| URL: | https://projects.eclipse.org/proposals/jakarta-contexts-and-dependency-injection | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | 548749, 548753, 548755 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Cydnie Smith
You can put me up as a mentor. Ivar (In reply to Ivar Grimstad from comment #1) > You can put me up as a mentor. > > Ivar I have added you as mentor! Thank you for stepping up Ivar. For your information, I already contacted former Expert Group members to propose them to be listed as initial committer of the project. Let's just use "cdi" as the project's short name. I've updated this in the proposal document (and designated the proposal as a specification project for the Jakarta EE Working Group). We’ve received all of the project requirements and have scheduled the creation review to conclude on July 17 2019. 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 The Specification Committee discussed the scope on their last call. I've updated the scope to the following: -- Jakarta Contexts and Dependency Injection defines a programming model based on component’s lifecycle and typesafe dependency injection providing multiple services and integrating with other specifications. -- with the following in qualification: -- It also provides an event system and interception mechanism that adds loose decoupling to the programming model, a powerful SPI and extension mechanism allows extension of the programming model and better integration of third party frameworks. -- (In reply to Cydnie Smith from comment #5) > We’ve received all of the project requirements and have scheduled the > creation review to conclude on July 17 2019. Please continue to monitor > communication channels. Cydnie, the proposal has been posted for two weeks. I believe that the requirements of the EDP have been met. We have everything that we need; let's change the end of the review to July 10, please. (In reply to Wayne Beaton from comment #7) > (In reply to Cydnie Smith from comment #5) > > We’ve received all of the project requirements and have scheduled the > > creation review to conclude on July 17 2019. Please continue to monitor > > communication channels. > > > Cydnie, the proposal has been posted for two weeks. I believe that the > requirements of the EDP have been met. We have everything that we need; > let's change the end of the review to July 10, please. Review date has been updated! Note: I've updated Matej's email address to use the one that we have on file (Matej is already a committer on Eclipse MicroProfile). I've changed the end of the review date to July 15. We need to give the specification committee time to complete their vote on the proposal. I declare the Creation 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). The next step is to submit an initial contribution [2] 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. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution FYI I resend a personal mail to former EG amber or very active CDI 2.0 contributor to have more people on initial committer list for the specification The cdi-tck source snapshot, even compressed is 5.6Mb in compressed format, so it cannot be attached. How should that snapshot be provided? Created attachment 279279 [details] cdi api and spec snapshot The cdi api and spec snapshot from the https://github.com/cdi-spec/cdi repository. Created attachment 279280 [details] cdi-tck snapshot The snapshot from https://github.com/cdi-spec/cdi-tck (In reply to Scott M Stark from comment #13) > The cdi-tck source snapshot, even compressed is 5.6Mb in compressed format, > so it cannot be attached. How should that snapshot be provided? I was able to upload it. Use IPzilla to deliver the initial contribution to the IP Team for their review. Click here and follow the workflow: (note that this won't work until after the project provisioning is complete; that's in progress right now, so this should work on Tuesday morning). https://projects.eclipse.org/projects/ee4j.cdi/cq/create There's help in the handbook: https://www.eclipse.org/projects/handbook/#ip-initial-contribution Ok, snapshots added to IPZilla here: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20394 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. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: Github issues will be enabled for your project. Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/cdi-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/ee4j/cdi.git Commits will be published to www.eclipse.org/ee4j/cdi within 5 minutes Downloads: http://download.eclipse.org/cdi Archives: http://archive.eclipse.org/cdi Builds: You can upload releases to ~committer_id/downloads/cdi 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. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution Sorry, but I need some clarification to be sure that I understand the process and that we are waiting for approval. Is the current status and subsequent phases are : 1 Scott submitted the requested initial contribution with the attachment on this ticket. 2 We are waiting for the IP team validation (BTW my account is not allowed on IPzilla) 3 We are also waiting for the repo creation in the Github Eclipse organization 4 When 2 and 3 will be met, we'll be allowed to push existing CDI repository to this new repo (In reply to Antoine Sabot-Durand from comment #21) > 1 Scott submitted the requested initial contribution with the attachment on > this ticket. Correct. > 2 We are waiting for the IP team validation Yes. The IP Team has made this their highest priority. > (BTW my account is not allowed on IPzilla) I'm not sure why. I've added you in CC to the CQ; let me know if you're still having trouble. > 3 We are also waiting for the repo creation in the Github Eclipse > organization When the IP Team has completed their preliminary assessment, they'll grant "check-in" and instruct you to work with the webmaster to move the content over into an Eclipse repository. > 4 When 2 and 3 will be met, we'll be allowed to push existing CDI > repository to this new repo We can either move an existing GitHub repository or create a new one. It's your call. The current CDI team has given Webmaster access. Just to be clear are we moving all of the existing CDI repos or a subset? -M. (In reply to Eclipse Webmaster from comment #23) > The current CDI team has given Webmaster access. Just to be clear are we > moving all of the existing CDI repos or a subset? > > -M. We are just moving these two: https://github.com/cdi-spec/cdi https://github.com/cdi-spec/cdi-tck (In reply to Scott M Stark from comment #24) Sorry I missed this update. I've started the transfer. Committers that have added their Github IDs to their Eclipse.org account should receive access in an hour or so when the sync tool runs. -M. As this project has engaged in a release, I am declaring this project fully operational. This bug is now resolved! |