Bug 511055

Comment 1 Stephanie Swart 2017-04-18 13:30:00 EDT

I've scheduled the creation review to conclude on May 3/2017. 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 2017-05-04 10:13:49 EDT

I declare this 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).

Immediately following the provisioning process, your next step will be 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. In anticipation of this step, you may consider ensuring that your code has the required copyright headers and namespace (if applicable).

If you have any questions, please send a message to emo@eclipse.org and we will provide assistance.

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

An overview of the complete project creation process is in the Project Handbook [4].

[1] https://www.eclipse.org/projects/handbook/#paperwork
[2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution
[3] https://dev.eclipse.org/mailman/listinfo/incubation
[4] https://www.eclipse.org/projects/handbook/#starting

Comment 3 Eclipse Webmaster 2017-05-09 09:45:05 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[0].  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=gemoc

Forums and Outbound Communication:
Mailing list: https://dev.eclipse.org/mailman/listinfo/gemoc-dev
Forum: www.eclipse.org/forums

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

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

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

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

Builds: You can upload releases to ~committer_id/downloads/gemoc 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.
 
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 “checkin” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository.
 
For more information on how to use these resources, please see _this section_ of the Project Handbook

[0] https://wiki.eclipse.org/GitHub
[1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution

-M.

Comment 4 Benoit Combemale 2017-05-09 09:53:23 EDT

(In reply to Eclipse Webmaster from comment #3)
> 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[0]. 
> 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=gemoc
> 
> Forums and Outbound Communication:
> Mailing list: https://dev.eclipse.org/mailman/listinfo/gemoc-dev
> Forum: www.eclipse.org/forums
> 
> Project Website repository:
> ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/gemoc.git
> 
> Commits will be published to www.eclipse.org/gemoc within 5 minutes
> 
> Downloads: http://download.eclipse.org/gemoc
> 
> Archives: http://archive.eclipse.org/gemoc
> 
> Builds: You can upload releases to ~committer_id/downloads/gemoc 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.
>  
> 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 “checkin” and/or “full approval” you are now ready to
> check the initial project code contribution into your project’s repository.
>  
> For more information on how to use these resources, please see _this
> section_ of the Project Handbook
> 
> [0] https://wiki.eclipse.org/GitHub
> [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution
> 
> -M.

Why the name of the project "gemocstudio" has been shortened to "gemoc"?

BTW, wold it be possible ta have different separate git repositories?

Thanks, 
benoit

Comment 5 Wayne Beaton 2017-05-09 10:55:25 EDT

(In reply to Benoit Combemale from comment #4)
> Why the name of the project "gemocstudio" has been shortened to "gemoc"?

We try to pare the short name down to the shortest distinguishable name. This is only used in URLs. Page titles and text use the full name, "Eclipse GEMOC Studio".

Is this a problem?

> BTW, wold it be possible ta have different separate git repositories?

Yes. For projects that run on GitHub, you'll need to open a bug against Community/GitHub to request Webmaster assistance. There's more help in the handbook [1]

[1] https://www.eclipse.org/projects/handbook/#resources-github

Comment 6 Benoit Combemale 2017-05-09 12:17:07 EDT

(In reply to Wayne Beaton from comment #5)
> (In reply to Benoit Combemale from comment #4)
> > Why the name of the project "gemocstudio" has been shortened to "gemoc"?
> 
> We try to pare the short name down to the shortest distinguishable name.
> This is only used in URLs. Page titles and text use the full name, "Eclipse
> GEMOC Studio".
> 
> Is this a problem?

ok, I'm fine with this. But is it not a problem for you guys to have modeling.gemoc from the URLs point of view, and modeling.gemocstudio from a source code point of view (namespace, etc.). I fell like it can be disturbing, no?

> 
> > BTW, wold it be possible ta have different separate git repositories?
> 
> Yes. For projects that run on GitHub, you'll need to open a bug against
> Community/GitHub to request Webmaster assistance. There's more help in the
> handbook [1]
> 
> [1] https://www.eclipse.org/projects/handbook/#resources-github

Excellent, thanks. 

benoit

Comment 7 Cydnie Smith 2018-12-06 13:05:40 EST

This project is fully operational! This bug is now resolved.