Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-members-committers] Project updates

Greetings Folks. In this note, I'm discussing some upcoming reviews, the ongoing Project Management Infrastructure work, and our Git migration status.

Reviews
=====

We have several reviews running this week, wrapping up on September 26/2012.

First up, is the Emfatic [1] project's 0.8 Release Review [2]. Emfatic is a language designed to represent EMF Ecore models in a textual form. This will be the project's first incubation release.

Next, is a combined 2.1 Release Review [3] for the EGit [4] and JGit [5] projects. EGit and JGit are very good examples of project diversity: EGit's nineteen committers and JGit's ten committers come from eight different organizations. The new and noteworthy documents for these projects (accessible through the web site links) detail the many new features.

Next is the m2e-wtp [6] project's first incubation release, 0.16 [7]. m2e-wtp provides tight integration between Maven Integration for Eclipse (m2e) and the Eclipse Web Tools Project (WTP).

Finally, the Test and Performance Tools Platform [8] is engaging in a restructuring review [9]. This former top-level project is consolidating and moving under Tools. Activity on the project has reduced significantly over the past year and so the PMC has decided that TPTP is no longer viable as a top-level project. With this restructuring, the TPTP subprojects will be combined into a single project. The actual day-to-day operation of the projects will remain more-or-less unchanged. Source code repositories, downloads, and the project website do not need to be moved, so there should be no impact on adopters or developers.

Project Management Infrastructure (Portal)
===========================

Most committers should already be aware of our efforts to replace the developer portal with new technology in what we're calling the "Project Management Infrastructure" (PMI). My plan is to start rolling out the new implementation over the next couple of weeks and run it in parallel with the existing system. Over time, we'll phase functionality out of the old portal in favour of the new system.

As part of the PMI effort, we've reimplemented the CQ experience. Nathan, wrote about his work in this area on his blog [A]. The process is basically the same as it is in the existing portal, with a few cosmetic differences. The look and feel is a lot better, IMHO.

One of the things that I am particularly fond of is the first class way in which we're able to treat things like projects, releases, and elections. With the new system, we'll be able to do very simple things that just aren't currently possible like provide a pointer to a release, election (ongoing or complete), or even a committer's relationship with a project.

There's still a lot of work to do. I'm keen to implement some "Getting Involved/Contributing" eye-candy for projects [B], along with other improvements that will increase the transparency and openness of projects without requiring a lot of effort from the project's developers. I'm hopeful that the new "project" pages in the PMI will be suitable project web sites (thereby getting project developers out of the business of maintaining HTML and PHP web site code).

The evolving implementation of the PMI is online now [C]. Feel free to take a tour (FWIW, if you create a CQ, it'll go into our test instance of IPZilla, not the real one).

I'm presenting a talk on the PMI at EclipseCon Europe. I hope to see you there.

Git Migration
========

The migration to Git is moving along quite well. More than 60% of our repositories are Git. Similarly, more than 60% of our projects have completely migrated to Git, another ~5% of our projects have a combination of Git and either SVN or CVS.

If your project hasn't made plans to move to Git, time is running short. We're pulling the plug on CVS on December 21/2012 [D].

We have started migrating project web sites to Git. If you're ready to migrate your project's web site. There's lots of information on Git migration (including how to get help) on the wiki [E].

Questions
======

If you have any questions, comments, or concerns, please let me know. Or... open a bug.

Wayne

[1] http://www.eclipse.org/projects/project.php?id=modeling.emft.emfatic
[2] https://bugs.eclipse.org/bugs/attachment.cgi?id=221147
[3] https://bugs.eclipse.org/bugs/attachment.cgi?id=220951
[4] http://www.eclipse.org/projects/project.php?id=technology.egit
[5] http://www.eclipse.org/projects/project.php?id=technology.jgit
[6] http://www.eclipse.org/projects/project.php?id=technology.m2e.m2e-wtp
[7] https://bugs.eclipse.org/bugs/attachment.cgi?id=221191
[8] http://www.eclipse.org/projects/project.php?id=tptp
[9] http://wiki.eclipse.org/TPTP/Move_To_Tools
[A] http://nathangervais.blogspot.ca/2012/06/redesigning-ipzilla-cq-experience.html
[B] https://bugs.eclipse.org/bugs/show_bug.cgi?id=378016
[C] http://projects.eclipse.org
[D] http://eclipse.org/projects/scmcountdown.php
[E] http://wiki.eclipse.org/Git/Migrating_to_Git#Migrating_Your_Project_Website
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
EclipseCon
          Europe 2012

Back to the top