There are a whole bunch of little utilities like browser extensions and bookmarklets and even an entire in-house cloud infrastructure that is used for hosting various kinds of bots and web-based tools for automating workflows. It's all very ad-hoc, crude and not very well organized or publicized. There have been a few efforts over the years to create a repository for all of the little tools to help with exposure and some level of vetting for security risks. I'm not sure any of those projects were ever successful (or even made it past the planning stage) but there has been some appetite for improving that ecosystem.
replyThey have excess money as an org, why don’t they hire SWEs to improve it?
replyMy impression has been that the project has never been fully scoped and kind of bounced around between teams with nobody ever fully dedicated to seeing it through to completion. Scope creep and a whole lot of competing ideas, on top of a genuinely hard to solve set of problems has caused it to get put on the back burner more than once.
replySometimes perfect is the enemy of good enough.
I should disclose that I am a former employee of Wikimedia, however, my impression is based solely on reading about the projects on publicly available project planning pages. That is, on https://www.mediawiki.org/wiki/MediaWiki and https://phabricator.wikimedia.org
replyThey're constantly hiring engineers.
replyShe tried to add herself to a list called “professional Canadian painter”, and from what I see, she is a professional Canadian painter for 10+ years.
replyBut not notable. Unless notable for long-term Wikipedia abuse. Maybe eventually she gets mentioned on a news site for that, and then she can finally have an article.
reply