Hi. Do you know, by chance, what change in the New Vector could broke the
svg files rendering or clickable area image HTML tags? Because now the
areas are moved aside from there original places, in the New Vector only,
and it broke me hundreds of articles. You can see some screensots here:
https://phabricator.wikimedia.org/T368034. Thank you,
Igal
(User:IKhitron)
Hi friends,
Apologies for the short notice, but please be aware of some
interruption to lists.wikimedia.org tomorrow, Tuesday 18th June 2024
between 10:00 and 12:00 UTC.
We will be migrating the Mailman service off of the old virtual
machine and onto new physical hardware. We hope the window will be
shorter than scheduled, but during this time mail delivery to lists
may be delayed, and the web interface will be intermittently
unavailable.
You can follow along with the work on the task [0] or in irc at
#wikimedia-sre-collab
If there are any questions or comments, please let me know
--Eoghan
[0] https://phabricator.wikimedia.org/T367521
Hello Everyone :)
I am Rohit and I am contributing to the commons-android app.
The issue reference:- https://github.com/commons-app/apps-android-commons/issues/5728 and
the solution PR:- https://github.com/commons-app/apps-android-commons/pull/5741
Before:-
1. Before the PR, the feature to edit the depicts was using wbeditentity API to edit the
entity with a (clear=1) flag.
2. This was causing the whole identity data deletion and adding new data sent to the API
with a data field containing updated depictions.
3. I tried removing that clear flag and it prevented the deletion of the whole data.
However, it was causing depiction to add repeatedly the same without removing the old
ones.
4. I know that it could be the scenario where only the updated depicts were sent to the
API and it'll add the new depicts without causing repetition. But, what about if the
user has removed a depiction?
My Solution:-
1. I used another API to delete the previous depiction first and then, used webeditentity
API to update the new depictions.
2. But, this approach is causing two edit actions on the entity.
Please look at the problem and tell me if there is any way to achieve the desired
functionality in a single edit.
Cloud-vps users:
There are now a mere two weeks remaining before Debian Buster ends its
period of long term support. After June 30th, security upgrades will no
longer be available for this release and VMs running Buster will become
ever more risky and difficult to maintain.
As of today there are still 143 Buster servers running in our cloud[0]
-- some of them are probably yours! Please take some time to delete VMs
that are no longer needed, and rebuild those that are still needed with
a more modern release, ideally Debian Bookworm.
There is a task for your project on phabricator[1] where you can update
your progress. If you have vital VMs that you absolutely cannot rebuild
by July 15th, please update the associated task with your plan and
anticipated timeline. WMCS staff will start shutting down unacknowledged
VMs in mid July in order to attract the attention of users who do not
read email or follow phabricator.
Buster's end of life has been a long time coming, and frequently
announced. If you've been waiting for the right time to think about
this, the time is now.
Thank you!
-Andrew + WMCS staff
[0] https://os-deprecation.toolforge.org/
[1] https://phabricator.wikimedia.org/project/view/6373/
Hello all,
The Code of Conduct Committee is a team of five trusted individuals (plus
five auxiliary members) with diverse affiliations responsible for general
enforcement of the Code of conduct for Wikimedia technical spaces.
Committee members are in charge of processing complaints, discussing with
the parties affected, agreeing on resolutions, and following up on their
enforcement. For more on their duties and roles, see
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee.
This is a call for community members interested in volunteering for
appointment to this committee. Volunteers serving in this role should be
experienced Wikimedians or have had experience serving in a similar
position before.
The current committee is doing the selection and will research and discuss
candidates. Six weeks before the beginning of the next Committee term, they
will publish their candidate slate (a list of candidates) on-wiki. The
community can provide feedback on these candidates, via private email to
the group choosing the next Committee. The feedback period will be two
weeks. The current Committee will then either finalize the slate, or update
the candidate slate in response to concerns raised. If the candidate slate
changes, there will be another two week feedback period covering the newly
proposed members. After the selections are finalized, there will be a
training period, after which the new Committee is appointed. The current
Committee continues to serve until the feedback, selection, and training
process is complete.
If you are interested in serving on this committee or like to nominate a
candidate, please write an email to techconductcandidates AT wikimedia.org
with details of your experience on the projects, your thoughts on the code
of conduct and the committee and what you hope to bring to the role and
whether you have a preference in being auxiliary or main member of the
committee. The committee consists of five main members plus five auxiliary
members and they will serve for a year; all applications are appreciated
and will be carefully considered. The deadline for applications is *the end
of day on June 25, 2024*.
Please feel free to pass this invitation along to any users who you think
may be qualified and interested.
Best,
Amir Sarabadani, on behalf of the Code of Conduct Committee
Last week I saw this in a WMF internal chat: "Now we just need to make
it a weeee easier to edit the Deployments calendar. (or…is there an
easier way than squinting at wikitext tables and copy/pasting
templates?)"
I'm sure that a number of y'all can relate to this. The
<https://wikitech.wikimedia.org/wiki/Deployments> page is pretty nice
to read as a human and not too bad for bots. Editing it though can be
a bit painful as that pull quote implies. I decided I would try to do
something about that. The result is a tool at
<https://schedule-deployment.toolforge.org/>.
The new "Wikimedia Deployment Scheduler" tool tries to make adding
your Gerrit change to a backport window as simple as possible. All it
needs from you is the Gerrit change number, your IRC nick, and the
backport window you want to use. Using some python magic, including
the always useful mwparserfromhell library, it finds the right place
in [[wikitech:Deployments]] to insert your request for deployment.
To make things even easier, Gerrit will now show you a "Schedule
backport of this change" link underneath the commit message for
changes that are eligible for a backport deployment. What changes are
those? Any open, unmerged change on the master branch of
operations/mediawiki-config.git or changes on "wmf/*" branches in
mediawiki/core.git, mediawiki/extensions/*.git, or
mediawiki/skins/*.git.
Thanks to Antoine Musso and Tyler Cipriani for their help and
encouragement in building this tool. If you are interested in seeing
what the Gerrit integration needed, check out
<https://gerrit.wikimedia.org/r/plugins/gitiles/operations/software/gerrit/+…>
Bryan
--
Bryan Davis Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808