Distinguished Planning Council (cc: Shawn Pearce, EGit Project Lead).
As you are already aware, the EGit Project did not declare their
desire to participate in the Helios release train prior to the M4
release deadline. The EGit project does however, does need to be part
of the release and has indicated their desire to participate in the
Foundation portal. I/we believe that it is in the best interests of
the broader Eclipse Community to permit an exception and include EGit
despite them missing M4 deadline.
The Eclipse webmasters are in the process of implementing a number of
upgrades to our development tools. Part of this upgrade strategy is
the establishment of Git as a first-class source code repository at
eclipse.org (see bug 257706 [1]). After consultation with members of
the community and the Eclipse Architecture Council, it was decided
that a "quality team provider" for Git must be in place prior to any
attempt to make Git first-class at Eclipse (see bug 293192 [2]). The
EGit project provides the required first-class tools for Git-based
development.
To summarize: the success of the EGit project is fundamental to the
adoption of Git at eclipse.org.
I ask the Planning council to make an exception to the participation
deadline requirement and permit EGit to participate in the Helios
Release Train.
Thank your for your consideration.
Wayne
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=257706
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=293192
