x-posted to wikimania-l
The Wikimania Foundation events team, the Wikimania steering committee, and
members of the 2021 Wikimania organizing team would like to invite you to
help organize Wikimania 2022! Wikimania 2022 will again primarily be a
virtual event, with distributed in-person events if local and global
We need volunteers to be a part of the core organizing team as well as for
other roles. You can find more information here:
The core team will help determine the structure and timeline of the event,
lead programming, scholarship, communication and other teams for the event,
and help ensure our global conference is a success.
For the process to volunteer, see:
There's a set of questions on the meta page linked above; you can email
your answers to the events team or post on meta by January 9th, 2022.
Events staff and Wikimania steering committee members will review
applications, meet with shortlisted candidates the following week, and
announce the core organizing team by January 21st. Please post any
questions on the talk page. We look forward to building an amazing
vice-chair Wikimania Steering Committee
* I use this address for lists; send personal messages to phoebe.ayers <at>
On behalf of the team behind the iOS Wikipedia app: Over the past quarter
the iOS team has been working hard on new features to support notifications
in the app and we would love to hear your feedback and insights.
If you have an iPhone or iPad running iOS 13 or later and edit in more than
one language we’d love to hear from you. The study will take place over two
weeks between January and February, 2022. The survey results (diary
entries) collected throughout this study will be used by the developers to
make improvements to the Wikipedia iOS app
Throughout the course of the study you will be asked to use a beta build of
the Wikipedia app, which includes echo-style notifications. You will need
to allow the Wikipedia app to send ‘push’ notifications to your device.
Every two days (for a total of six entries) you will be asked via email to
fill out a ‘Diary entry’ survey, regardless of if you have used the
Wikipedia app over the past two days. This short survey will ask you to
answer a few questions about your use of the notifications within the app
and also includes space for general comments and thoughts.
At the end of the study you will be asked to fill out one final ten-minute
exit survey, which will focus on your overall experience with the Wikipedia
app notifications and any general thoughts or feedback you might have.
Surveys throughout this study will be conducted via a third-party service,
which may subject it to additional terms. For more information on privacy
and data-handling, see the survey privacy statement
We are able to offer $75 to selected study participants who successfully
complete the full study (a total of six diary entries across two weeks and
completion of the onboarding and exit survey). This is because we’re asking
for a not insignificant participation in the software development process
whether it suits the participant or not at the time; in that way, this is
more like work than the editing which can be picked up or not depending on
what happens elsewhere in life. It can only be offered to those who fully
complete the study.
If you are interested in participating please email Carolyn Li-Madeo (
Thank you for your help and feedback.
Problem statement: Various movement processes, programs, often request
feedback, suggestions or comments. In the process, they get feedback and
questions through different channels such as mailing lists, office hours,
talk pages etc. Now, sometimes it remains unclear what happens next.
Sometimes it remains unclear if a requested feedback is taken/incorporated
or not (and why?). And sometimes feedback and questions remain just
Possible solution: "Feedback was requested" and "Feedback is received" —
now this loop needs to be closed. Closing the loop in a consultation
process is important. (narration below)
A technology policy analyst spoke at Wikimedia Summit 2019. I'll quote a
part from the video. He told—
"The core of responsive regulation is community consultation processes.
However, closing the loop on the consultation process is critical,
otherwise participants feel that they have wasted time providing feedback.
For example, the Indian telecom regulator first issues a consultation
paper. Then solicits the first round of feedback, then solicits a second
round of counter comments, then they hold round tables, and, finally, they
issue the recommendation or the regulation. But when they do that, they
make sure they close the loop. They provide reasoned explanations for why
suggestions were rejected... ..."
When any important major Wikimedia process comes forward and asks for
feedback or suggestions, there might be different results such as
feedback/suggestion accepted, partially accepted, rejected, not actionable,
kept on hold etc. However, closing the loop in this process is important,
example: "we received "this" feedback and this feedback was not
incorporated or was not actionable "because _______"..."
How can it help?
"Closure of a feedback loop" can:
a) help to understand how a feedback/suggestion was taken/noted, and what
were the observations?
b) show respect to the people and their feedback, and most possibly
encourage people to share feedback and ask questions in the next
c) eliminate duplication. If a particular feedback is taken to a
conclusion, several other people don't need to suggest the same thing in
I am posting this as an individual, and over-all this is a process-related
If the major Wikimedia processes or programs soliciting feedback or
questions consider this, I think that will be very helpful.
(quoted timestamp: around 3:40 of the video). Used as a general citation
from resource available on Wikimedia Commons