Portal:Toolforge/Ongoing Efforts/Toolforge Workgroup

Toolforge

• Cloud Services overview
• Toolforge user docs
• Toolforge changelog

Get started

• Quickstart: set up and get access
• How Toolforge works
• Rules you must follow
• Tutorials

Build and run tools

• Navigate tool accounts and files
• Build container images for tools
• Run a web service
• Schedule and manage jobs
• Manage tool runtime configuration (envvars)
• Language-specific details:
  • Python
  • Pywikibot
  • Node.js
  • PHP
  • ...more languages/frameworks
• Use Redis for caching
• Index content with Elasticsearch

Access shared storage and databases

• Access shared storage and public wiki dumps
• Access the Wiki Replicas databases
• Access replica search indices
• Manage tool databases

Share and maintain tools

• Set up version control and code review
• Develop successful tools
• Find and share tools on Toolhub
• Delete a tool
• Contribute to Toolforge

Get help

• How and where to get help
• Troubleshooting

Useful links

• Toolforge admin docs
• List of tools
• Toolforge Admin Console (toolsadmin)

[]

Toolforge Workgroup

About

Project Overview

Reports

Feedback

About

The Toolforge Workgroup is a focused workgroup to tackle both the maintenance and evolution of the Toolforge service itself.

It's formed by some WMCS team members (as of writing this), but any volunteer is welcome to participate. Note that you are expected to exclusively dedicate some time to it and to attend the sync meetings. For smaller contributions feel free to contact us on irc or phabricator and we can help you something to work on or just go ahead and pick whichever task you want to tackle.

Background

We started a workgroup for the Toolforge Build Service that worked pretty well, and at the same time, we started having toolforge admins periodical meetings to sync between ourselves.

Some time after, the Build Service evolved and it started needing and affecting more and more other Toolforge components, to the point that it was not about just the Build Service anymore. At that point we decided to widen the scope of the workgroup to the whole of Toolforge.

There's still the need to discuss and communicate between Toolforge admins what are the next steps and changes needed for Toolforge, so the toolforge admins periodical meetings will still happen, but there will be now a group of people coordinating to plan and implement the outcomes (this effort).

Communication and support

Support and administration of the WMCS resources is provided by the Wikimedia Foundation Cloud Services team and Wikimedia movement volunteers. Please reach out with questions and join the conversation:

Discuss and receive general support

• Chat in real time in the IRC channel #wikimedia-cloud ^connect or the bridged Telegram group
• Discuss via email after you have subscribed to the cloud@ mailing list

Stay aware of critical changes and plans

• Subscribe to the cloud-announce@ mailing list (all messages are also mirrored to the cloud@ list)
• Read the News wiki page

Track work tasks and report bugs

Use a subproject of the #Cloud-Services Phabricator project to track confirmed bug reports and feature requests about the Cloud Services infrastructure itself

Read stories and WMCS blog posts

Read the Cloud Services Blog (for the broader Wikimedia movement, see the Wikimedia Technical Blog)