Thank you Danny & Company! Pine
On Wed, Dec 16, 2015 at 12:22 PM, Toby Negrin <tneg...@wikimedia.org> wrote: > No one asked for 10 more wishes? :) > > Thanks Danny and the Community Tech team. This is a great model for working > with our Communities. > > -Toby > > On Wed, Dec 16, 2015 at 12:18 PM, Nirzar Pangarkar < > npangar...@wikimedia.org > > wrote: > > > It's really cool to see community wish list coming together! > > > > > We're going to talk with the other Wikimedia product teams, to see if > > they can take on some of the ideas the the community has expressed > interest > > in. > > > > +1 > > > > On Thu, Dec 17, 2015 at 1:42 AM, Danny Horn <dh...@wikimedia.org> wrote: > > > >> Hi everyone, > >> > >> I'm happy to announce that the Community Tech team's Community Wishlist > >> Survey has concluded, and we're able to announce the top 10 wishes! > >> > >> 634 people participated in the survey, where they proposed, discussed > and > >> voted on 107 ideas. There was a two-week period in November to submit > and > >> endorse proposals, followed by two weeks of voting. The top 10 proposals > >> with the most support votes now become the Community Tech team's > backlog of > >> projects to evaluate and address. > >> > >> And here's the top 10: > >> > >> #1. Migrate dead links to the Wayback Machine (111 support votes) > >> #2. Improved diff compare screen (104) > >> #3. Central global repository for templates, gadgets and Lua modules > (87) > >> #4. Cross-wiki watchlist (84) > >> #4. Numerical sorting in categories (84) > >> #6. Allow categories in Commons in all languages (78) > >> #7. Pageview Stats tool (70) > >> #8. Global cross-wiki user talk page (66) > >> #9. Improve the "copy and paste detection" bot (63) > >> #10. Add a user watchlist (62) > >> > >> You can see the whole list here, with links to all the proposals and > >> Phabricator tickets: > >> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results > >> > >> So what happens now? > >> > >> Over the next couple weeks, Community Tech will do a preliminary > >> assessment on the top 10, and start figuring out what's involved. We > need > >> to have a clear definition of the problem and proposed solution, and > begin > >> to understand the technical, design and community challenges for each > one. > >> > >> Some wishes in the top 10 seem relatively straightforward, and we'll be > >> able to dig in and start working on them in the new year. Some wishes > are > >> going to need a lot of investigation and discussion with other > developers, > >> product teams, designers and community members. There may be some that > are > >> just too big or too hard to do at all. > >> > >> Our analysis will look at the following factors: > >> > >> * SUPPORT: Overall support for the proposal, including the discussions > on > >> the survey page. This will take the neutral and oppose votes into > account. > >> Some of these ideas also have a rich history of discussions on-wiki and > in > >> bug tickets. For some wishes, we'll need more community discussion to > help > >> define the problem and agree on proposed solutions. > >> > >> * FEASIBILITY: How much work is involved, including existing blockers > and > >> dependencies. > >> > >> * IMPACT: Evaluating how many projects and contributors will benefit, > >> whether it's a long-lasting solution or a temporary fix, and the > >> improvement in contributors' overall productivity and happiness. > >> > >> * RISK: Potential drawbacks, conflicts with other developers' work, and > >> negative effects on any group of contributors. > >> > >> Our plan for 2016 is to complete as many of the top 10 wishes as we can. > >> For the wishes in the top 10 that we can't complete, we're responsible > for > >> investigating them fully and reporting back on the analysis. > >> > >> So there's going to be a series of checkpoints through the year, where > >> we'll present the current status of the top 10 wishes. The first will > be at > >> the Wikimedia Developer Summit in the first week of January. We're > planning > >> to talk about the preliminary assessment there, and then share it more > >> widely. > >> > >> If you're eager to follow the whole process as we go along, we'll be > >> documenting and keeping notes in two places: > >> > >> On Meta: 2015 Community Wishlist Survey/Top 10: > >> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Top_10 > >> > >> On Phabricator: Community Wishlist Survey board: > >> https://phabricator.wikimedia.org/tag/community-wishlist-survey/ > >> > >> Finally: What about the other 97 proposals? > >> > >> There were a lot of good and important proposals that didn't happen to > >> get quite as many support votes, and I'm sure everybody has at least one > >> that they were rooting for. Again, the whole list is here: > >> > >> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results > >> > >> We're going to talk with the other Wikimedia product teams, to see if > >> they can take on some of the ideas the the community has expressed > interest > >> in. We're also going to work with the Developer Relations team to see if > >> some of these could be taken on by volunteer developers. > >> > >> It's also possible that Community Tech could take on a small-scale, > >> well-defined proposal below the top 10, if it doesn't interfere with our > >> commitments to the top 10 wishes. > >> > >> So there's lots of work to be done, and hooray, we have a whole year to > >> do it. If this process turns out to be a success, then we plan to do > >> another survey at the end of 2016, to give more people a chance to > >> participate, and bring more great ideas. > >> > >> For everybody who proposed, endorsed, discussed, debated and voted in > the > >> survey, as well as everyone who said nice things to us recently: thank > you > >> very much for coming out and supporting live feature development. We're > >> excited about the work ahead of us. > >> > >> We'd also like to thank Wikimedia Deutschland's Technischer > >> Communitybedarf team -- they came up with this whole survey process, and > >> they've been working successfully on lots of community wishes since > their > >> first survey in 2013. > >> > >> You can watch this page for further Community Tech announcements: > >> https://meta.wikimedia.org/wiki/Community_Tech/News > >> > >> Thanks! > >> > >> Danny Horn > >> Product Manager, WMF Community Tech > >> > >> _______________________________________________ > >> Wmfall mailing list > >> wmf...@lists.wikimedia.org > >> https://lists.wikimedia.org/mailman/listinfo/wmfall > >> > >> > > > > _______________________________________________ > > Wmfall mailing list > > wmf...@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wmfall > > > > > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines > wikimedi...@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
