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

Bug 414023

Summary: Provision the vert.x project
Product: Community Reporter: Denis Roy <denis.roy>
Component: ProcessAssignee: Eclipse Management Organization <emo>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: mike.milinkovich, nobody, sharon.corbett, thanh.ha, timvolpe, wayne.beaton, webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Denis Roy CLA 2013-07-30 11:12:18 EDT
The vert.x project has completed the NPPR, so we can begin the provisioning aspect.  As a reminder, vert.x is the first project we're provisioning there the main code repo will be hosted on GitHub.

Here's a list of tasks that should happen:

a) WEBMASTER: Move the vert.x core repo into the Eclipse organization on Github.  The master branch should only contain the code as tagged here:
https://github.com/vert-x/vert.x/tree/Eclipse_Foundation_Initial_Contribution

All the history will be preserved, but the refs will be rewritten in such a way that will not affect cloning to eclipse.org. Thanh has experimented with this and can likely provide more details.


b) WEBMASTER: create the project resources on eclipse.org as usual (mailing lists, Bugzilla components, Git repos, etc).



c) WEBMASTER: Once IP has been cleared on the Initial Contribution, the repos on git.eclipse.org should be read-only, and updated from the GitHub master frequently.



d) TIM FOX/PROJECT LEAD: Discuss the development process changes with your community, as the Git URLs will change, code history will be elsewhere, and you'll be using this Bugzilla and eclipse.org mailing lists to conduct open and transparent development.  Again, you will have more info about these resources once the project is provisioned.

Am I missing anything?
Comment 1 Thanh Ha CLA 2013-07-30 11:20:30 EDT
(In reply to comment #0)
> All the history will be preserved, but the refs will be rewritten in such a
> way that will not affect cloning to eclipse.org. Thanh has experimented with
> this and can likely provide more details.

I started a wiki page which I will put Migration details. I'll try to insert all my notes in there today.

http://wiki.eclipse.org/GitHub
Comment 2 Denis Roy CLA 2013-08-02 10:09:33 EDT
(In reply to comment #0)
> a) WEBMASTER: Move the vert.x core repo into the Eclipse organization on
> Github.  The master branch should only contain the code as tagged here:
> https://github.com/vert-x/vert.x/tree/Eclipse_Foundation_Initial_Contribution

DONE.


 
> All the history will be preserved, but the refs will be rewritten in such a
> way that will not affect cloning to eclipse.org. Thanh has experimented with
> this and can likely provide more details.

The process is documented at http://wiki.eclipse.org/GitHub

> 
> 
> b) WEBMASTER: create the project resources on eclipse.org as usual (mailing
> lists, Bugzilla components, Git repos, etc).

Mailing list: https://dev.eclipse.org/mailman/listinfo/vertx-dev

Forum: to do

Bugzilla components: to do


> c) WEBMASTER: Once IP has been cleared on the Initial Contribution, the
> repos on git.eclipse.org should be read-only, and updated from the GitHub
> master frequently.

To do.

> d) TIM FOX/PROJECT LEAD: Discuss the development process changes with your
> community, as the Git URLs will change, code history will be elsewhere, and
> you'll be using this Bugzilla and eclipse.org mailing lists to conduct open
> and transparent development.  Again, you will have more info about these
> resources once the project is provisioned.

A provisioning email has been sent to Tim with these details.  Please contact me at webmaster@eclipse.org if you need further assistance, at any time, setting up Hudson, using Bugzilla, the mailing lists, etc.
Comment 3 Denis Roy CLA 2013-08-02 10:45:53 EDT
> c) WEBMASTER: Once IP has been cleared on the Initial Contribution

Wayne is currently on holidays -- he will send Tim some instructions on how to submit the Initial Contribution to the IP team for review.

In the meanwhile, I am told that you (Tim) can continue working on your code on Github.  I will need to revoke GitHub committer access from Stuart and Norman since we have not yet received their Eclipse Committer paperwork.
Comment 4 Mike Milinkovich CLA 2013-08-02 10:55:32 EDT
(In reply to comment #3)
> In the meanwhile, I am told that you (Tim) can continue working on your code
> on Github.  I will need to revoke GitHub committer access from Stuart and
> Norman since we have not yet received their Eclipse Committer paperwork.

I'm pretty sure that Stuart would be covered under VMware's MCA (Member Committer Agreement). I'm not sure who Norman works for.
Comment 5 Sharon Corbett CLA 2013-08-02 17:16:51 EDT
A quick Google search indicates Norman is with Redhat as well(?).

Tim:  If you could be so kind as to pass along the same info I provided to you concerning the online questionnaire (which creates records in our internal systems) and completes the legal paperwork requirement, we will be able to arrange Stuart and Norman's UNIX accounts as well.


Thanks,
Sharon
Comment 6 Sharon Corbett CLA 2013-08-05 22:44:39 EDT
I've just pushed Stuart and Norman's committer account provisioning requests through to the Webmaster queue.

Thanks,
Sharon
Comment 7 Denis Roy CLA 2013-08-28 16:34:43 EDT
(In reply to comment #2)
> Forum: to do

Is an Eclipse forum mandatory for Github projects?  Or, in other words, will the project committers monitor the forum?


> Bugzilla components: to do

Done.

> c) WEBMASTER: Once IP has been cleared on the Initial Contribution, the
> repos on git.eclipse.org should be read-only, and updated from the GitHub
> master frequently.

To do.
Comment 8 Wayne Beaton CLA 2014-05-23 16:15:00 EDT
I think that we done here. Can we declare victory?
Comment 9 Denis Roy CLA 2014-05-23 16:18:11 EDT
Agreed