Hello all!
For the last 2 quarters, the Search Platform team has been working on
upgrading our Elasticsearch clusters to version 7.10.2 [1]. Keeping our
software up to date is part of the usual project hygiene, allowing us to
benefit from bugs and security fixes, performance improvements, and new
features. In our case, upgrading to Elasticsearch 7.10.2 is also a required
step towards a potential move to OpenSearch [2].
After much testing, fixes and validations, we are now ready to start the
final migration process. We are anticipating a 3-week migration process,
starting on August 29 2022. You can follow along on Phabricator [3].
What does this mean for you?
For users of Special:Search, Special:MediaSearch and other user-facing
Search interfaces, the upgrade should be fully seamless, and should not
cause any disruptions to normal usage.
For users of Cloudelastic [4] who are accessing the Elasticsearch API
directly, there might be minor API changes that could affect your queries.
Please review the documented breaking changes [5]. Most of the breaking
changes are not related to queries, so it is unlikely that any client code
will break with this upgrade.
If you have any questions about this process, you can find us in
#wikimedia-search on IRC, or at discovery(a)lists.wikimedia.org. Have fun!
The Search Platform team
[1] https://phabricator.wikimedia.org/T263142
[2] https://phabricator.wikimedia.org/T280482
[3] https://phabricator.wikimedia.org/T308676
[4]
https://wikitech.wikimedia.org/wiki/Help:CirrusSearch_elasticsearch_replicas
[5]
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/breaking-chang…
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello everyone,
As part of the effort to align Parsoid's output with the output of the
legacy parser [1], we introduced a possibly backwards incompatible change
[2] in the latest Parsoid version (0.17.0-a1, deployed along with
1.40.0-wmf.1).
Up until that version, while there was no guarantee that it was the case,
the "rel" attribute of HTML tags only had a single value. In particular, it
was possible to access all the external links of a page with
`a[rel="mw:ExtLink"]`. We updated our known clients [3], but did not
communicate that fact outside of the update of our Parsoid HTML
specification [4].
Selectors relying on the "rel" attribute of Parsoid HTML should
consequently be updated to take into account that they can (and do) now
contain space-separated multi-values, as specified in the HTML Living
Standard [5]. A list of what to check is provided in the client-side ticket
[3]. In most cases, a selector like `a[rel=”mw:ExtLink”]` just needs a
single character added: `a[rel~=”mw:ExtLink”]` will correctly match
multi-valued rel attributes.
We apologize for the late communication and the inconvenience.
Best regards,
Isabelle, for the Content Transform Team
[1] https://phabricator.wikimedia.org/T186241
[2] https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/822655
[3] https://phabricator.wikimedia.org/T315209
[4] https://www.mediawiki.org/wiki/Specs/HTML/2.6.0
[5] https://html.spec.whatwg.org/multipage/semantics.html#attr-link-rel
--
*Isabelle Hurbain-Palatin* (she/her)
Senior Software Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
This email is a summary of the Wikimedia production deployment of
1.40.0-wmf.1
- Conductor: Ahmon Dancy
- Backup Conductor: Jeena Huneidi
- Blocker Task: T314190 <https://phabricator.wikimedia.org/T314190>
- Status: Deployed to all wikis
🔢 Stats
Sparklines comparing with the last 5 trains.
- 242 Patches ▁▃██▇
- 2 Rollbacks █▃▁▃▆
- 1 Days of delay ▁█▁██
- 3 Blockers ▃█▁▁▃
🌈 Traintastic Folks 😻Thanks to folks who reported or resolved blockers:
- C. Scott Ananian
- Michael Große (WMDE)
- Taavi Väänänen
- Lucas Werkmeister (WMDE)
- Amir Sarabadani
- Jon Robson
I'm having some issues with Jenkins running the latest version of MW for an
extension (Wikispeech <https://www.mediawiki.org/wiki/Extension:Wikispeech>).
Jenkins run with the 1.40 alpha, but we want the extension to support the
latest LTS (1.35 as of right now).
I tried changing in extension.json to:
"requires": {
"MediaWiki": "1.35.*"
}
which caused an error for Jenkins:
> 12:44:09 A dependency error was encountered while installing the extension
> "Wikispeech": Wikispeech is not compatible with the current MediaWiki core
> (version 1.40.0-alpha), it requires: 1.35.*.
>
The whole log is here: https://phabricator.wikimedia.org/P34482.
How can I specify what version of MW to run with? I've looked at both the
MW wiki and Wikitech, but hasn't found any instructions for this.
Best,
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
Sure, we can do that!
On Thu, Sep 8, 2022, 1:59 PM Gnangarra <gnangarra(a)gmail.com> wrote:
> can 3.b be removed and replaced with
>
> 3.b.1. uploading content
> 3.b.2 creating content
>
> because there are more AI type content creation tools coming online
>
> On Thu, 8 Sept 2022 at 17:21, Seyram Komla Sapaty <ssapaty(a)wikimedia.org>
> wrote:
>
>> Hello!
>>
>> Thanks to everyone who took the time to provide their valuable feedback
>> on the Toolhub taxonomy[0]!
>>
>> After a round of community feedback and input, we made the following
>> decisions about which categories and values to implement in the first
>> productionized version of the taxonomy.
>>
>> === Summary of Changes ===
>>
>> 1.
>>
>> Exclude the proposed Programming language attribute.
>> 2.
>>
>> Exclude the proposed Platform attribute
>> 3.
>>
>> Revise the Tasks attribute values:
>> 1.
>>
>> Remove "Creating or uploading content"
>> 2.
>>
>> Add "Creating new content"
>> 3.
>>
>> Rename "Generating and recommending content" to "Recommending
>> content"
>> 4.
>>
>> Revise the Content types attribute values:
>> 1.
>>
>> Add additional level of hierarchy to group content types and
>> enable both broad or specific values to be applied.
>> 2.
>>
>> Remove "Files".
>> 3.
>>
>> Split "Maps" and "Geographic Data"
>>
>>
>>
>> Find more details of additional changes on the decision record log page[0]
>>
>>
>> === Next Steps ===
>>
>> The team will continue to observe and improve the taxonomy as the
>> community continues to use Toolhub.
>> We will monitor tags and community created lists to determine if certain
>> attributes would be useful or feasible in the future.
>>
>> [0]: https://meta.wikimedia.org/wiki/Toolhub/Data_model#Taxonomy_v2 [1]:
>> https://meta.wikimedia.org/wiki/Toolhub/Decision_record#Taxonomy_v2
>>
>> --
>> Seyram Komla Sapaty
>> Developer Advocate
>> Wikimedia Cloud Services
>> _______________________________________________
>> Wikimedia-l mailing list -- wikimedia-l(a)lists.wikimedia.org, guidelines
>> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>> https://meta.wikimedia.org/wiki/Wikimedia-l
>> Public archives at
>> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org…
>> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
>
>
>
> --
> Boodarwun
> Gnangarra
> 'ngany dabakarn koorliny arn boodjera dardoon ngalang Nyungar
> koortaboodjar'
>
> _______________________________________________
> Wikitech-ambassadors mailing list --
> wikitech-ambassadors(a)lists.wikimedia.org
> To unsubscribe send an email to
> wikitech-ambassadors-leave(a)lists.wikimedia.org
>
Hello everyone,
Wikimedia is participating in the winter edition of this year's Outreachy <
https://www.outreachy.org/> [1] (December 2022–March 2023)! The deadline to
submit projects on the Outreachy website is September 30th, 2022. We are
currently working on a list of interesting project ideas. If you have some
ideas for coding or non-coding (design, documentation, translation,
outreach, research) projects, share them here: <
https://phabricator.wikimedia.org/T313361> [2].
*About the Outreachy program*
Outreachy offers three-month internships to work remotely in Free and Open
Source Software (FOSS), coding, and non-coding projects with experienced
mentors. These internships run twice a year–from May to August and December
to March. Interns are paid a stipend of USD 7000 for the three months of
work. Interns often find employment after their internship with Outreachy
sponsors or jobs that use the skills they learned during their internship.
This program is open to both students and non-students. Outreachy expressly
invites the following people to apply:
* Women (both cis and trans), trans men, and genderqueer people.
* Anyone who faces under-representation, systematic bias, or discrimination
in the technology industry in their country of residence.
* Residents and nationals of the United States of any gender who are
Black/African American, Hispanic/Latinx, Native American/American Indian,
Alaska Native, Native Hawaiian, or Pacific Islander.
See a blog post highlighting the experiences and outcomes of interns who
participated in a previous round of Outreachy with Wikimedia <
https://techblog.wikimedia.org/2021/06/02/outreachy-round-21-experiences-an…>
[3]
*Tips for mentors for proposing projects*
* Follow this task description template when you propose a project in
Phabricator: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects> [4]. Add
#Outreachy-Round-25 tag.
* Project should require an experienced developer ~15 days and a newcomer
~3 months to complete.
* Each project should have at least two mentors, with one of them holding a
technical background.
* Ideally, the project has no tight deadlines, a moderate learning curve,
and fewer dependencies on Wikimedia's core infrastructure. Projects
addressing the needs of a language community are most welcome.
* If you don't have an idea in mind and would like to pick one from an
existing list, check out these projects: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects/> [4]
* To learn more about the roles and responsibilities of mentors, visit our
resources on MediaWiki.org: <
https://www.mediawiki.org/wiki/Outreachy/Mentors> [5].
We look forward to your participation!
Cheers,
Srishti
[1] https://www.outreachy.org/
[2] https://phabricator.wikimedia.org/T313361
[3]
https://techblog.wikimedia.org/2021/06/02/outreachy-round-21-experiences-an…
[4] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
[5] https://www.mediawiki.org/wiki/Outreachy/Mentors
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
(This is a crosspost.)
Hi everyone!
I'm happy to announce that the beloved Community Tech team (the folks
behind the Community Wishlist, as you know) invite you to meet them on
2022-09-14 for a chat on Zoom.
All details are on Meta [1]; your support in translating the message and
getting the word out is welcome, as usual.
Bonus!
They have a mini-survey for you (also at [1]). Please consider taking a few
minutes to let them know what you would like to see covered in future
meetings. You can leave your thoughts on the talk page. [2]
For everything related to this announcement and the event, please contact
Karolin Siebert (ksiebert(a)wikimedia.org).
Thanks for your attention!
[1]
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey/Updates/Talk_to_U…
[2]
https://meta.wikimedia.org/wiki/Talk:Community_Wishlist_Survey/Updates/Talk…
--
------------------------------
Erica Litrenta (she/her)
Senior Manager, Community Relations Specialists (Product)
Wikimedia Foundation <https://meta.wikimedia.org/wiki/User:Elitre_(WMF)>