Given the topic, let's keep the QA list in the loop on this so the MW-Vagrant maintainers can participate/see.
Also, it looks like the original bug (reported in the MW-Vagrant project) covers this specific request from Reading, no? Essentially, let's see how far we can get with a general "MW-Vagrant (WMF?) testing data import" instead of a vertical specific "reading-web test data set". If what the Reading team needs is way too much for this then we can break it out, otherwise it seems like a needless distinction.
Greg
PS: https://wikitech.wikimedia.org/wiki/Labs_labs_labs
<quote name="Rob Moen" date="2015-07-20" time="17:11:07 -0700">
Historically developers have had to setup their own content in mediawiki and in mediawiki-vagrant. While this can be done with a simple import, getting everyone on the same page is apparently not as easy. This is generally problematic as we would like to test code locally and remotely with the same content for various reasons.
Slightly more frustrating, there are pages titled "0.4425590476103759" on beta labs. While trying to sign off on a feature, there is usually a struggle when trying to find an article with suitable content. AFAIK this won't change beta labs but would provide a nice standard for our content on test wikis.
We aim to better things by creating a vagrant role for importing a set of articles for testing purposes. For more information please see related phabricator tasks [1] and [2].
In hopes of making this a nice collection of articles that multiple teams would use, we would like to get input from our designers and devs on what types of articles should be in this import. What qualities should these articles contain?
1: https://phabricator.wikimedia.org/T104561 2: https://phabricator.wikimedia.org/T62116
-- Rob Moen Wikimedia Foundation rmoen@wikimedia.org
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l