Community
Participate
Working Groups
After we deal with Bug 463691 and actually shut down dash.eclipse.org, we should terminate the Dashboard (technology.dash.dashboard) project.
AFAICT, the process that runs the dashboard code last ran in April 2017. I believe that from this we can reasonably assert that any other processes that are dependent on the data harvested by this process will not break if we archive the repository. I'll take a full inventory before I schedule this review.
I have tentatively scheduled the termination review for Feb 20 2019. Following termination, we'll need to shutdown/archive: * Website * Git repositories * Mailing list * Forum * Bugzilla product * Retire committers, project leads, and mentors Have I missed anything?
I have retired the committers and project lead and marked the project as archived in the PMI. Webmaster, please archive this project's resources.
I'm pretty sure that the project has no resources. Webmaster, can you please confirm that the dash/org.eclipse.dash.dashboard repository is no longer being checked out to run statistics gathering on any of our systems (I'm pretty sure that we shut this down a long while back). Further, can you confirm whether or not the UNIX group exists for this project team and whether or not it has access to any Git resources? If if anything, it may have control of dash/org.eclipse.dash.dashboard
(In reply to Wayne Beaton from comment #4) > Webmaster, can you please confirm that the dash/org.eclipse.dash.dashboard > repository is no longer being checked out to run statistics gathering on any > of our systems (I'm pretty sure that we shut this down a long while back). I don't see anything that references that repo so I don't think it's being checked out. > Further, can you confirm whether or not the UNIX group exists for this > project team and whether or not it has access to any Git resources? If if > anything, it may have control of dash/org.eclipse.dash.dashboard There is a group, but it doesn't have access to anything that I can see. -M.
I'm closing this bug since the issue has been resolved a long time ago.
I've marked the project as inactive in the Database.