(This announcement is relevant for all Wikidata users working with Labels
and Aliases.)
Hello,
We're excited to invite you to participate in the community testing of the
“default values for labels and aliases” feature. Based on a long-standing
community request around language fallback (T285156
<https://phabricator.wikimedia.org/T285156>), and based on your feedback
from our previous announcement
<https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/me…>,
we are currently testing this feature on https://test.wikidata.org
<https://test.wikidata.org/wiki/Q42> with the release planned for Q1 2024.
What is coming?
1.
Default values for labels and aliases (mul): Items that repeat the same
label and aliases over and over are hard to maintain and can strain our
infrastructure, especially the Wikidata Query Service. As a solution, we
are introducing the option for default values in the termbox. The
default values are considered in the language fallback chain (language code
“mul”).
1.
Visualisation of the language fallback chain: Previously, Wikidata’s
fallback chain was not visible in the user interface, making it challenging
to determine if additional information was needed. As a first step toward
improvement, we will now clearly show what content is already available via
language fallback in the placeholders for labels (including default values).
We need your feedback
Please leave your feedback on Help talk:Default values for labels and
aliases
<https://www.wikidata.org/w/index.php?title=Help_talk:Default_values_for_lab…>.
Your feedback will play a crucial role in verifying if the current version
is ready for Wikidata. Additionally, you can find some test Items, known
limitations and open questions there for you to review. We will analyze
your feedback one week after today's announcement.
The next steps
After you have left your feedback, please make sure that the
guidelines on Help:Default
values for labels and aliases
<https://www.wikidata.org/wiki/Help:Default_values_for_labels_and_aliases>
are ready for the launch. You can also already plan bot-runs for mul, but
please be sure to start with uncontroversial cases. If there are no
blockers, we will then prepare a limited release on Wikidata in the coming
weeks. The limited release will only be visible if you put mul in your
Babel boxes. We will use this limited release to test the performance and
verify that everything works as planned. Please don’t start any bot-runs
for mul during the limited release. A full release will follow a few weeks
later, displaying default values for everyone by default, and featuring an
onboarding element that will guide people to the help page. Bot-runs for mul
can commence at this stage.
Do not hesitate to reach out with questions or concerns in the talk page of
the help page
<https://www.wikidata.org/wiki/Help_talk:Default_values_for_labels_and_alias…>
and for technical details in this Phabricator ticket (T356169
<https://phabricator.wikimedia.org/T356169>).
Thank you for your support!
Cheers,
--
Mohammed Sadat Abdulai
*Community Communications Manager, Wikidata*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
https://wikimedia.de
Grab a spot in my calendar for a chat: calendly.com/masssly.
A lot is happening around Wikidata - Keep up to date!
<https://www.wikidata.org/wiki/Wikidata:Status_updates> 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 Charlottenburg, VR 23855 B.
Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin,
Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine,
Dr. Christian Humborg
Hello,
As many of you may already know, we have been working on introducing a
new Wikidata
data type <https://www.wikidata.org/wiki/Help:Data_type> that will make it
easier to find EntitySchemas
<https://www.wikidata.org/wiki/Wikidata:Schemas> and use them to connect to
other Wikibase Entities. This will allow editors to refer to existing
EntitySchemas in statements to indicate what class of Items, Lexemes etc.
are governed by an EntitySchema. This new EntitySchema datatype is now live
on Test Wikidata <https://test.wikidata.org/wiki/Wikidata:Main_Page> for
testing and your feedback.
Background
EntitySchemas were first introduced in 2019 as a way to model the structure
of Wikidata Items and validate data against those specifications. There are
a number of shortcomings with EntitySchemas still, which means they are not
as useful and used as much as they should be. We are now addressing a
number of those issues, starting with this new data type.
In 2019, we built the first version of the EntitySchema datatype, but it
was eventually rolled back based on your feedback. We have made a lot of
progress since then and take your feedback into account when developing
this new iteration.
The main goal of this development is to help editors model data more
consistently by making EntitySchemas more visible and integrated into
day-to-day editing work. The new EntitySchema data type offers the
following features:
-
A new data type that allows making statements that take an EntitySchema
ID as a value
-
A canonical URI scheme for EntitySchemas has been developed that matches
prefixes of other Semantic Entities (Items, Lexemes, and Properties) to
identify them as concepts and access them when they are referred to in
statements in various formats such as RDF
-
"What Links Here" now enables you to see what Items, Lexemes, and
Properties link to an EntitySchema in a statement
-
A “Concept URI” link has also been added to the EntitySchema’s sidebar,
mirroring the same format as Items
What will come next for EntitySchemas:
-
Displaying EntitySchemas linked in statements by their labels instead of
their IDs, making them more readable and easier to understand.
-
Support for language fallback to make EntitySchemas legible across
languages.
-
An updated termbox (the table with labels, descriptions and aliases) to
provide a more consistent experience between Items, Properties and
EntitySchemas in the future.
Testing and Feedback
Today, we’d love for you to explore EntitySchemas on Test Wikidata
<https://test.wikidata.org/wiki/Wikidata:Main_Page> and provide feedback.
We hope that the new EntitySchema data type will increase centralized
discussions around the modelling of specific classes in Wikidata. This new
visibility will allow for more integration of EntitySchemas into the
ecosystem, leading to improved data quality through more consistent
modelling. Ultimately making the reuse of our data easier, especially for
small to medium-sized reusers.
Here is an example we prepared earlier Q497
<https://test.wikidata.org/wiki/Q497>.
If you encounter any issues, have questions or concerns, or want to provide
feedback, please don’t hesitate to reach out to us on Wikidata talk:Schemas
<https://www.wikidata.org/wiki/Wikidata_talk:Schemas#New_EntitySchema_data_t…>
or
leave a comment on this ticket phab:T332724
<https://phabricator.wikimedia.org/T332724>.
Thanks so much,
Arian
--
Arian Bozorg (he/him)Junior Product Manager Wikidata
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30-577 11 62-230https://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.
Hi everyone,
It’s time to nominate your favorite tool(s) for the fifth edition of the
Coolest Tool Award!! 🎉
The Coolest Tool Award seeks to spotlight the diverse range of tools
created by Wikimedia community members. These tools play a vital role in
improving the efficiency, accessibility, and functionality of Wikimedia
projects, ultimately enriching the experience for Wikimedia communities.
We’d like to invite you all to nominate your favorite & most used tools and
help us celebrate the people who create them!
To nominate your favorite tools, simply follow this link: [
https://wikimediafoundation.limesurvey.net/797991?lang=en] . Feel free to
submit multiple nominations by completing the form as many times as you'd
like. The deadline for Nomination is *May 10th 2024.* For further details
on the nomination and selection process, the Coolest Tool Award academy,
and the upcoming award ceremony, please visit:
https://meta.wikimedia.org/wiki/Coolest_Tool_Award.
We plan to award the coolest tools in a variety of categories (see last
year’s categories
<https://meta.wikimedia.org/wiki/Coolest_Tool_Award/2022#2022_Winners> [2]
for an example). Excitingly, we're returning to an in-person event for the
first time since 2019, with winners set to be unveiled at Wikimania 2024.
If you have any questions or suggestions, don't hesitate to reach out via
the Talk Page <https://meta.wikimedia.org/wiki/Talk:Coolest_Tool_Award>.
We're here to help!
Thank you for your participation and recommendations.
Regards,
Onyinyechi, for the 2024 Coolest Tool Academy
[1] https://meta.wikimedia.org/wiki/Coolest_Tool_Award#Coolest_Tool_Academy
[2] https://meta.wikimedia.org/wiki/Coolest_Tool_Award/2022#2022_Winners
https://www.genericmedsaustralia.com/product/kamagra-jelly/
Kamagra Oral jelly is an innovative medication that has garnered attention for its effectiveness in treating erectile dysfunction (ED). It contains sildenafil citrate, which is also found in Viagra.
However, Kamagra Oral Jelly is not FDA-approved and hasn’t been subjected to the same rigorous testing as medications like Viagra. Buying ED treatments online can pose significant health risks.
== How Does Kamagra Work? ==
Sildenafil citrate, which is found in Kamagra Oral Jelly, works to treat ED by inhibiting the enzymes that manage blood flow to the penis during sexual arousal. This allows the muscles in the penis to remain relaxed, which results in an erection that is hard enough for sexual intercourse. Many people who suffer from erectile dysfunction report a significant improvement in their quality of life following treatment with Kamagra. For example, one elderly man reported that he had been socializing again with women of all ages after he started using Kamagra to improve his sexual performance. This is important for elderly individuals because a lack of relationships can lead to depression and mental decline.
However, it is vital to note that Kamagra is not FDA-approved and that it cannot be purchased legally in the US or Europe without a prescription from a doctor. This is because it is illegal to sell or purchase medications without medical testing and approval in those countries. Buying unlicensed Kamagra could therefore pose serious health risks since there is no way to know what exactly is contained in the medication. It may merely contain sildenafil or it might have different ingredients that can have dangerous or unwanted effects on the body.
Fortunately, there are safe, inexpensive, and reliable alternatives to Kamagra that have been tested and approved for use in the US and other European countries. Purchasing them from trusted and regulated suppliers eliminates the need to buy Kamagra online and may even save you money in the long run.
== What Are the Side Effects of Kamagra? ==
Like all erectile dysfunction medications, Kamagra is intended to help men achieve and maintain an erection. It works by combining two active ingredients to address two common sexual health issues: ED and premature ejaculation (PE).
Sildenafil citrate, the main ingredient in Kamagra, is also used in Viagra. It is a PDE5 inhibitor that increases blood flow to the penis, allowing for an erection to be achieved when a person is sexually aroused. Kamagra is marketed as an ED treatment, but it can also be used to treat PE in off-label use.
There are several potential side effects associated with Kamagra. These include headache, nausea, dizziness, indigestion, and blurred vision. The medication can also lead to prolonged erections (priapism), which is a medical emergency and requires immediate medical attention.
Aside from the potentially serious side effects, there is a risk that Kamagra may contain impurities due to its unregulated production. Because it is manufactured in India, it doesn’t have to comply with the same strict hygiene and production regulations that other medicines must follow. This can increase the risk of side effects, and even poisoning, as has been documented in a recent case. Several safer, regulated treatments for ED don’t have these risks.
== Can I Buy Kamagra Online? ==
Kamagra Oral Jelly is a medication that treats sexual problems like erectile dysfunction and premature ejaculation. It works by increasing blood flow to the penis, making it easier for men to get and maintain an erection when they’re aroused. You should also know that like Kamagra Oral Jelly, Super Kamagra tablets are also a good ED medicine if you are taking Kamagra oral jelly medicine. It’s manufactured by the pharmaceutical company Ajanta Pharma Limited, an Indian multinational corporation with locations all over the world.
Kamagra is available in single-use packets of flavored jelly. It contains the same active ingredient as Viagra (sildenafil citrate), but it comes in a gel form that is easy to swallow. The medication can be bought online, but it’s important to choose a trustworthy and regulated supplier. Buying unlicensed ED treatments can be dangerous. They may contain less of the active ingredient than advertised or they could have other ingredients that can be harmful to your health.
Buying unlicensed drugs is illegal in the UK, and it can also be very dangerous to your health. If you buy a Kamagra oral jelly or tablet that doesn’t have a medical license, it may be counterfeit and contain less sildenafil citrate than advertised. It could also have other ingredients that can be harmful to your body, such as talcum powder, commercial paint, or printer ink. In addition, unlicensed Kamagra may not have been properly produced or stored, which can increase the risk of side effects and complications.
== Is Kamagra Safe? ==
Kamagra is an ED treatment that works by dilating the blood vessels in your penis to help you achieve and sustain an erection. It is a PDE5 inhibitor, which means it works similarly to Viagra. Unlike many erectile dysfunction medications that only work when combined with sexual stimulation, Kamagra can start working within an hour of taking it.
However, Kamagra is not FDA-approved, so there's no way to know if it's safe to take for any length of time. In addition, it's often purchased online through unregulated websites, which can make it difficult to know if the medication is pure or has been mixed with anything else, such as talcum powder or commercial paint.
If you decide to purchase Kamagra, make sure you do so from a reputable website. It's also best to avoid combining it with any other medications, including those used to treat HIV like ritonavir, zidovudine, and saquinavir, since these can cause a serious interaction. It's also important to note that purchasing medicines from other countries without a prescription is against the law, even for personal use.
Lastly, Kamagra should never be used as a substitute for other treatments for erectile dysfunction, such as psychotherapy or vacuum constriction devices. These therapies can help you address the root causes of your ED rather than just masking your symptoms.
*[[Note: I've received feedback that the previous announcement email may
have been buried in older threads, so I'm resending this for visibility.
Apologies if you are seeing this more than once.]]*
Hello all,
The TDMP Retro Committee has finalized the gathering and analysis of
the Technical
Decision-Making Process Retrospective and Consultation phase
<https://www.mediawiki.org/wiki/Technical_decision_making/Technical_Decision…>
.
This document presents the findings of the survey conducted among the
Wikimedia technical community regarding their perspectives on a technical
decision-making process in July 2023.
The purpose of this document is to serve as a comprehensive summary,
offering insights from the retrospective collection of opinions and voices
within the technical community. It is not intended to provide a new
decision-making methodology or devise a fresh process.
It serves to inform the next steps of the process of re-evaluating and
adjusting the current technical decision making process.
The report is now available on MediaWiki at Retrospective and Consultation:
Results and Analysis
<https://www.mediawiki.org/wiki/Technical_decision_making/Technical_Decision…>
Mark Bergsma (VP SRE), Tajh Taylor (VP Data Sci and Eng), and Suman
Cherukuwada (Senior Dir Feature Eng) are taking on the responsibility to
determine what changes to make to the TDMP. They will guide a process to
solicit input and feedback on a proposal that will be open to staff and
volunteer technical contributors.
Thank you,
Moriel, on behalf of the TDMP Retro Core Group.
Core group:
- Moriel Schottlender (chair)
- Daniel Kinzler
- Chris Danis
- Kosta Harlan
- Temilola Adeleye
--
Moriel Schottlender (she/her <https://pronoun.is/she>)
Principal Software Engineer
Wikimedia Foundation https://wikimediafoundation.org/
We operate Wikipedia <https://wikipedia.org> and its sister sites
Hello all,
The Technical Decision-Making Forum Retrospective team
<https://www.mediawiki.org/wiki/Technical_decision_making> invites you to
complete a survey about Wikimedia's technical decision-making processes.
While there will be more ways to participate, this is the first and most
important step in our data collection. It aims to gather information about
your experience, thoughts, and needs regarding the process of making
technical decisions across the Wikimedia technical spaces.
This survey will be used for gathering information about the process and
the needs around technical decision-making that touches our production
systems.
You can find the survey link here:
https://wikimediafoundation.limesurvey.net/885471?lang=en
Who should take this survey?
People who do technical work that relies on software maintained by the
Wikimedia Foundation (WMF) or affiliates. If you contribute code to
MediaWiki or extensions used by Wikimedia, or you maintain gadgets or tools
that rely on WMF infrastructure, this survey is for you.
What is the deadline?
*August 7th, 2023 *
What will the Retrospective team do with the information?
The retrospective team will synthesize the collected data and publish an
anonymized analysis that will help leadership make decisions about the
future of the process.
We will collect anonymized information that we will analyze in two main
ways:
-
Sentiments based on demographic information: these will tell us whether
there are different needs and desires from different groups of people.
-
General needs and perceptions about decision-making in our technical
spaces: This will help us understand what kind of decisions happen in
the spaces, who is involved, and how to adjust our processes accordingly.
Is the survey the only way to participate?
The survey is the most important way for us to gather information because
it helps us gather input in a structured manner. But it will not be the
only way you can share your thoughts with us - we will have more
information soon about upcoming listening sessions where you can talk with
us live. In the meantime, you are always welcome to leave feedback on the
talk page:
https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Technical_Dec…
Where can I see more information?
There are several places where you can find more information about the
Technical Decision-Making Process Retrospective:
-
The original announcement about the retrospective from Tajh Taylor:
https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…
-
The Technical Decision-Making Process general information page:
https://www.mediawiki.org/wiki/Technical_decision_making
-
The Technical Decision-Making Process Retrospective on MediaWiki:
https://www.mediawiki.org/wiki/Technical_decision_making/Technical_Decision…
-
Phabricator ticket: https://phabricator.wikimedia.org/T333235
How to contact the retrospective core team:
-
Write to the core team mailing list: tdf-retro-2023(a)lists.wikimedia.org
-
The Technical Decision-Making Process Retrospective on MediaWiki talk
page:
https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Technical_Dec…
Thank you,
Moriel, on behalf of the TDMP Retro Core Group
Core group:
-
Moriel Schottlender (chair)
-
Daniel Kinzler
-
Chris Danis
-
Kosta Harlan
-
Temilola Adeleye
--
Moriel Schottlender (she/her <https://pronoun.is/she>)
Principal Software Engineer
Wikimedia Foundation https://wikimediafoundation.org/
Hello everyone,
The third edition of the Language & Internationalization newsletter (April
2024) is available at this link: <
https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Newsletter/20…
>.
This newsletter is compiled by the Wikimedia Language team. It provides
updates from January–March 2024 quarter on new feature development,
improvements in various language-related technical projects and support
efforts, details about community meetings, and contributions ideas to get
involved in projects.
To stay updated, you can subscribe to the newsletter on its wiki page. If
you have any feedback or ideas for topics to feature in the newsletter,
please share them on the discussion page, accessible here: <
https://www.mediawiki.org/w/index.php?title=Talk:Wikimedia_Language_enginee…
>.
Cheers,
Srishti
On behalf of the WMF Language team
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>