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: TBD

Area		Staff
		Cory	Daphne	David	Geno	Grace	James
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

• 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

• 🛠️ Regularly works on/with this
• 🔧Occasionally works on/with this
• 💡 Can mentor/teach someone
• 🐾 Is currently learning/wants to start learning