Letter petitioning WMF to reverse recent decitionsEdit
The Wikimedia Foundation recently created a new feature, "superprotect" status. The purpose is to prevent pages from being edited by elected administrators -- but permitting WMF staff to edit them. It has been put to use in only one case: to protect the deployment of the Media Viewer software on German Wikipedia, in defiance of a clear decision of that community to disable the feature by default, unless users decide to enable it.
If you oppose these actions, please add your name to this letter. If you know non-Wikimedians who support our vision for the free sharing of knowledge, and would like to add their names to the list, please ask them to sign an identical version of the letter on change.org.
Greetings! You are receiving this message because, at some point in the past, you have participated in a discussion around the topic of harassment. The Support and Safety team is holding a series of consultations gathering feedback on the best potential solutions to the problem. The next stage is a workshop where we hope to narrow the focus to individual actionable ideas and explore how to bring some of these ideas to life.
Notifications concerning Flow are no longer all grouped together in your preferences. The "Edits to my user talk page" category will now include Flow notifications about your user talk page (if your user talk page uses Flow), and the "Mentions" category will now include mentions on Flow pages. Previously, all notifications related to Flow were grouped together in the "Structured Discussion" category. 
The orange bar will now also be displayed when a message is posted on a your user talk page if your talk page uses Flow; previously, it was only displayed if you had a wikitext talk page. 
A decision has been made about how the Recent Changes filtering scheme will affect current ORES beta feature users. When this new filtering system rolls out as part of the beta, it will replace the current ORES display on the Recent Changes page. That means the automatic color coding, the red “r” symbol and the “hide probably good edits” filter will go away, to be replaced by the new, more nuanced set of filters and user-defined color coding. All other pages that have ORES features, like Watchlist and Related Changes, will remain as they are now for ORES beta users. We think those pages could also benefit from the new filtering system. But we'll wait to see how users react to the beta test—and make any necessary changes—before we start spreading the new UI around. That's the plan as it currently stands. As always, please let us know if you have any thoughts, in any language.
Flow satisfaction survey’s results are available. The survey provides useful data on what users like and don't like about Flow. This information will be helpful in discussions recently begun as part of the editing team's Annual Plan process. As the editing team investigates its priorities for next fiscal year (which begins in July), many ideas for improvements have been suggested, including projects to research the future of wiki discussions and to fix Flow's shortcomings.
Mentions were not recognized when more than one section is added during the same edit or when an new section was added and a change (new message or deletion) was done in another section. This is now solved. 
Rich text mode is now the default in Flow replies. Some inconsistencies used to exist. Now the preference between visual mode and wikitext mode is updated when a content change is made in the selected editor, literally when it is typed in, not when it is saved or when the editor is switched. 
We plan to change Flow's URLs to make them more human readable. Your feedback is still welcome, the conversation will be closed on February 28th.
The fourth fiscal quarter began the first of this month, and Collaboration Team has begun work on our new quarterly goals. In the coming months, we'll be working to release the New Filters for Edit Review beta on all wikis and then to improve the beta as much as possible based on user feedback. On that score, we're planning a round of user interviews on the new tools in May to get detailed information about usability and usefulness. If you've tried the new features and have thoughts, please share them with us in any language.
Our other focus right now is to look at what changes will be needed to spread the new filtering interface to other review pages, especially Watchlist. We're also exploring how to incorporate the tools we didn't include in the new interface in this round, like the Tag Filters, time-frame selector and Namespace filter.
Special:RecentChangesLinked now displays a message when no results are found for a given combination of filters. 
Polish Wikipedia is experiencing an issue with predictions (quality and intent filters using ORES). The different predictions are in conflict. An edit can be considered as "good" and "bad" at the same time, and the filter levels are somewhat redundant. We have formulated a plan to address this and are working on a fix, which is deployed progressively on Polish Wikipedia. 
The issue on Polish Wikipedia is shared by a few other wikis: Dutch, Czech and Hebrew, and Wikidata. The deployment for those wikis has been postponed to Tuesday, May 9. Wikis without this predictions problem have been deployed or will be deployed with no change on the schedule. 
Interestingly, the "problem" with those wikis is that they perform better than we anticipated. Once the fix is in place, the tools will work with particular simplicity on these wikis.
English Wikipedia and all wikis without ORES prediction services will get the New Filters for Edit review on Monday, April 24. 
All remaining wikis will get the New Filters for Edit review on Tuesday, May 9. 
Wikidata edits will be added as a type of change on New Filters for Edit review. 
Tell us your ideas—but don’t wait: The team is focused right now in making changes to the New Filters beta. But in a few months, we’ll be moving on to other projects. So now is the time to give the new tools a try and then tell us what you think. What works well? What could make things better for you?
In the medium-term: By the end of summer, we plan to complete a suite of improvements that will, among other things: incorporate all the remaining Recent Changes tools into the new filtering interface; create new ways for reviewers to move back and forth through the filter queue; implement a “Reverted” filter; and, finally, bring the New Filters UI and tools to Watchlist.
Have time for a talk? We're looking for people we can interview about their experiences with the new beta. If you’re a regular user of Recent Changes and have tried the new features—and if you can spare an hour to chat in English with our design researcher—please email dchenwikimedia.org with the subject line “user interview.” Let us know how to get in touch with you and what time zone (city, country...) you’re in.
The team is moving full speed ahead on a follow-up project to the New Filters for Edit Review beta dubbed "Integrated Filters." The name refers to the fact that we are integrating the Recent Changes tools that currently remain in the old user interface (like Namespace and Tag filters), along with some tools and capabilities from Watchlist and elsewhere, into the new Recent Changes interface.
Category filters: We'll be adding the ability to filter by category. This is a little tricky, since wiki categories often work in a somewhat counter-intuitive way, with the broadest categories returning the fewest results—because categories like "Science" or "Art" tend to contain not articles but other categories. So we're exploring solutions where a category search will crawl at least a layer or two down the category treat to, hopefully, bring back more useful results. 
User filters: We're adding the ability to filter by any username, similar to what's available already on the the User Contributions page. 
Live update: Users will have the ability to look at a more or less continuous flow of changes. This is a much requested feature that we expect will open up new possibilities for Recent Changes, especially for patrollers who want to see vandalism or other changes as they happen. While the updates won't truly be "live," the page updates will be frequent, similar to the way real-time tools (like RTRC or LiveRC) works. 
We're looking for people we can interview about their experiences with the new beta. If you’re a regular user of Recent Changes and have tried the new features—and if you can spare an hour to chat in English with our design researcher—please email dchenwikimedia.org with the subject line “user interview.” Let us know how to get in touch with you and what time zone (city, country...) you’re in.
It is now possible to save your favorite filters sets by using bookmarks. 
There were some issues with loading highlighted results when the URL was copied and pasted. This is now fixed. 
A "Watchlisted pages" filter group now lets reviewers use Recent Changes, and all its tools, to patrol changes to pages they've Watchlisted. If you have any feedback about how useful this is nor isn't—especially given that we plan to add the new filtering interface to the Watchlist page — let us know.
There were issues with the tools still in the older filtering UI — like the Namespace filter and the number of results selectors. These have been fixed. 
Now that users can save filter settings, and declare any settings they want as the Recent Changes page default, we'll be reviewing the RC page Preferences with an eye to getting rid of as many as we can. For instance, if you want to hide minor edits or Category changes by default, you can now do that right on the RC page, instead of having to go to a separate page to manage defaults.
On many Recent Changes Pages, the community has defined a large number of links that are displayed directly under the page name (example on Polish Wikipedia). Many of these links are unrelated or only peripherally related to Recent Changes, add informational complexity of the RC page. Research shows that they are used only rarely or never. We want to clarify RecentChanges page functionality, so we plan to put the links into a collapsible panel.
Should the panel default to open or closed? That is, should the default state (which users can change with one click) show the links as hidden or displayed? Let us know what you think.
The most used links are shortcuts to certain type of edits, (Mobile, Newcomers...). Users can already save their favorite filter settings to the Saved Settings menu, which should make some of the existing links redundant. We plan to provide default bookmarks for the most used filters combinations. 
Wikimedia Deutschland have scheduled the notifications of Wikibase notifications to Wikimedia projects: all the Wikivoyages on May 3; all the Wikipedias except en, fr, de on May 30; all other projects on June 13 and Wikipedias en, fr, de on September 5. 
It will be possible to restrict who can send you notifications. 
The team is currently working on three main goals, which we expect to complete this summer or in September:
Graduate New Filters for Edit Review core features out of beta:
The core New Filters features slated to become standard parts of Recent Changes are the ones that have been out in beta for a while and fully road-tested by the community.
These include the new filtering interface, the machine-learning filter groups “User Intent Predictions” and “Quality Predictions,” the highlighting tools, the ability to save your filter settings for later use, and the new filter groups: “Watchlisted pages,” “Last revision” and "User registration and experience."
We expect to release those features by default in September. A more precise message will be sent to communities. If you have questions about it, you can write a message on Mediawiki.org, in any language.
Extend the New Filters to Watchlist: The Watchlists of very active editors can include thousands of pages. To help these busy folks keep up with their work, we’re adding the New Filters UX and tools to Watchlist. The Watchlist and Recent Changes pages are similar, but there is some work involved in adapting the tools to their new setting. That work should be ready some time in late summer or early fall. Stay tuned for an announcement!
Continuing work on “Integrated Filters”:
While the New Filters for Edit Review beta brought probably 70% of the old-style Recent Changes features into the new user interface, it left some behind—like the Tag and Namespace filters and the controls for the number of days searched and number of results presented. As the name is meant to suggest, “Integrated filters” integrates those old-style tools into the new UI.
It also adds some new tools users have asked for, such as:
“Live updates” which provides a near real-time automatic refresh of the Recent Changes page.
You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.
You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:24, 30 October 2018 (UTC)
Dear Wiki Project Med Supporter, you are receiving this message as you have shown interest in supporting Wiki Project Med in the past. As our organization grows and evolves, we want to be able to verify peoples ongoing interest in being involved. To that end, the board has decided to require renew of membership every two years. So -- whether you are a current member or not, please fill out our updated membership form, to ensure your membership till the end of 2020. Please note -- We ask that you fill out the form by Feb 3rd, as we are close to elections and only members can nominate themselves for the board and vote!
Elections for 5 seats on the board of WPMEDF & Annual MeetingEdit
Dear WikiProject Medicine member, the election for 5 seats on the board is underway and voting is now open till March 24th. We encourage you to use your right to vote by supporting the candidates you prefer HERE. Please also note that on Monday, March 25,
between 1900-2000 UTC we will be holding our open annual meeting online. A link will be sent via the mailing list / Facebook group so stay tuned. We hope you can join us! Best, James & Shani. 14:16, 11 March 2019 (UTC)
Hello, Tom_(LT)! The Community Tech team has posted an April update to the Watchlist Expiry project, and we would love your feedback. The update includes new mockups, which show how users can determine watch status when viewing/editing watched pages or the watchlist. We invite you to check out the update and share your feedback on the project talk page. Thank you! --IFried (WMF) (talk) 17:59, 23 April 2020 (UTC)
The 2021 Community Wishlist Survey is now open!
This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 November, or comment on other proposals to help make them better.
The communities will vote on the proposals between 8 December and 21 December.
The Community Tech team is focused on tools for experienced Wikimedia editors.
You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!
We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.
In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.
We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.