Re: [rt-pmc] [ercp-dev] Time for a termination review for eRCP?

[Glyn Normington <gnormington@xxxxxxxxxx>]

Hi Wayne

If time runs out and option 3, archiving the project, is the same as terminating the project and making tarballs available, that sounds fine to me.

In that scenario, if someone wanted to fork the code later, wouldn't they be free to untar the source and store it in github, for example, *without* changing the org.eclipse namespace? I don't remember changing the namespace being required by the EPL (although I see why we might choose to do that if we were "dumping" a project on github).

Regards,

Glyn

---

From: "Wayne Beaton" <wayne@xxxxxxxxxxx>
To: "ERCP developers list" <ercp-dev@xxxxxxxxxxx>
Cc: "Eric MF Hsu" <mfhsu@xxxxxxxxxx>, "Runtime Project PMC mailing list" <rt-pmc@xxxxxxxxxxx>
Sent: Tuesday, 27 November, 2012 8:47:16 PM
Subject: Re: [rt-pmc] [ercp-dev] Time for a termination review for eRCP?

Time is running out for CVS at Eclipse. By extension, time is running out for eRCP.

There needs to be a plan to get eRCP off of CVS. I've listed three possible options. I am ready to hear alternatives.

The CVS server _will_ be shut off after December 21/2012. At that point, the project's code will be inaccessible, and I will ask the RT PMC to initiate a termination review.

Thanks,

Wayne

On 09/26/2012 10:23 AM, Wayne Beaton wrote:

AFAICT, eRCP is in CVS only.

If the project is terminated, we will tarball the downloads, repositories, website, etc. They will all be accessible, but not readily or easily.

We have some options:

1) The current development team can step up, request the Git migration, and start contributing to the project again;
2) The PMC can declare the current development team and project leadership ineffective and request that they be replaced (assuming replacement committers and project leads can be identified); or
3) Archive the project.

If existing adopters aren't willing/able to step up and take over responsibility for the project (option #2), they might consider either grabbing the CVS repository, or Git cloning the current code base. If the project is moved to GitHub, then the 'org.eclipse' namespace will have to be changed and--possibly--the project name (as 'eRCP' is trademarked by the Eclipse Foundation).

Is there anybody from the project who can respond?

Wayne

On 09/26/2012 09:13 AM, Thomas Watson wrote:

My understanding is that eRCP is contained in CVS (http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.ercp/?root=RT_Project) and not SVN.  The foundation is planning to pull the plug on the CVS support this year.  If there is still interest in the community to build the current project then I think it is in your best interest to have the current project leadership for eRCP to create a git repository at eclipse.org to host the code. Then it can get mirrored to github and you can do your own maintenance there in a fork.

Wayne, does this sound reasonable to you?  Should we get Eric Hsu to open a bug to request a git repo get created to house the eRCP bits

Tom



andrea antonello ---09/26/2012 01:25:41 AM---Even if I am not part of the project I wanted to ask what the termination review would mean.

From: andrea antonello <andrea.antonello@xxxxxxxxx>
To: ERCP developers list <ercp-dev@xxxxxxxxxxx>,
Date: 09/26/2012 01:25 AM
Subject: Re: [ercp-dev] Time for a termination review for eRCP?
Sent by: ercp-dev-bounces@xxxxxxxxxxx

Even if I am not part of the project I wanted to ask what the
termination review would mean.

I mean, even if the SVN is not migrated, are the latest snapshots
archived and made available?

We have still projects building on the community version of eRCP, so
it would be good to know we are not completely lost in space.

Thanks,
Andrea Antonello

On Tue, Sep 25, 2012 at 4:28 PM, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:
> The RT PMC list has been discussing the migration to git [1].  The last RT
> project to move to git is eRCP.  I think this project is no longer active
> and I don't see the need to migrate eRCP to git.  The PMC has been
> discussing the need to start a termination review for eRCP [2].  Are there
> any active committers for eRCP that have the time and interest to keep the
> project moving forward?  If not then the PMC is going to move forward with a
> termination review.
>
> Thanks.
>
> Tom Watson
>
> [1] - http://dev.eclipse.org/mhonarc/lists/rt-pmc/msg03154.html
> [2] - http://dev.eclipse.org/mhonarc/lists/rt-pmc/msg03161.html
>
>
> _______________________________________________
> ercp-dev mailing list
> ercp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ercp-dev
>
_______________________________________________
ercp-dev mailing list
ercp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ercp-dev

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc