Forwarding the message below to this list as some of you might be
interested in the topic - there is a dedicated room to talk about all
things Python (PAWS, Pywikibot, etc.). If you are interested in claiming a
session slot, now is the time!
Cheers,
Srishti
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
---------- Forwarded message ---------
From: Melinda Seckington <mseckington(a)wikimedia.org>
Date: Thu, May 5, 2022 at 2:21 PM
Subject: [Wikidata] Wikimedia Hackathon May 20-22: Info about the online
space, local meetups and more
To: <wikimedia-l(a)lists.wikimedia.org>, <wikitech-l(a)lists.wikimedia.org>, <
wikidata-l(a)lists.wikimedia.org>, <cloud(a)lists.wikimedia.org>, <
wikitech-ambassadors(a)lists.wikimedia.org>
Hi all,
The Wikimedia Hackathon
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022> is coming up in
two weeks, on May 20-22. The Hackathon is an event by and for technical
contributors from around the world. It’s a space to work together on
technical projects, learn new skills, and meet others in the technical
community. Newcomers are welcome
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/How_to/Newcomers>!
A few updates:
The main event will happen in an online game-style space
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/How_to#Joining_the_…>,
supported by local meetups
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Meetups> organized
by community members around the world. Instructions on how to enter the
online space will be published shortly before the start of the hackathon.
If you would like to attend a meetup, please visit the local meetups
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Meetups> page to
learn if there is one nearby and how to join.
If you already know what you are going to be working on or need help on a
project, please add your project to the hackathon Phabricator board
<https://phabricator.wikimedia.org/project/view/5802/>. If you have tasks
that are good for newcomers and are up to helping others, please also tag
them with #good first tasks
<https://phabricator.wikimedia.org/tag/good_first_task/>.
If you have an idea for a session or social activity, you can pick an open
slot in the category which fits your topic and add the session directly to
the schedule
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule>. All
topics are welcome, as long as they are connected to the technical
environment of the Wikimedia projects! We are particularly interested in
sessions that are useful for newcomers.
If you are new to the technical community or this is your first Wikimedia
Hackathon, please check out the list of tips for newcomers
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/How_to/Newcomers>.
If you have any questions, feel free to ask on the talk page
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Hackathon_2022>. If you want
to brainstorm ideas or find a co-speaker for your session, the hackathon
social channels
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Discussions> are a
good place to find others. You can also add your name to the participants
list <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Participants>
and find out what others are interested in.
Many thanks to the folks who already expressed interest in helping with
facilitation or newcomer support! We plan to publish the shift plan early
next week. Those up for helping are welcome to pick an open slot once it’s
up.
We are looking forward to meeting you all soon!
Melinda, for the hackathon committee
--
Melinda Seckington
Developer Advocacy Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
_______________________________________________
Wikidata mailing list -- wikidata(a)lists.wikimedia.org
To unsubscribe send an email to wikidata-leave(a)lists.wikimedia.org
Hello fellow bot writers,
I have a problem which must have been solve a million times before,
but I can't find a full solution. I need to add sections to a talk
page in various locations (depending on the page):
# at the top of the page
# before the first section (i.e. at the top, but after some header)
# at the end of the page, before categories etc.
The first case is trivial and I know about pywikibot.textlib.add_text
which covers the third case, but there doesn't seem to be a ready-made
solution for #2. Do you know any?
Thank you,
Strainu
(This change is relevant for all Wikidata users working with labels,
descriptions, and aliases.)
Based on a long-standing community request we have enabled a new language
code for labels, descriptions, and aliases on Test Wikidata: “mul”, a
special language code meaning “multiple languages”. It is intended to
replace the current duplication of certain labels and aliases in many
languages: instead of the given name Douglas (Q463035)
<https://www.wikidata.org/wiki/Q463035> having the label “Douglas” in
hundreds of Latin-script languages, it should be enough to add it once as
the “mul” label and have all other languages falling back to that (before,
as usual, falling back to “en” as a last resort). This should reduce the
amount of redundant data in Wikidata, and relieve some pressure from the
query service. A big thank you goes to all people involved in the
discussions!
The purpose of the Test Wikidata version of this feature is to determine
whether the current functionality is already sufficient, or whether the
feature needs more work before it can be enabled on Wikidata proper.
Current implementation:
-
You can interact with the new language code using the API.
-
The new language code appears in the table of labels at the top of an
item page for users whose Babel information includes “mul” (or who use ?
uselang=mul in the URL). If there is already a “mul” label, it will be
available for everyone under the usual “all entered languages” option.
-
The page heading will fall back to the “mul” label if necessary.
Fallbacks to “mul” have the usual “indicator” that shows a fallback took
place (CSS class wb-language-fallback-mul).
For more details, see T285156 <https://phabricator.wikimedia.org/T285156>
(or T297393 <https://phabricator.wikimedia.org/T297393> for the Test
Wikidata implementation). You are welcome to leave any feedback about the
technical implementation of the new language code on these tickets.
The new language code will very likely need adjustment of Wikidata policies
and guidelines. In case you would like to contribute to drafting
preliminary new guidelines, a good starting point is: Help
talk:Label#Drafting of guidelines for new language code mul
<https://www.wikidata.org/wiki/Help_talk:Label#Drafting_of_guidelines_for_ne…>
.
Cheers,
--
Mohammed Sadat
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de
Keep up to date! Current news and exciting stories about Wikimedia,
Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now
<https://www.wikimedia.de/newsletter/>.
Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us to achieve our vision!
https://spenden.wikimedia.de
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Forwarding here on this list in case folks here are interested in attending
an upcoming workshop on Pywikibot framework..
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
---------- Forwarded message ---------
From: Srishti Sethi <ssethi(a)wikimedia.org>
Date: Wed, Mar 23, 2022 at 2:45 PM
Subject: Second Pywikibot workshop on Friday, March 25th, 16:00 UTC
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikimedia
Mailing List <wikimedia-l(a)lists.wikimedia.org>, <
wikidata(a)lists.wikimedia.org>, <cloud(a)lists.wikimedia.org>
Cc: Seyram Komla Sapaty <ssapaty(a)wikimedia.org>
Hello everyone,
The second workshop on the topic of "Running Pywikibot scripts" is coming
up - it will take place on Friday, March 25th at 16:00 UTC. You can find
more details on the workshop and a link to join here: <
https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_run_a_…>
[1].
This workshop will introduce participants to the bot scripts available via
the Pywikibot framework and how to use them. If you missed attending the
first one, it would be beneficial to have Pywikibot installed on your
computer before the workshop.
We look forward to your participation!
Best,
Srishti
On behalf of the SWT Workshops Organization team
[1]
https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_run_a_…
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
This is an announcement for a significant, but not breaking, change to the
response format of the wbsearchentities API. So far, each search result has
included "label" or "description" members- which included the
label/description of the matched entity- so that it could be shown to
users. However, these were plain strings with no indication of the language
of the label or description: if language fallback happened (e.g. if the
search was in Arabic, but the item only had an English description), then
there would be no indication of this in the response. Users of the API
couldn’t know what the language of the returned label/description was
without a separate API call to retrieve the entity’s data. This is for
example necessary for screen readers to read out the label/description in
the correct language. (We will follow up with other changes to make use of
it in the Wikibase UI, so that screen readers there are getting a better
indication of which language to read out.)
We have resolved this with the addition of a new "display" member to the
search result structure, which contains a "label" and "description" that
are not plain strings, but rather objects with "language" and "value"
members (like labels and descriptions in the normal JSON serialization
<https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_json.html#json…>).
The old "label" and "description" fields are still there, but deprecated:
we recommend that you don’t use them in new code. Please note that, just
like the "label" and "description" were always optional (i.e. could be
missing for entities that had no label or description available in the
request language or a fallback language), so the "label" and "description"
in the new response are also optional (under the same conditions).
This change was already deployed to Beta Wikidata, Test Wikidata, and
Wikidata. If you have any questions or feedback, please feel free to let us
know in this ticket <https://phabricator.wikimedia.org/T104344>.
Cheers,
--
Mohammed Sadat
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de
Keep up to date! Current news and exciting stories about Wikimedia,
Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now
<https://www.wikimedia.de/newsletter/>.
Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us to achieve our vision!
https://spenden.wikimedia.de
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
-------- Forwarded Message --------
Subject: stream.wikimedia.org - stream retention change
Date: Mon, 21 Mar 2022 09:00:59 -0400
From: Andrew Otto <otto(a)wikimedia.org>
Hello!
*
*
tl;dr: all publicly available event streams at stream.wikimedia.org
<http://stream.wikimedia.org> will have their retention time set to 7 days.
*
*
Many of the streams available at stream.wikimedia.org
<http://stream.wikimedia.org/>have retention times of 31 days. This
means that at any given time, the past 31 days of these streams are
consumable.
*
*
Sometimes, within these streams, certain data may accidentally contain
personally identifiable information. For example, someone might
accidentally enter their personal email into a revision comment field.
On the wikis, this information can be quickly suppressed so that it is
not viewable externally. However, because streams are historical and
immutable, it is difficult to remove this information from the stream
history.
*
*
To help mitigate the risk of PII exposure, we are reducing the retention
of these streams to 7 days. We plan to make this change on *Monday April
4th 2022*.
**
In the future, we would like to intentionally remove this data from
streams. Doing so requires us to maintain new services that produce new
streams with PII information redacted. Doing this is not a trivial thing
to stand up, hence this mitigation effort for now.
-Andrew Otto
Wikimedia Foundation
Hello everyone,
Please I get this error while running scripts
*WARNING: API error modification-failed: ⧼wikibase-validator-bad-prefix⧽*
Please what is the cause of this? and what is the possible fix for it?
Thank you in anticipation.
Chima
Hey Folks,
How are you doing today and I hope you are safe and well wherever you are.
My name is Omoleye Julius Fortunate and I'm a year three statistics student
of the federal University of Agriculture Abeokuta Ogun State Nigeria.
I would like to contribute to the Wikimedia pywikibot project for the 2022
google summer of code programme , and would really love to get an headstart
on how to get started.
I have skills using the Python Django framework, weak machine learning
skills , also some basic site reliability Engineering skills too.
I would be expecting a positive response from anyone that can help soon.
Thank you for your time.
Omoleye Julius