TPTP/Move To Tools
TPTP no longer makes sense as a top-level project. With a single PMC member and limited development being done on TPTP projects by a small number of developers, it makes sense to move TPTP under the Tools banner.
We can do this with limited disruption, as very little of the infrastructure has to change to make this work. The existing projects will be merged into a single project, "tools.tptp". The source code repositories, project downloads, and community forum can stay where they are. Some change will be required in Bugzilla and IPZilla. We will use this opportunity to consolidate the many mailing lists.
Along with the move, the existing TPTP project charter will be revoked. This has already been added to the agenda for the board's September 2012 meeting.
The currently-separate subprojects (Tracing & Profiling Tools, TPTP Platform, Testing Tools) will roll up into the parent project as de facto components. The existing committers will be rolled up into the new project.
PMC leads and members, architecture council and planning council representatives will be deactivated.
TPTP Top-level charter will be revoked.
The repositories can stay where they are. They will need to be migrated to Git at some point, and so can stay at /cvsroot/tptp for now. The downloads can stay where they are, under /home/data/httpd/download.eclipse.org/tptp. There are no builds running in Hudson.
The existing UNIX groups, tptp.performance, tptp.platform, and tptp.test will be rolled into a single "tools.tptp" group. That group will be given access to all TPTP resources (including all nested subdirectories, recursively):
- /home/data/httpd/download.eclipse.org/tptp; and
All existing Bugzilla products under the TPTP classification will be migrated to a single "TPTP" product with existing components left intact.
All existing IPZilla components under the "tptp" product will be merged into a single "tools.tptp" component and the product removed.