Hi!
With the recent final release of Page previews (Extension:Popups), we have
also published a series of technical blog posts about the frontend tooling
that we have used for developing this extension.
Master post: Extension:Popups (Page Previews) front-end tooling
<https://phabricator.wikimedia.org/phame/post/view/93/extension_popups_page_…>
Table of contents:
- Automatic JavaScript file bundling and library consumption
- Better minification for frontend sources
- Fast and isolated JS unit tests
- Conclusions
We hope this is interesting to read and hopefully useful to other teams or
projects working on products with complex front-end needs.
We're more than happy to chat about these topics, or help you with these
kind of workflows if you are interested.
Have a nice day!
---
Joaquin - Jhernandez - JHernandez (WMF)
Readers Web Team
Hi all,
Page previews[1] have now been promoted out of beta to the remaining two
Wikipedias - English and German, after a series of consultations on both
wikis [2][3][4]. The feature is now on by default for all logged-out users
and off by default for all logged-in users (can be enabled using user
preferences) on all Wikipedias. Further changes to configuration based on
our conversations with communities (such as turning the feature on for new
accounts) are coming up soon.
Page previews allows readers to read an excerpt of a linked article’s lead
section without leaving the page they’re currently on, by hovering their
mouse over the link. It has been activated by default for logged-out users
on all Wikipedias except German and English since August 2017, and numerous
further bug fixes and technical improvements have been implemented since. A
few weeks ago we published the results of our latest round of A/B testing
[5]. We found that when the feature is enabled, readers will open pages in
their browser slightly less often (a decrease of around 3–5% in regular
pageviews). But on the other hand, they interact with a lot more different
pages when one counts both the seen page previews and the regular pageviews
(an increase of around 20–22% in the number of distinct pages interacted
with via either method). In addition, the option to deactivate the feature
was used very rarely (disable rates were around 0.01%). This leads us to
believe that Page Previews is a welcomed feature that is helping readers
learn more during their visits.
More information about Page previews can be found on the project page on
MediaWIki.org [1]. The team also recently wrote a few blog posts. One about
the work that went into the design of the feature [6] and another giving an
overview of the functionality [7].
If you see any issues, please report them in Phabricator. [8]
Thanks,
Olga
[1] https://www.mediawiki.org/wiki/Page_Previews
[2]
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_16…
[3]
https://de.wikipedia.org/wiki/Wikipedia:Fragen_zur_Wikipedia/Archiv/2018/Wo…
[4]
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(miscellaneous)#Next_S…
[5] https://www.mediawiki.org/wiki/Page_Previews/2017-18_A/B_Tests
[6]
https://medium.com/freely-sharing-the-sum-of-all-knowledge/how-we-designed-…
[7] https://blog.wikimedia.org/2018/04/17/wikipedia-page-previews/
[8] https://phabricator.wikimedia.org/tag/page-previews/
--
Olga Vasileva // Product Manager // Reading Web Team
https://wikimediafoundation.org/
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/wiki
/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
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.
Hello,
I'm trying to migrate a HTMLForm to use ooui
by following https://www.mediawiki.org/wiki/OOUI/Using_OOUI_in_MediaWiki
htmlForm = HTMLForm::factory( 'ooui', $formDescriptor, 'myform' );
I noticed that a file upload form field that I had defined is not
rendered correctly when using ooui.
'fileupload' => array(
'section' => 'upload',
'label' => 'Upload file',
'class' => 'HTMLTextField',
'type' => 'file'
),
This is shown as a text field but not as a file upload, as I would have
expected...
Is there any way to handle this and using OOUI at the same time?
Thanks!
Hello and thank you.
What do you mean in country named "--"?
Igal (User:IKhitron)
On Feb 15, 2018 00:15, "Nuria Ruiz" <nuria(a)wikimedia.org> wrote:
Hello from Analytics team:
Just a brief note to announce that Wikistats 2.0 includes data about
pageviews per project per country for the current month.
Take a look, pageviews for Spanish Wikipedia this current month:
https://stats.wikimedia.org/v2/#/es.wikipedia.org/reading/
pageviews-by-country
Data is also available programatically vi APIs:
https://wikitech.wikimedia.org/wiki/Analytics/AQS/
Pageviews#Pageviews_split_by_country
We will be deploying small UI tweaks during this week but please explore
and let us know what you think.
Thanks,
Nuria
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi!
Over the next fiscal year, the Wikimedia Foundation Readers Web team will
be making technical improvements to the mobile web codebases
(MobileFrontend and MinervaNeue).
The project, which we’re calling ‘Invest in the MobileFrontend &
MinervaNeue frontend architecture’, contained in Output 2.7 of the Platform
Evolution CDP [1], is currently in its specification and planning stages.
The outcomes 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
ecosystem
MobileFrontend & MinervaNeue, which power the Wikimedia mobile sites, make
heavy use of client-side UIs with templates, CSS and JavaScript. Over the
past eight years of developing a mobile-first wiki experience we have
learnt and frontend technology has evolved. We will improve and modernize
the code bases to continue supporting our mobile web users in the future.
Please see 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 for
more detail.
Please visit the project page on MediaWiki.org to learn more about the
outcomes and outputs, and share your questions. [2]
N.B. This project is distinct from “Output 3.1: Contribution tools on
mobile web via an existing mediawiki skin” [3], described in the FY
2018-2019 plan.
_____________________
Joaquin Oltra Hernandez
Senior Software Engineer, Readers Web
[1]:
https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19/2/7
[2]:
https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFro…
[3]:
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/…
Dear Sir,
As i found information below, I did not know how to get Bitcoin into
my wallet. Pls help me.
bitcoin:1NhNVfGXYNY5Z43iErDnmLx7w62TcJuKhm?amount=15.03000000&label=bitcoin%3A3FkenCiXpSLqD8L79intRNXUgjRoH9sjXa
On 3/30/18, wikitech-l-request(a)lists.wikimedia.org
<wikitech-l-request(a)lists.wikimedia.org> wrote:
> Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikitech-l digest..."
>
>
> Today's Topics:
>
> 1. Re: changes coming to large dumps (Ariel Glenn WMF)
> 2. TechCom Radar, 2018-03-28 (Kate Chapman)
> 3. Code of conduct committee call for new members (Amir Ladsgroup)
> 4. Re: MediaWiki train rolled back to wmf.26 (Greg Grossmeier)
> 5. Better Support for Mobile in Wikistats2 (Nuria Ruiz)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 29 Mar 2018 15:42:19 +0300
> From: Ariel Glenn WMF <ariel(a)wikimedia.org>
> To: Ariel Glenn WMF <ariel(a)wikimedia.org>
> Cc: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikipedia
> Xmldatadumps-l <Xmldatadumps-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] changes coming to large dumps
> Message-ID:
> <CALCvg_4S1zrn1ysjDhRAWtWtNvH5ZB2ARa5arSNEn401c5j8hA(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Here it comes:
>
> For the April 1st run and all following runs, the Wikidata dumps of
> pages-meta-current.bz2 will be produced only as separate downloadable
> files, no recombined single file will be produced.
>
> No other dump jobs will be impacted.
>
> A reminder that each of the single downloadable pieces has the siteinfo
> header and the mediawiki footer so they may all be processed separately by
> whatever tools you use to grab data out of the combined file. If your
> workflow supports it, they may even be processed in parallel.
>
> I am still looking into what the best approach is for the pags-articles
> dumps.
>
> Please forward wherever you deem appropriate. For further updates, don't
> forget to check the Phab ticket! https://phabricator.wikimedia.org/T179059
>
> On Mon, Mar 19, 2018 at 2:00 PM, Ariel Glenn WMF <ariel(a)wikimedia.org>
> wrote:
>
>> A reprieve! Code's not ready and I need to do some timing tests, so the
>> March 20th run will do the standard recombining.
>>
>> For updates, don't forget to check the Phab ticket!
>> https://phabricator.wikimedia.org/T179059
>>
>> On Mon, Mar 5, 2018 at 1:10 PM, Ariel Glenn WMF <ariel(a)wikimedia.org>
>> wrote:
>>
>>> Please forward wherever you think appropriate.
>>>
>>> For some time we have provided multiple numbered pages-articles bz2 file
>>> for large wikis, as well as a single file with all of the contents
>>> combined
>>> into one. This is consuming enough time for Wikidata that it is no
>>> longer
>>> sustainable. For wikis where the sizes of these files to recombine is
>>> "too
>>> large", we will skip this recombine step. This means that downloader
>>> scripts relying on this file will need to check its existence, and if
>>> it's
>>> not there, fall back to downloading the multiple numbered files.
>>>
>>> I expect to get this done and deployed by the March 20th dumps run. You
>>> can follow along here: https://phabricator.wikimedia.org/T179059
>>>
>>> Thanks!
>>>
>>> Ariel
>>>
>>
>>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 29 Mar 2018 08:45:12 -0500
> From: Kate Chapman <kate(a)cascadiatm.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] TechCom Radar, 2018-03-28
> Message-ID: <e1814151-0fad-2da4-6242-bd1a1075d4b3(a)cascadiatm.com>
> Content-Type: text/plain; charset=utf-8
>
> Hi All,
>
> Here are the minutes from this week's TechCom meeting:
>
> * This week’s IRC Meeting: Tracking dependencies for multiple Content
> objects per page (MCR) <https://phabricator.wikimedia.org/T190063>
> Meeting log:
> <https://tools.wmflabs.org/meetbot/wikimedia-office/2018/wikimedia-office.20…>
> (summary still to be posted in Phabricator ticket)
>
> * RFC Declined (topic can be picked up again when resourced): Define an
> official thumb API <https://phabricator.wikimedia.org/T66214>
>
> * Ops has turned on some services in Eqsin data center, showing
> improvement for readers in Singapore. Still experimental, but initial
> results positive.
>
> You can also find our meeting minutes at
> <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>
>
> See also the TechCom RFC board
> <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
>
> --
> Kate Chapman
> TechCom Facilitator (Contractor)
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 29 Mar 2018 18:25:04 +0000
> From: Amir Ladsgroup <ladsgroup(a)gmail.com>
> To: wikitech-l <wikitech-l(a)lists.wikimedia.org>, Wikimedia Mailing
> List <wikimedia-l(a)lists.wikimedia.org>, MediaWiki announcements and
> site admin list <mediawiki-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] Code of conduct committee call for new members
> Message-ID:
> <CA+ttme2gtsmoGWivh3=O7AA5kRMBZzmnJPVA6ux-05f2D_k49A(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hello all,
>
> It's coming close to time for annual appointments of community members to
> serve on the Code of Conduct (CoC) committee. The Code of Conduct Committee
> is a team of five trusted individuals plus five auxiliary members with
> diverse affiliations responsible for general enforcement of the Code of
> conduct for Wikimedia technical spaces. Committee members are in charge of
> processing complaints, discussing with the parties affected, agreeing on
> resolutions, and following up on their enforcement. For more on their
> duties and roles, see
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee
> <http://meta.wikimedia.org/wiki/Ombudsman_commission>
>
> This is a call for community members interested in volunteering for
> appointment to this committee. Volunteers serving in this role should be
> experienced Wikimedians or have had experience serving in a similar
> position before.
>
>
>
> The current committee is doing the selection and will research and discuss
> candidates. Six weeks before the beginning of the next Committee term,
> meaning 8th of April 2018, they will publish their candidate slate (a list
> of candidates) on-wiki. The community can provide feedback on these
> candidates, via private email to the group choosing the next Committee. The
> feedback period will be two weeks. The current Committee will then either
> finalize the slate, or update the candidate slate in response to concerns
> raised. If the candidate slate changes, there will be another two week
> feedback period covering the newly proposed members. After the selections
> are finalized, there will be a training period, after which the new
> Committee is appointed. The current Committee continues to serve until the
> feedback, selection, and training process is complete.
>
> If you are interested in serving on this committee or like to nominate a
> candidate, please write an email to techconductcandidates AT wikimedia.org
> with details of your experience on the projects, your thoughts on the code
> of conduct and the committee and what you hope to bring to the role and
> whether you have a preference in being auxiliary or constant member of the
> committee. The committee consists of five members plus five auxiliary
> members and they will serve for six months; all applications are
> appreciated and will be carefully considered. The deadline for applications
> is end of day on 5th of April, 2018.
>
> Please feel free to pass this invitation along to any users who you think
> may be qualified and interested.
>
>
> Best,
>
> Amir on behalf of the CoC committee
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 29 Mar 2018 14:36:56 -0700
> From: Greg Grossmeier <greg(a)wikimedia.org>
> To: Wikitech-l <wikitech-l(a)lists.wikimedia.org>, Development and
> Operations engineers <engineering(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] MediaWiki train rolled back to wmf.26
> Message-ID: <20180329213656.k3tsfomkfc4w45sd@x1>
> Content-Type: text/plain; charset="utf-8"
>
> This is still the case. Updates available on the relevant tasks.
>
> We plan to resume the train (catch up) early next week.
>
> Sorry for the inconvenience.
>
> Greg
>
> <quote name="Greg Grossmeier" date="2018-03-28" time="16:03:23 -0700">
>> The new MediaWiki weekly branch has some issues that are preventing us
>> from deploying as planned.
>>
>> The specific issue: https://phabricator.wikimedia.org/T190960
>>
>> The tracking task for the train: https://phabricator.wikimedia.org/T183966
>>
>>
>> Reminder that you can use the "Wikimedia MediaWiki versions"[0] tool on
>> ToolForge to to know which wikis have which version at any time.
>>
>>
>> Greg
>>
>> [0] https://tools.wmflabs.org/versions/
>>
>> --
>> | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
>> | Release Team Manager A18D 1138 8E47 FAC8 1C7D |
>
>
>
> --
> | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team Manager A18D 1138 8E47 FAC8 1C7D |
>
I have made a patch for a responsive version of MonoBook with mobile
support. See: https://gerrit.wikimedia.org/r/c/421199/ or if you just
want a live demo,
https://wiki.zaori.org/wiki/Page_title?useskin=monobook - load it on a
phone or make your browser window narrow or something and you can see
what it looks like. This is a prototype nojs version; I intend to make
an even sillier js layout with popovers and stuff as a followup patch.
A potential issue has already been raised with the icons: I don't really
know how to make text strings actually, well, reliably fit on mobile
devices, but a lack of support for no-image usage could also be a real
problem in MonoBook. Feedback on that or whatever, as well as other
testing and reviews, would be greatly appreciated.
There is also a rather more immediate problem at present. As you can see
on the patch, jenkins has -1ed it for style problems. Unfortunately I
have no idea what the style problems are because the output of that test
is totally useless (https://phabricator.wikimedia.org/T190072) - can
anyone tell me what the problem(s) are so I can fix them? And/or just
resolve T190072? Please? It's starting to get a bit annoying, frankly,
as it's been coming up across several of these patches.
-I
.jpg){kind=link}