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

Bug 540269

Summary: [proposal] technology.jemo
Product: Community Reporter: Cydnie Smith <cydnie.smith>
Component: Proposals and ReviewsAssignee: Eclipse Management Organization <emo>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: christopher.stura, sharon.corbett, wayne.beaton, webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X   
URL: https://projects.eclipse.org/proposals/eclipse-jemo-cloud-application-runtime
Whiteboard: stalebug
Bug Depends on: 540270, 540271    
Bug Blocks:    

Description Cydnie Smith CLA 2018-10-18 14:05:56 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
-Transfer ownership of the project name trademark to the Eclipse Foundation
-Get approval for non-standard licensing from the Eclipse Foundation’s Board of Directors

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-12-11 15:42:48 EST
Note that, per Bug Bug 540271 Comment 4, the project is renamed Eclipse Jemo.
Comment 2 Cydnie Smith CLA 2018-12-19 12:11:51 EST
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
Comment 3 Eclipse Webmaster CLA 2019-01-09 10:02:57 EST
The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project:


Source Code Management:

ssh://committer_id@git.eclipse.org:29418/jemo/jemo.git


Issue Tracker: 

https://bugs.eclipse.org/bugs/describecomponents.cgi?product=jemo


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


Project Website repository:

ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/jemo.git


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


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


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


Builds: You can upload releases to ~committer_id/downloads/jemo 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 Cydnie Smith CLA 2019-01-09 10:22:49 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. 

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
Comment 5 Cydnie Smith CLA 2019-01-28 10:10:10 EST
Your initial contribution has received "check-in" by the IP Team!

You may now begin pushing source code into Eclipse project repositories. 

Projects may not be released until intellectual property receives "full approval" by IP Team.

While "full approval" is pending, you may begin creating "CQ's" (Contribution Questionnaires) for Third Party content.
Your first set of "CQ's" should be submitted in a small batch. After your first submission, the IP team will direct you through the rest of that process.

[1] https://www.eclipse.org/projects/handbook/#release
Comment 6 Christopher Stura CLA 2019-01-29 04:53:32 EST
I am having trouble checking code into the git repository as via the command line a mac will require public key authentication and via tools where you can specify the username and password I can't seem to get the credentials I use to login to the foundation or the shorthand to work. I assume my committer id is cstura as per a document I found on-line.

Could you please look into this for me?
Comment 7 Eclipse Webmaster CLA 2019-01-30 14:58:11 EST
(In reply to Christopher Stura from comment #6)

> Could you please look into this for me?

Based on the logs it looks like you can login to gerrit, and I don't see any errors reported for jemo.git so things look ok.

Have you logged into the web interface (https://git.eclipse.org/r) and added your public key?

-M.
Comment 8 Cydnie Smith CLA 2019-07-25 14:48:42 EDT
Greetings Project Team, 

AFAICT, your initial contribution was approved on 2019-03-22 and you have no outstanding CQs. 

Your next step should be to start planning your first release! What are your plans with regards to releasing?

For more information on the release process, check out the handbook: https://www.eclipse.org/projects/handbook/#release
Comment 9 Eclipse Genie CLA 2021-09-27 05:03:41 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 10 Wayne Beaton CLA 2021-09-29 17:46:45 EDT
Eclipse Jemo is up and running, so I'm going to close this.

The project looks pretty active... it should be time soon for a release and corresponding release review. Please engage with the EMO at your earliest convenience.