Page MenuHomePhabricator

SWT Indic Workshop Series 2020: Run a session on Phabricator
Closed, ResolvedPublic



Due Date
Jun 28 2020, 2:00 PM

Event Timeline

Aklapper created this task.

Etherpad notes

copied from



  • Andre: Technical Engagement team, spends a lot of time on Phabricator. Budg wrangler, see incoming tickets and organise better, and be of help to volunteer, staff developers, and community members.
  • Satdeep: Punjabi Wikipedia and Wikisource; also with WMF
  • Krishna: from Delhi, India. Have used it for few outreach events, but didn't work so well - looking to learn more.
  • Urvashi: did bachelors in CS, contributed to Wiki Education Dashboard, generally uses GitHub bug tracker
  • Nirajan: from Nepali, have used it for bug reporting few times
  • Jay: Wikipedian from 2015, Indic TechCom, uses phabricator for tech work
  • Jinoy: ml Wikipedia, haven't used much, few times for bug reporting
  • Durga Soren - Santali Wikipedian
  • Rajeeb-Bengali Wikipedian, eager to learn Phabricator
  • AdityaK


  • Basically a project management tool; used for software development and also to manage projects such as conferences.
  • Tasks; bug reports, small to-dos in a project, for example, a session in a conference.
  • People can interact, change, add comments etc
  • Generally, technically interested people generally use. There are a wide variety of roles.
    • Designers use it for mockups
    • Triagers help to improve tasks and make it better
  • People can post request to lift IP limit, when organizing events.
  • Site configuration changes; pre-filled to make it easier;
  • For broken scripts; better be asked to the maintainer itself;
  • A task can have several projects associated with it.
  • Teams; WMDE-Design, Indic TecCom etc. are generally groups who want to work together
  • Projects and teams have workboards - which has all the to-dos consolidated together, into various columns. Tasks are shown as cards
  • Priorities; unbreak now (super important, needs to be worked on, right now! everything else later), lowest (not urgent), needs triage (priority yet to be decided)
  • Phabricator has a different user profile than that of general Wikimedia projects. A log is also shown.
  • Tasks are public, security issues are not made public until fixed
  • Creating a task;
    • a good title; 10 words - more specific the better.
    • assigned to field is generally empty; unless you have spokent to somebody and they agreed to do it.
    • description;
      • should have steps to reproduce, include links, and be clear - more information the better.
      • If there is not enough information, people will ask.
      • You can also upload screenshots.
      • MediaWiki markup doesn't work here.
      • Preview is available before publishing
  • Creating projects;
  • Workboards;
    • Consolidation of all the tasks, to-dos
    • can be organised and sorted according to different projects
  • you can also mark for notifications; web/email; even though you don't work on the project. Also, can watch the projects as a whole
  • sub-tasks can be created for dependencies
  • More at


  • Krishna - Examples of non-technical usages of Phabricator
    • Wikimedia Sweden uses it, for example, Wikimedia Hackathon
  • Krishna - How to make a task non-public
    • Trusted users can do that
    • Jay is in the trusted users group but doesn't have the option to restrict visibility
      • Talk to Andre. Creation of restricted spaces is possible.
  • Nirajan - What types of tasks require Community Consensus?
  • Satdeep: How do we bring technical contributors to work on a particular task? - basically avoid being left there forever