Commons android app team process presented at the Wikimedia Technical Conference 2019, Atlanta

1. Commons Android App
Team Process

2. ● We avoid over engineering, use the minimal set of tools we
need
● We have a small but relatively strict set of procedures that
we follow
● Meetings are difficult, part-time / different time zones ->
asynchronous communication
How we do things as a small remote team

3. Planning
● Annual goals (based on
grant tasks).
● Tracking pending tasks for
the upcoming release via
Github task lists.
● Priority list for short time
planning.

4. Facilitators
● GitHub wiki for documentation
● Github bots like automated test checker, deleting unused
branches and auto closing solved issues.
● Tagging issues as beginner-friendly, bugs, help-wanted.
● Travis Continuous Integration for automated builds and
alpha releases on every commit to master

5. Communication
● Recently we switched to
Zulip from Hangouts, for
better integration and
automation
● Usage of pull request
templates to have single
style of issue titles and
descriptions

6. Cautions
● Keeping collaborators (members with review and merge
privilege) narrow
● Preventing merging your own PR
● Wait for all automated tests to pass before merging any
PRs

7. Human Relationships
● Remember to add
motivating words on
reviews
● Encourage first time
contributors
● Trying to get interns
when we have
available mentors
by Takuya Murakami. Creative Commons Attribution 2.0 Generic. Link