Abstract Wikipedia team/Skill Matrix

This is a way for the Abstract Wikipedia team's engineers to self-assess their level of familiarity, expertise, and comfort across a range of areas which are important to the team.

Abstract Wikipedia Team self-assessed recent skills matrix
Last updated: 2022-05-25
Area Staff Google.org Fellows External participants e.g. volunteers
Cory David Geno James Julia Ali Ariel Mary Ori
General Wikifunctions conceptual model πŸ’‘ πŸ’‘ πŸ’‘ πŸ’‘ πŸ”§ πŸ’‘πŸ”§
function-schemata definitions πŸ’‘ πŸ› οΈ πŸ’‘πŸ”§ πŸ’‘ πŸ”§
function-schemata schemata πŸ’‘ πŸ”§ πŸ’‘πŸ› οΈ πŸ”§ πŸ”§
function-schemata utilities πŸ’‘ πŸ› οΈ πŸ’‘πŸ”§ πŸ’‘ 🐾
Natural language generation model 🐾 🐾 🐾 🐾
"Front-end" WikiLambda front-end Vue components πŸ”§πŸΎ πŸ”§ πŸ”§ πŸ› οΈ
WikiLambda front-end design & styling πŸ”§ πŸ”§ πŸ› οΈ
WikiLambda front-end Vue data/app model πŸ”§πŸΎ πŸ”§ πŸ”§ πŸ› οΈ
WikiLambda PHP 'middleware' πŸ”§ 🐾 πŸ’‘πŸ› οΈ πŸ’‘ πŸ”§
WikiLambda integration with MW 🐾 🐾 πŸ’‘πŸ› οΈ πŸ’‘
Altering Vue/Codex/etc. upstream libraries πŸ”§ πŸ”§
UX & the Wikimedia design process πŸ› οΈ πŸ› οΈ
"Back-end" function-orchestrator framework & security πŸ› οΈ πŸ› οΈ πŸ”§πŸΎ πŸ› οΈ 🐾 πŸ”§πŸΎ
function-orchestrator logging & measurement πŸ”§ πŸ› οΈ 🐾 🐾
function-orchestrator caching & performance πŸ”§ πŸ”§ 🐾 🐾
function-evaluator framework & security πŸ› οΈ πŸ› οΈ 🐾 πŸ› οΈ 🐾 🐾
function-evaluator executors & (de)serialisers πŸ’‘ πŸ”§ 🐾 πŸ”§ 🐾
Wikimedia Production Configuring production MW πŸ”§πŸΎ πŸ’‘
Configuring production services (helm/k8s) πŸ”§πŸΎ πŸ”§
Monitoring production MW 🐾 πŸ’‘
Monitoring production services 🐾 🐾 🐾
Production MW deployment πŸ”§πŸΎ πŸ’‘
Deploying production services (helm/k8s) πŸ”§ πŸ”§
Interacting on-wiki with community 🐾 🐾 πŸ› οΈ 🐾
Ways of working Using local development environments πŸ’‘ πŸ› οΈ πŸ› οΈπŸ’‘ πŸ› οΈ πŸ”§πŸ’‘
Using and configuring gerrit / CI πŸ› οΈ πŸ”§ πŸ”§πŸΎ πŸ’‘ 🐾
Using and configuring GitLab 🐾 🐾 πŸ› οΈπŸ’‘ πŸ”§
Using and configuring Phabricator πŸ”§πŸΎ πŸ”§ πŸ’‘ 🐾
Building and using code coverage πŸ”§ 🐾 πŸ’‘ 🐾

Notes edit

  • As a team, we aim to have a strong grasp of all the different parts of our ecosystem, with many people having the ability to understand, make, and approve changes in each area, and two or more people feeling comfortable being an 'expert' and training up colleagues and volunteers in the area.
  • As individuals, we aim to improve our expertise across a range of areas over time, keeping current and training up others to share the load.
  • As they are self-assessments, each rating should generally be compared along columns and not along rows – i.e. people's self-ratings in one field X should be compared against their self-ratings in another field Y, not against other people's self-ratings in the same field X.
  • We consider engineering to be a craft on which we iterate. We commit to think regularly about ways we could change the systems and processes we own (and those in which we are significant stakeholders) to be better engineered – more efficient, more welcoming, more effective, and more understandable.

Legend edit

  • πŸ› οΈΒ Regularly works on/with this
  • πŸ”§ Occasionally works on/with this
  • πŸ’‘ Can mentor/teach someone
  • 🐾 Is currently learning/wants to start learning