Community
Participate
Working Groups
Created attachment 169127 [details] Termination Review Slides. This bugzilla is opened as a result of the termination review of the TPTP Monitoring Tool sub-project. The review slide file is attached. The following steps will need to be performed as part of the termination process: - Notify the community about project shutdown and provide a timeline of feedback. - De-committerize project committers. - Shut down: - Project Web Pages - CVS - Bugzilla products - Mailing lists - Archive: - Release builds. - CVS Following committers will have to be removed from the tptp.monitoring project . Joel Cayne (active) . Eugene Chan (active) . Kathy Chan (active) . Richard Huang (inactive) . Joanna Kubasta (inactive) . Ernest Mah (inactive) Released drivers to be archived on eclipse.org serves and link on the project shut down description page. Mailing list to be shutdown, disabled from posting and retain the archive. tptp-monitoring-tools-dev@eclipse.org WebSite to be shutdown: Replace http://www.eclipse.org/projects/project_summary.php?projectid=tptp.monitoring with a new archive description page. CVS module dev.eclipse.org/cvsroot/tptp/monitoring will be removed and archived on the eclipse.org servers. Remove the following products from Bugzilla: TPTP Build to Manage . Monitor.Agents . Monitor.UI.ManagedResourcesExplorer . Monitor.UI.WSDMTooling TPTP GLA . Documentation . Monitoring.Execution . Monitor.UI.GLARules TPTP Log Analyzer . Monitor.Analysis . Monitor.UI . Monitor.UI.Reporting . Monitor.UI.SDBEditor TPTP Resource Monitoring . Documentation . Monitor.Agents . Monitor.UI.CustomizedStatsView
Adding Anne and Webmaster to this bug so that the work can be started.... Webmaster: Please remove all remaining committer access and update the DB by way of script. I've checked remaining committer records and they all still commit to other projects; so no further action required. The project will also need to be archived in the DB. Thanks, Sharon
Is this something I can do now, or is there a better time? -M.
Webmaster, would you please let me know once you have a link to the achieved project file. Thanks!
Eugene; Can you tell me what parts of download.eclipse.org/tptp constitute the Monitoring downloads? -M.
(In reply to comment #4) > Eugene; > > Can you tell me what parts of download.eclipse.org/tptp constitute the > Monitoring downloads? > > -M. Joel, Would you please provide the information that webmaster is looking for?
(In reply to comment #4) > Eugene; > > Can you tell me what parts of download.eclipse.org/tptp constitute the > Monitoring downloads? > > -M. I believe you are referring to the Monitoring driver downloads (e.g. http://www.eclipse.org/downloads/download.php?file=/tptp/4.6.2/TPTP-4.6.2/tptp.monitoring.runtime-TPTP-4.6.2.zip). These are contained as part of the TPTP releases and not separated out. The older released versions are on archive.eclipse.org (currently up to Eclipse 3.5.2) and the remaining are on download.eclipse.org (Eclipse 3.5.2, and Eclipse 3.6). They are also part of the TPTP update site. Should those be left where they are for download?
Ok, I'll presume Eugene does mean the driver downloads and I'll add them to the archive tarball. Once that is done you should probably move the content to archive. -M.
(In reply to comment #7) > Ok, I'll presume Eugene does mean the driver downloads and I'll add them to the > archive tarball. > > Once that is done you should probably move the content to archive. > > -M. Joel, all released standalone monitoring project downloads should be archived. Please provide the information of them.
One final thing on the IP side, there are four CQs for Monitoring that were not marked "obsolete" as part of the recent IP Log Review for Helios. Unless the following CQs need to be moved to another TPTP project, we will mark them as "obsolete" as well. Please see: CQ113 - Axiom Dom.Jar 1.2 CQ1272 - Build to Manage Toolkit (EPL) CQ133 - Commons Logging 1.0.4 CQ306 - MX4J (JMX Engine Only) 3.0.1. Regards, Sharon
I've marked the four CQs identified in Comment #9 as "obsolete" and all project committers are marked as inactive via our internal DB. The project is still showing as "active" in our systems so perhaps there is more work to be done? As such I turn it back to Webmaster and the project for next steps. Regards, Sharon
The Foundation database has been updated. This project is marked as inactive and archived. Are we ready to close this bug?
I believe that Sharon's concerns in comment 10 have been addressed. I am marking this as FIXED.
closing bug.
