Esteemed technical community,
The WMF’s SRE Observability team
<https://wikitech.wikimedia.org/wiki/SRE/Observability> invites you to join
our ongoing effort to migrate MediaWiki metrics to Prometheus
<https://wikitech.wikimedia.org/wiki/Prometheus>, utilizing StatsLib
<https://www.mediawiki.org/wiki/Manual:Stats>, an internally developed,
Prometheus-capable metrics interface. This initiative is fundamental in
unifying our metrics, improving MediaWiki observability, and reducing tool
fragmentation. Your participation is crucial to drive this effort forward.
The Ask
We invite you to contribute to this project
<https://phabricator.wikimedia.org/T350592>. Your expertise can drive the
success of this migration, helping us streamline and improve our monitoring
capabilities.
We appreciate your support in migrating your component’s metrics to
StatsLib (*T350592*) <https://phabricator.wikimedia.org/T350592>; this
involves:
-
Look up your component, extension, or module in the task above, claim
(or create) the corresponding sub-task for your metrics, and follow the
examples/docs available to migrate your metrics to the new metrics
interface.
-
Help deprecate and clean up/remove outdated metrics not in use (or
graphed in dashboards).
-
Collaborate with testing and provide feedback for a seamless transition.
Why Prometheus <https://prometheus.io/docs/introduction/overview/>?
We have been using Prometheus in production for several years as it offers
several benefits over Graphite
<https://prometheus.io/docs/introduction/comparison/>. Migrating MediaWiki
off Graphite ensures we stay ahead with a supported, scalable metrics
platform for more effective long-term, multidimensional metrics analysis
and storage. The new stack provides more robust data labeling, storage, and
query capabilities. This project facilitates the improvement of our
production metrics infrastructure and deprecates older systems. The general
thought process is outlined in T249164 RFC: Better interface for
generating metrics in MediaWiki <https://phabricator.wikimedia.org/T249164>.
Support and Resources:
We can assist via various channels such as email, phabricator and IRC
(#wikimedia-observability on Libera.Chat), including periodic technical
office hours (to be scheduled soon). Please contact me or visit the SRE
Observability Team Interface Page
<https://office.wikimedia.org/wiki/Team_interfaces/SRE_-_Observability> for
ways to get involved.
Timeline
Please prioritize and schedule this work within the next few quarters to
ensure a seamless transition and the sustainability of the MW production
ecosystem. Together, we can achieve a more efficient and reliable
Observability platform. Thank you in advance for your understanding and
support.
Hackathon 2024!
We will be at this year’s hackathon
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2024> for those
attending who are interested in participating or have any questions.
We appreciate your support and help; many thanks for your attention and to
all those who have/are participating already!
Respectfully,
Leo
*Leo Mata* (he/him)
Engineering Manager - Observability
Wikimedia Foundation <https://wikimediafoundation.org/>
*[[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
Hi all!
- Results:
https://www.mediawiki.org/wiki/Developer_Satisfaction_Survey/2024
- The developer satisfaction survey launched in December 2023 and closed in
January 2024[0].
- 171 members of the Wikimedia developer community responded to questions
about developer tools and processes.
____
The developer satisfaction survey results show what's important to our
developer community—the parts of the developer experience that work well,
and the parts that need more resources to improve.
➡️ Read it. Talk about it. And ask questions! (please ;))!
____
🎉 Thanks to everyone who took the time to fill out our survey.
And huge thanks to the Wikimedia Research Team for helping Cloud
Services, Release
Engineering, Technical Documentation and other Wikimedia Research team
members build the survey and process the data. In particular, Yu-Ming Liou
for survey-building expertise. And Caroline Myrick who was an absolute hero
processing, exploring, graphing, and patiently explaining all the data.
<3
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <
https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…
>
i've never contributed to any mailing lists, or partaken much, so i don't know how to start this off...
hi? i've realized i can compressed a dataset of lossless .png files down to between a third- or a fourth of the initial size on disk.
that said: in compressing my own backups i find that lossless .png files converted to .xpm (not .ppm, not .bmp) before being compressed result in a compression that of 3- to 4 times smaller in size on disk than the initial .png with it's own compression --- irregardless of any 'PNG optimization' done beforehand: the resulting .xpm files remain identical in size and compress to precisely the same size.
the following commands¹ can surely be tinkered with to greater effect:
---start of shell commands---
mkdir -p xpm
magick convert image.png xpm/image.xpm
mkdwarfs -i xpm/ -o compressed.dfs -l9
---end of shell commands---
now you have a compressed image, three to four times smaller in size on disk, to inspect.
here i openly wonder how a comparison - to assert whether the resulting .xpm file and the lossless .png are indeed the same picture still - would be carried out.
likewise i see this quality of compression extends to the .xgm .xbm formats.
in sharing i wish to bring up the above observation to my best ability. insights welcome as to why this happens and if indeed the image resulting from a lossless .png to .xpm conversion is the same - if this compressed bitmap outperforms the PNG compression significantly without compromising image integrity. (do reply with saying if this is irrelavant information and or presented inadequately in any way: i don't wish to bring red herrings to this mailing list.)
ultimately this is about if a large portion of WikiMedia imagedata indeed can be compressed further by this process - in a 'Pareto improvement' kind of way.
-Ivy, 25
for interest: sources to programs referenced and my brief notes on these.
[1]
magick: https://imagemagick.org/index.php
mkdwarfs, part of the inappropriately named dwarfs toolset:
https://github.com/mhx/dwarfs/blob/main/doc/mkdwarfs.md
note that the -l flag is given the option 9 in the command - this means LZMA is used in this program.
also note that while i use 'mkdwarfs' with LZMA here, i realize the same result on any other program using LZMA or XZ occurs - like the following 'dar', more adequate for single file extraction from an archive and analyzing individual file compression values en masse.
dar: http://dar.linux.free.fr/doc/man/dar.html
unfortunately the projects' website doesn't use HTTPS, so a wayback machine link with HTTPS:
https://web.archive.org/web/20240423233825/http://dar.linux.free.fr/doc/man…
---start of referenced dar command---
dar -c output -zxz9 -R input/
---end of referenced dar command---
lastly two clarifications:
'a lossless .png file' here means an imagefile which never has been converted in a lossy way. a .jpg file converted to a .png used in this procedure produces an output taking more space on disk.
'the procedure' here refers to conversion of a lossless .png to .xpm imagefile format then compressed with either LZMA or XZ in any program.
thank you for reading.
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/
Introduction
https://onlineclassservices.com/pay-someone-to-take-my-online-course/
In the ever-evolving landscape of education, the advent of nurs fpx 6105 assessment 1 has brought both convenience and challenges. For students juggling multiple commitments, the option to seek help with online classes has become increasingly prevalent. This article delves into the dynamics of utilizing online class helpers, particularly in the context of two distinct courses: BUS 3040 Unit 7 and NURS FPX 6105 Assessment 1.
Understanding the Need for Assistance in Online Learning
Online education offers flexibility, enabling individuals to bus 3040 unit7 endeavors while balancing work, family, and other responsibilities. However, the autonomy inherent in online classes requires a high level of self-discipline and time management. For some students, navigating complex course materials and meeting assignment deadlines can be overwhelming, prompting them to seek external assistance.
Exploring the Role of Online Class Helpers
Online class helpers are individuals or services that offer support to students in various aspects of their online coursework. From providing tutoring sessions to completing assignments on behalf of students, these helpers cater to the diverse needs of learners. While some view this assistance as a valuable resource, others raise ethical concerns regarding academic integrity and the authenticity of learning experiences.
BUS 3040 Unit 7: Analyzing Business Strategies
In BUS 3040 Unit 7, students delve into the intricacies of business strategies, help with online class topics such as market analysis, competitive positioning, and strategic decision-making. Assessments may entail case studies, research papers, or strategic business plans. For students grappling with complex business concepts or struggling to meet assignment deadlines, the option to enlist the support of online class helpers may seem enticing.
NURS FPX 6105 Assessment 1: Addressing Healthcare Challenges
NURS FPX 6105 focuses on healthcare assessment, emphasizing the evaluation of online class helpers diagnostic procedures, and treatment plans. Assessment 1 may involve clinical case studies, patient care simulations, or research presentations. Given the demanding nature of nursing education and the critical importance of accurate assessments, students may seek assistance to ensure comprehensive understanding and proficiency in their coursework.
The Controversy Surrounding Paying for Academic Support
While the availability of online class helpers may offer a lifeline to struggling students, it also raises ethical dilemmas and questions regarding academic integrity. Critics argue that paying someone to take online classes or complete assignments undermines the fundamental principles of learning and devalues academic achievements. Moreover, reliance on external assistance may hinder students' personal and intellectual growth, depriving them of valuable learning experiences.
Conclusion: Balancing Support and Academic Integrity
As the demand for online education continues to soar, the debate surrounding the use of pay someone to take my online class . While these services may provide temporary relief for students grappling with academic challenges, educators and institutions must prioritize fostering an environment that promotes academic integrity and independent learning. Ultimately, striking a balance between seeking support and upholding ethical standards is essential in ensuring the integrity and value of online education.
In conclusion, while the convenience of online class helpers may seem appealing, students should carefully consider the long-term implications and ethical considerations associated with seeking external assistance in their academic pursuits.
I'm trying to recreate a CI build to debug things locally. I've followed
the instructions under
https://doc.wikimedia.org/quibble/#reproducing-a-ci-build, but the command
for listing Docker images doesn't work. There are no images with "quibble"
in the name. Where can I find the available Quibble images?
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
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/>