User:Pavithraes/Sandbox/Help:Toolforge/Developing

This page is currently a draft.
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.

Toolforge
Toolforge technical documentation Toolforge administrator documentation Help and communication List of tools Terms of use Glossary
Getting started Cloud VPS and Toolforge at a glance About Toolforge Toolforge quickstart guide How to's, tutorials and walkthroughs Create a Wikimedia developer account Access Toolforge instances with PuTTY and WinSCP Troubleshooting Toolforge
Developing tools Tool accounts How to develop tools Develop Mono/.NET tools and bots Develop tools in Java Develop tools in Python Develop tools using Pywikibot framework Web servers for tools (Kubernetes) Grid engine
Additional documentation Version control in Toolforge Elasticsearch for Toolforge Redis for Toolforge Dumps and Toolforge Database

Overview

How to develop tools: Steps, best practices and resources.

Developing a successful tool

• License your source code and document that with a LICENSE or COPYING file in the tool's home directory and header comments in the source code. See Help:Toolforge/Developing § Licensing your source code.
• Use public version control (gerrit, diffusion, GitHub, Bitbucket, ...) for your tool's source code and deploy changes to the Toolforge servers by updating a checkout of that public version control. See Help:Toolforge § Setting up code review and version control. (Note: Keep passwords and other credentials (OAuth secrets, etc) separated from the main application code so that they are not exposed publicly in your version control system of choice.)
• Document the basics of what your tool does and how to start and stop it. Create a page in the Tool: namespace.
• If your tool is a web application, include some useful links on it for users. For example, you can include links to: feedback page, documentation, source code and license, authors name(s), etc.
• Find co-maintainers for your tools who can help out at least with starting/stopping jobs when needed.
• Make many small tools that each do one specific task rather than a catch-all tool that does many different tasks.

Writing tools

• Help:Toolforge/Java
• Help:Toolforge/Mono
• Help:Toolforge/Python
• Help:Toolforge/Pywikibot

Shared Tool code and files

Sharing files via packages or version control

• Package shared libraries using the package manager for your implementation language: PHP Composer packages, Python PyPI packages, Ruby gems, etc. This is the recommended and most portable and future-proof method of sharing code with multiple projects.
• Shared code can be stored in git submodules, which allow users to keep a git repository within another git repository. Sharing code in this way retains the maintainability and other source controls advantages of git. For more information about git submodules, please see the git documentation.

Sharing files via NFS

Programs running on the job grid and in Kubernetes webservice containers have access to shared NFS directories. This shared access can be used to share files between multiple tool accounts. This is the least portable method of sharing and may not be supported in all future Toolforge services.

• Access to a tool's code can be delegated to other tools by adding the tools as maintainers of the tool that is hosting the code. This can be done at https://toolsadmin.wikimedia.org/tools/id/<tool>/maintainers/. (It may be appropriate to create a new tool to house the shared code.)
• Shared config or other files may be placed in the /data/project/shared directory, which is readable (and potentially writeable) by all Toolforge tools and users. In this directory are available, for instance: a full MediaWiki checkout (core and all extensions in gerrit)

Licensing your source code

All code in the ‘tools’ project must be published under an OSI approved open source license. Please add a license at the beginning!

The absence of a license means that default copyright laws apply. Without a clear license you are implicitly claiming copyright without providing an explanation of the rights you are willing to grant to others who wish to use or modify your software. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work until standard copyright lapses. In the United States today that means until 70 years after your death. This is counter to the general principles of the Wikimedia movement.

The two easiest choices are GPL-3.0+ if you want to ensure that all derivative works are made available under the same license terms (an older GPL license is used for MediaWiki itself) or MIT if you only want to ensure that your original work is mentioned in a derivative project. This is a gross simplification of course. See choosealicense.com as a light primer on choosing a license.

Additional notes

Heavy processing

During heavy processing like compiles, tool test runs, etc.,

• use the (functionally identical) development environment instead of the primary login host to help maintain the interactive performance of the primary login host.
• use the job grid, because even when running on tools-dev, your processes may be killed without notice by system administrators or automated watch processes if performance of the shared server is severely impacted.

Support and communication

	Connect	Best for
Phabricator Workboard	#Cloud-Services	Task tracking and bug reporting
IRC Channel	#wikimedia-cloud connect	General discussion and support
Mailing List	cloud@	Information about ongoing initiatives, general discussion and support
Announcement emails	cloud-announce@	Information about critical changes (all messages mirrored to cloud@)
News wiki page	News	Information about major near-term plans
Blog	Clouds & Unicorns	Learning more details about some of our work