The Eclipse Foundation has designated December 21/2012 as the day that
CVS will no longer be supported for Eclipse projects. TPTP is therefore
compelled to move the existing repositories to Git.

The actual process of migration is pretty well-defined [1] and--with
assistance from the Webmaster team--darned easy. The biggest challenge
is the transition of developer skills from CVS to Git. There are some
resources in the Eclipse Wiki [2,3,4]. Are TPTP developers ready for a
transition to Git?

In terms of structuring the repositories, we have some flexibility. The
webmaster will provide the project with space on the Git server. The
project can make as many Git repositories in that space as are
necessary. Right-sizing the repositories is an interesting challenge.
There are five subdirectories in TPTP CVS: hyades, platform, test,
test-results, and trace. The naive approach would be to just make each
of these directories into a separate Git repository. This is probably as
good a choice as any. Other ideas?

Are all of the directories that I listed (hyades, platform, test,
test-results, and trace) current? Should any of them just be archived?

Torsten

Wayne

[1] http://wiki.eclipse.org/Git/Migrating_to_Git
[2] http://wiki.eclipse.org/EGit/Git_Introduction
[3] http://wiki.eclipse.org/Git_for_Committers
[4] http://wiki.eclipse.org/EGit/Git_For_Eclipse_Users
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects <http://www.eclipse.org/projects>

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

I'm going to move forward with the move of TPTP to Tools.

Thanks for addressing that.

In terms of day-to-day operations, I don't think that anything will
change as a result of the restructuring. Independent of this
restructuring, however, CVS has been deprecated and will be taken out of
service in December 2012; TPTP is therefore compelled to migrate the
existing CVS repositories to Git.

I intend to complete the restructuring first, and the migration to Git
second. As part of the move, we will collapse the TPTP subprojects into
a single project under Tools. This will mean joining the committer lists
which shouldn't be a big deal since the committer lists are the same
across all projects anyway. While the underlying UNIX groups will
change, this will have no impact on operations.

I'll address the Git migration in a separate thread.

The moved project will be put into the incubation phase. I will switch
roles from PMC lead to project mentor. I will solicit the Architecture
Council for a second mentor.

I intend to kill off all but the tptp-platform-dev mailing list and
leave the TPTP forum in place. Does it make sense to consider creating a
tptp-dev mailing list?

tptp-platform-dev is sufficient in my view.

Note that we do not have the ability to change
the name of a mailing list, so any history would be accessible only
through an archive.

I have already asked the EMO(ED) to ask the Eclipse board to revoke the
TPTP project charter. This will hopefully be addressed in the Sept. 18
meeting.

The charter [1] describes the scope of the project as such:

The Eclipse Test & Performance Project will extend the family of
Eclipse technologies to provide an open development platform supplying
frameworks and services for test and performance tools that are used
throughout the lifecycle (e.g., testing, tracing/profiling, tuning,
logging, monitoring, analysis, autonomics, administration, etc., but
not development tools such as optimizing compilers) and support a
spectrum of standalone through highly-distributed and embedded through
enterprise computing systems.

The project will also deliver exemplary tools that verify the utility
of and illustrate the appropriate use of the platform, support the
development and maintenance of the platform itself, and are extensible
via documented programmatic interfaces.

I feel that this scope is too broad for a Tools subproject, so we'll
have to work out something different. Perhaps we can combine the scopes
of the three subprojects and use that. I'll try to take a crack at that.
Any thoughts or input is appreciated.

I'd like to schedule the restructuring review in the next couple of
weeks (i.e. before the end of August). Once that is complete, we can
tackle the Git migration.

Torsten

Wayne

[1] http://www.eclipse.org/tptp/groups/PMC/project_charter.php
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects <http://www.eclipse.org/projects>

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