|
|
|
# Summary
|
|
|
|
# Summary
|
|
|
|
|
|
|
|
The Eclipse Foundation has a MediaWiki instance(wiki.eclipse.org), and is proposing to deprecate this service in January 2024, and ultimately remove it in April 2026.
|
|
|
|
|
| ... | ... | @@ -6,7 +6,7 @@ The Eclipse Foundation has a MediaWiki instance(wiki.eclipse.org), and is propos |
|
|
|
|
|
|
|
The Foundation's community wiki instance was started in 2005 as somewhere for the community to collaborate on relevant content(documentation, meeting minutes, planning, etc) in a time where there was little integrated support for such activities. Now, it is more common and more convenient to find wiki content alongside the code repository. GitHub and Eclipse GitLab both support this more modern approach.
|
|
|
|
|
|
|
|
Furthermore, we are aware that there is a non-negligible amount of stale and orphaned content on the wiki which may have equally non-negligible consequences on our community as a whole : https://wiki.eclipse.org/Special:AncientPages
|
|
|
|
Furthermore, we are aware that there is a non-negligible amount of stale and orphaned content on the wiki which may have equally non-negligible consequences on our community as a whole : https://wiki.eclipse.org/Special:AncientPages
|
|
|
|
|
|
|
|
As such our proposal is driven by the following:
|
|
|
|
|
| ... | ... | @@ -18,31 +18,31 @@ To that end the Foundation’s IT team will work towards shutting down the stand |
|
|
|
|
|
|
|
### What’s been done so far
|
|
|
|
|
|
|
|
Only some preliminary planning and a few discussions about the path forward. Some projects have already elected to remove or duplicate their content in wikis that are available alongside their code.
|
|
|
|
Only some preliminary planning and a few discussions about the path forward. Some projects have already elected to remove or duplicate their content in wikis that are available alongside their code.
|
|
|
|
|
|
|
|
### What needs to be done
|
|
|
|
|
|
|
|
#### Content Migration Phase
|
|
|
|
#### Content Migration Phase
|
|
|
|
|
|
|
|
Help Projects migrate from wiki.eclipse.org to other integrated options:
|
|
|
|
|
|
|
|
* Provide Documentation, FAQ/How-Tos and examples of successful project migrations
|
|
|
|
* Agree on a timeline with projects and their communities
|
|
|
|
* Provide Documentation, FAQ/How-Tos and examples of successful project migrations
|
|
|
|
* Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/681
|
|
|
|
* Agree on a timeline with projects and their communities
|
|
|
|
* Create URL redirection rules for projects that want to move their content and would like wiki.eclipse.org to redirect to the new content location
|
|
|
|
|
|
|
|
#### Post-migration phase
|
|
|
|
#### Post-migration phase
|
|
|
|
|
|
|
|
* Medium Term read only copy
|
|
|
|
* Create a static copy of the existing wiki pages.
|
|
|
|
* Disable the MediaWiki application
|
|
|
|
|
|
|
|
* Disable the MediaWiki application
|
|
|
|
* Long Term service shutdown
|
|
|
|
* Remove the static copy, and replace with a generic 'service shutdown' page for pages that have not been redirected
|
|
|
|
* URL redirects remain active
|
|
|
|
|
|
|
|
### Proposed timeline
|
|
|
|
|
|
|
|
Throughout the entirety of this timeline, the IT team will use mailing lists, [eclipsestatus.io](https://eclipsestatus.io), Twitter and other means of communicating with projects the upcoming activities ahead of time.
|
|
|
|
### Proposed timeline
|
|
|
|
|
|
|
|
Throughout the entirety of this timeline, the IT team will use mailing lists, eclipsestatus.io, Twitter and other means of communicating with projects the upcoming activities ahead of time.
|
|
|
|
|
|
|
|
#### Apr-Jun 2023
|
|
|
|
|
| ... | ... | @@ -50,18 +50,19 @@ Throughout the entirety of this timeline, the IT team will use mailing lists, [e |
|
|
|
|
|
|
|
#### Oct-Dec 2023
|
|
|
|
|
|
|
|
* Send a notice reminding committers that the wiki will be made read-only
|
|
|
|
* Create a static copy of wiki.eclipse.org
|
|
|
|
* \[MW Oct/Dec\] Send two notices reminding committers that the wiki will be made read-only
|
|
|
|
* \[MW\] Create a static copy of wiki.eclipse.org
|
|
|
|
* Gather any potential redirects (a project may ask to redirect a Wiki namespace to another URL)
|
|
|
|
|
|
|
|
#### Jan-Mar 2024
|
|
|
|
|
|
|
|
* Deploy static copy of wiki.eclipse.org with redirects
|
|
|
|
* Archive the MediaWiki DB and application
|
|
|
|
* Shutdown and Archive the MediaWiki DB and application
|
|
|
|
|
|
|
|
#### Oct-Dec 2025
|
|
|
|
|
|
|
|
* Schedule service 'brownouts' for the static site.
|
|
|
|
* Send service shutdown reminder tp cpmitters
|
|
|
|
* Send service shutdown reminder to committers
|
|
|
|
|
|
|
|
#### Jan-Mar 2026
|
|
|
|
|
| ... | ... | @@ -71,5 +72,4 @@ Throughout the entirety of this timeline, the IT team will use mailing lists, [e |
|
|
|
#### Apr-Jun 2026
|
|
|
|
|
|
|
|
* Replace static site with a generic 'service shutdown' page
|
|
|
|
* Previously created redirects will remain active
|
|
|
|
|
|
|
|
* Previously created redirects will remain active |
|
|
\ No newline at end of file |
