User:Taavi/History of Toolforge

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This is a brief history of Toolforge.

Toolserver

Source for this is mw:Toolserver:History unless otherwise noted.

2005
- zedler (a Sun V40z server originally donated for Wikimania use) becomes the first Wikimedia "tools server".
2014
- Toolserver is shut down.^[1]

Tool Labs/Toolforge

Technical

2011
- Wikimedia Labs is founded, with a goal of making it possible for community members to develop and test infrastructure changes.^[2]
2013
- Wikimedia Tool Labs project is started, with a goal of replacing Toolserver.^[3]
2015
- Kubernetes selected as the replacement for the Grid Engine.^[4]
2016
- Kubernetes backend available for web services.^[5]
- toolsadmin.wikimedia.org (aka Striker) is introduced.^[6]
- toolsadmin extended to allow self-service git repository creation.^[7]
2017
- Wiki Replicas are rebuilt. The new cluster no longer supports user databases mixed with MediaWiki databases.^[8]
2019
- Last Ubuntu hosts are retired.^[9]
2020
- Kubernetes cluster is rebuilt.^[10]
- Kubernetes becomes the default backend (Grid Engine remains available).^[11]
- Toolforge.org domain is introduced with a single subdomain for each tool.^[12]
- Wiki Replicas are rebuilt. The new cluster no longer supports cross-section joins.^[13]
2022
- Toolforge Jobs Framework is released.^[14]
- Plans to deprecate the Grid Engine are announced.^[15]
2023
- lima-kilo development environment tool is released.^[16]
- Toolforge Build Service is released.^[17]
- Functionality to manage envvars for Kubernetes jobs is announced.^[18]
2024
- Grid Engine is shut down.^[15]

2016
- Wikimedia Foundation Community Tech Tool Labs support team is founded.^[19]
- Right to fork policy and abandoned tool policy adopted by community after vote on meta.
2017
- Toolforge standards committee created to help manage the right to fork and abandoned tool policies.^[20]
- Community Tech Tool Labs support team and Labs Ops team are merged to form the Wikimedia Cloud Services team.^[21]
- Tool Labs is rebranded as Toolforge.^[22]

References

[1] w:Tool Labs/Collection of issues after Toolserver shutdown

[2] Ever wondered how the Wikimedia servers are configured?

[3] Old revision of mw:Wikimedia Labs/Toolforge

[4] [Labs-announce] [Tools] Kubernetes picked to provide alternative to GridEngine

[5] [Labs-announce] Kubernetes Webservice Backend Available for PHP webservices

[6] T136256 Deploy "Striker" Tool Labs console to WMF production

[7] [Labs-l] [NEW] Self-service git repository creation for tools

[8] News/2017 Wiki Replica c1 and c3 shutdown

[9] News/2019 Toolforge Trusty deprecation

[10] News/2020 Kubernetes cluster migration

[11] T154504

[12] News/2020 Toolforge.org domain introduction

[13] News/2020 Wiki Replicas Redesign

[14] Revision history of Help:Toolforge/Jobs framework

[grid-deprecation-15] 15.0 ^15.1 News/Toolforge Grid Engine deprecation

[16] Portal:Toolforge/Admin/Kubernetes/lima-kilo

[17] Help:Toolforge/Build Service

[18] Help:Toolforge/Envvars Service

[19] ta:Community Tech/Tool Labs support

[20] [Labs-l] [Labs-announce] [Tools] Announcing right to fork policy, abandoned tool policy, and Tool Labs standards committee

[21] [Wikimedia-l] Wikimedia Cloud Services: new team, new name, renewed focus

[22] Wikimedia Cloud Services team/Rebranding Cloud Services products

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

Toolserver

Tool Labs/Toolforge

Technical

Social

References