(If you don’t work with pagelinks table, feel free to ignore this message)
Hello,
Here is an update and reminder on the previous announcement
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>
regarding normalization of links tables that was sent around a year ago.
As part of that work, soon the pl_namespace and pl_title columns of
pagelinks table will be dropped and you will need to use pl_target_id
joining with the linktarget table instead. This is basically identical to
the templatelinks normalization that happened a year ago.
Currently, MediaWiki writes to both data schemes of pagelinks for new rows
in all wikis except English Wikipedia and Wikimedia Commons (we will start
writing to these two wikis next week). We have started to backfill the data
with the new schema but it will take weeks to finish in large wikis.
So if you query this table directly or your tools do, You will need to
update them accordingly. I will write a reminder before dropping the old
columns once the data has been fully backfilled.
You can keep track of the general long-term work in T300222
<https://phabricator.wikimedia.org/T300222> and the specific work for
pagelinks in T299947 <https://phabricator.wikimedia.org/T299947>. You can
also read more on the reasoning in T222224
<https://phabricator.wikimedia.org/T222224> or the previous announcement
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>
.
Thank you,
--
*Amir Sarabadani (he/him)*
Staff Database Architect
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
We have communicated
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>
this change in August 2022 but here is a reminder that if you query
externallinks table in wikireplicas, you will need to rework your queries.
Changes are: el_to, el_index and el_index_60 fields will be dropped and you
need to query el_to_domain_index and el_to_path fields instead.
The data has been migrated in all wikis except English Wikipedia, Wikimedia
Commons and Wikidata, you can keep track of the data migration in T326314
<https://phabricator.wikimedia.org/T326314>.
In late June, we will stop updating the old fields and will start dropping
them
This is done to optimize storage of external links (drastically reducing
its size by removing duplication) and enabling user requested features such
as resolving two <https://phabricator.wikimedia.org/T14810> fifteen-year-old
tickets <https://phabricator.wikimedia.org/T17218> or easier aggregating of
external links domain [1], something that wasn’t possible until now.
[1] For example, If you want to get list of the top-linked websites, you
can query `SELECT el_to_domain_index, count(*) from externallinks group by
el_to_domain_index order by count(*) desc limit 50;`
Thank you and sorry for the inconvenience.
--
*Amir Sarabadani (he/him)*
Staff Database Architect
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello, all!
Starting today we are kicking off the process to shut down Grid Engine and
we want to share the timeline with you.
== Background ==
WMCS made the Grid Engine available as a backend engine for hosting tools
on Toolforge - our Platform as a Service(PaaS) offering.
An additional backend engine, Kubernetes, was also made available on
Toolforge.
Over time, maintaining and securing the grid has proven to be difficult and
making it harder to provide support to the community in other ways because
a lot of man-hours of maintenance work is spent on this.
This is mainly due to the fact that there has been no new Grid Engine
releases (bug fixes, security patches, or otherwise) since 2016.[0]
Maintenance work on the grid continued because it was widely popular with
the community and the Kubernetes offering didn't yet have many grid-like
features that contributors came to love.
Once the Kubernetes platform could handle many of the workloads, we started
the grid deprecation process by asking maintainers to migrate off the
grid.[1]
Over the past year, we've been reaching out to our tool maintainers and
working with them to migrate their tools off the Grid to Kubernetes.
We have reached out directly to all maintainers with their phabricator
ticket IDs.
The latest updates to Build Service[2] have addressed many of the issues
that prevented tool maintainers from migrating.
== Initial Timeline ==
The detailed grid shutdown timeline is available on wiki.[3] The important
dates have been copied below.
* 14th December, 2023: Any maintainer who has not responded on phabricator
will have tools shutdown and crontabs commented out. Please plan to migrate
or tell us your plans on phabricator before that date.
* 14th February, 2024: The grid is completely shut down. All tools are
stopped.
If you need further clarification or help migrating your tool, don't
hesitate to reach out to us on IRC, Telegram, Phabricator[4] or via any of
our support channels.[5]
Thank you.
[0]: https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/
[1]:
https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation
[2]: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service
[3]:
https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#…
[4]: https://phabricator.wikimedia.org/project/profile/6135/
[5]:
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Commun…
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hi all! This is a reminder that the language community meeting is coming up
this Friday, November 17th, from 16:00 to 17:00 (UTC).
Feel free to add any technical updates or challenges related to your
project that you would like to share during the meeting to the agenda
document.
Learn more details: <
https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…
>
Cheers,
Srishti
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
On Tue, Oct 31, 2023 at 2:47 PM Ndahiro Derrick Alter <
ndahiroderric(a)gmail.com> wrote:
> Thanks a lot for the invitation , for the technical issues around
> kinyarwanda wiki , I have to attend alongside my fellow kinyarwanda
> contributors
>
> derrick
>
>
> On Wed, 1 Nov 2023 at 00:32 Srishti Sethi <ssethi(a)wikimedia.org> wrote:
>
>> Hello all,
>>
>> The first language community meeting is coming up in a few weeks -
>> November 17th, 16:00 UTC.
>>
>> If you're interested, you can sign up on this wiki page: <
>> https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…>
>> [1].
>>
>> We would like to invite all of you who are involved in creating content
>> or managing technical aspects across different language communities. This
>> will be a participant-driven meeting, where we collectively discuss
>> specific technical issues related to our language wikis and work together
>> to find possible solutions. This could involve anything from fixing a
>> broken template on the Kurdish wiki to brainstorming ideas for growing
>> content on the Tulu Wiktionary, currently in the Wikimedia Incubator, or
>> celebrating the creation of Fon Wikipedia, to using MinT for content
>> translation.
>>
>> You can view the meeting structure and add ideas for discussion to the
>> notes document here: <
>> https://etherpad.wikimedia.org/p/language-community-meeting-november-2023>
>> [2]
>>
>> If you need interpretation support from English to another language,
>> please let us know by sending an email to ssethi(a)wikimedia.org.
>>
>> Looking forward to your participation!
>>
>> Cheers,
>> Srishti & Jon
>>
>> [1]
>> https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…
>>
>> [2]
>> https://etherpad.wikimedia.org/p/language-community-meeting-november-2023
>>
>> *Srishti Sethi*
>> Senior Developer Advocate
>> Wikimedia Foundation <https://wikimediafoundation.org/>
>>
>> _______________________________________________
>> 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
>
>
Hello!
The 2022 Cloud Services results have been published!
We had 159 participants who responded and provided valuable feedback and
suggestions.
For the first time, we moved from Google Forms to using LimeSurvey.
Some of you have long requested for this change and we will continue to use
LimeSurvey going forward.
The publication of the results have delayed but it's finally here:
https://meta.wikimedia.org/wiki/Research:Cloud_Services_Annual_Survey/2022
Thanks to everyone who participated and provided input and comments!
We will launch the 2023 Cloud Services survey next month!
Thank you!
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hi,
Wikimedia Chat, is a mattermost instance hosted in chat.wmcloud.org and
meet is a jitsi instance hosted in meet.wmcloud.org (both are shut down
now).
I made these two services back in 2020 when we were all in lock-down and
stuck at our homes and virtual social tools were scarce. I wanted it to be
a way to connect to fellow wikimedians.
We are no longer in lockdown and a lot of virtual social tools have
emerged, I'm sure there are many many jitsi and mattermost instances out
there. and on top of that, I really don't have the capacity to maintain
these services anymore.
Here is a call for people who are willing to take over the maintenance, if
no one shows up by end of November, I'll hand over the projects for
deletion.
Best
--
Amir (he/him)