The Signpost

Technology report

Labs improvements impact 2016 Tool Labs survey results

Servers in the Virginia datacenter

“We have a new database cluster coming online soon", said Davis. “Rather than just setting up the same old system on bigger hardware the database administration team has taken a deep look at the problem of replication with filtering and made configuration and architecture changes to improve the whole stack.”

Another goal is to improve the OpenStack networking system by upgrading it to “Neutron”. This would allow the Labs team to distribute servers better in the datacenter, ensuring that a power outage for a single row of servers won’t take down all of Labs (as it currently would).

And as mentioned earlier, work on transitioning away from OGE will continue. Davis is currently working on evaluation criteria for the OGE replacement system, and expects to do actual testing next quarter.

89% of Tool Labs developers found the support to be as good as or better than the support they received while using the Toolserver, compared with 71% last year. Davis credited the community for coming together and helping each other more, citing the number of people answering questions on IRC and improving documentation on wikis.

He also saw a lot of room for improvement, noting that documentation was the most mentioned problem in the free form comment section of the survey.

“We have pretty good coverage of highly technical topics on the Wikitech wiki, but there are very few start to finish tutorials on how to create an account, upload your code, and see your app running”, said Davis. “It would be nice to see "my first X" tutorials for different basic projects (web service, editing bot, IRC bot, etc) for various languages.”

Usage of the three main services of Tool Labs, LabsDB, cron jobs, and web services, were all down from last year; but the number of respondents who don’t actively maintain any tools went up from 16% to 22%. Davis had a few hypotheses as to why, such as people switching to Quarry for database queries instead of direct access, or people signing up, finding it difficult, and then losing interest.

“I'd love to hear more from the Tool Labs community on the 'why' here”, said Davis. He can be contacted on his Wikitech talk page.

Davis expects the survey results to affect planning for the Labs team in 2017–2018 and the longer term.

“The single biggest take away for us early on is that the documentation needs to be improved”, said Pettet. “We need to update it, curate it, and make sure our users understand it.” He added that it's heartening that users are seeing the benefits of all of their efforts working on uptime and availability.

Stealing some of Wikimedia's Principles to Democratize Programming

“I've got this vision that I think a few others share of a world where making a technical contribution to the movement has a really low barrier of entry”, said Davis. “Ideally manipulating the data we have about what is happening in the wikis should be as easy as editing an article. Sure there will always be a few rules and local conventions that you need to follow, but you shouldn't have to learn a lot of new technology before you can get some work done.” He pointed to YuviPanda’s talk on “Stealing some of Wikimedia's Principles to Democratize Programming” that discusses the same kind of world, using the popular Quarry and relatively new PAWS tools as examples of lowering barriers to technical tasks.

“We are never going to get everyone to freely share in the sum of all knowledge if there are arbitrary silos that large numbers of people are locked out of just because they don't use the right computer operating system or understand the technical difference between an array and a vector”, said Davis.

The full survey results are available on Meta-Wiki. L


















Wikipedia:Wikipedia Signpost/2016-12-22/Technology_report