Jump to: navigation, search

Difference between revisions of "TPTP/Move To Tools"

(New page: [http://www.eclipse.org/tptp 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 developer...)
 
 
Line 4: Line 4:
  
 
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.
 
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.
 +
 +
Discussion regarding this move is captured on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=377692 Bug 377692].
  
 
==Projects==
 
==Projects==
  
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.  
+
The currently-separate subprojects, Tracing & Profiling Tools (tptp.performance), TPTP Platform (tptp.platform), Testing Tools (tptp.test) will roll up into a new parent project, TPTP (tools.tptp) as de facto components (the EDP does not have a formal concept of component). The existing committers will be rolled up into the new project. The existing TPTP projects will all be marked as terminated. No archival is required.
  
PMC leads and members, architecture council and planning council representatives will be deactivated.
+
TPTP PMC leads and members, architecture council and planning council representatives will be deactivated. The new tools subproject will be put into incubation with Wayne Beaton as a single project mentor.
  
 
TPTP Top-level charter will be revoked.
 
TPTP Top-level charter will be revoked.
Line 15: Line 17:
 
==Resources==
 
==Resources==
  
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 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 project website does not require any major modification.
  
 
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):
 
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):
Line 22: Line 24:
 
* /home/data/httpd/download.eclipse.org/tptp; and
 
* /home/data/httpd/download.eclipse.org/tptp; and
 
* /cvsroot/org.eclipse/www/tptp
 
* /cvsroot/org.eclipse/www/tptp
 +
 +
==Mailing lists==
 +
 +
Keep:
 +
*tptp-platform-dev
 +
 +
Create:
 +
*tptp-commit
 +
 +
Kill:
 +
*tptp-news
 +
*tptp-pmc
 +
*tptp-testing-tools-dev
 +
*tptp-trace-cvs-commit
 +
*tptp-tracing-profiling-tools-dev
 +
*tptp.monitoring-cvs-commit
 +
*tptp.platform-cvs-commit
 +
*tptp.test-cvs-commit
 +
*tptp.test-results-cvs-commit
  
 
==Bugzilla==
 
==Bugzilla==

Latest revision as of 14:05, 20 August 2012

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.

Discussion regarding this move is captured on Bug 377692.

Projects

The currently-separate subprojects, Tracing & Profiling Tools (tptp.performance), TPTP Platform (tptp.platform), Testing Tools (tptp.test) will roll up into a new parent project, TPTP (tools.tptp) as de facto components (the EDP does not have a formal concept of component). The existing committers will be rolled up into the new project. The existing TPTP projects will all be marked as terminated. No archival is required.

TPTP PMC leads and members, architecture council and planning council representatives will be deactivated. The new tools subproject will be put into incubation with Wayne Beaton as a single project mentor.

TPTP Top-level charter will be revoked.

Resources

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 project website does not require any major modification.

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):

  • /cvsroot/tptp;
  • /home/data/httpd/download.eclipse.org/tptp; and
  • /cvsroot/org.eclipse/www/tptp

Mailing lists

Keep:

  • tptp-platform-dev

Create:

  • tptp-commit

Kill:

  • tptp-news
  • tptp-pmc
  • tptp-testing-tools-dev
  • tptp-trace-cvs-commit
  • tptp-tracing-profiling-tools-dev
  • tptp.monitoring-cvs-commit
  • tptp.platform-cvs-commit
  • tptp.test-cvs-commit
  • tptp.test-results-cvs-commit

Bugzilla

All existing Bugzilla products under the TPTP classification will be migrated to a single "TPTP" product with existing components left intact.

IPZilla

All existing IPZilla components under the "tptp" product will be merged into a single "tools.tptp" component and the product removed.