Re: Nearby for all...
Hi, there is certainly a use for being proactive now rather than later.
- Quite often, it's just about contacting the local sysop (ideally in their language) and explaining things more carefully. If you could do this even on a handful wikis, your contribution would be substantial.
- Another useful thing to do is looking into the mechanics of local templates: on it.wiki for instance our indefatigable admin Bultro, after the initial introduction of the feature, had to fix several templates which were passing incorrect coordinates, and so on; many wikis do not have sufficient knowledge for this.
As for Wikidata, those APIs used by the mobile systems don't quite seem likely to jump on Wikidata very quickly. --Nemo 15:43, 24 August 2015 (UTC)
- Nemo, i will put some effort to reach that local sysops. Lets see how i proceed. Another idea i had, was to implement a fallback into Extension:GeoData so that it fetches that coordinates from Wikidata instead from database. This is transparent to the API users such as the mobile app but of course not consistent. --Aschroet (talk) 10:12, 25 August 2015 (UTC)
- Yes, I file such requests from time to time. --Nemo 11:58, 25 August 2015 (UTC)
Hi! You voted for improving plagiarism detection as an important suggestions in the community wishlist survey last year. I'm pinging people who showed interest in that task to tell them we have some suggestions for how things could look, if you'd like to glance at them and give us some feedback. They're available here: phab:T120435#2266283. It's easiest if comments are left in Phabricator, since that's where much of the development is happening, but they can be left on Meta too, of course. /Johan (WMF) (talk) 17:15, 13 May 2016 (UTC)
2016 Community Wishlist Survey
You’re getting this message because you participated in the 2015 Community Wishlist Survey and we want to make sure you don't miss it this year – or at least can make the conscious choice to ignore if it you want to. The 2015 survey decided what the Community Tech team should work on during 2016. It was also the focus of Wikimedia hackathons and work by other developers. You can see the status of wishes from the 2015 wishlist at 2015 Community Wishlist Survey/Results.
The 2016 Community Wishlist Survey is now open for wishes. You can create proposals until November 20. You will be able to vote on which wishes you think are best or most important between November 28 and December 12. /Johan (WMF) (talk) via MediaWiki message delivery (talk) 11:17, 14 November 2016 (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!
18:25, 20 November 2020 (UTC)
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.
We are waiting for your votes. Thank you!
16:09, 11 December 2020 (UTC)