Project management tools

Current situation
Bugzilla

http://bugzilla.wikimedia.org | Technical information | Workflow information

RT

http://rt.wikimedia.org | Technical and workflow information

Gerrit

http://gerrit.wikimedia.org

Mingle and Trello are proprietary project management tools. Some teams at the Foundation use them in addition to the open source Bugzilla tool.

A third proprietary project management tool, Asana, is used by The Grantmaking Learning & Evaluation team to manage collaborative research projects. It supports lightweight task assignment, easy email and Google Calendar integration. It also makes it easy for other Grantmaking staff to propose tasks and monitor the status of a given task.

Mingle
The purpose of Mingle is to plan your work and keep track of who did what along the way. The Foundation is using Mingle as part of a push toward adoption of an Agile approach to software development, for which Mingle was specifically built. Mingle is made by ThoughtWorks, and ThoughtWorks has done a few training sessions at the Foundation about adopting Agile processes in general. Mingle somewhat duplicates functionality present in Bugzilla, but can be integrated with both that and some version control systems.

WMF engineers have developed tools to integrate Mingle with Bugzilla, see Bingle

Wikimedia Foundation installation

 * URL: https://wikimedia.mingle.thoughtworks.com/

In 2013 projects were on a server managed by WMF Office IT technical team, https://mingle.corp.wikimedia.org/, before migrating to the host above.

Teams using Mingle

 * Analytics
 * Core features (Flow project) switching to Trello
 * Fundraising
 * i18n
 * Mobile
 * Wikidata (Wikimedia Deutschland)

Trello
Trello is a lighter-weight project management tool, lacking Mingle's story points, velocity, story hierarchy, etc. Several Wikimedia Foundation projects, including Wikipedia Zero, Mobile Apps, Core features, design, notifications, research/data analysis, and Growth, are using Trello boards, which collectively paid for with a "Business Class" license. Though it is closed source, non-members of Trello boards can view and comment on cards, and all data is exportable in open formats if we decide Trello is not for us.

You can see all WMF boards at trello.com/wikimediafoundation

How much does Trello cost per year?

 * Trello Business Class costs $25/month ($200 a year) for the WMF collectively

What are the alternatives to Mingle and Trello?
The following are very popular alternatives in the context of Mingle's approach, which is roughly similar to other scrum task boards or Kanban boards. They may not necessarily be viable alternatives, but since we're already using a closed source tool, this list should probably include them.

In somewhat hazy order of popularity and suitability for use by wiki-familiar developers:


 * Pivotal Tracker. Closed source, but wildly popular in the Agile crowd. Provides free licenses to public projects and/or non-profits.
 * 1) Fulcrum, an open source Pivotal Tracker clone
 * 2) various extensions and dashboards for Bugzilla, mostly developed by Mozilla. Wikimedia Deutschland experiments with Scrumbugz.
 * GreenHopper + JIRA. Popular but closed source and often a bear. Not particularly attractive for our needs.
 * Trac. Open source. More project management than Agile development.  Apache Bloodhound is built on top of Trac.
 * Redmine. Open source. More project management than Agile development
 * 1) iceScrum. Open source, made for agile (cards, automatic graphics). Code integration only in the separate commercial version.
 * 2) github + a Kanban layer on top of it.  Closed source.  Examples include like huBoard or gitban.
 * 3) Phabricator, an open source tool that integrates a number of project management tools, including code review. (Wikimedia Labs instance)
 * 4) Storyboard of OpenStack, which might replace their Launchpad use.
 * 5) Online Kanban board of Kanban Tool. Closed source. Provides some extensions and integration possiblities. Tries to remain in line with the Kanban method. Offers time tracking and time reports.

Is MediaWiki itself a viable project management tool?
People often use non-specialized tools for project management. MediaWiki certainly can and has been extended for this purpose. Notable examples (please add more) include:
 * Creative Commons released a task management extension called cc:Teamspace
 * Extension:Semantic_Project_Management released with Halo.

Neither extension is being actively maintained for the Semantic Bundle or current versions of mediawiki.

Some weaknesses that inhibit the use of mediawiki for task management include:
 * lack of facilities to automatically create obvious pages when linked, e.g. names of modules or persons or concepts already existing in large public wikis such as Wikipedia - laborious creation of manual redirects
 * poor integration with GitHub, SourceForge, or any software IDE - updating documentation in a mediawiki is not going to automatically update documentation in those, nor vice versa
 * poor conciousness of dates and times, e.g. no automatic sequencing of pages unless named alphabetically with a standard naming convention
 * poor conciousness of dependencies, e.g. when one page must be modified just because another has been, including making it quite difficult to embed pages from say a development wiki into a documentation wiki en masse.

If you are aware of any extensions which address these issues or generate task lists with dependencies, or automatically embed or import or generate pages when a new link indicates they are important to a project, please list here. Also you are or were a developer of Teamspace or SPM or know of any attempt to revive these.