Hi all,
Wikimedia projects would not be possible without the work of the countless
volunteers, passionately working on bringing free knowledge to the world.
This month we Wikicelebrate
<https://meta.wikimedia.org/wiki/Communications/WikiCelebrate>one of such
volunteers: Donatien Kangah (User:Papischou), a Wikimedian from Côte
d'Ivoire, editor of French language Wikipedia, a community leader active on
local, regional, and global levels, a huge football fan, and the co-creator
of the Wikimedia Community User Group Côte d'Ivoire.
Donatien is an experienced Wikipedia trainer, and a member of Wikifranca
micro grant committee. He supported Wikimania through his activity in the
scholarship committee, worked in the capacity building group for Movement
Strategy and collaborated with communities from Senegal, Togo, Chad and
Guinea. Most of his engagement is connected to the Community User Group
Côte d'Ivoire, which he co-founded and which he now leads.
For Donatien the value of editing lies in learning through sharing. “Each
act of sharing knowledge in Wikipedia is about checking sources,
discovering new facts. Even if I already know a lot about the topic, I
discover new facts in sources. It is like swimming in information. Sharing
knowledge is not a passive process, it is a constant discovery. Through
contributing I have learned a lot about my country, Africa and the world.
Editing allows you to grow through giving”, says Donatien.
Learn more about Donatien, and his amazing work on Diff
<https://diff.wikimedia.org/2024/02/23/donatien-bridging-wikipedias-goalpost…>
or on Meta <https://meta.m.wikimedia.org/wiki/User:Papischou>.
Each month we WikiCelebrate a different Wikimedian, acknowledging the
amazing community, the pillars of our movement. We warmly invite you to
participate in the celebrations. If there’s an outstanding Wikimedian that
you think should be celebrated, recommend
<https://wikimediafoundation.limesurvey.net/WikiCelebrate>them.
Happy Celebrating,
Mahuton, Mehrdad and Natalia
Dear all,
I’m Ziski from the Global Advocacy team. I’d like to draw your attention
to important hearings happening this week at the United States Supreme
Court.
The hearings on two cases that will be crucial for Wikimedia have just
started: NetChoice, LLC v. Paxton and Moody v. NetChoice, LLC. Both cases
are challenges to state laws in Texas and Florida, which impact content
moderation on social media websites. You may recall that back in December,
the Foundation issued a "friend of the court
<https://en.wikipedia.org/wiki/Amicus_curiae>" brief urging the Justices to
strike down these laws, explaining that they pose a serious threat to
projects like Wikipedia. You can read about our position on Diff, in our
<https://diff.wikimedia.org/2023/12/07/texas-and-florida-laws-are-unconstitu…>press
release
<https://wikimediafoundation.org/news/2023/12/07/wikimedia-foundation-calls-…>,
and in the
<https://diff.wikimedia.org/2023/12/07/texas-and-florida-laws-are-unconstitu…>
brief
<https://www.supremecourt.gov/DocketPDF/22/22-555/292649/20231207143139081_2…>
itself.
<https://diff.wikimedia.org/2023/12/07/texas-and-florida-laws-are-unconstitu…>
The US Supreme Court is hearing the cases now, and we are there in person
talking to stakeholders and observing the proceedings. We expect the Court
to rule this year and will be providing updates as we know more.
The problem: As they are written, these laws prohibit website operators
from banning users or removing speech and would generally risk Wikipedia’s
volunteer-led systems of content moderation. That’s because these laws were
designed to prevent social media platforms from engaging in politically
motivated content moderation, but were drafted so broadly that they would
also impact Wikipedia. The case is also important beyond the impact it
might have on our projects. It represents a scenario that is part of a
trend globally, where governments introduce legislation to address harms
from big tech actors, yet Wikimedia ends up as the dolphin inadvertently
caught in the net. This is one reason that WMF is working alongside
affiliates to raise awareness about how Wikimedia’s model of community-led
content governance works and why it is important to protect.
What to watch for: We will be monitoring these developments closely in the
United States, with an eye to possible ripple effects in other countries.
We will provide updates on how the Court rules later this year. In the
meantime, please reach out with any questions or comments and look at
the resources
we’re compiling on how to explain the Wikimedia model
<https://meta.wikimedia.org/wiki/Global_Advocacy/Resources> to
policymakers.
All the best,
Ziski
Franziska Putz (she/her)
Senior Movement Advocacy Manager
Global Advocacy, Wikimedia Foundation
Fputz(a)wikimedia.org
UTC Timezone
Thanks Marshall for your pointing out an official answer from the WMF,
Let me say that this is not only disappointing, you are also presenting a false dichotomy where we can only "save a kitten" OR "plant a tree", while we have budget, staff and enough talented volunteers to do both. The dichotomy is presented in a way that makes us think that an estimation of the cost of solving this problem has been done and it is out of all the possibilities, but we don't know what the estimation is. Is there an estimation of how much would this cost? If so, could you please share it so we know why this is out of our possibilities?
I say that this dichotomy is false and I will try to explain why:
* When Maryana Iskander assumed her CEO role, she pointed that the way the annual plan is done should be changed, because the previous monolithic assumption that only things reflected in the annual plan can be done (and nothing else) was preventing us from going forward. You can read it the full reflection here:https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Chief_Executive_O…. Claiming that a high priority problem can't be solved now because it wasn't planned one year ago is not the way it was supposed this to be done.
*
The message is not about the Graphs extension. It has some weight there, but reading this message about interactive content in terms of "if we solve the graphs issue, our job here is done" is also a wrong reduction. But let's think that, indeed, this was the only problem we should solve. Arguing that it is not in the Annual plan so it can't be solved is a fallacy, as explained above, but even then, the annual plan was done AFTER the graph extension was broken. Waiting two years for a high importance problem to be solved can't be the way to do things.
*
Two weeks after Iskander's message, Yael Weissburg wrote in Diff this post: https://diff.wikimedia.org/2022/01/28/what-does-the-world-need-from-us-now-…<https://diff.wikimedia.org/2022/01/28/what-does-the-world-need-from-us-now-…>. In this post Weissburg wrote about "trends that we should expect to accelerate in the years to come because they relate to key changes in how people access, interact with, and share knowledge". You can read the post by yourself, but there is an important takeaway: people is searching for content in another way, and we should give them "rich content". Whatever it takes.
*
One year after Iskander assumed she wrote an update. There we can read that the number 2 priority is "Re-centering the Foundation's responsibility in supporting the technology needs of the Wikimedia movement by understanding the needs of our contributor communities, as well as emerging topics like machine learning/artificial intelligence and innovations for new audiences." We should be doing that "innovations for new audiences", but from you message it seems that we still need "a conversation to happen" https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Chief_Executive_Office…
*
Later that year, Selena Deckelmann wrote that "The Foundation needs to exhibit better accountability in maintaining essential services (e.g. 2-factor authentication), and to be explicit about the technical tasks that it is definitely leaving for volunteers to own." (https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Executive_and_Leadersh…). Yes, I understand that the example given is another one, but the idea is there: "the foundation needs to exhibit better accountability in maintaining essential services". The message follows with an elephant in the room, but we are not going to talk again about the elephant, for sure.
* Finally, last two years annual plans were said to be rooted in the 2030 Strategy (which talks about this issue) and, more specifically, on the 2019 Medium Term plan.https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Medium-term_plan_…. This Medium Term plan (which, again, is the one used as a roadmap) has only two high priority topics, the second one being: "2. Modernize our product experience. We will make contributor and reader experiences useful and joyful; moving from viewing Wikipedia as solely a website, to developing, supporting, and maintaining the Wikimedia ecosystem as a collection of knowledge, information, and insights with infinite possible product experiences and applications.". Then, there's a priority named "Platform evolution" which says literally this: "The Platform Evolution priority encompasses improving and modernizing Wikimedia’s technical ecosystem to respond to a landscape where Artificial Intelligence is creating content, rich media dominates learning, content is structured, and collaboration tools work across multiple devices and have minimal technical requirements. (...)Addressing content gaps also includes making it easier to incorporate rich media, which requires more storage and server power, and better tooling for editing, uploading, and incorporating more types of media. On the engineering front, better automation of the software release process through continuous integration, and a more intentional focus on code quality and testing will allow for more innovative and faster experimentation". Again, this is not something new that happened two months ago, this was written in 2019 coming for an extremely long conversation that already happened between 2017-2019 and that is the guiding principle of our current Annual Plan, stated by the authors of the annual plan. If we are not moving in the way we decided, we are doing it wrong.
I could continue making a list of claims, but I think that is enough to understand that the conversation has happened, that we can save the kitten and plant the tree, that we already have decided that we need this and that it is already written in the annual plan. Claiming that there's no budget is also a bad move, because we don't know how much would this cost. In fact, knowing the cost would be the result of having a plan, but if there's no plan, we can't know if we can pay for it.
Let me end pointing again the big issue here: if we don't go forward with our top importance strategic goals because they are too complex to be solved, then every year will be more difficult to get there. The only way to solve complex issues is to start doing them. Postponing them while we try to take the low hanging fruits is a bad move; claiming that we are not working on them ("one that we have not yet started given the other priorities we’ve been working on") because we have been solving other issues is the worst news we can have.
Have a nice day
Galder
*
________________________________
From: Butch Bustria <bustrias(a)gmail.com>
Sent: Wednesday, February 7, 2024 5:19 AM
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Subject: [Wikimedia-l] Re: We need more interactive content: we are doing it wrong
Hi Everyone,
My earnest hope that the Wikimedia Foundation on its 2024-2025 Annual Financial Plan prioritize and I mean put first among all is the technical infrastructure among all its budgetary items. We can scale down budgets to 3rd party organizations like the Knowledge Equity Fund, Movement Strategy Governance funding, campaign grants, and other "wants" to accomodate a highly technically reliable and stable Wikimedia online projects ("needs"), future proof, and user friendly experience which require investments on quality manpower, hardware, applications and the like. We love open source but we also be pragmatic and wise on selection of choices because we want our content be conveniently available and reliable to our readers, users, consumers and also editors.
A welcome development is the MediaWiki Users and Developers Conference, the successor to EMWCon.
https://www.mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conference_20…
The said conference will be held in Portland, Oregon, from April 17–19, 2024.
I also hope the Foundation invest in more technical gatherings, both onsite, hybrid or online to engage and reach out to more technical contributors, within and beyond the Wikimedia movement. I also hope WMF to start exploring eastward to Asia or elsewhere in the world as well fully diversify the technical community.
Kind regards,
Butch Bustria
On Wed, Feb 7, 2024, 4:54 AM Brion Vibber <bvibber(a)wikimedia.org<mailto:bvibber@wikimedia.org>> wrote:
Thanks for weighing in, Marshall!
I agree wholeheartedly that we need to do a proper architecture for a sandbox for interactive media, that will be safe (first and foremost), perform well in the browser, work across device types (desktop web, mobile web, mobile apps), and maintain our key requirements on editability and reusability, balanced against the security and privacy needs of users if we're going to invest the effort.
Backing up to do it right rather than patch up Graphs “one more time” is the right thing, and I’m very happy to see a confluence of interest around this now!
My hope is we can figure out how to make that architecture & testing work happen in the near term until we collectively (inside WMF and out) can wrangle resources to make the implementation production-ready.
Once we have a common infrastructure to build on, it’ll be easier for work to progress on individual types of media (graphs, charts, maps, animations, editable simulations, coding examples, etc, as well as classics like panorama viewers and integrating the audio/video player into a sandbox for heightened security).
My biggest hope is that we’ll enable more work from outside WMF to happen – letting volunteers and other orgs who might have their own specialty areas and work funding to progress without every change being a potential new security risk.
When we have succeeded in the past, we have succeeded by making tools that other people can use as their own basis to build their own works. I’m confident we can get there on interactive media with some common focus.
Let's all try to capture some of this momentum while we've got it and set ourselves up for success down the road.
– b
On Tue, Feb 6, 2024, 12:27 PM <mmiller(a)wikimedia.org<mailto:mmiller@wikimedia.org>> wrote:
Hi everyone – My name is Marshall Miller, I am a Senior Director of Product at the Wikimedia Foundation, and I work with many of the teams that are involved with the user experience of our websites and apps, such as the Editing, Web, Growth, and Mobile Apps teams (among others) [1]. I’m part of the leadership group that makes decisions about how the WMF teams approach things like graphs, interactive content, and video. Thank you all for having this in-depth and important discussion.
I know that issues with graphs [2] are what started this discussion, but I agree that it makes sense to think about this in terms of the broader category of “interactive content”, because other kinds of interactive content, such as maps or timelines, would share architecture with what is needed for graphs (video is a different and more complicated content type). I wrote a lot in this email, but here are a couple of the main points up front: to support graphs and other interactive content, we would need to take a step back and make a substantial investment in sustainable architecture to do it – so that it works well, safely, and is built to last. And because that’s a substantial investment, we need to weigh it against other important investments in order to decide whether and when to do it.
I know that it is very frustrating that the Graph extension has not been operational for many months – it means readers haven’t been seeing graphs in articles, and editors haven’t been able to use graphs to do things like monitor backlogs in WikiProjects. Over the months of trying to find a way to turn graphs back on, it has become clear that there isn’t a safe shortcut here and that the path forward will require a substantial investment – one that we have not yet started given the other priorities we’ve been working on. Every year we have to make difficult tradeoffs around what areas of our technical infrastructure we can and cannot take on. In the current fiscal year, the Product and Technology department has made experienced editors a priority [3], and many things that volunteers have asked for are either accomplished or in flight:
Improvements to PageTriage (complete) [4]
Watchlist in the iOS app (complete) [5]
Patrolling in the Android app (in progress) [6]
Dark mode (in progress) [7]
Improvements to the Commons Upload Wizard (in progress) [8]
…and other projects.
But I know this conversation isn’t as much about what editors need as what current and future readers need. Between talking about interactive content and talking about video, it sounds like we’re having the larger conversation of what we should be offering today’s and tomorrow’s readers to help them learn from encyclopedic content – whether we need to be offering interactivity, or video, or perhaps enabling other platforms/apps to use our content to make interactive or video materials there. This is a really important conversation, because even working together we probably will not be able to build all of it – we’ll have to make hard choices about where to invest. One place where this broader conversation is happening is called “Future Audiences”, which does experiments on how to reach newer generations who use the internet differently than previous generations – and thinking particularly about video. Future Audiences has regular calls with community members to shape the direction of those experiments, which in turn inform how the broader Foundation prioritizes. I hope many of you will get involved in those conversations – you can sign up here. [9]
Focusing back on graphs, since that’s what kicked this thread off, the several approaches we’ve attempted for quickly re-enabling the extension have ended up having security or performance problems. Therefore, we think that if we were to support graphs and other interactive content, we would need to plan substantial investment in sustainable architecture. This way, our approach would work securely and stably for the longer term. But that would take significant resources, and we’ll need to weigh it against many other important priorities, like tools for functionaries, improvements to the editing experience, automated ways to stop vandals, etc.
To be clear, if we do assign resources to the planning and building of an architecture for graphs (and other interactive content), it means that we are still at least several more months away from having a working Foundation-supported architecture. Therefore, I think we should also be having the additional conversation that many others have brought up about what volunteers can do in these intervening months to make graphs somewhat available to users. I know people are talking about that concretely on the Phabricator task, and I will join that conversation as well.
For the bigger question, I would like to start with some more learning about which kinds of interactive content are important for our encyclopedia, and how our community members see the evolution of the reading experience on our projects. I’d like to have some small conversations with many of you so that we can get into the details and ideas, joined by some of my colleagues. I’ll start reaching out to see who is interested in talking – and please let me know directly if you’d like to talk.
Thank you for weighing in so far, and let’s keep talking and planning together.
Marshall
[1] https://meta.wikimedia.org/wiki/User:MMiller_(WMF)
[2] https://phabricator.wikimedia.org/T334940
[3] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024#…
[4] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation/2023_Moderator_Tools_…!
[5] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS/Watchlist#October_20…
[6] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Anti_Vandalism
[7] https://www.mediawiki.org/wiki/Reading/Web/Accessibility_for_reading
[8] https://commons.wikimedia.org/wiki/Commons:WMF_support_for_Commons/Upload_W…
[9] https://meta.wikimedia.org/wiki/Future_Audiences#Sign_up_to_participate!
_______________________________________________
Wikimedia-l mailing list -- wikimedia-l(a)lists.wikimedia.org<mailto:wikimedia-l@lists.wikimedia.org>, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org…
To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org<mailto:wikimedia-l-leave@lists.wikimedia.org>
_______________________________________________
Wikimedia-l mailing list -- wikimedia-l(a)lists.wikimedia.org<mailto:wikimedia-l@lists.wikimedia.org>, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org…
To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org<mailto:wikimedia-l-leave@lists.wikimedia.org>
Dear Wikimedians,
It has been a year since we were formally recognized, and we are grateful
for all the volunteers who have contributed to making our program a
success. We also appreciate the supportive Wikimedians who have
collaborated with our efforts and have always been on our side in promoting
our activities. On behalf of the Wiki Advocates Philippines User Group
<https://meta.wikimedia.org/wiki/Wiki_Advocates_Philippines_User_Group>, I
would like to present our 2023 annual report on Meta.
<https://meta.wikimedia.org/wiki/Wiki_Advocates_Philippines_User_Group/Repor…>
Best regards,
*Anthony Diaz*
*Wiki Advocates Philippines Inc., Co-founder*
Forwarding to wikimedia-l.
Best,
*Johan Jönsson*Manager, Product Ambassadors
Wikimedia Foundation <https://wikimediafoundation.org/>
---------- Forwarded message ---------
From: Jelto Wodstrcil <jwodstrcil(a)wikimedia.org>
Date: Fri, Feb 23, 2024 at 12:51 PM
Subject: [Wikitech-l] Etherpad maintenance 2024-02-26 09:00 - 10:00 UTC
Hi all,
we have to do *maintenance* on etherpad.wikimedia.org next *Monday,
2024-02-26** 09:00 UTC*. The maintenance involves the switch of the
underlying hardware and a version upgrade. So the estimated downtime is
around *60 minutes*.
If you are working on a document currently please make a backup outside of
Etherpad and do not use Etherpad during the maintenance window. I'll let
you know when the maintenance is finished.
You can find more information in https://phabricator.wikimedia.org/T316421.
Greetings
jelto
_______________________________________________
Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
We are excited to inform the global community that Yoruba Wikipedia hits 25
million views in 2023. This groundbreaking achievement makes Yoruba
Wikipedia the most read Nigerian language Wikipedia and the most visited
website in Yoruba.
Kudos to the Yoruba Wikipedians, and thanks to WMF for their unending
supports.
https://thenationonlineng.net/yoruba-wikipedia-hits-25-million-views-in-202…
Hello all,
The next language community meeting is coming up in a few weeks - *February
21st, 12:00 pm UTC*.
If you're interested, you can sign up on this wiki page: <
https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…
>.
This meeting is for individuals involved in creating content or managing
technical aspects across different language communities. This will be a
participant-driven meeting, where we collectively discuss specific
technical issues related to language wikis and work together to find
possible solutions. This could involve anything from fixing a broken
template on the Kurdish wiki to brainstorming ideas for growing content on
the Tulu Wiktionary, currently in the Wikimedia Incubator, or celebrating
the creation of Fon Wikipedia, to using MinT for content translation.
Feel free to add any *technical updates* related to your project or ideas
for *problem-solving* discussion that you would like to share during the
meeting to the notes document here: <
https://etherpad.wikimedia.org/p/language-community-meeting-february-2024>.
If you need interpretation support from English to another language, please
let us know by sending an email to ssethi(a)wikimedia.org.
Looking forward to your participation!
Cheers,
Jon, Mary & Srishti
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
TL;DR: Are you organizing activities around International Women's Day or
Women's History Month this March 2024? Did you know that there is a central
page where you can showcase your campaigns and learn about what other
Wikimedians are doing globally? Let's chat! Join the Celebrate Women
conversation hour on Monday, February 19th, 2024 at 16:30 UTC. Language
interpretation will be available - English, Spanish, French and Portuguese.
Hi Wikimedia Organizers,
To respond to the gender gap and create opportunities to grow content on
women and non-binary people on Wikipedia, the Gender Organizing community
in the Wikimedia Movement hosts an annual campaign every March called Celebrate
Women <https://meta.wikimedia.org/wiki/Celebrate_Women>. This campaign is
an important opportunity for the Wikimedia movement to engage with the work
of different communities highlighting the gender gap in each Wikimedia
project.
The WMF Campaign Programs team is supporting the movement’s efforts in this
area, working with seasoned organizers to advance coordination of efforts
to #ChangetheStats on gender in the movement.
We would like to invite you to this Celebrate Women 2024 conversation hour
to:
-
Share what your community is doing for this year in campaign organizing
on the Gender Gap during International Women’s Day and beyond.
-
Learn about this year’s volunteer-led Central Notice banner and calendar
and how you can give feedback on the pages.
-
Learn how the event registration tool
<https://meta.wikimedia.org/wiki/EventCenter/Registration/Instructions>
can help improve your registration experience for newcomers joining events,
and other exciting developments in the tools to support your campaign, like
event invitation.
-
Learn about some of the work that has taken place to enhance gender
equity in the movement of the past few months!
Join us on February 19 at 16:30 UTC
<https://meta.wikimedia.org/wiki/Event:Celebrate_Women_2024_conversation_hour>
Interpretation will be available - English, Spanish, French and Portuguese
*Masana Mulaudzi (She/Her)*
Senior Manager, Campaigns Programs
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi all,
The next Research Showcase will be live-streamed on Wednesday, February 21,
at 8:30 AM PST / 16:30 UTC. Find your local time here
<https://zonestamp.toolforge.org/1708533000>. The theme for this showcase is
*Platform Governance and Policies*.
You are welcome to watch via the YouTube stream:
https://www.youtube.com/watch?v=Q1xYwRw1rHU. As usual, you can join the
conversation in the YouTube chat as soon as the showcase goes live.
This month's presentation:
Sociotechnical Designs for Democratic and Pluralistic Governance of Social
Media and AIBy *Amy X. Zhang, University of Washington*Decisions about
policies when using widely-deployed technologies, including social media
and more recently, generative AI, are often made in a centralized and
top-down fashion. Yet these systems are used by millions of people, with a
diverse set of preferences and norms. Who gets to decide what are the
rules, and what should the procedures be for deciding them---and must we
all abide by the same ones? In this talk, I draw on theories and lessons
from offline governance to reimagine how sociotechnical systems could be
designed to provide greater agency and voice to everyday users and
communities. This includes the design and development of: 1) personal
moderation and curation controls that are usable and understandable to
laypeople, 2) tools for authoring and carrying out governance to suit a
community's needs and values, and 3) decision-making workflows for
large-scale democratic alignment that are legitimate and consistent.
Best,Kinneret
--
Kinneret Gordon
Lead Research Community Officer
Wikimedia Foundation <https://wikimediafoundation.org/>