On Wed, Apr 4, 2018 at 11:26 AM, Jonas Kress <jonas.kress(a)wikimedia.de>
I am interested in improving the patrolling workflow for mobile users of
Wikidata and I wonder if you only plan to refactor the code or if you
also will improve the user experience?
This project is technical improvements only, so we are not expecting
workflow or feature changes on it.
That said, Audiences has a top level outcome (Outcome 3: Mobile
Contributing ) as I mentioned and the Readers Web team will be indeed
responsible for the related output "Output 3.1: Contribution tools on
mobile web via an existing mediawiki skin".
As far as I know at this point in time, the annual plan was just finalized.
I think the *outputs* will go to the planning and definition phase soon, in
preparation for next fiscal year. I think improving the patrolling workflow
for mobile web users could neatly fit under such Output, and would be a
great collaboration. I'll connect you with our PM so that we can talk about
specifics and see how we could help each other.
2018-04-04 11:05 GMT+02:00 Derk-Jan Hartman <d.j.hartman+wmf_ml(a)gmail.com>
I really like all of these goals, but I have to
say that many of them
seem to be a recurring theme (which to me is understandable, but maybe
not to others). I pose to you an additional challenge.. Don't do this
just to mobilefrontend/minervaneue. Do it to a component of core/an
extension as well (i'd pick something small, oft used, but not the
1. This will help expose you to any challenges that other parts of the
ecosystem have in following your direction.
2. It will show the way. Examples are good teaching methods.
3. A component that needs it, but might otherwise not get it, will get
4. It will close the mobile/desktop gap for whatever component you pick
5. it will close the mobile/desktop gap in general.
Because I think that if you don't expand on your target codebase, the
risk will be that you remain more isolated than you should be.
On Tue, Apr 3, 2018 at 7:40 PM, Joaquin Oltra Hernandez
Over the next fiscal year, the Wikimedia Foundation Readers Web team
> making technical improvements to the mobile web codebases
The project, which we’re calling ‘Invest in the MobileFrontend &
> frontend architecture’, contained in Output 2.7 of the Platform
is currently in its specification and planning stages. The
of the project are:
1. Improve developer experience (on-boarding, maintenance, development)
2. Reduce technical debt and make production improvements
3. Separate presentation and logic
4. Make Minerva and MobileFrontend better citizens of the MediaWiki
MobileFrontend & MinervaNeue, which power the Wikimedia mobile sites,
eight years of developing a mobile-first wiki experience we have
and frontend technology has evolved. We will
improve and modernize the
bases to continue supporting our mobile web users
in the future. Please
> Outcomes 1, 2 and 3 in the wiki page for more detail.
> Minerva will become an independent skin without a dependency on
> MobileFrontend, and vice versa. Please see Outcome 4 in the wiki page
Please visit the project page on MediaWiki.org
to learn more about the
outcomes and outputs, and share your questions. 
N.B. This project is distinct from “Output 3.1: Contribution tools on
web via an existing mediawiki skin” ,
described in the FY 2018-2019
Joaquin Oltra Hernandez
Senior Software Engineer, Readers Web
Mobile-l mailing list
Wikitech-l mailing list
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Wikitech-l mailing list