Re: [WikimediaMobile] Extension Responsibility
On Tue, Jul 21, 2015 at 6:52 PM, Ryan Kaldari rkald...@wikimedia.org wrote: If the MultimediaViewer extension is transferred to Editing (i.e. Multimedia), TimedMediaHandler should probably go with it, as they are both mainly for presenting media within pages. I agree with Jon that MMV should belong to Reading Web (especially since they already own the mobile media viewer and the plan is to merge the two), but the comparison does not really stand up. TMH is about a whole lot of things: it adds and manages a new page content type (TimedText), it integrates the file upload with machinery to run and control video transcoding jobs, it is deeply entangled with WMF infrastructure (it has its own server cluster), it provides its own file metadata API (although it probably shouldn't https://phabricator.wikimedia.org/T89971). And it also presents media within pages. It could go to any number of teams - Reading Infrastructure is IMO a practical decision for now because all the recent TMH breakage I can remember was MW core or devops related (mostly because those have more interdependencies and a higher rate of change than frontend code), and the other potential teams focus on frontend. And while frontend is the part of TMH in the biggest need of a rewrite (TheDJ actually started that and anyone from the frontend teams helping out by reviewing his code would be great), extension responsibility is explicitly not about improvements but about reacting to breakage. ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
+1 to thus On 21 Jul 2015 4:52 pm, Ryan Kaldari rkald...@wikimedia.org wrote: If the MultimediaViewer extension is transferred to Editing (i.e. Multimedia), TimedMediaHandler should probably go with it, as they are both mainly for presenting media within pages. On Mon, Jul 20, 2015 at 3:58 PM, Adam Baso ab...@wikimedia.org wrote: Hi all - I've been reviewing a list of extensions with Reading Engineering and Reading Infrastructure leads - props to James Forrester for promoting this discussion. Here's a list of extensions we believe currently falls under Reading for triage (n.b., not all extensions will get active development support). https://www.mediawiki.org/wiki/User:ABaso_(WMF)/Extension_Responsibility Presuming no major issues with this, I think we should move the page to mw:Reading/Extension_Responsibility. One important outstanding question: Is MultimediaViewer appropriate for Reading given its consumption-oriented nature? Or is this actually better suited to Editing (where there exists a team named Multimedia)? I agree. They should come as a package (fwiw im a little confused why viewing images and thus multimedia viewer doesn't come under reading). Some other notes: * For skins with low utilization, we in time probably should coordinate handover to interested community members (or discuss with community members practical approaches for EOL). * Regarding the Nostalgia skin, we believe it's only used on https://nostalgia.wikipedia.org/wiki/HomePage, so maintenance would be updating for breaking skin changes or security issues only. * JsonConfig, ZeroBanner, ZeroPortal - we'll need to examine this more closely. Yuri (who has deepest PHP knowledge on extensions) is now over in Discovery, Jeff (JS Lua) is in Reading, and now I'm managing instead of writing lots of code. * Collection probably belongs in Services ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] [QA] Qualifiers for selecting test articles for vagrant role
On 20 Jul 2015 5:56 pm, Greg Grossmeier g...@wikimedia.org wrote: Given the topic, let's keep the QA list in the loop on this so the MW-Vagrant maintainers can participate/see. Great :) 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. It does yup. I've already tagged the bug with it. I'm hoping by tackling this we can come up with a common solution. The way I imagine this working in future is we have various vagrant roles for stock data e.g. reading-web-stock-data, editing-web-stock-data, sad-web-stock-data There would also be non team specific stock data that might be a sub role of this, for example, the reading web team commonly has to setup the wikidata role and manually create articles in the wikidata instance and local instance that are tied to each other - this takes a ridiculous amount of time and is one I'm keen to automate, given that we are leaning more heavily on wikidata descriptions and other data in there. Rob - I've setup https://www.mediawiki.org/wiki/Reading/QA/Sample_articles as a place we can start to collect and think about these pages. 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 rm...@wikimedia.org ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ QA mailing list q...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
On Mon, Jul 20, 2015 at 3:58 PM, Adam Baso ab...@wikimedia.org wrote: Hi all - I've been reviewing a list of extensions with Reading Engineering and Reading Infrastructure leads - props to James Forrester for promoting this discussion. Here's a list of extensions we believe currently falls under Reading for triage (n.b., not all extensions will get active development support). https://www.mediawiki.org/wiki/User:ABaso_(WMF)/Extension_Responsibility Presuming no major issues with this, I think we should move the page to mw:Reading/Extension_Responsibility. Definitely not a *major* issue, but VipsScaler https://www.mediawiki.org/wiki/Extension:VipsScaler would logically belong together with the media handler extensions (which are all on the list) IMO. ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
Shall I make it so? On Tue, Jul 21, 2015 at 3:59 PM, Gergo Tisza gti...@wikimedia.org wrote: On Mon, Jul 20, 2015 at 3:58 PM, Adam Baso ab...@wikimedia.org wrote: Hi all - I've been reviewing a list of extensions with Reading Engineering and Reading Infrastructure leads - props to James Forrester for promoting this discussion. Here's a list of extensions we believe currently falls under Reading for triage (n.b., not all extensions will get active development support). https://www.mediawiki.org/wiki/User:ABaso_(WMF)/Extension_Responsibility Presuming no major issues with this, I think we should move the page to mw:Reading/Extension_Responsibility. Definitely not a *major* issue, but VipsScaler https://www.mediawiki.org/wiki/Extension:VipsScaler would logically belong together with the media handler extensions (which are all on the list) IMO. ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
On Tue, Jul 21, 2015 at 6:11 PM, Adam Baso ab...@wikimedia.org wrote: Shall I make it so? I don't see a reason not to. While one could argue both for media handlers belonging to Reading and to Editing, they should in any case be all at the same place as they require the same knowledge (familiarity with core MediaHandler classes, File etc). VipsScaler is not itself a media handler, but it is about modifying media handler behavior via hooks so it is close enough. ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
Okay, to be clear, VipsTest, too, right? On Tue, Jul 21, 2015 at 4:22 PM, Gergo Tisza gti...@wikimedia.org wrote: On Tue, Jul 21, 2015 at 6:11 PM, Adam Baso ab...@wikimedia.org wrote: Shall I make it so? I don't see a reason not to. While one could argue both for media handlers belonging to Reading and to Editing, they should in any case be all at the same place as they require the same knowledge (familiarity with core MediaHandler classes, File etc). VipsScaler is not itself a media handler, but it is about modifying media handler behavior via hooks so it is close enough. ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
On Tue, Jul 21, 2015 at 6:27 PM, Adam Baso ab...@wikimedia.org wrote: Okay, to be clear, VipsTest, too, right? Yes, that's essentially the same extension (a different PHP endpoint in the same repo). ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
Done. On Tue, Jul 21, 2015 at 4:30 PM, Gergo Tisza gti...@wikimedia.org wrote: On Tue, Jul 21, 2015 at 6:27 PM, Adam Baso ab...@wikimedia.org wrote: Okay, to be clear, VipsTest, too, right? Yes, that's essentially the same extension (a different PHP endpoint in the same repo). ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Extension Responsibility
If the MultimediaViewer extension is transferred to Editing (i.e. Multimedia), TimedMediaHandler should probably go with it, as they are both mainly for presenting media within pages. On Mon, Jul 20, 2015 at 3:58 PM, Adam Baso ab...@wikimedia.org wrote: Hi all - I've been reviewing a list of extensions with Reading Engineering and Reading Infrastructure leads - props to James Forrester for promoting this discussion. Here's a list of extensions we believe currently falls under Reading for triage (n.b., not all extensions will get active development support). https://www.mediawiki.org/wiki/User:ABaso_(WMF)/Extension_Responsibility Presuming no major issues with this, I think we should move the page to mw:Reading/Extension_Responsibility. One important outstanding question: Is MultimediaViewer appropriate for Reading given its consumption-oriented nature? Or is this actually better suited to Editing (where there exists a team named Multimedia)? Some other notes: * For skins with low utilization, we in time probably should coordinate handover to interested community members (or discuss with community members practical approaches for EOL). * Regarding the Nostalgia skin, we believe it's only used on https://nostalgia.wikipedia.org/wiki/HomePage, so maintenance would be updating for breaking skin changes or security issues only. * JsonConfig, ZeroBanner, ZeroPortal - we'll need to examine this more closely. Yuri (who has deepest PHP knowledge on extensions) is now over in Discovery, Jeff (JS Lua) is in Reading, and now I'm managing instead of writing lots of code. * Collection probably belongs in Services ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Re: [WikimediaMobile] Fwd: [reading-wmf] interesting topic readouts
Hi Jon -- I created a ticket to track your request. ( https://phabricator.wikimedia.org/T106451) -- we have some directional data from a 2104 study that indicates that users read articles that focus on entertainment (http://www.dcs.gla.ac.uk/~mounia/Papers/wiki.pdf) As far as the taxon counts -- there are a few wikis that are more open than others to automatically created articles. I don't think there's much of a relationship beyond that. -Toby On Mon, Jul 20, 2015 at 10:33 AM, Jon Robson jdlrob...@gmail.com wrote: So basically as a project grows the percentage of taxon articles go down? :) It would be interesting to see equivalents of these for readership. Are there any initiatives to measure page views based on wikidata instance of property value? I'd love to know whether readership figures reflect content available. On Thu, Jul 16, 2015 at 2:34 PM, Adam Baso ab...@wikimedia.org wrote: Fun visualizations! -- Forwarded message -- From: Toby Negrin tneg...@wikimedia.org Date: Thu, Jul 16, 2015 at 11:58 AM Subject: [reading-wmf] interesting topic readouts snip https://www.wikidata.org/wiki/Wikidata:Statistics/Wikipedia ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
