Developer Advocacy/Metrics

This page lists metrics that the Developer Advocacy team was interested in when it still existed. (For a general list of links to metrics and statistics, refer to mw:Development statistics.)

Core workflows

edit

Metrics related to non-programmatic work.

Code review (Gerrit)

edit

New changesets submitted per month

edit

For data on new changesets (patches) contributed in Wikimedia Gerrit, see https://wikimedia.biterg.io/goto/e8cdbe289481bf2cf7bebd2911aeead6 (see mw:Community metrics for help).

Code uploaders per month

edit

For data on changeset (patch) authors in Wikimedia Gerrit, see https://wikimedia.biterg.io/goto/e8cdbe289481bf2cf7bebd2911aeead6 (see mw:Community metrics for help).

Project management (Phabricator)

edit

Active users in Phabricator Maniphest per month

edit

Data source: "Phabricator monthly statistics" email on wikitech-l

New accounts in Phabricator per month

edit

Data source: "Phabricator monthly statistics" email on wikitech-l

Programs

edit

Metrics related to our annual programs.

Technical Contributors Map

edit

This section is a draft.

This was a FY2019-20 Q1 team goal to identify related metrics for the target audiences of the Developer Advocacy subteam. (See phab:T212904.)

  • A black box means: Infrastructure tool not used for such implementations, unless otherwise proven. (Feel free to correct!)
  • A green box means that developer contributions can currently be measured.
  • A yellow box means that developer contributions can currently be measured by performing potentially cumbersome manual steps.
  • A red box means that developer contributions could currently not be measured.
  • The number in a cell is the number of code projects, as of 2019-12-20
  • ☹ means that we would either like to measure this in the long run, or that we would like to make measuring easier and less cumbersome.

Caveats: Usernames and corresponding email addresses might differ across systems.

↘ Infra­structure Tools Implemen­tations → MediaWiki Core MediaWiki extensions (and skins) Modules and Templates User scripts, Gadgets[1], MediaWiki:­Common.js, etc Tools and Bots on Toolforge or VPS[2] Misc (Wikimedia server config, Services, etc)
Code Review / Code Location Wikimedia Gerrit[3] 1 827 [4] [5] 98 [6] ~1300? (cannot detect replication)
Github[7] >400 ☹ [8][9] <50? ☹ [10][11] ? ☹ [10] ~600?
On-wiki content 138 [12] >270000? ☹ [13] >10600 ☹ [14]
Unknown or Misc (Gitlab, Bitbucket, Sourceforge, local hard disk, on server, etc) ? ☹ [15] [9] ? ☹ [16] [10]
Wikimedia Phabricator Differential or Diffusion >450 ☹ [17]
Issue Trackers Wikimedia Phabricator Maniphest[18] [19] [20]
Github[21] [8]
Unknown or Misc (Gitlab, Bitbucket, JIRA, Sourceforge, local Excel sheet, etc) [15]

Notes

edit
  1. For cross-wiki gadget usage statistics, see meta:User:Alexis_Jazz/GUS2Wiki.json
  2. Hay's Tools Directory (opt-in; parses toolinfo.json listed in this file) lists for 437 out of 620 listed entries a "Source available" link. https://tools.wmflabs.org/admin/tools lists for 362 out of 2660 account entries a "Source" link.
  3. Indexed by Bitergia though adding new repositories requires manual changes, see phab:T218519
  4. mw:Category:Extensions in Wikimedia version control
  5. Until phab:T121470 is resolved
  6. See labs/tools/ project entries in Gerrit
  7. Indexed by Bitergia though adding new repositories requires manual changes, see phab:T218528
  8. 8.0 8.1 mw:Category:Extensions in GitHub version control
  9. 9.0 9.1 Any repositories, once their URL is known, can be indexed by Bitergia if added to projects.json which could be done to some extent by pulling the "Download" URLs from the Infobox on each mediawiki.org extension homepage
  10. 10.0 10.1 10.2 Any repositories, once their URL is known, can be indexed by Bitergia if added to projects.json
  11. Example: https://github.com/azatoth/twinkle/
  12. mw:Category:Extensions which host their code in-wiki
  13. "The best you might do would be to look at the top editors in the Module namespace on different wikis, although that might as well catch [...] edits to some test module [...] or (on smaller wikis) people who copy-paste modules from other wikis." -- Anomie in phab:T190164. For Modules, hive (wmf_raw)> select count(*) from mediawiki_page where page_namespace = 828 and snapshot = '2019-11'; lists 270430 modules which might be unrealistic. For the number of Module editors in the 2019, hive (wmf)> select distinct caused_by_user_text from mediawiki_page_history where snapshot = '2019-11' and page_namespace = 828 and start_timestamp > '2018-12-16 00:00:00' and caused_by_user_text not like '%>%' and not caused_by_anonymous_user; lists 1565 editors. These Hive queries were provided by Tgr.
  14. Ugly manual shell script in phab:T190164 to collect editor usernames and number of their edits. Lacks affiliation and not combinable with Gerrit/Github data; plus searches for gadgets in MediaWiki: namespace; those gadgets are not necessarily listed under Special:Preferences or MediaWiki:Gadgets-definition. Quarry might be used for this in the future but does not allow querying across sites as per phab:T95582
  15. 15.0 15.1 mw:Category:Extensions in SourceForge version control‎, mw:Category:Extensions in GitLab version control‎, mw:Category:Extensions in Bitbucket version control‎, mw:Category:Extensions in Google Code version control‎
  16. Toolforge rules require "publishing"
  17. See phab:T315706 about disabling Diffusion repositories in September 2022 and moving to GitLab. Between 01/2019 and 01/2021 there were 2558 code commits in git master in Diffusion by 78 different addresses (see phab:T241659#6773192). See monthly "Active Differential users" stats; see phab:T191182 for potentially disabling Differential.
  18. Indexing by Bitergia limited to task submitters and task resolvers, but not adding comments etc; see phab:T161928
  19. Only if specifically requested, e.g. phab:tag/DannyS712-Global_watchlist.js, phab:tag/Navigation-Popups or phab:tag/wikidata-gadgets; otherwise phab:T121470 applies
  20. See subprojects under phab:tag/tools/
  21. See phab:T218529 for non-existing Bitergia configuration

Onboarding New Developers (2017-2018)

edit

Onboarding New Developers was a program between July 2017 and June 2018. See the program page.

Volunteers contributing patches for review

edit

For data on volunteers who contributed changesets (patches) in Wikimedia Gerrit, see https://wikimedia.biterg.io/goto/6aee9cd3de316109f3fbed46fab86d23 (see mw:Community metrics for help).

New volunteers attracted

edit

For data on newly attracted volunteers who contributed changesets (patches) in Wikimedia Gerrit, see https://wikimedia.biterg.io/goto/4c23163b7251e8c8b2d7680efad97852 (see mw:Community metrics for help).

New volunteers retained

edit

See mw:New Developers/Quarterly#Summary of key findings for data from July 2017 to June 2018 on volunteers retained. See phab:T160430#3653379 for instructions how anyone could calculate newer data.

edit