If you continue to disrupt Wikipedia and deliberately ignore all community input, you will be blocked. Please see WT:Flow to get an idea of the backlash you are creating. Your actions wrt Flow only have a negative impact on Wikipedia. If you want to be active here, you'll have to respect the community input and wishes a lot more than you have done until now. Willful provocation, like the enabling o Flow on more pages on enwiki or the activation of an already widely criticized Echo change, is not acceptable any longer. Fram ( talk) 12:00, 5 September 2014 (UTC)
Hello, Danny. As the product manager for Flow, you may be interested in this philosophical exchange of perspectives about the nature of the tool, in particular my reply to Erik. Diego ( talk) 09:53, 6 September 2014 (UTC)
Hi, I have heard about your new project flow which provides UI rich interface for editing discussion and talk pages. I am skilled in various web based programming laguages such as javascript, PHP etc. I was just wondering if you needed any help with the development of flow, as I am eager to help.
Thank you in advance
NetworkOP ( talk) 19:51, 27 December 2014 (UTC)
On my talk page, a user has requested help with errors that have occurred on the Wikipedia talk:WikiProject Breakfast talk page per using Flow. I am unable to fix the matter on the project's talk page. Please see the discussion. Thanks. NORTH AMERICA 1000 16:35, 23 February 2015 (UTC)
For God's sake please stop referring to Flow pages as "boards." Rightly or wrongly, it reinforces the perception that WMF is trying to convert talk pages into freeform discussion fora. I know you mean well, but words matter. Short Brigade Harvester Boris ( talk) 00:11, 7 April 2015 (UTC)
Hi Danny. I received the notice for the Tech support satisfaction survey on my talk, but my account is less than one year old, so I shouldn't have been on the list based on the criteria listed. I noticed you edited the message, so figured you might be the best person to ask about this. Do you happen to know what happened here? Should I respond to the survey or would you prefer I not because I'm not within the target group? ~ Rob Talk 05:53, 20 October 2015 (UTC)
Hi Danny, just checking in with you and Kaldari as to what the technical progress was on the code for ACTRIAL. Is there a phab task available to follow? The consensus at WT:NPPAFC seems to have settled on option 3 with the blacklist being a viable alternative. Kudpung had pointed out on my talk page that it had been All Quiet on the San Francisco Front, so just checking in. Hope all is well. TonyBallioni ( talk) 16:29, 17 July 2017 (UTC)
There is a question here regarding the Spanish Wiki which you may wish to answer. Kudpung กุดผึ้ง ( talk) 09:10, 5 August 2017 (UTC)
Hi Danny, it was very nice to meet you at Wikimania. I've started a follow-up discussion to what we've discussed concerning the future of Article Alerts (link above). Please comment there. Headbomb { t · c · p · b} 10:58, 16 August 2017 (UTC)
As I mentioned on the talk page, the Foundation's needs for the data have different goals from those of the volunteer community that creates and maintains en.Wiki. It would be good if the Foundation staff and/or contractors could collaborate with us in a manner that is helpfull and without telling us to finish their paid-for work for them before we can use it. Otherwise there is no need for them to post on the English Wikipedia talk pages at all, and such comments and or illustrations could be best kept at on the WMF project page where they belong. I'm not criticising anyone but IMO there should be a more clearly defined distribution of roles and where the work takes place. Kudpung กุดผึ้ง ( talk) 23:49, 28 August 2017 (UTC)
( edit conflict)::::I don't think there is a misunderstanding. We already know that there is going to be an impact on new accounts. We already know that less than 0.1% of accounts have ever edited. We already know that a significant number of accounts are deliberately created for the sole purpose of making mischief. We do not believe for a moment that ACTRIAL will increase the number of good articles - that would be simple wishful thinking and is not a serious expectation. But these are the empirical conclusions that a) the Foundation does not wish to entertain, probably because it has no practical experience in these areas, and b) are difficult to explain anyway with pure math. That said, ACTRIAL is designed as a measure to protect Wikipedia's content, integrity, and reputation (which is rapidly deterorating) for quality. 'Quality' per se however, is no within the mandate of New Page Review, and at the end of the day, that's what it all about - and getting he Foundation to produce the software enhancements that are needed to do it efficiently. Kudpung กุดผึ้ง ( talk) 00:57, 29 August 2017 (UTC)
Sorry to say this Danny, but WHY are you butting in here? You should either have helped shape the RfC, or have left a single post with a link to a separate statement of the foundation and just left it at that. You know you are not going to convince Fram, and every word you utter is just another stick for him to fight with and the community will just cheer him on. I know you intend well, but when people don't want to hear you/foundation, this will only result in more trouble (don't feed the troll-effects). Please just let the community run with .. well whatever this total clusterfuck is. — TheDJ ( talk • contribs) 14:56, 13 December 2017 (UTC)
I recently pinged this account on village pump, and I was wondering where is your normal/non WMF a/c? I also didnt know you are founder of muppetwiki, neither that you have a photo of yourself. You remind me of Luke Wilson for some unknown reason. —usernamekiran (talk) 18:26, 19 December 2017 (UTC)
Can you please ping/notify the correct folks at WMF to chime in at Wikipedia:Village pump (proposals)#List of previous creators of an article.Regards:) Winged Blades Godric 11:09, 22 December 2017 (UTC)
Always a pleasure to see you take on community discussions respectfully and constructively. Thanks! effeiets anders 19:37, 2 January 2018 (UTC) |
Oh, thank you, effeiets! I appreciate it. :) -- DannyH (WMF) ( talk) 19:38, 2 January 2018 (UTC)
Is there any problems (legal, technical et al) from WMF's side to not extend storing IP data etc. at the CU logs beyond the current 90 days.You may wish to chime in at User talk:Kudpung/PE - things to do#CU time-span.Regards:) Winged Blades Godric 05:57, 14 January 2018 (UTC)
Any chance that you could have someone look into the massive list of requested improvement to the page curation tools at Wikipedia:Page_Curation/Suggested_improvements? Either that, or tell us that it is never going to happen so we can tell people that they are going to be more successful pissing into the wind. In all seriousness though, the page curation tools might be useful, but they are far from perfect and we have no way to improve them ourselves. If they had been written as a user script, this wouldn't be an issue, but clearly some very shortsighted people over in your neck of the woods decided that we couldn't be trusted with the levers and gears of our own tool set. You had one job, but apparently it is too much for y'all, so either rewrite them as a user script so that we can update and improve them ourselves, or if the tools have indeed been abandoned, please release the code to us so that we can build our own user script version that we will actually have the capacity to update as times and needs change.
If you have noticed a lack of respect in my words, you aren't mistaken, I've been helping to keep New Page Patrol running for a few months now, and I have to wonder what the hell you guys are doing all day? Why would you write a program for NPP to use and then drop it from active development? You team's job is "supporting the most active Wikimedia contributors with the features and fixes that they need" and I am here to inform you that You Are Failing. Wikipedia only keeps running because we develop our own tools to keep our efficiency up in the face of a never ending onslaught of adverts and promotional garbage. Maybe next time when developing something intended to help us, you could actually contact us and ask a few questions? Any numbskull would have said that it should have been written as a script so that it could be updated rather than being entirely backend. — Insertcleverphrasehere ( or here) 03:51, 5 February 2018 (UTC)
The Original Barnstar | ||
For bringing ACPERM live. -- Dlohcierekim ( talk) 01:59, 27 April 2018 (UTC) |
I got head bitten off for reverting an edit that removed a short description. Was I wrong to revert this edit? I don't expect you to interject yourself in the dispute with the other editor but I would like a definitive answer on whether we should or should not be adding short descriptions to every page.
Please respond over here.--- Coffeeand crumbs 08:30, 31 May 2018 (UTC)
{{ Annotated link}} is up and running. This template can be used to automatically annotate a link in a list using the associated short description, making short descriptions actually useful in Wikipedia. This can be used in outline and index lists, and in shorter lists in articles which will be automatically populated with annotations using the associated short descriptions, or any other place where disambiguation is needed. These will remain up to date when the short description is edited. · · · Peter (Southwood) (talk): 12:41, 13 September 2018 (UTC)
Hello DannyH (WMF), I was one of those "most active Wikimedia contributors" that you are supporting "with the features and fixes that they need". I have lost faith the WMF's ability and willingness to support NPP. I have relinquished my new page reviewer right. My decision to quit NPP is a direct consequence of your contributions at meta:Community Wishlist Survey 2019/Miscellaneous/Page Curation and New Pages Feed improvements. I thought you should know that. With regret, Vexations ( talk) 21:37, 3 November 2018 (UTC)
When the WMF treats us like we don’t matter you can expect more people walking away from the job,, it's happening already - just look at the rising graph pf the backlog, what will you do when no one is left to patrol new pages? Until then, the volunteer workforce will continue to lay down their tools. Kudpung กุดผึ้ง ( talk) 00:28, 4 November 2018 (UTC)
Apparently my efforts to manage expectations have caused this group a lot of worry and distress. I'll try to be more clear, because this really is a very positive message, and my intention is for you to feel excited, not stressed out.
I'm talking about "managing expectations" because there have been problems in the past with the Community Tech team allowing huge "improve X system" proposals into the voting phase, doing a lot of work on the wish, and having people still unhappy because we aren't putting an entire team on that wish for an indefinite period of time. The best example is the Maps wish from last year's survey.
The Maps wish was voted #1 on the survey, and we worked on a Map improvements project that took about five months for the Collaboration team (now the Growth team). We delivered significant progress that made it possible for Wikipedia editors to add tens of thousands of maps to wiki articles, in every language.
However, the folks who care about maps are still expecting us to create a full-time Maps team for the next two years, and that's the proposal that they posted this year. As you can see in the discussion on that page, I'm currently having the same kind of "managing expectations" conversation that I'm having with you. We're happy to do more work on maps tools, but we can't promise to work on a huge list of tickets that we haven't evaluated and estimated yet. For that proposal, I've asked them to take out the line about having a team work for 1-2 years on the project, and to scale down their list of requests to the things that they really need this year.
That's what we do for every proposal in the Community Wishlist Survey -- make sure that the proposals are feasible and appropriately scaled before they go to the voting phase. There's an archive of proposals that have been rejected for various reasons: the proposal asks for a social or policy change rather than a technical one, it would open up security or legal risks, or it requires more work than the team can provide in a year. It's important for us that we don't allow people to vote on wishes that we know we can't work on.
Now, to be extra clear -- the NPP proposal is in no danger of being rejected and archived. That's why I posted earlier this week, to reassure you that the current proposal is fine, and it's definitely going to be included in the voting phase. I'm pointing out the archive right now just to give you more context about how the process works.
The voting phase ends at the end of November, and in December/January, the team will investigate all of the tickets involved in the top 10 wishes, and estimate how long they'll take. At this stage, it's possible that the team discovers that the wish as written involves more work than the team can provide in a year. Sometimes a wish needs to be scaled back, or an alternate solution can be found. This is a normal part of the process that applies to every wish. We don't do that estimation in advance because there are probably going to be 300+ wishes posted in two weeks; all we can give them right now is a quick look to see if a wish is obviously going to be unfeasible.
So -- with 17 (now 18) tickets listed in your proposal, it is possible that we'll discover during that estimation process that a small number of them are unfeasible for the team. I know that you all have been thinking and working on these tickets for a long time, and you have a good idea of how much work it might be, but we haven't done that yet, and the team may find a couple of problems that you don't know about. If that's the case, then the team will talk to the NPP group, explain any problems that have come up, and talk to you about possible alternative solutions. That is the only thing that I'm saying in this "managing expectations" message -- that the exact list of 18 tickets as written may have a surprise or two, and you should be aware of that possibility.
If your proposal is voted into the top 10, it is a guarantee that Page Curation will get a significant amount of work from the Community Tech team. I expect that the great majority of tickets listed will get done. This is good news for your group. You're doing the correct thing that will lead you to getting what you want.
I understand that there's a long history of the Foundation not providing you with the support that you needed to do your work, and that you don't trust the people who work at the Foundation to follow through on promises. I don't expect you to suddenly regain trust for me or the Foundation; that's not how trust works. All I can do right now is to act in a trustworthy way. I believe that's what I'm doing in this conversation.
Now, it's true that if your proposal doesn't get the required number of votes to get into the top 10, then the Community Tech team won't work on Page Curation, and you'll have to try again next year. The same is true for every other person participating in the Wishlist Survey. I know that you feel that NPP is more important than Maps and event organizer tools and all of the other projects that the Community Tech team is working on. The most effective way for you to get that message across is to get people to vote for your proposal. I'm happy to keep talking with you about this, but I think your time would be better spent in encouraging editors to vote. -- DannyH (WMF) ( talk) 20:06, 4 November 2018 (UTC)
Could you elucidate, why exactly why you have declined my proposal at the meta: Community Wishlist 2019 ? How does making cosmetic changes to MiniveraNeue have anything to do with my proposal which asks for the ability to change skins on the Mobile Frontend ? Timeless/Monobook mobile, supports the Twinkle gadget, something which is absent from MiniveraNeue even in desktop mode, as is the extremely useful RefToolbar — f r + 11:09, 17 November 2018 (UTC)
in a case, when en-wiki editors can't agree on the optimum short-description which ought be used over an article (and atleast, some of the parties vehemently dislike the WD one)? In most of the general cases of content, the particular prose will be left out of the article unless a t/p discussion leads to consensus for any version pending which it's inserted. In other words, how to force the system to display nothing? ∯WBG converse 18:26, 23 March 2019 (UTC)
Welcome to the nineteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
18:36, 26 October 2021 (UTC)
Welcome to the twentieth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
As of February, 300,000 suggested edits have been completed since the feature was first deployed in December 2019.
Add a link is the team's first structured task, deployed in May 2021. It has improved outcomes for newcomers. The team is now working on a second iteration based on community feedback and data analysis. Improvements will include: improved algorithmic suggestions, guardrails to prevent too many similar links to be added, and clearer encouragement for users to continue making edits. After adding these improvements, we will deploy this task to more Wikipedias.
Add an image is the second structured task built by our team. It was deployed in November 2021 to four pilot Wikipedias. This is a more challenging task for newcomers. However, it adds more value to articles (so far, over 1,000 images have been added). We are currently learning from communities and from the data on what is working well and what needs improvements. The project page contains links to interactive prototypes. We are very interested to hear your thoughts on this idea as we build and test the early versions. We will soon deploy this task to more Wikipedias as a test.
"Add a link" and "Add an image" now both have a limitation on how many of these tasks newcomers can do per day. It is meant to discourage careless newcomers from making too many problematic edits.
Over the last two years, the Growth team has focused on building suggested edits: easy tasks for newcomers to start with. We have learned with this experience that these tasks help many newcomers to make their first edits. Now, the team is starting a new project : " positive reinforcement". Its goal is to make newcomers proud of their editing and to make them want to come back for more of them. With the positive reinforcement project, we are considering three kinds of features:
This project is just beginning, and we hope for community thoughts on the direction. We know that things can wrong if we offer the wrong incentives to newcomers, so we want to be careful. Please visit the talk page to help guide the project!
Some wikis have created userboxes that mentors can display on the user pages. If your wiki has one, please link it to Wikidata!
Previously, at most Wikipedias, only 80% of newcomers were getting the Growth features. This was done for experimentation, to have a control group. We have changed this setting. Now 100% of new accounts at all Wikipedias get the Growth features ( except a few, kept as test wikis). We invite communities to update their onboarding documentation and tutorials. Please include the Growth features in it. To help you, we have created an help page that can be translated and adapted to your wiki.
Do you have questions about the Growth features? This translatable FAQ contains answers to the most common questions about the Growth team work. We regularly update it.
Interface translations are important for newcomers. Please help for your language, by translating or copyediting interface translations for the Growth features.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:12, 16 March 2022 (UTC)
Welcome to the twenty-first newsletter from the Growth team!
Communities can configure how the features work, using Special:EditGrowthConfig.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
13:03, 5 July 2022 (UTC)
Welcome to the twenty-second newsletter from the Growth team!
As of the last week of June 2022, the newcomers of the world have completed over 500,000 newcomer tasks. In other words, newcomers have made over half a million Wikipedia edits via Growth’s “Suggested Edits” module.
We have added some new data to Grafana. You can now check the number of edits and reverts by task types, or the number of questions asked to mentors. You can filter the data by wiki.
If you have any questions, or there is more data you want access to, please let us know.
We are continuing our work on our new project, Positive Reinforcement. User testing of initial Positive Reinforcement designs was just completed. Interviews were conducted in Arabic, English, and Spanish. The outcome has been published on the Positive Reinforcement page. We are now utilizing user testing feedback along with prior community feedback to iterate and improve designs.
We are exploring the idea of a Copy Edit structured task. We have tested copy edits in Wikipedia articles for arwiki, bnwiki, cswiki, eswiki (Growth pilot-wikis) and enwiki with two different methods: LanguageTool and Hunspell. We will share more details here and on the associated Copy Edit page once the evaluation is complete.
Add an image was utilized at GLAM events in Argentina, Mexico, and Chile. For an overview of what was learned from these events, read: #1Pic1Article I: how Latin American heritage experts added images to Wikipedia (in English).
Add a Link Experiment Analysis has been published. The most important points are:
Newcomer task edit type analysis has been published.
A new system for the mentors list
The configuration of the mentors list will change over the next weeks. In the future, mentors will sign up, edit their mentor description and quit using Special:MentorDashboard. This new system will make the development of new features for mentors much easier.
At the moment, the mentor list is a simple page anyone can edit, unless it’s protected. With the new page, mentors will be able to edit only their own description, while administrators will be able to edit the entire mentors' list if needed.
The deployment will happen first at the pilot wikis, then at all wikis. Existing lists of mentors will be automatically converted, no action will be needed from the mentors. [13] [14]
Mentors will be informed about the next steps soon, by a message posted on the talk page of existing Mentor lists.
Learn more about this new structured page on mediawiki.org.
A tip for mentors
Did you know that mentors can filter their mentees' changes at Special:MentorDashboard (and star the ones that require attention)? This feature helps to keep an eye on newcomers' edits, helping mentors to fix minor details, and encourage them if necessary.
And did you know that mentors have special filters to highlight their mentees' edits at Special:RecentChanges? Look for the following filters in RecentChanges: Your starred mentees, Your unstarred mentees.
Other improvements
Some improvements will be made to the mentor dashboard in the coming weeks:
Please let us know! You can also read our FAQ page.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:18, 21 September 2022 (UTC)
Welcome to the twenty-third newsletter from the Growth team!
The goal of the Growth team is to encourage newcomers to try editing for the first time, and encourage them to keep editing. We want to increase newcomers' motivation by showing them how impactful their edits are.
Newcomers have access to an impact module; you can find yours at Special:Impact. The revised impact module provides new editors with more context about their impact. It will display the number of edits, the number of thanks received, the last time they edited, the number of consecutive days they edited, and the number of views for the articles they edited.
This module will soon be available at our pilot wikis starting December 1. You can already test this new module at Beta Wikipedia. For safety reasons, do not use your regular account and password at Beta wiki. Create a new, specific account for this wiki, with a different password.
After the deployment of Structured tasks, we received feedback from various communities regarding how patrollers of recent changes were feeling overwhelmed by an increase in edits to check, and how some edits were poor quality or of poor relevance.
We made several improvements based on the feedback we received. Several points of improvement have already been addressed:
The Positive Reinforcement project will also address some of the concerns around encouraging newcomers to progress to higher value edits. The Growth team will soon work on strategies geared at " Leveling up" newcomers so they progress from easy to more difficult tasks.
Special:MentorDashboard
.Special:ManageMentors
— now displays the list of mentors. This page can be transcluded on any other page. There are also new processes to
signup as a mentor or to
quit mentorship, and we improved
community mentorship management.We plan to have a more regular newsletter, every two months. We also want to know if the current format suits you! Let us know what you like, what you like less and your suggestions of improvements: leave us a comment, in your preferred language.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
20:57, 29 November 2022 (UTC)
Welcome to the twenty-fourth newsletter from the Growth team!
The Growth team partnered with other WMF teams to conduct several experiments around increasing account creation and new editor retention. Results from four of these experiments are now available:
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.• Help with translations
14:44, 31 January 2023 (UTC)
If you continue to disrupt Wikipedia and deliberately ignore all community input, you will be blocked. Please see WT:Flow to get an idea of the backlash you are creating. Your actions wrt Flow only have a negative impact on Wikipedia. If you want to be active here, you'll have to respect the community input and wishes a lot more than you have done until now. Willful provocation, like the enabling o Flow on more pages on enwiki or the activation of an already widely criticized Echo change, is not acceptable any longer. Fram ( talk) 12:00, 5 September 2014 (UTC)
Hello, Danny. As the product manager for Flow, you may be interested in this philosophical exchange of perspectives about the nature of the tool, in particular my reply to Erik. Diego ( talk) 09:53, 6 September 2014 (UTC)
Hi, I have heard about your new project flow which provides UI rich interface for editing discussion and talk pages. I am skilled in various web based programming laguages such as javascript, PHP etc. I was just wondering if you needed any help with the development of flow, as I am eager to help.
Thank you in advance
NetworkOP ( talk) 19:51, 27 December 2014 (UTC)
On my talk page, a user has requested help with errors that have occurred on the Wikipedia talk:WikiProject Breakfast talk page per using Flow. I am unable to fix the matter on the project's talk page. Please see the discussion. Thanks. NORTH AMERICA 1000 16:35, 23 February 2015 (UTC)
For God's sake please stop referring to Flow pages as "boards." Rightly or wrongly, it reinforces the perception that WMF is trying to convert talk pages into freeform discussion fora. I know you mean well, but words matter. Short Brigade Harvester Boris ( talk) 00:11, 7 April 2015 (UTC)
Hi Danny. I received the notice for the Tech support satisfaction survey on my talk, but my account is less than one year old, so I shouldn't have been on the list based on the criteria listed. I noticed you edited the message, so figured you might be the best person to ask about this. Do you happen to know what happened here? Should I respond to the survey or would you prefer I not because I'm not within the target group? ~ Rob Talk 05:53, 20 October 2015 (UTC)
Hi Danny, just checking in with you and Kaldari as to what the technical progress was on the code for ACTRIAL. Is there a phab task available to follow? The consensus at WT:NPPAFC seems to have settled on option 3 with the blacklist being a viable alternative. Kudpung had pointed out on my talk page that it had been All Quiet on the San Francisco Front, so just checking in. Hope all is well. TonyBallioni ( talk) 16:29, 17 July 2017 (UTC)
There is a question here regarding the Spanish Wiki which you may wish to answer. Kudpung กุดผึ้ง ( talk) 09:10, 5 August 2017 (UTC)
Hi Danny, it was very nice to meet you at Wikimania. I've started a follow-up discussion to what we've discussed concerning the future of Article Alerts (link above). Please comment there. Headbomb { t · c · p · b} 10:58, 16 August 2017 (UTC)
As I mentioned on the talk page, the Foundation's needs for the data have different goals from those of the volunteer community that creates and maintains en.Wiki. It would be good if the Foundation staff and/or contractors could collaborate with us in a manner that is helpfull and without telling us to finish their paid-for work for them before we can use it. Otherwise there is no need for them to post on the English Wikipedia talk pages at all, and such comments and or illustrations could be best kept at on the WMF project page where they belong. I'm not criticising anyone but IMO there should be a more clearly defined distribution of roles and where the work takes place. Kudpung กุดผึ้ง ( talk) 23:49, 28 August 2017 (UTC)
( edit conflict)::::I don't think there is a misunderstanding. We already know that there is going to be an impact on new accounts. We already know that less than 0.1% of accounts have ever edited. We already know that a significant number of accounts are deliberately created for the sole purpose of making mischief. We do not believe for a moment that ACTRIAL will increase the number of good articles - that would be simple wishful thinking and is not a serious expectation. But these are the empirical conclusions that a) the Foundation does not wish to entertain, probably because it has no practical experience in these areas, and b) are difficult to explain anyway with pure math. That said, ACTRIAL is designed as a measure to protect Wikipedia's content, integrity, and reputation (which is rapidly deterorating) for quality. 'Quality' per se however, is no within the mandate of New Page Review, and at the end of the day, that's what it all about - and getting he Foundation to produce the software enhancements that are needed to do it efficiently. Kudpung กุดผึ้ง ( talk) 00:57, 29 August 2017 (UTC)
Sorry to say this Danny, but WHY are you butting in here? You should either have helped shape the RfC, or have left a single post with a link to a separate statement of the foundation and just left it at that. You know you are not going to convince Fram, and every word you utter is just another stick for him to fight with and the community will just cheer him on. I know you intend well, but when people don't want to hear you/foundation, this will only result in more trouble (don't feed the troll-effects). Please just let the community run with .. well whatever this total clusterfuck is. — TheDJ ( talk • contribs) 14:56, 13 December 2017 (UTC)
I recently pinged this account on village pump, and I was wondering where is your normal/non WMF a/c? I also didnt know you are founder of muppetwiki, neither that you have a photo of yourself. You remind me of Luke Wilson for some unknown reason. —usernamekiran (talk) 18:26, 19 December 2017 (UTC)
Can you please ping/notify the correct folks at WMF to chime in at Wikipedia:Village pump (proposals)#List of previous creators of an article.Regards:) Winged Blades Godric 11:09, 22 December 2017 (UTC)
Always a pleasure to see you take on community discussions respectfully and constructively. Thanks! effeiets anders 19:37, 2 January 2018 (UTC) |
Oh, thank you, effeiets! I appreciate it. :) -- DannyH (WMF) ( talk) 19:38, 2 January 2018 (UTC)
Is there any problems (legal, technical et al) from WMF's side to not extend storing IP data etc. at the CU logs beyond the current 90 days.You may wish to chime in at User talk:Kudpung/PE - things to do#CU time-span.Regards:) Winged Blades Godric 05:57, 14 January 2018 (UTC)
Any chance that you could have someone look into the massive list of requested improvement to the page curation tools at Wikipedia:Page_Curation/Suggested_improvements? Either that, or tell us that it is never going to happen so we can tell people that they are going to be more successful pissing into the wind. In all seriousness though, the page curation tools might be useful, but they are far from perfect and we have no way to improve them ourselves. If they had been written as a user script, this wouldn't be an issue, but clearly some very shortsighted people over in your neck of the woods decided that we couldn't be trusted with the levers and gears of our own tool set. You had one job, but apparently it is too much for y'all, so either rewrite them as a user script so that we can update and improve them ourselves, or if the tools have indeed been abandoned, please release the code to us so that we can build our own user script version that we will actually have the capacity to update as times and needs change.
If you have noticed a lack of respect in my words, you aren't mistaken, I've been helping to keep New Page Patrol running for a few months now, and I have to wonder what the hell you guys are doing all day? Why would you write a program for NPP to use and then drop it from active development? You team's job is "supporting the most active Wikimedia contributors with the features and fixes that they need" and I am here to inform you that You Are Failing. Wikipedia only keeps running because we develop our own tools to keep our efficiency up in the face of a never ending onslaught of adverts and promotional garbage. Maybe next time when developing something intended to help us, you could actually contact us and ask a few questions? Any numbskull would have said that it should have been written as a script so that it could be updated rather than being entirely backend. — Insertcleverphrasehere ( or here) 03:51, 5 February 2018 (UTC)
The Original Barnstar | ||
For bringing ACPERM live. -- Dlohcierekim ( talk) 01:59, 27 April 2018 (UTC) |
I got head bitten off for reverting an edit that removed a short description. Was I wrong to revert this edit? I don't expect you to interject yourself in the dispute with the other editor but I would like a definitive answer on whether we should or should not be adding short descriptions to every page.
Please respond over here.--- Coffeeand crumbs 08:30, 31 May 2018 (UTC)
{{ Annotated link}} is up and running. This template can be used to automatically annotate a link in a list using the associated short description, making short descriptions actually useful in Wikipedia. This can be used in outline and index lists, and in shorter lists in articles which will be automatically populated with annotations using the associated short descriptions, or any other place where disambiguation is needed. These will remain up to date when the short description is edited. · · · Peter (Southwood) (talk): 12:41, 13 September 2018 (UTC)
Hello DannyH (WMF), I was one of those "most active Wikimedia contributors" that you are supporting "with the features and fixes that they need". I have lost faith the WMF's ability and willingness to support NPP. I have relinquished my new page reviewer right. My decision to quit NPP is a direct consequence of your contributions at meta:Community Wishlist Survey 2019/Miscellaneous/Page Curation and New Pages Feed improvements. I thought you should know that. With regret, Vexations ( talk) 21:37, 3 November 2018 (UTC)
When the WMF treats us like we don’t matter you can expect more people walking away from the job,, it's happening already - just look at the rising graph pf the backlog, what will you do when no one is left to patrol new pages? Until then, the volunteer workforce will continue to lay down their tools. Kudpung กุดผึ้ง ( talk) 00:28, 4 November 2018 (UTC)
Apparently my efforts to manage expectations have caused this group a lot of worry and distress. I'll try to be more clear, because this really is a very positive message, and my intention is for you to feel excited, not stressed out.
I'm talking about "managing expectations" because there have been problems in the past with the Community Tech team allowing huge "improve X system" proposals into the voting phase, doing a lot of work on the wish, and having people still unhappy because we aren't putting an entire team on that wish for an indefinite period of time. The best example is the Maps wish from last year's survey.
The Maps wish was voted #1 on the survey, and we worked on a Map improvements project that took about five months for the Collaboration team (now the Growth team). We delivered significant progress that made it possible for Wikipedia editors to add tens of thousands of maps to wiki articles, in every language.
However, the folks who care about maps are still expecting us to create a full-time Maps team for the next two years, and that's the proposal that they posted this year. As you can see in the discussion on that page, I'm currently having the same kind of "managing expectations" conversation that I'm having with you. We're happy to do more work on maps tools, but we can't promise to work on a huge list of tickets that we haven't evaluated and estimated yet. For that proposal, I've asked them to take out the line about having a team work for 1-2 years on the project, and to scale down their list of requests to the things that they really need this year.
That's what we do for every proposal in the Community Wishlist Survey -- make sure that the proposals are feasible and appropriately scaled before they go to the voting phase. There's an archive of proposals that have been rejected for various reasons: the proposal asks for a social or policy change rather than a technical one, it would open up security or legal risks, or it requires more work than the team can provide in a year. It's important for us that we don't allow people to vote on wishes that we know we can't work on.
Now, to be extra clear -- the NPP proposal is in no danger of being rejected and archived. That's why I posted earlier this week, to reassure you that the current proposal is fine, and it's definitely going to be included in the voting phase. I'm pointing out the archive right now just to give you more context about how the process works.
The voting phase ends at the end of November, and in December/January, the team will investigate all of the tickets involved in the top 10 wishes, and estimate how long they'll take. At this stage, it's possible that the team discovers that the wish as written involves more work than the team can provide in a year. Sometimes a wish needs to be scaled back, or an alternate solution can be found. This is a normal part of the process that applies to every wish. We don't do that estimation in advance because there are probably going to be 300+ wishes posted in two weeks; all we can give them right now is a quick look to see if a wish is obviously going to be unfeasible.
So -- with 17 (now 18) tickets listed in your proposal, it is possible that we'll discover during that estimation process that a small number of them are unfeasible for the team. I know that you all have been thinking and working on these tickets for a long time, and you have a good idea of how much work it might be, but we haven't done that yet, and the team may find a couple of problems that you don't know about. If that's the case, then the team will talk to the NPP group, explain any problems that have come up, and talk to you about possible alternative solutions. That is the only thing that I'm saying in this "managing expectations" message -- that the exact list of 18 tickets as written may have a surprise or two, and you should be aware of that possibility.
If your proposal is voted into the top 10, it is a guarantee that Page Curation will get a significant amount of work from the Community Tech team. I expect that the great majority of tickets listed will get done. This is good news for your group. You're doing the correct thing that will lead you to getting what you want.
I understand that there's a long history of the Foundation not providing you with the support that you needed to do your work, and that you don't trust the people who work at the Foundation to follow through on promises. I don't expect you to suddenly regain trust for me or the Foundation; that's not how trust works. All I can do right now is to act in a trustworthy way. I believe that's what I'm doing in this conversation.
Now, it's true that if your proposal doesn't get the required number of votes to get into the top 10, then the Community Tech team won't work on Page Curation, and you'll have to try again next year. The same is true for every other person participating in the Wishlist Survey. I know that you feel that NPP is more important than Maps and event organizer tools and all of the other projects that the Community Tech team is working on. The most effective way for you to get that message across is to get people to vote for your proposal. I'm happy to keep talking with you about this, but I think your time would be better spent in encouraging editors to vote. -- DannyH (WMF) ( talk) 20:06, 4 November 2018 (UTC)
Could you elucidate, why exactly why you have declined my proposal at the meta: Community Wishlist 2019 ? How does making cosmetic changes to MiniveraNeue have anything to do with my proposal which asks for the ability to change skins on the Mobile Frontend ? Timeless/Monobook mobile, supports the Twinkle gadget, something which is absent from MiniveraNeue even in desktop mode, as is the extremely useful RefToolbar — f r + 11:09, 17 November 2018 (UTC)
in a case, when en-wiki editors can't agree on the optimum short-description which ought be used over an article (and atleast, some of the parties vehemently dislike the WD one)? In most of the general cases of content, the particular prose will be left out of the article unless a t/p discussion leads to consensus for any version pending which it's inserted. In other words, how to force the system to display nothing? ∯WBG converse 18:26, 23 March 2019 (UTC)
Welcome to the nineteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
18:36, 26 October 2021 (UTC)
Welcome to the twentieth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
As of February, 300,000 suggested edits have been completed since the feature was first deployed in December 2019.
Add a link is the team's first structured task, deployed in May 2021. It has improved outcomes for newcomers. The team is now working on a second iteration based on community feedback and data analysis. Improvements will include: improved algorithmic suggestions, guardrails to prevent too many similar links to be added, and clearer encouragement for users to continue making edits. After adding these improvements, we will deploy this task to more Wikipedias.
Add an image is the second structured task built by our team. It was deployed in November 2021 to four pilot Wikipedias. This is a more challenging task for newcomers. However, it adds more value to articles (so far, over 1,000 images have been added). We are currently learning from communities and from the data on what is working well and what needs improvements. The project page contains links to interactive prototypes. We are very interested to hear your thoughts on this idea as we build and test the early versions. We will soon deploy this task to more Wikipedias as a test.
"Add a link" and "Add an image" now both have a limitation on how many of these tasks newcomers can do per day. It is meant to discourage careless newcomers from making too many problematic edits.
Over the last two years, the Growth team has focused on building suggested edits: easy tasks for newcomers to start with. We have learned with this experience that these tasks help many newcomers to make their first edits. Now, the team is starting a new project : " positive reinforcement". Its goal is to make newcomers proud of their editing and to make them want to come back for more of them. With the positive reinforcement project, we are considering three kinds of features:
This project is just beginning, and we hope for community thoughts on the direction. We know that things can wrong if we offer the wrong incentives to newcomers, so we want to be careful. Please visit the talk page to help guide the project!
Some wikis have created userboxes that mentors can display on the user pages. If your wiki has one, please link it to Wikidata!
Previously, at most Wikipedias, only 80% of newcomers were getting the Growth features. This was done for experimentation, to have a control group. We have changed this setting. Now 100% of new accounts at all Wikipedias get the Growth features ( except a few, kept as test wikis). We invite communities to update their onboarding documentation and tutorials. Please include the Growth features in it. To help you, we have created an help page that can be translated and adapted to your wiki.
Do you have questions about the Growth features? This translatable FAQ contains answers to the most common questions about the Growth team work. We regularly update it.
Interface translations are important for newcomers. Please help for your language, by translating or copyediting interface translations for the Growth features.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:12, 16 March 2022 (UTC)
Welcome to the twenty-first newsletter from the Growth team!
Communities can configure how the features work, using Special:EditGrowthConfig.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
13:03, 5 July 2022 (UTC)
Welcome to the twenty-second newsletter from the Growth team!
As of the last week of June 2022, the newcomers of the world have completed over 500,000 newcomer tasks. In other words, newcomers have made over half a million Wikipedia edits via Growth’s “Suggested Edits” module.
We have added some new data to Grafana. You can now check the number of edits and reverts by task types, or the number of questions asked to mentors. You can filter the data by wiki.
If you have any questions, or there is more data you want access to, please let us know.
We are continuing our work on our new project, Positive Reinforcement. User testing of initial Positive Reinforcement designs was just completed. Interviews were conducted in Arabic, English, and Spanish. The outcome has been published on the Positive Reinforcement page. We are now utilizing user testing feedback along with prior community feedback to iterate and improve designs.
We are exploring the idea of a Copy Edit structured task. We have tested copy edits in Wikipedia articles for arwiki, bnwiki, cswiki, eswiki (Growth pilot-wikis) and enwiki with two different methods: LanguageTool and Hunspell. We will share more details here and on the associated Copy Edit page once the evaluation is complete.
Add an image was utilized at GLAM events in Argentina, Mexico, and Chile. For an overview of what was learned from these events, read: #1Pic1Article I: how Latin American heritage experts added images to Wikipedia (in English).
Add a Link Experiment Analysis has been published. The most important points are:
Newcomer task edit type analysis has been published.
A new system for the mentors list
The configuration of the mentors list will change over the next weeks. In the future, mentors will sign up, edit their mentor description and quit using Special:MentorDashboard. This new system will make the development of new features for mentors much easier.
At the moment, the mentor list is a simple page anyone can edit, unless it’s protected. With the new page, mentors will be able to edit only their own description, while administrators will be able to edit the entire mentors' list if needed.
The deployment will happen first at the pilot wikis, then at all wikis. Existing lists of mentors will be automatically converted, no action will be needed from the mentors. [13] [14]
Mentors will be informed about the next steps soon, by a message posted on the talk page of existing Mentor lists.
Learn more about this new structured page on mediawiki.org.
A tip for mentors
Did you know that mentors can filter their mentees' changes at Special:MentorDashboard (and star the ones that require attention)? This feature helps to keep an eye on newcomers' edits, helping mentors to fix minor details, and encourage them if necessary.
And did you know that mentors have special filters to highlight their mentees' edits at Special:RecentChanges? Look for the following filters in RecentChanges: Your starred mentees, Your unstarred mentees.
Other improvements
Some improvements will be made to the mentor dashboard in the coming weeks:
Please let us know! You can also read our FAQ page.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:18, 21 September 2022 (UTC)
Welcome to the twenty-third newsletter from the Growth team!
The goal of the Growth team is to encourage newcomers to try editing for the first time, and encourage them to keep editing. We want to increase newcomers' motivation by showing them how impactful their edits are.
Newcomers have access to an impact module; you can find yours at Special:Impact. The revised impact module provides new editors with more context about their impact. It will display the number of edits, the number of thanks received, the last time they edited, the number of consecutive days they edited, and the number of views for the articles they edited.
This module will soon be available at our pilot wikis starting December 1. You can already test this new module at Beta Wikipedia. For safety reasons, do not use your regular account and password at Beta wiki. Create a new, specific account for this wiki, with a different password.
After the deployment of Structured tasks, we received feedback from various communities regarding how patrollers of recent changes were feeling overwhelmed by an increase in edits to check, and how some edits were poor quality or of poor relevance.
We made several improvements based on the feedback we received. Several points of improvement have already been addressed:
The Positive Reinforcement project will also address some of the concerns around encouraging newcomers to progress to higher value edits. The Growth team will soon work on strategies geared at " Leveling up" newcomers so they progress from easy to more difficult tasks.
Special:MentorDashboard
.Special:ManageMentors
— now displays the list of mentors. This page can be transcluded on any other page. There are also new processes to
signup as a mentor or to
quit mentorship, and we improved
community mentorship management.We plan to have a more regular newsletter, every two months. We also want to know if the current format suits you! Let us know what you like, what you like less and your suggestions of improvements: leave us a comment, in your preferred language.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
20:57, 29 November 2022 (UTC)
Welcome to the twenty-fourth newsletter from the Growth team!
The Growth team partnered with other WMF teams to conduct several experiments around increasing account creation and new editor retention. Results from four of these experiments are now available:
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.• Help with translations
14:44, 31 January 2023 (UTC)