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

Bug 527489

Summary:	[proposal] ee4j.jaxrs
Product:	Community	Reporter:	Kasandra Darwin <kasandra.darwin>
Component:	Proposals and Reviews	Assignee:	Eclipse Management Organization <emo>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	cydnie.smith, dmitry.kornilov, ed.bratt, gunnar, kwsutter, sharon.corbett, sharon.macdonald, wayne.beaton, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows NT
URL:	https://projects.eclipse.org/proposals/eclipse-restful-web-services-api-java
Whiteboard:
Bug Depends on:	527487, 527488
Bug Blocks:

Description Kasandra Darwin

2017-11-20 08:53:38 EST

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:
-Identify a mentor for the project
-Transfer ownership of the project name trademark to the Eclipse Foundation

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 [1].

We look forward to working with you and your team to make this project a success! 
 
[1] https://www.eclipse.org/projects/handbook/#starting

Comment 1 Kasandra Darwin

2017-12-12 13:09:27 EST

We have scheduled the creation review to conclude on December 18, 2017. Please continue to monitor communication channels.

Please encourage all future project committers to join the incubation mailing list [1]. 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.

Once the creation review has concluded, we will initiate the provisioning process. As part of this process, we will bring committers on board. To gain committer status, some paperwork [2] 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.

**When we initiate provisioning, committers will be sent an email with paperwork completion instructions; please don't send any paperwork in until after you receive those instructions.


[1] https://dev.eclipse.org/mailman/listinfo/incubation
[2] https://www.eclipse.org/projects/handbook/#paperwork

Comment 2 Kasandra Darwin

2018-01-02 14:38:01 EST

Congratulations! Your project review is 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 3 Eclipse Webmaster

2018-01-04 11:30:01 EST

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=jaxrs

Outbound Communication:
Mailing list: https://dev.eclipse.org/mailman/listinfo/jaxrs-dev

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

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

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

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

Builds: You can upload releases to ~committer_id/downloads/jaxrs 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.

Comment 4 Kasandra Darwin

2018-01-04 13:34:30 EST

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 5 Cydnie Smith

2018-12-06 09:57:26 EST

The project is fully operational! Bug has been resolved.