Re: [Wikitech-l] List of all articles about cities?

[Daniel Zahn]

Another way to do it is:

Start at https://en.wikipedia.org/wiki/Category:Cities

Click through the category tree.. for example from there to
"Category:Cities by country" then
"Category:Cities in the United States" -> "Category:Cities in the
United States by county" ->
and so on until you get to a leaf category like "Category:Cities in
Pemiscot County, Missouri"
that contains actual pages instead of more subcategories.

Now go to:

https://en.wikipedia.org/wiki/Special:Export

and paste the Category:... name into the form field "Add pages from
category:". Click "Add" and
then "Export".

Now you have a single XML file with the contents of the articles of
these cities.










https://en.wikipedia.org/wiki/Special:Export

-> "Add pages from category:"and click 'add' button.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] List of all articles about cities?

[petr . kadlec]

On Wed, Aug 12, 2020 at 9:18 PM Thomas Güttler Lists <
guettl...@thomas-guettler.de> wrote:

> Do you have an idea how I can get a list of articles which are about a
> city?
>

Since this is a huge list anyway, so you don’t really want a list of _all_
of them, there are many options to approach it. For start, you can try
https://w.wiki/ZQd as an example.

-- [[cs:User:Mormegil | Petr Kadlec]]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] List of all articles about cities?

[Thomas Güttler Lists]

Hi,

I would like to download all articles about cities and then do some

machine learning fun with the text

For example:

https://en.wikipedia.org/wiki/New_York_City

https://en.wikipedia.org/wiki/Rio_de_Janeiro

 ...

Do you have an idea how I can get a list of articles which are about a city?

Regards,

  Thomas Güttler


--

Thomas Guettler http://www.thomas-guettler.de/
I am looking for feedback: https://github.com/guettli/programming-guidelines


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Scrum of scrums/2020-08-05 & 2020-08-12

[Deb Tankersley]

Hello,

This email contains updates for the last two weeks - August 5 and 12, 2020.

For the HTML versions, see:

https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-08-05
https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-08-12

Cheers,

Deb





*= 2020-08-05 =*

== Callouts ==
* FYI: Removing our old helm charts endpoint (
https://releases.wikimedia.org/charts) and moving to a new one,
powered by chartmuseum. https://helm-charts.wikimedia.org/.
if you are using helm locally with the old repo, you will have to switch to
the new one. On the plus side, this is integrated with our CI now and no
longer requires manually creating helm chart artifacts. Docs at 
https://wikitech.wikimedia.org/wiki/ChartMuseum

== Product ==

=== iOS native app ===
* Blocked by:
* Blocking:
* Updates:
** Continuing development on [[phab:project/view/4661/|6.7 release]].
*** "Article as a living document" experiment
*** Event Platform Client MVP
*** iOS14 widgets & bug fixes

=== Web ===
* Updates:
**'''Summary''': Desktop Improvements Project's (DIP) deployment continues;
continuing WVUI Vector integration and the network client now has a
MediaWiki REST API implementation in review.
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** [[phab:T250968|[ShoutWikiAds] Replace use of deprecated hook
VectorBeforeFooter]]
*** [[phab:T254227|Switch test wikis to new version of vector by default]]
*** [[phab:T253842|Fix the printable versions of modern Vector]]
*** [[phab:T250851|Allow skins to override mediawiki.page.ready
initialisation to enable search JavaScript to be swapped]]
*** [[phab:T249363|Move the existing search to the header in preparation
for Vue.js search development]]
*** [[phab:T259372|Refactor: Move PHP logic into JS for collapsing tabs
under more menu]]
*** [[phab:T257647|Integrate WVUI into Vector for Vue.js search]]
*** [[phab:T251212|[Dev] Drop VectorTemplate usage in Vector]]
*** [[phab:T248399|Document Skin API and their stability, if any (including
Vector)]]
*** [[phab:T247790|wgLogos follow up work]]
*** [[phab:T255319|Eventually deprecate SkinTemplateNavigation::SpecialPage
and SkinTemplateNavigation hooks in favor of
SkinTemplateNavigation::Universal]]
*** [[phab:T244392|Vue.js search case study]]:
 See [[Reading/Web/Desktop Improvements/Vue.js case study/Status
log|weekly status updates]].
** Mobile website (MinervaNeue / MobileFrontend):
*** [[phab:T259080|Minerva bundle checks are broken]]
*** [[phab:T257872|Uncaught Error: Set map center and zoom first on mobile
domain Android]]
*** [[phab:T258096|Regression: Nested references do not open if user clicks
on [ or ] (which are wrapped in span)]]
** Standardization
*** [[phab:T250762|UsersMultiselectWidget not announcing status message]]
*** [[phab:T248062|Deprecate and remove `.background-image-svg()` mixin
from 'mediawiki.mixins.less']]
*** [[phab:T259086|Remove obsolete 'set-graphics'/'svg2png'/'imagemin'
tasks and Less background-image raster fallback for former Grade C browser
support]]
*** [[phab:T254195|Implement a core 'clearfix' mixin in mediawiki.mixin and
evaluate deprecation/removal of 'visualClear' class]]
*** [[phab:T258752|Unify `line-height` to `20px` in widgets to simplify
code and better i18n]]
*** [[phab:T257279|Standardize 'mediawiki.ui' variables to CSS variables
naming scheme in preparation for WikimediaUI Base variables takeover]]
*** [[phab:T247033|Add 'i18n-directionality.less' file to core and extract
overarching theme styles from legacy.less]]
** Portals
*** [[phab:T128546|[Recurring Task] Update Wikipedia and sister projects
portals statistics]]
** Miscellaneous
*** [[phab:T258256|OOUI window management broken on pages with with
additional frames, due to cross document access]]
*** [[phab:T255913|Document tagline and icon options of $wgLogos by putting
them in the installer]]
*** [[phab:T253047|TypeError: undefined is not an object (evaluating
'mw.config.get('wgFormattedNamespaces')[namespace].replace')]]
*** [[phab:T257877|MediaWiki installer appears unstyled]]

== Technology ==

=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Updates:
** Removing our old helm charts endpoint (
https://releases.wikimedia.org/charts) and moving to a new one,
powered by chartmuseum. https://helm-charts.wikimedia.org/.
if you are using helm locally with the old repo, you will have to switch to
the new one. On the plus side, this is integrated with our CI now and no
longer requires manually creating helm chart artifacts. Docs at 
https://wikitech.wikimedia.org/wiki/ChartMuseum





*= 2020-08-12 =*

== Product ==

=== Web ===
* Updates:
** '''Summary''': WVUI Vector integration in Vector, Vue.js-focused week
starting.
** [[Reading/Web/Desktop Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** [[phab:T258493|[Spike 8hrs] "Use Legacy Vector" is not working as a
global preference]]
*** [[phab:T254227|Switch test wikis to 

Re: [Wikitech-l] [Wikimedia Technical Talks] Retargeting extensions to work with Parsoid

[Alexandra Paskulin]

This talk will be starting in 15 minutes on YouTube:
https://www.youtube.com/watch?v=lS1xPkERWCM

See you soon!

On Wed, Aug 12, 2020 at 8:00 AM Alexandra Paskulin 
wrote:

> Hi everyone,
>
> Just a reminder that this talk will take place today at 17:00 UTC.
>
> Hope to see you there!
>
> Best,
> - Alex
>
> On Thu, Jul 30, 2020 at 11:19 AM Sarah R  wrote:
>
>> Hi Everyone,
>>
>> Mark your calendars! Wikimedia Tech Talks 2020 Episode 6 will take
>> place on Wednesday
>> on 12 August 2020 at 17:00 UTC.
>>
>> Title: Retargeting extensions to work with Parsoid
>>
>> Speaker: Subramanya Sastry
>>
>> Summary:
>>
>> The Parsing team is aiming to replace the core wikitext parser with
>> Parsoid
>> for Wikimedia wikis sometime late next year. Parsoid models and processes
>> wikitext quite differently from the core parser (all that Parsoid
>> guarantees is that the rendering is largely identical, not the specific
>> process of generating the rendering). So, that does mean that extensions
>> that extend the behavior of the parser will need to adapt to work with
>> Parsoid instead to provide similar functionality [1]. With that in mind,
>> we
>> have been working to more clearly specify how extensions need to adapt to
>> the Parsoid regime.
>>
>> At a high level, here are the questions we needed to answer:
>> 1) How do extensions "hook" into Parsoid?
>> 2) When the registered hook listeners are invoked by Parsoid, how do they
>> process any wikitext they need to process?
>> 3)  How is the extension's output assimilated into the page output?
>>
>> Broadly, the (highly simplified) answers are as follows:
>> 1) Extensions now need to think in terms of transformations (convert this
>> to that) instead of events (at this point in the pipeline, call this
>> listener). So, more transformation hooks, and less parsing-event hooks.
>> 2) Parsoid provides all registered listeners with a ParsoidExtensionAPI
>> object to interact with it which extensions can use to process wikitext.
>> 3) The output is treated as a "fully-processed" page/DOM fragment. It is
>> appropriately decorated with additional markup and slotted into place into
>> the page. Extensions need not make any special efforts (aka strip state)
>> to
>> protect it from the parsing pipeline.
>>
>> In this talk, we will go over the draft Parsoid API for extensions [2] and
>> the kind of changes that would need to be made. While in this initial
>> stage, we are primarily targeting extensions that are deployed on the
>> Wikimedia wikis, eventually, all MediaWiki extensions that use parser
>> hooks
>> or use the "parser API" to process wikitext will need to change. We hope
>> to
>> use this talk to reach out to MediaWiki extension developers and get
>> feedback about the draft API so we can refine it appropriately.
>>
>> [1] https://phabricator.wikimedia.org/T258838
>>
>> [2] https://www.mediawiki.org/wiki/Parsoid/Extension_API
>>
>>
>> The link to the Youtube Livestream can be found here:
>> 
>>
>> https://www.youtube.com/watch?v=lS1xPkERWCM
>>
>> During the live talk, you are invited to join the discussion on IRC at
>> #wikimedia-office
>>
>> You can browse past Tech Talks here:
>> https://www.mediawiki.org/wiki/Tech_talks
>>
>> If you are interested in giving your own tech talk, you can learn more
>> here:
>>
>> https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Tech_talks
>>
>> Kindly,
>>
>> Sarah R. Rodlund
>> Senior Technical Writer, Developer Advocacy
>> 
>> srodl...@wikimedia.org
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
> --
> Alex Paskulin
> Technical Writer
> Wikimedia Foundation
>


-- 
Alex Paskulin
Technical Writer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] realtime notifications disabled in Phabricator

[Tyler Cipriani]

On 20-08-11 15:04:56, Daniel Zahn wrote:

re: >  "aphlict" service had been disabled on Phabricator because it
caused stability issues.

I am happy to announce that aphlict, the notification service for
Phabricator using websockets, is now finally back again.


\o/ This is great news!

Thank you for working to get this restored.

Realtime notifications are super useful for us; particularly for train
blocker tasks: very happy this service is back!

-- Tyler


signature.asc
Description: PGP signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia Technical Talks] Retargeting extensions to work with Parsoid

[Alexandra Paskulin]

Hi everyone,

Just a reminder that this talk will take place today at 17:00 UTC.

Hope to see you there!

Best,
- Alex

On Thu, Jul 30, 2020 at 11:19 AM Sarah R  wrote:

> Hi Everyone,
>
> Mark your calendars! Wikimedia Tech Talks 2020 Episode 6 will take
> place on Wednesday
> on 12 August 2020 at 17:00 UTC.
>
> Title: Retargeting extensions to work with Parsoid
>
> Speaker: Subramanya Sastry
>
> Summary:
>
> The Parsing team is aiming to replace the core wikitext parser with Parsoid
> for Wikimedia wikis sometime late next year. Parsoid models and processes
> wikitext quite differently from the core parser (all that Parsoid
> guarantees is that the rendering is largely identical, not the specific
> process of generating the rendering). So, that does mean that extensions
> that extend the behavior of the parser will need to adapt to work with
> Parsoid instead to provide similar functionality [1]. With that in mind, we
> have been working to more clearly specify how extensions need to adapt to
> the Parsoid regime.
>
> At a high level, here are the questions we needed to answer:
> 1) How do extensions "hook" into Parsoid?
> 2) When the registered hook listeners are invoked by Parsoid, how do they
> process any wikitext they need to process?
> 3)  How is the extension's output assimilated into the page output?
>
> Broadly, the (highly simplified) answers are as follows:
> 1) Extensions now need to think in terms of transformations (convert this
> to that) instead of events (at this point in the pipeline, call this
> listener). So, more transformation hooks, and less parsing-event hooks.
> 2) Parsoid provides all registered listeners with a ParsoidExtensionAPI
> object to interact with it which extensions can use to process wikitext.
> 3) The output is treated as a "fully-processed" page/DOM fragment. It is
> appropriately decorated with additional markup and slotted into place into
> the page. Extensions need not make any special efforts (aka strip state) to
> protect it from the parsing pipeline.
>
> In this talk, we will go over the draft Parsoid API for extensions [2] and
> the kind of changes that would need to be made. While in this initial
> stage, we are primarily targeting extensions that are deployed on the
> Wikimedia wikis, eventually, all MediaWiki extensions that use parser hooks
> or use the "parser API" to process wikitext will need to change. We hope to
> use this talk to reach out to MediaWiki extension developers and get
> feedback about the draft API so we can refine it appropriately.
>
> [1] https://phabricator.wikimedia.org/T258838
>
> [2] https://www.mediawiki.org/wiki/Parsoid/Extension_API
>
>
> The link to the Youtube Livestream can be found here:
> 
>
> https://www.youtube.com/watch?v=lS1xPkERWCM
>
> During the live talk, you are invited to join the discussion on IRC at
> #wikimedia-office
>
> You can browse past Tech Talks here:
> https://www.mediawiki.org/wiki/Tech_talks
>
> If you are interested in giving your own tech talk, you can learn more
> here:
>
> https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Tech_talks
>
> Kindly,
>
> Sarah R. Rodlund
> Senior Technical Writer, Developer Advocacy
> 
> srodl...@wikimedia.org
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Alex Paskulin
Technical Writer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l