STP/Termination Review

All of the projects operating under the SOA Tools Project (STP) top-level project have been moved to the SOA top-level project. It is time to retire the STP project itself.

This document contains the Termination Review documentation.

This document is a work-in-progress. There are currently several open questions that must be answered before we can move forward with the review

Bugzilla

• Archive website bugs
• Archive remaining bugs (after required project moves)

IPZilla

There are 94 CQs in IPZilla assigned to STP. These need to be moved.

Move to where? Do we just archive some/all of them?

(omh) as I understand it, projects that have migrated from STP to elsewhere will need to keep their IPzilla entries, others may be archived, right?

Projects/Components

There are several active subprojects. Most of these projects are inactive and will be terminated and archived as part of this review.

Terminate and Archive stp.b2j

Comments

• No CQs associated with this subproject

Action Items

• Deactive project committers

Terminate and Archive stp.build

Comments

• No CQs associated with this subproject
• No bugs associated with this subproject

Action Items

• Deactive project committers

Terminate and Archive stp.core

Comments

• No CQs associated with this subproject
• No Bugs associated with this subproject

Action Items

• Deactive project committers

Terminate and Archive stp.creation

Comments

• No CQs associated with this subproject
• No Bugs associated with this subproject

Action Items

• Deactive project committers

Terminate and Archive stp.eid

Action Items

• Archive stp.eid bugs

Terminate and Archive stp.web

The stp.web project is the pseudo project created to manage commit access to the project website.

• Deactive project committers
• Deactive stp.web UNIX group.

Top Level Project

• Archive STP Project website
• Archive STP Project Downloads

Dash

Dash is reporting some recent activity (some of it in 2011) against the STP top-level project.

mysql> select distinct substring_index(FileName, '/', 2) from commits where topproject='stp' and year>2009;
+-----------------------------------+
| substring_index(FileName, '/', 2) |
+-----------------------------------+
| /build                            | 
| /org.eclipse.stp.model            | 
| /org.eclipse.stp.validation       | 
| /org.eclipse.stp.policy           | 
+-----------------------------------+

I suspect that this is just old metadata in the STP record. Have these CVS/SVN directories been assigned to other projects?

(omh) These are not dead - there is some tiny activity there, especially in .model, which is being used by one company - a new version of this code has been checked into the SOA TLP, but the company is not able to migrate at this time. Validation and policy again are aligned with SOA TLP afaik, so do consult with those guys.

Mailing Lists, Forums, and Newsgroups

The following lists should be archived:

• stp-pmc
• stp-users
• stp-dev
• stp-user

The "Service Oriented Architecture Tools Platform (STP)" forum and corresponding newsgroup should be archived.