Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "STP/Termination Review"

< STP
(→‎Dash)
(→‎Move stp.model to eBPM)
 
(32 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
This document contains the Termination Review documentation.
 
This document contains the Termination Review documentation.
  
−
{{message|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}}
+
End of review date: April 25/2012.
  
−
=Bugzilla=
+
=General=
 +
Project/component-specific move information is captured below. After all project/component-specific changes have been effected, here's what we plan to do with everything else.
  
−
Over [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;classification=STP five hundred bugs] in various states exist for STP. These bugs need to be moved.
+
*Bugzilla
 +
** Archive [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;type0-0-0=anywordssubstr;value0-0-0=iplog;component=website;classification=STP website bugs]
 +
** Archive [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;classification=STP remaining bugs] (after required project moves)
 +
*IPZilla
 +
** Archive [https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=stp&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= STP CQs in IPZilla]
 +
* Archive and remove Mailing lists
 +
** stp-pmc
 +
** stp-users
 +
** stp-dev
 +
** stp-user
 +
* Archive and remove Forums/Newsgroups
 +
** [http://www.eclipse.org/forums/index.php/f/103/ Service Oriented Architecture Tools Platform (STP)] and corresponding [news://news.eclipse.org/eclipse.stp newsgroup]
 +
** [http://www.eclipse.org/forums/index.php/f/185/ SOA Policy tools project] and corresponding [news://news.eclipse.org/eclipse.soapolicytools newsgroup]
 +
* Hudson Jobs
 +
** There are no Hudson Jobs
 +
* Archive and remove downloads
 +
** /home/data/httpd/download.eclipse.org/stp
 +
** /home/data/httpd/archive.eclipse.org/stp
 +
* Archive and remove Top-level project Website
 +
** /www/stp
 +
* Archive and remove Top-level project source repositories (contains nested subproject repositories)
 +
** /svnroot/stp
 +
* Deactivate members
 +
** Committers
 +
** Project Leads
 +
** PMC Lead/Members
 +
** Architecture Council Representative
 +
** Planning Council Representative
  
−
Move to where? Do we just archive some/all of them?
+
=Projects/Components=
  
−
{{message| (omh) Suggest that everything that is marked RESO is archived at least and that we look at the NEW/ASSI/REOPs only. There are a number of bugs there that are related to the operation of the project and, upon termination, will no longer be relevant. We should mark as RESO/WONT and then archive. }}
+
There are several active subprojects. Most of these projects are inactive and will be terminated and archived as part of this review.
  
 +
== Move stp.model to eBPM  ==
 +
Due to the termination of STP project the project will be moved in the Eclipse SOA [http://www.eclipse.org/ebpm eBPM Project] repositories.
  
−
=IPZilla=
+
NOTE: The [http://www.eclipse.org/mangrove/ Mangrove project] in Eclipse SOA is the future home for this code. The reason for moving stp.model to eBPM is for immediate practical maintenance reasons due to legacy code dependencies that have not been migrated to Mangrove's new code structure. A move review will be scheduled when Mangrove is prepared to receive this code.
  
−
There are [https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=stp&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 94 CQs in IPZilla] assigned to STP. These need to be moved.
+
Comments
 +
* Downloads will be archived with the top-level project;
 +
* Source directories not explicitly listed below will be archived along with the top-level project
  
−
Move to where? Do we just archive some/all of them?
+
Source Code
 +
* Move the source code:
 +
** from /svnroot/stp/org.eclipse.stp.intermediate-model/org.eclipse.stp.model/trunk/
 +
**to /svnroot/soa/org.eclipse.ebpm/trunk/im/:
 +
* Subdirectories
 +
**org.eclipse.stp.im
 +
**org.eclipse.stp.im.edit
 +
**org.eclipse.stp.im.editor
 +
**org.eclipse.stp.im.in.bpmn
 +
**org.eclipse.stp.im.resources
 +
**org.eclipse.stp.im.runtime
 +
**org.eclipse.stp.im.tests
 +
**org.eclipse.stp.im.in.bpmneditor
  
−
{{message| (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?}}
+
Bugzilla
 +
* Move [https://bugs.eclipse.org/bugs/buglist.cgi?list_id=1010417;classification=STP;query_format=advanced;component=org.eclipse.stp.model;product=SOA Bugzilla records]
  
−
=Projects/Components=
+
IPZilla
 +
* Move CQ [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1588 1588]|[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1630 1630]|[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1635 1635]
 +
 
 +
==Terminate and Archive stp.policy==
 +
 
 +
Comments
 +
*No CQs associated with this subproject;
 +
*No special handling required for Bugzilla Records;
 +
*Website is nested under /stp (will be archived along with the top-level project);
 +
*Downloads are nested under /stp (will be archived along with the top-level project);
 +
*Source code is nested under /svnroot/stp (will be archived along with the top-level project)
 +
 
 +
Action Items
 +
*Deactivate project committers
 +
 
 +
==Terminate and Archive stp.b2j==
 +
Comments
 +
* No CQs associated with this subproject;
 +
* No special handling required for Bugzilla Records;
 +
* Website is nested under /stp (will be archived along with the top-level project);
 +
* Downloads are nested under /stp (will be archived along with the top-level project);
 +
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
 +
 
 +
Action Items
 +
* Deactivate project committers
  
−
The Eclipse Foundation database lists several 'components' of STP. I believe that some of these may have been created as components by accident. Regardless, these components either need to be shutdown or moved.
+
==Terminate and Archive stp.build==
 +
Comments
 +
* No CQs associated with this subproject;
 +
* No special handling required for Bugzilla Records;
 +
* Website is nested under /stp (will be archived along with the top-level project);
 +
* Downloads are nested under /stp (will be archived along with the top-level project);
 +
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
  
−
*stp.b2j
+
Action Items
−
*stp.build
+
* Deactivate project committers
−
*stp.core
+
−
*stp.creation
+
−
*stp.eid
+
−
*stp.model
+
−
*stp.policy
+
−
*stp.system
+
−
*stp.web
+
  
−
I believe that the stp.web project is the pseudo project created to manage commit access to the project website.
+
==Terminate and Archive stp.core==
 +
Comments
 +
* No CQs associated with this subproject;
 +
* No special handling required for Bugzilla Records;
 +
* Website is nested under /stp (will be archived along with the top-level project);
 +
* Downloads are nested under /stp (will be archived along with the top-level project);
 +
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
  
−
{{message| (omh) b2j, core, creation, system, eid, build should all be shutdown as they are not in operation. model and policy may still be in operation. Web is indeed the website pseudo-project and doesn't existing in the STP SVN repo.}}
+
Action Items
 +
* Deactivate project committers
  
−
=Dash=
+
==Terminate and Archive stp.creation==
 +
Comments
 +
* No CQs associated with this subproject;
 +
* No special handling required for Bugzilla Records;
 +
* Website is nested under /stp (will be archived along with the top-level project);
 +
* Downloads are nested under /stp (will be archived along with the top-level project);
 +
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
  
−
Dash is reporting some recent activity (some of it in 2011) against the STP top-level project.
+
Action Items
 +
* Deactivate project committers
  
−
<pre>mysql> select distinct substring_index(FileName, '/', 2) from commits where topproject='stp' and year>2009;
+
==Terminate and Archive stp.eid==
−
+-----------------------------------+
+
Comments
−
| substring_index(FileName, '/', 2) |
+
* No CQs associated with this subproject;
−
+-----------------------------------+
+
* No special handling required for Bugzilla Records;
−
| /build                            |
+
* Website is nested under /stp (will be archived along with the top-level project);
−
| /org.eclipse.stp.model            |
+
* Downloads are nested under /stp (will be archived along with the top-level project);
−
| /org.eclipse.stp.validation      |
+
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
−
| /org.eclipse.stp.policy          |
+
−
+-----------------------------------+</pre>
+
  
−
I suspect that this is just old metadata in the STP record. Have these CVS/SVN directories been assigned to other projects?
+
Action Items
 +
* Deactivate project committers
  
−
{{message| (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.}}
+
==Terminate and Archive stp.system==
 +
Comments
 +
* No CQs associated with this subproject;
 +
* No special handling required for Bugzilla Records;
 +
* Website is nested under /stp (will be archived along with the top-level project);
 +
* Downloads are nested under /stp (will be archived along with the top-level project);
 +
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
  
−
=Mailing Lists, Forums, and Newsgroups=
+
Action Items
 +
* Deactivate project committers
  
−
The following lists should be archived:
+
==Terminate and Archive stp.web ==
−
* stp-pmc
+
Comments
−
* stp-users
+
* No CQs associated with this subproject;
−
* stp-dev
+
* No special handling required for Bugzilla Records;
−
* stp-user
+
* Website is nested under /stp (will be archived along with the top-level project);
 +
* Downloads are nested under /stp (will be archived along with the top-level project);
 +
* Source code is nested under /svnroot/stp (will be archived along with the top-level project)
  
−
The "Service Oriented Architecture Tools Platform (STP)" forum and corresponding newsgroup should be archived.
+
Action Items
 +
* Deactivate project committers

Latest revision as of 12:52, 19 April 2012

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.

End of review date: April 25/2012.

General

Project/component-specific move information is captured below. After all project/component-specific changes have been effected, here's what we plan to do with everything else.

  • Bugzilla
  • IPZilla
  • Archive and remove Mailing lists
    • stp-pmc
    • stp-users
    • stp-dev
    • stp-user
  • Archive and remove Forums/Newsgroups
  • Hudson Jobs
    • There are no Hudson Jobs
  • Archive and remove downloads
    • /home/data/httpd/download.eclipse.org/stp
    • /home/data/httpd/archive.eclipse.org/stp
  • Archive and remove Top-level project Website
    • /www/stp
  • Archive and remove Top-level project source repositories (contains nested subproject repositories)
    • /svnroot/stp
  • Deactivate members
    • Committers
    • Project Leads
    • PMC Lead/Members
    • Architecture Council Representative
    • Planning Council Representative

Projects/Components

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

Move stp.model to eBPM

Due to the termination of STP project the project will be moved in the Eclipse SOA eBPM Project repositories.

NOTE: The Mangrove project in Eclipse SOA is the future home for this code. The reason for moving stp.model to eBPM is for immediate practical maintenance reasons due to legacy code dependencies that have not been migrated to Mangrove's new code structure. A move review will be scheduled when Mangrove is prepared to receive this code.

Comments

  • Downloads will be archived with the top-level project;
  • Source directories not explicitly listed below will be archived along with the top-level project

Source Code

  • Move the source code:
    • from /svnroot/stp/org.eclipse.stp.intermediate-model/org.eclipse.stp.model/trunk/
    • to /svnroot/soa/org.eclipse.ebpm/trunk/im/:
  • Subdirectories
    • org.eclipse.stp.im
    • org.eclipse.stp.im.edit
    • org.eclipse.stp.im.editor
    • org.eclipse.stp.im.in.bpmn
    • org.eclipse.stp.im.resources
    • org.eclipse.stp.im.runtime
    • org.eclipse.stp.im.tests
    • org.eclipse.stp.im.in.bpmneditor

Bugzilla

IPZilla

Terminate and Archive stp.policy

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.b2j

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.build

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.core

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.creation

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.eid

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.system

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers

Terminate and Archive stp.web

Comments

  • No CQs associated with this subproject;
  • No special handling required for Bugzilla Records;
  • Website is nested under /stp (will be archived along with the top-level project);
  • Downloads are nested under /stp (will be archived along with the top-level project);
  • Source code is nested under /svnroot/stp (will be archived along with the top-level project)

Action Items

  • Deactivate project committers
Retrieved from "https://wiki.eclipse.org/index.php?title=STP/Termination_Review&oldid=298685"

This page was last modified 12:52, 19 April 2012 by Wayne Beaton. Based on work by Adrian Mos, Andrea Zoppello and Oisin Hurley.

Back to the top