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
The Android team[0] is delighted to announce a new Wikipedia Android app
beta release, v2.0.106-beta-2015-07-20[1]. In summary[2], this revision
includes the following improvements:
* New! Floating table of contents access button.
* New! Language selection button in search bar.
* New! Bett
Just an FYI, a recent change in the selenium gem is causing the bot
Barry to report false positives for MobileFrontend patches. If you see
a -1 from him on your MobileFrontend patch, please read the log in the
mean time - if only 2 tests are failing it's highly likely your patch
is fine.
+2ers ple
Ooh can you point me to mocks for the floating toc button?
> On Jul 20, 2015, at 1:49 PM, Stephen Niedzielski
> wrote:
>
> The Android team[0] is delighted to announce a new Wikipedia Android app
> beta release, v2.0.106-beta-2015-07-20[1]. In summary[2], this revision
> includes the follow
The Reading Web team kicked off Sprint 52 today [1].
Work undertaken in this sprint will include rounding out the efforts that
were started in the previous sprint to increase test coverage and a create
a staging environment for testing and review, and diving in to performance
goals with an audit o
What is this... A sprint for ants!?
(Sorry.)
On Mon, Jul 20, 2015 at 2:09 PM, Kristen Lans wrote:
> The Reading Web team kicked off Sprint 52 today [1].
>
> Work undertaken in this sprint will include rounding out the efforts that
> were started in the previous sprint to increase test coverage
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 developmen
I believe this[0] was the original task. I don't know of any mocks but
here's the final implementation in a restful state[1] and when
scrolling[2]. It's quite Material-y[3] so I suspect you will be putting an
iOS spin on it, in which case Android screenshots / mocks probably won't be
very useful.
I've managed to find a workaround for time being so Barry should be
+1ing / -1ing correctly again. Let's continue this conversation on the
phabricator task from now on :)
On Mon, Jul 20, 2015 at 11:58 AM, Jon Robson wrote:
> Just an FYI, a recent change in the selenium gem is causing the bot
> Ba
Correction: I didn't find a workaround :)
On Mon, Jul 20, 2015 at 3:50 PM, Jon Robson wrote:
> I've managed to find a workaround for time being so Barry should be
> +1ing / -1ing correctly again. Let's continue this conversation on the
> phabricator task from now on :)
>
> On Mon, Jul 20, 2015 a
Adam Baso, 20/07/2015 22:58:
I think we should move the page to mw:Reading/Extension_Responsibility.
Or better, merge with https://www.mediawiki.org/wiki/Developers/Maintainers
Nemo
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://list
Ah, yes, that.
On Mon, Jul 20, 2015 at 4:41 PM, Federico Leva (Nemo)
wrote:
> Adam Baso, 20/07/2015 22:58:
>
>> I think we should move the page to mw:Reading/Extension_Responsibility.
>>
>
> Or better, merge with
> https://www.mediawiki.org/wiki/Developers/Maintainers
>
> Nemo
>
A SLA and point person for each of these extensions would be a good
next step. I worry that saying the reading vertical maintains the
"Cologne blue" skin sets an expectation that we will be code reviewing
all patches for Modern which is simply untrue.
This may also be a good time to revisit this t
Neat! Thanks Stephen!
> On Jul 20, 2015, at 4:35 PM, Stephen Niedzielski
> wrote:
>
> I believe this[0] was the original task. I don't know of any mocks but
> here's the final implementation in a restful state[1] and when scrolling[2].
> It's quite Material-y[3] so I suspect you will be put
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 sa
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-Vagra
Agreed. Borrowing a snippet from the earlier discussion on this, and I
should have copied this in earlier:
"This is entirely about ... fixing urgent issues that affect production,
ideally before they hit it (security issues, deprecated code, etc.). It is
not necessarily about doing planning, devel
17 matches
Mail list logo
