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/>
Hello all!
We’ve been moving forward on the WDQS Graph Split [1], time for an update!
We have new documentation to help the migration to the split graph:
* Federation limits [2]: Explanation of the limitations of the SPARQL
federation as used on the graph split. This might help you understand what
is possible and what isn’t when you need to federate the main WDQS graph
with the scholarly subgraph.
* Federated queries examples [3]: This document explains how to rewrite
queries to use SPARQL federation over the split graph. We’ve taken a number
of real life examples, and we’ve rewritten them to use federation. While
rewriting queries is not always trivial, the examples that we tried are all
possible to make work over a split graph.
We have been reaching out to people who will be impacted by the graph
split. In particular, we have been having conversations with community
members close to the Scholia and Wikicite projects. In that context, we are
realizing that our initial split proposal (moving all instances of
Scholarly articles to a separate graph - ?entity wdt:P31 wd:Q13442814) is
not sufficient. We have prepared a second and last proposal that will
refine this split to make it easier to use. See "WDQS Split Refinement" [4]
for details. We are open for feedback until May 15th 2024, please send it
to the related talk page [5].
While we refine this split, we are starting work on the implementation of
the missing pieces to make the graph split available. This includes
modifying the update pipeline to support the split and better automation of
the data loading process. We are also working on a migration plan, which we
will communicate as soon as it is ready. Our current assumption is that we
will leave ~6 months for the migration once the split services are
available before shutting down the full graph endpoint.
We need your help more than ever!
If you have use cases that need access to scholarly articles, please read
"Federation Limits" [2] and "Federated Queries Examples" [3], rewrite and
test your queries, and add your working examples to "Federated Queries
Examples" [3].
Send your general feedback to the project page [1].
On a side note, WDQS isn’t the only SPARQL endpoint exposing the Wikidata
graph. You can have a look at "Alternative endpoints" [6], which lists a
number of alternatives not hosted by WMF, which might be helpful during the
transition.
Thanks!
Guillaume
[1]
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_graph_split
[2]
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_graph_spli…
[3]
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_graph_spli…
[4]
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_graph_spli…
[5]
https://www.wikidata.org/w/index.php?title=Wikidata_talk:SPARQL_query_servi…
[6]
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/Alternative_end…
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Dear Wikidata Community,
Wikidata is a treasure trove of data — data we would love to be brought to
light and used for the benefit of the Wikimedia community and beyond!
In order to support that, Wikimedia Deutschland is excited to announce the
launch of a Call for Software Contributions
<https://meta.wikimedia.org/wiki/Software_Collaboration_for_Wikidata/Open_Ca…>
as part of the Software Collaboration for Wikidata program
<https://meta.wikimedia.org/wiki/Software_Collaboration_for_Wikidata>,
funded by the Arcadia Fund <https://www.arcadiafund.org.uk/>. The Software
Collaboration for Wikidata program fosters collaboration with the purpose
of enabling partners from within the Wikimedia Movement to contribute to
the software development of Wikidata and Wikibase in a sustainable and
scalable way. With this program Wikimedia Deutschland wants to explore ways
to create a distributed software development environment within the
Wikimedia Movement. We believe that software is best built by the
communities in which the needs for digital tools arise.
About the Call:
This Call for Software Contributions aims to promote collaboration within
the Wikimedia Movement by inviting affiliates to develop software solutions
leveraging the power of the Wikidata Rest API
<https://www.wikidata.org/wiki/Wikidata:REST_API>. Through this, Wikimedia
Deutschland supports advancing the capabilities of the Wikidata Rest API to
enable the creation of applications (anything from mobile apps to desktop
apps to websites or services) that provide value not only to the Wikimedia
community but also to broader audiences.
With this call, Wikimedia Deutschland aims to support projects that make
Wikidata's data more accessible and usable for a wider audience.
Application deadline is April 21th, 23:59 (GMT+1) (check local time
<https://zonestamp.toolforge.org/1713735900>).
Learn more about this Call on our project page on meta
<https://meta.wikimedia.org/wiki/Software_Collaboration_for_Wikidata/Open_Ca…>
.
We look forward to receiving your exciting project proposals and
collaborating with you to advance the capabilities of Wikidata. If you have
any comments, suggestions or questions please use the call’s talk page
<https://meta.wikimedia.org/w/index.php?title=Talk%3ASoftware_Collaboration_…>
to get in contact with us.
Sincerely,
Maria Lechner