Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 534340

Summary: [proposal] ee4j.ejb
Product: Community Reporter: Wayne Beaton <wayne.beaton>
Component: Proposals and ReviewsAssignee: Eclipse Management Organization <emo>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: david.blevins, dmitry.kornilov, frainone, sharon.corbett, webmaster, yamini.k.b
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
URL: https://projects.eclipse.org/proposals/eclipse-project-ejb
Whiteboard:

Description Wayne Beaton CLA 2018-05-03 23:10:02 EDT
We’ll use this Bugzilla record to track the onboarding process for the project. This channel will be the primary means of communication for the project team, your mentors, and the Eclipse Foundation during this process. 
 
To get started on your new project, we need to do the following:
-Ensure that all of the committers listed on the proposal have Eclipse Foundation Accounts [1]
-Identify a mentor for the project

We will open separate Bugzilla records to track this.
 
Once we have all of the requirements above and the proposal has been open for community review for a minimum of two weeks, we will schedule the project for creation. If you have any questions for us, please feel free to reach out anytime! As well, if you’d like an overview of the project creation process, check out our Project Handbook [2].

We look forward to working with you and your team to make this project a success! 
 
[1] https://accounts.eclipse.org/user/register
[2] https://www.eclipse.org/projects/handbook/#starting
Comment 1 Wayne Beaton CLA 2018-05-10 15:39:56 EDT
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
Comment 2 Wayne Beaton CLA 2018-05-16 16:40:26 EDT
> Committer Tracy Burroughs must create an Eclipse Foundation Account.
> Committer Olen Cook must create an Eclipse Foundation Account.
> Committer Brian Decker must create an Eclipse Foundation Account.

I have removed these committers from the proposal.
Comment 3 Wayne Beaton CLA 2018-05-16 16:42:31 EDT
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
Comment 4 Eclipse Webmaster CLA 2018-05-24 10:51:35 EDT
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=ejb

Outbound Communication:
Mailing list: https://accounts.eclipse.org/mailing-list/ejb-dev

Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/ee4j/ejb.git

Commits will be published to www.eclipse.org/ee4j/ejb within 5 minutes

Downloads: http://download.eclipse.org/ejb

Archives: http://archive.eclipse.org/ejb

Builds: You can upload releases to ~committer_id/downloads/ejb 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.
Comment 5 Wayne Beaton CLA 2018-05-25 10:02:42 EDT
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
Comment 6 Yamini K B CLA 2018-05-25 11:46:54 EDT
The initial contribution for EJB API project has been cleared:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16446

Can we have the repository created please?

eclipse-ee4j/ejb-api
Comment 7 Eclipse Webmaster CLA 2018-05-28 11:25:11 EDT
Done, the ejb Github team will get access in the next hour or so when the sync tool runs.

-M.
Comment 8 Cydnie Smith CLA 2018-12-05 14:40:54 EST
Project is fully operational. This bug is now closed.