Hi Denny,
Speaking for the apps, we do not load any JavaScript, except for a few
packaged scripts used for app-specific features (e.g. collapsing infoboxes).
-Dmitry
On Thu, Oct 13, 2016 at 7:30 PM, Denny Vrandečić <vrandecic(a)gmail.com>
wrote:
> Two stupid questions, I couldn't find the answer on MediaWiki.org:
>
> 1) is MediaWiki:common.js being loaded on the mobile web view? Or any other
> js? What about User:Name/common.js?
>
> 2) same question but for the Wikipedia app. Does the app run any js?
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
Two stupid questions, I couldn't find the answer on MediaWiki.org:
1) is MediaWiki:common.js being loaded on the mobile web view? Or any other
js? What about User:Name/common.js?
2) same question but for the Wikipedia app. Does the app run any js?
Toby,
Right thanks for the top level info, I am going to step back and think
about this a bit.
I have tried out the Hovercards beta which provides something like
summaries and its very nice so have made a few suggestions regarding the
idea. i.e. optional explicit summary markdown for overriding implicit
summary generation behaviour. And summary types like simple and expert
summaries and accessing summaries for terms from wikctionary.
I am looking into the mechanics of whats involved in implementing both
summary markup and classification "bread crumbs" as extensions.
Regards,
Aaron
On 11 October 2016 at 17:17, Toby Negrin <tnegrin(a)wikimedia.org> wrote:
> Hi Aaron --
>
> Thanks for your interest and suggestions!
>
> A bit late to the thread but I thought I'd point you at the WMF's annual
> plan[1]. The Foundation puts forward a proposal to the community in the
> March/April timeframe and after discussion it is approved by the board.
>
> This and the quarterly planning process[2] are good venues for feature
> oriented discussions like some of your suggestions.
>
> -Toby
>
> [1] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_
> Annual_Plan/2016-2017/Final
> [2] https://www.mediawiki.org/wiki/Wikimedia_Engineering/2016-17_Q2_Goals
>
> On Sun, Oct 9, 2016 at 5:37 AM, Aaron Gray <aaronngray.lists(a)gmail.com>
> wrote:
>
>> Dear Wikipedia and MediaWiki people,
>>
>> Hers are some suggested ideas that may allow Wikipedia and MediaWiki to
>> be organized better in the future and for the future of organizing the
>> worlds open public information.
>>
>> *Summaries - popup summaries for pages*
>>
>> Using automated generation of content for the title attribute on the <a>
>> tag containing a summary containing either the content from an
>> <article><header><section id="summary"> or a designated section from
>> Wikimedia markdown a popup summary could be generated for quick browsing
>> for definition of terms on hyperlinks. This would vastly aid the user
>> experience.
>>
>>
>> *Categories - bread crumb like hierarchical and cross referencing
>> categorization and navigation*
>> By creating a set of categorical navigation pages the whole of fields of
>> knowledge on Wikipedia could be categorized.
>>
>> By having a set of clickable list of hierarchical categories displayed
>> like 'bread crumb' navigation lists under the page title the user could
>> quickly navigate this hierarchy.
>>
>> By adding pop up menus to the separating chevrons with each subcategories
>> elements cross category navigation would be made possible.
>>
>> Double clicking on chevrons should navigate to the categorical navigation
>> page.
>>
>> *QuickLink - Quick Link Creation*
>>
>> A hotkey and JavaScript script could allow the creation of links from a
>> selected highlighted bit of normal text to lookup a term, display its
>> summary and allow the user to confirm the generation of a new hyperlink
>> very quickly without having to edit markdown.
>>
>> *Move towards semantic content*
>>
>> By using new HTML elements like <article>, <section> and <header> and
>> id's and classes more of a semantic mapping of content may be established.
>> Tis maybe done incrementally and also for example by a bot auto generating
>> new summary information that maybe verified by either users or editors for
>> publishing.
>>
>> *API*
>>
>> API's from summaries, categories, and semantic content should be made
>> available.
>>
>> More to come ...
>>
>> Regards,
>>
>> Aaron Gray
>>
>>
>> _______________________________________________
>> Wiki-research-l mailing list
>> Wiki-research-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
>>
>>
>
> _______________________________________________
> Wiki-research-l mailing list
> Wiki-research-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
>
>
On Thu, 2016-09-22 at 18:27 +0000, Jon Robson wrote:
> Would you be also open to flagging some of our oldest patches
To randomly start somewhere, here is a list of MediaWiki Core patches
from 2015, touching <=10 lines, with CR=0 + Verified>0, without merge
conflicts in Gerrit, sorted by age.
Decisions (=CR) welcome.
Thanks in advance for your reviews + help reducing our review backlog.
https://gerrit.wikimedia.org/r/#/c/225371/
Improve Doxygen template used by mwdocgen.php
/maintenance/Doxyfile
https://gerrit.wikimedia.org/r/#/c/211034/
Move up devunt's name to Developers
/CREDITS
https://gerrit.wikimedia.org/r/#/c/111126/
Subst templates and clean tildes even if $wgCleanSignatures is false
/includes/parser/Parser.php
https://gerrit.wikimedia.org/r/#/c/150210/
Special:Newpages feed now shows first revision instead of latest revision
/includes/specials/SpecialNewpages.php
https://gerrit.wikimedia.org/r/#/c/142701/
Allow specifying sort keys for tracking categories
/includes/parser/Parser.php and ParserOutput.php
https://gerrit.wikimedia.org/r/#/c/250372/
Gallery: Use intrinsic width for gallery to center caption
/resources/src/mediawiki/page/gallery.css
https://gerrit.wikimedia.org/r/#/c/258037/
Qualify page titles as such in messages about editing or acting on a page
/languages/i18n/en.json
https://gerrit.wikimedia.org/r/#/c/259618/
Fix the TODO comment in documentation of getTitleLink
/includes/logging/LogPage.php
https://gerrit.wikimedia.org/r/#/c/261268/
Added documentation for wfClientAcceptsGzip()
/includes/GlobalFunctions.php
Cheers,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Your help is welcome to provide feedback (CR±1/2) and guidance:
== mediawiki/extensions/LdapAuthentication: ==
since 2016-09-27 (2nd time listed here):
Allow local user creation even if LDAP user creation is disabled
https://gerrit.wikimedia.org/r/#/c/313019/
== operations/mediawiki-config: ==
since 2016-09-27 (2nd time listed here):
Adding language name configuration for Wikidata
https://gerrit.wikimedia.org/r/#/c/312944/
== pywikibot/core: ==
since 2016-09-25 (2nd time listed here):
Checks the type of isbn and modifies accordingly
https://gerrit.wikimedia.org/r/#/c/312726/
Thanks in advance for your reviews.
Of last time's 5 listed patches, 1 got abandoned, 1 got reviewed.
Thanks to Krinkle and Reedy!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-10-12
== Product ==
=== Reading ===
Goals section:
https://www.mediawiki.org/wiki/Wikimedia_Engineering/2016-17_Q2_Goals#Readi…
==== iOS native app ====
Current Release Build: https://phabricator.wikimedia.org/project/view/2220/
Since we last met:
- * Notification UI is complete
- * Feed based off of MCS and persisting to YapDatabase is almost
complete
- * Bug fixes & event logging fixes landed
- * Working with Apple on fixing Siri integration
Before we meet again:
* Connect notification UI to data source - enable notifications
* Add notifications preferences to onboarding & feed
* Release a beta
No blockers
==== Android native app ====
* Current sprint (
https://phabricator.wikimedia.org/tag/mobile-app-android-sprint-93-neptuniu…)
:
* Start on Q2 goals for Wikidata descriptions
* v2.4.158 beta coming soon
* Alpha builds fixed
* CI screenshot regression testing
* Languages with three letter codes enabled
* Next sprint:
* More Q2 goals...
==== Mobile Content Service (MCS) ====
* adding a few more languages to feed endpoints (mainly news, maybe TFA):
Sv, Fr
* next gen of content endpoint: references only endpoint
* updated scap3 deploy host from tin to generic deployment server name
==== Reading Web ====
Since last met:
* Wrapped up the remaining sprint work
Until the next time we meet:
* Fix some Event Logging issues with Hovercards
* Move lead section before the infobox on mobile
* Clean up the old language button
Blocked on:
* We need input from the Performance team regarding "UC Mini should not
be supported by ResourceLoader" (https://phabricator.wikimedia.org/T147369)
==== Reading Infrastructure ====
* no blocking
* blocked on WMDE adding query modification hooks to
WatchedItemQueryService which can replicate
ApiQueryBaseBeforeQuery/ApiQueryBaseAfterQuery/ApiQueryBaseProcessRow
=== Community Tech ===
=== Editing ===
==== Collaboration ====
* Blocking: Hopefully nobody?
* Blocked:
** https://phabricator.wikimedia.org/T143743 disagrements between Collab
(Stephane), Analytics (Otto) and Services (Marko, Petr) about approach,
probably going to organize a meeting
* Update:
** Flow beta feature was disabled on all wikis due to breakage. Slowly
re-enabling now, beginning with frwikiquote today
** UI standardization improvements in Echo, thanks Volker!
** Fixing some small bugs in PageTriage
==== Language ====
* Blocked:
** Help with https://phabricator.wikimedia.org/T145650 is needed, this
affects translatewiki.net
=== Discovery ===
== Technology ==
=== Analytics ===
*Not blocking nor blocked
*Update:
Recruiting - Still screening, tasks sent to some applicants.
Pivot (UI over Druid, analytics datastore) is now available behind LDAP
- Fast access to pageviews (more datasets to come)
Kasocki - Discution around using SocketIO,WebSockets or SSE (in ticket:
https://phabricator.wikimedia.org/T130651)
We started work to replace last instance of Limn by Dashiki (limn1)
Old aqs machines are now spares.
=== Services ===
* Blocked: none
* Blocking: none
* Updates:
** Node 4.6.0 security release: please test your services.
=== Architecture / ArchCom ===
* Last week (E287): Magic Links deprecation:
https://phabricator.wikimedia.org/T145604
* This week (E316): CREDITS file: https://phabricator.wikimedia.org/T139300
* https://www.mediawiki.org/wiki/Architecture_committee/Status
=== Release Engineering ===
* Blocking:
** nobody
* Blocked:
** Ops: looking at throttle rate for nodepool/Openstack (
https://gerrit.wikimedia.org/r/#/c/315214/)
* Updates:
** Reminder: RelEng at offsite in DC next week. No train deploys. Other
deploys (like SWAT) ok.
=== Security ===
=== Services ===
=== Technical Operations ===
== Wikidata ==
* No blockers.
* Working on new network graph and diagram renderers for the Wikidata Query
Service: https://phabricator.wikimedia.org/T142179
* Working on referencing entities on foreign Wikibase repositories (Commons
will reference Wikidata items): https://phabricator.wikimedia.org/T76007
* Expanding client side integration with new Lua and parser formatter
function: https://phabricator.wikimedia.org/T142940
* We heard people being busy keeping up with changes in core (stuff being
deprecated and removed). Not all are happy with the frequency breaking
changes are done currently.
== Fundraising Tech ==
* Winter is coming... Annual reminder to please postpone risky rollouts
till after December's fundraising campaign
* One CentralNotice bug closed, one still happening:
https://phabricator.wikimedia.org/T144952
** Andrew's pretty sure it's a MessageCache thing
** Added logging, got some logs from the beta cluster
** Getting some help from Aaron and Timo, but any other suggestions are
welcome
* Cleaning up any remaining references to ActiveMQ
(It wasn't just you)
Gerrit was down today starting around 17:49 UTC. It is now back up and
services are coming back online.
A full investigation into the cause of the outage is still on-going.[0]
Apologies for the downtime.
WMF Release Engineering
[0] https://etherpad.wikimedia.org/p/gerrit-outage-20161006
But this is missing a lot of the information/discussion that is
happening in #wikimedia-operations on Freenode. A link to the
incident report will be pasted into that etherpad when it is
created.
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Hi everyone,
This week's ArchCom Office Hour[1] is going to be about a
long-neglected item: giving credit where credit's due in the CREDITS
file (Jon Robson's T139300 proposal[2]). Jon and I spoke about it
earlier today; he's not sure he can be there, and this is a meeting
where I would have hoped to have done more prep, but I'm hoping we can
at least come to a better collective understanding for the people at
the meeting.
The reason why this isn't as easy as it looks on the surface is
because the COPYING file notes: "MediaWiki contributors, including
those listed in the CREDITS file, hold the copyright to this work."
The fact that I hadn't gotten around to consulting our Legal
department made me very, very tempted to call off the meeting this
week. But I think maybe instead it'll be the "what does the
wikitech-l community want RobLa to go ask Legal about" meeting. :-)
Let's figure out what our viable options are.
I took the liberty of taking the prose in T139300, and adapting it to
wiki page[3]. We can conceivably use this as a space to figure out
what we want the policy page to say.
Our meeting is the same time as always (Wednesday 21 UTC, 14 PDT, 23
CEST) and place (#wikimedia-office).
Rob
p.s. Obligatory reminder about ArchComStatus page[4]
[1]: <https://phabricator.wikimedia.org/E316>
[2]: <https://phabricator.wikimedia.org/T139300>
[3]: <https://www.mediawiki.org/wiki/Requests_for_comment/CREDITS>
[4]: <https://www.mediawiki.org/wiki/ArchComStatus>
Hey,
This is the 24th and 25th weekly update from revision scoring team that we
have sent to this mailing list. We skipped a week due to travel and other
work.
Maintenance and robustness:
- We improved the performance of RecentChanges fitlering in the ORES
extension[1]
- We built and ran a maintenance script to clean up duplicate cached
data for the ORES extension[2,3]
- We updated the editquality models for the new version of revscoring
(1.3.0)[4] and made some upstream changes to json2tsv to make that easier[5]
- We quited down some of our error reporting so that our logs take up
less space[6]
Datasets:
- We generated a dataset that uses the "wp10" prediction model to assess
article quality in monthly intervals for English, French, and Russian
Wikipedia[7]. This should enable new research into the quality dynamics of
these wikis.
- We generated a dataset of vandalism, spam, and attack page creations
for building a new "draft quality" model[8]
Communication:
- Presented about transparent/open AI development practices around ORES
at the Association of Internet Researchers[9]
New development:
- We've made substantial progress towards adding ORES data to
MediaWiki's api.php endpoints with rcshow=oresreview[10] and rvprop=ores[11]
1. https://phabricator.wikimedia.org/T146111 -- hidenondamaging=1 query is
extremely slow on enwiki
2. https://phabricator.wikimedia.org/T145356 -- Ensure ORES data violating
constraints do not affect production
3. https://phabricator.wikimedia.org/T145503 -- Build a maintenance script
to clean up duplicate data
4. https://phabricator.wikimedia.org/T146410 -- Update editquality for
revscoring 1.3.0
5. https://phabricator.wikimedia.org/T146939 -- Add type decoding support
to tsv2json
6. https://phabricator.wikimedia.org/T146680 -- Quiet result.get Warning in
tasks
7. https://phabricator.wikimedia.org/T145655 -- Generate monthly article
quality dataset
8. https://phabricator.wikimedia.org/T135644 -- Generate spam and vandalism
new page creation dataset
9. https://phabricator.wikimedia.org/T147706 -- Present about ORES
transparency at AoIR
10. https://phabricator.wikimedia.org/T143616 -- Introduce
rcshow=oresreview and similar ones
11. https://phabricator.wikimedia.org/T143614 -- Introduce ORES rvprop
Sincerely,
Aaron from the Revision Scoring team
Hi I'm thinking we can install php 7.1 on Jessie too since php 7, would not be under the name php but under php7.0, so php7.1 would be the name, so we can switch between php 5.6, 7.0, and 7.1 if we install it too on Jessie.