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
*Wikimedia Documents - PDF Scraping and creating living working documents*
Wikimedia should have a way of creating documents that can easily be
imported and exported to PDF, Word and other formats.
- Document versioning as well as history should be able to be provided.
- Authorship and control of authorship I also needed.
- Fixed and editable status should also be provided
- Document licensing should also be feature, this should allow management
of information from different sources.
Document licensing should allow copying and collation to be done in
controlled way allowing information dissemination.
By scraping the content of PDF documents that are put into the public
domain or under open license that permits modification and that permission
is given to subsume and render them into MediaWiki Pages in modifiable
state. Those that are in the public domain or under a fixed content license
may still be rendered into MediaWiki Pages.
Quick access to the original document and modification history should be
mandatory at the top of every original document page. Auto quotations and
citations can also be generated at the bottom of the pages
More to come ...
Regards,
Aaron Gray
On 9 October 2016 at 13:37, 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
>
>
Hi.
I have an extension that hooks into ParserAfterParse to modify the
generated HTML (Lingo). The problem is, that apparently this hook is never
called when a page is edited using Visual Editor, which means my extension
does not get to modify the page's HTML content until it is purged
(action=purge) or edited using the old editor.
Is this intentional or is it a VE bug?
Does anybody have any advice on how I could work around this? E.g. an
alternative hook I should use?
Cheers
Stephan
Forwarding.
Pine
---------- Forwarded message ----------
From: "Léa Lacroix" <lea.lacroix(a)wikimedia.de>
Date: Oct 5, 2016 01:20
Subject: [Wikidata] Wikimedia Foundation directly funding Wikidata
To: "Discussion list for the Wikidata project." <
wikidata(a)lists.wikimedia.org>
Cc:
Hello folks,
An information that you could find useful : since the beginning of
Wikidata, the project and the development team (led by Wikimedia Germany)
were funded by the Wikimedia Foundation, through the Funds Dissemination
Committee, and by third parties. From now, the Wikimedia Foundation will
directly fund expenses for Wikidata software development. The two
organizations signed an agreement to have direct funding at least for the
next 3 years. This is good news, showing the strong support of our project
by the Foundation and will allow us more stability in the future.
You can read the full blog post here: https://blog.wikimedia.org/
2016/10/04/supporting-the-future-of-wikidata/
Thanks for making Wikidata more and more awesome every day :)
--
Léa Lacroix
Community Communication Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
Reminder, this is happening in about 45 minutes.
On Wed, Sep 28, 2016 at 2:34 PM, Adam Baso <abaso(a)wikimedia.org> wrote:
> Greetings -
>
> The next CREDIT showcase is Wednesday, 5-October-2016 at 1800 UTC (1100
> San Francisco).
>
> https://www.mediawiki.org/wiki/CREDIT_showcase
>
> We look forward to seeing your demos! Please add them to the Etherpad and
> mark your calendars:
>
> https://etherpad.wikimedia.org/p/CREDIT
>
> We welcome works in progress and would be thrilled to see works from
> Wikimedia community members, as well as staff.
>
> If you missed last month's CREDIT, here it is!
>
> https://www.youtube.com/watch?v=rfBQ6H14_SM&t=54
>
> Finally, If you would like to invite anyone to CREDIT, feel free to use
> this template.
>
> *Hi <FNAME>*
>
> *I hope all is well with you! I wanted to let you know about CREDIT, a
> monthly demo series that we’re running to showcase open source tech
> projects from Wikimedia Community, Reading, Editing, Discovery,
> Infrastructure and Technology.*
>
> *CREDIT is open to the public, and we welcome questions and discussion.
> The next CREDIT will be held on October 5th at 11am PT / 2pm ET / 18:00
> UTC. *
>
> *Here’s a link to the YouTube live stream
> <https://www.youtube.com/watch?v=PCn-oeHQnpU>, which will be available
> shortly before the event starts. There’s more info on MediaWiki.org
> <https://www.mediawiki.org/wiki/CREDIT_showcase>, and on Etherpad
> <https://etherpad.wikimedia.org/p/CREDIT>, which is where we take notes and
> ask questions. You can also ask questions on IRC in the Freenode chatroom
> #wikimedia-office (web-based access here
> <https://webchat.freenode.net/?channels=%23wikimedia-office>). *
>
> *Please feel free to pass this information along to any interested folks.
> Our projects tend to focus on areas that might be of interest to folks
> working across the open source tech community: language detection,
> numerical sort, large data visualizations, maps, and all sorts of other
> things.*
>
> *Thanks, and I hope to see you at CREDIT.*
>
>
> -
>
> *YOURNAME*
>
>
>
>
> -Adam
>
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-10-05
= 2016-10-05 =
REMINDER: Arthur will facilitate a retrospective on process in the
2016-10-12 instance of this meeting
== Product ==
=== Reading ===
==== Reading Infrastructure ====
* no blocking/blocked
==== Reading Web ====
* Current sprint:
- Fixed Hovercards instrumentation around `totalInteractionTime`
- Verified correctness of hovercards instrumenation around
`totalInteractionTime`
- Fixed open Hovercards issue when the user comes back to the
previous page by closing a hovercard when the user clicks on it
- Promoted footer from beta to stable
- Created a DeviceDetector service to move device detection code
away from MobileContext
- Spikes:
* Search in UC browser
* Reading debth
- Bugfixes:
* Wikidata UI
* New footer on diff pages
* Broken "edit" link on user pages
* Next sprint:
* Move the first paragraph above infobox
* More work on MobileContext service
* Remove the language button from the bottom of the page
* Page images should return the image from the lead section or
* infobox
* Prototype different options in order to remove FOUC from mobile
* pages (https://phabricator.wikimedia.org/T147338)
==== Mobile Content Service (MCS) ====
* Deployed:
* Fixed video anchors
* Work on a new version of mobile-sections API
==== iOS native app ====
* Current release board:
* https://phabricator.wikimedia.org/project/view/2220/
* Notifications for articles that are in the news (with new iOS 10
* notification UI)
* Updating feed to use MCS and persist to YapDatabase instead of the
* FS
* iOS 9 support for widgets
* Bug fixes (Chinese variants, License icons, iOS 9 Search Issue
==== Android native app ====
* Current sprint
* (https://phabricator.wikimedia.org/tag/mobile-app-android-sprint-92-uranium/):
* Q1 goals met
* v2.4.157 promoted to production
* (https://play.google.com/store/apps/details?id=org.wikipedia)
* Alpha builds currently not publishing
* Investigate Wikipedia Zero Android system notifications
* Fix for semi-protected page permissions
* Fix for image not shown on File pages
* CI screenshot regression testing
* Next sprint
* (https://phabricator.wikimedia.org/tag/mobile-app-android-sprint-93-neptuniu…):
* Start on Q2 goals for Wikidata descriptions
=== Editing ===
==== Parsing ====
* Nothing significant to report this week
==== Collaboration ===
* Blocked
** Continuing collaboration with Services team on ReviewStream
** Work on ORES extension in collaboration with the ORES team
* Blocking
** No change
* Updates
** Had to disable Flow opt-in beta feature temporarily due to a bug.
Working on that now. - https://phabricator.wikimedia.org/T138310
** Other Flow bug fixes to opt-in and other things
** Echo bug fixes and features
==== Language ====
* Blocked:
** Would appreciate (more) comments from ops or puppet-knowledgeable
person how to override restbase url in puppet for a service in labs
(https://phabricator.wikimedia.org/T129284#2674533 )
* Blocking:
** None
* Updates
** Apertium Jessie migration done.
** Work on CX templates continue.
=== Discovery ===
* No blockers
* Working on multiwiki indexes
* Working on ICU folding for Russian, Greek, French and other languages
* BM25 analysis: https://phabricator.wikimedia.org/T143589
** TLDR: BM25 beneficial, tracking typos in first 2 chars - not so much
* File properties search merged, waiting for reindex (hopefully this
* week) to enable (https://phabricator.wikimedia.org/T144447)
* New report on geographic distribution of queries in WDQS:
* https://commons.wikimedia.org/wiki/File:Exploration_on_the_Use_of_WDQS_-_Br…
* Portal: working on GUI improvements & translation improvements
* Portal: about to launch test for putting links to apps on portal page
=== Community Tech ===
* No blockers
* Not blocked
* Need security review for
* https://gerrit.wikimedia.org/r/#/q/topic:T144712 (Checking for &
* validating OATH tokens)
* PageAssessments extension deployed to enwiki, pending addition of
* parser function to master template
* Continued work on Programs Dashboard
* Continued work on sending a cookie with each block
* (https://phabricator.wikimedia.org/T5233)
* Updating CentralAuth tables for cross-wiki watchlist nearly done
* https://phabricator.wikimedia.org/T142507 (Gerrit review needed:
* https://gerrit.wikimedia.org/r/#/c/309553/ )
* Work on porting CopyPatrol to work for other languages is on hold this
* week
== Technology ==
=== Technical Operations ===
* '''Blocked'''
** None
* '''Blocking'''
** None
* Updates
** Offsite done, resuming normal work
** Apertium migrated to Jessie today
** Work on the Kubernetes goal started, will be multi quarter
=== Security ===
* Intake and interviews for security roles continue
* Reviewing OATHAuth patches
* (https://gerrit.wikimedia.org/r/#/q/topic:T144712) from bd808 for labs
* work
=== Services ===
* Blocking: none
* Blocked: none
* Updates:
** RESTBase drops support for node.js 0.10 and 0.12. 4 is now
minimal required version
** ServiceWorker composition work is ongoing
** Parsoid: we want to move config to deploy repo fron ops/puppet
and enable scap3 config deploys.
=== ArchCom ===
* Last week's IRC meeting was about
* https://www.mediawiki.org/wiki/WikiDev17
* This week's IRC meeting: Future of Magic Links
* https://phabricator.wikimedia.org/T145604
* More details/links:
* https://www.mediawiki.org/wiki/Architecture_committee/Status
=== RelEng ===
* Blocking:
** None
* Blocked
** Migration of gallium to contint1001
** https://phabricator.wikimedia.org/T95757
* Updates
** Phabricator
*** Phabricator upgrade this Thursday 1:00 AM UTC (Wednesday night
Pacific)
*** Phabricator database maintenance this week. Time TBA
** Reminder: No train week of Oct 17th (RelEng team offsite)
=== Analytics ===
* Increased aqs throttling to 100/second, new cluster is wicked fast
* Kasocki prototype ready for people to play with
* https://github.com/wikimedia/kasocki (connects kafka topics to a
* socket.io node server)
* Quarter wrap-up work (cleaning up layouts on dashiki, EventLogging
* monitoring, improving some reportupdater queries)
* Recruiting work to get through the many applications we received for
* our now closed junior track position
* Pondering labsdb, Sanitarium, dumps, and history reconstruction here:
* https://phabricator.wikimedia.org/T146444
== Wikidata ==
* No blockers.
* Progress on supporting "federation" (linking entities on foreign
* Wikibase repositories, e.g. linking Wikidata from Commons):
* https://phabricator.wikimedia.org/T76007
* Now allowing bzr://… and cvs://… URL schemes in Wikidata values (first
* time we add schemes core doesn't support).
== Fundraising Tech ==
* Andrew making progress on (one) CentralNotice bug:
* https://phabricator.wikimedia.org/T146880
** Some background here:
https://etherpad.wikimedia.org/p/CentralNotice_translation_magick
** Seems to be a race condition trying to apply protection to a
newly-created article
** We think we can work around by waiting for replication, but should
the race be fixed in core?
* Looks like this is different from the other recent CN bug:
* https://phabricator.wikimedia.org/T144952
** Getting some help from RobLa and Timo, but would appreciate any other
help from caching experts
* Migrated main donations queues to Redis, turning off last ActiveMQ
* usage real soon now
* Still more tweaks to CiviCRM contact de-duplication
* Testing backup credit card processor in other Big English countries
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Hi all,
This week[1]: let's talk about the future of magic links[2][3]
This is LegoKtm's proposal that we move magic links out of core, and
deprecate their use on the Wikimedia cluster. Magic links are the
links that get generated when you put "RFC 1149" or "ISBN
978-1-84685-039-4" in your wikitext, even on a typical MediaWiki
install with no extensions.
The RFC has three components:
1. Moving this functionality to an extension (via parser hook) in
time for the MediaWiki 1.28 release
2. Deprecation strategy for Wikimedia wikis (e.g. Wikipedia)
3. Disable magic links hooks a year later (in time for the next
MediaWiki LTS release)
Given that the implications of steps 2 and 3 are much broader than
just the MediaWiki community, this won't likely result in a "final
comment" period for anything other than step 1. But maybe(?) we can
agree to move forward with step 1.
Let's chat about that tomorrow. Same time as always (Wednesday 21
UTC, 14 PDT, 23 CEST) and place (#wikimedia-office).
Rob
p.s. note that I'm generally better about updating the ArchComStatus
page[4] than sending these emails. "Generally", that is. :-)
[1]: <https://phabricator.wikimedia.org/E269>
[2]: <https://phabricator.wikimedia.org/T145604>
[3]: <https://www.mediawiki.org/wiki/Requests_for_comment/Future_of_magic_links>
[4]: <https://www.mediawiki.org/wiki/ArchComStatus>