Umfrage zur Community-Wunschliste 2015
Die Umfrage zur Community-Wunschliste 2015 ist vorbei, und jetzt beginnt die Arbeit des Gemeinschaftstechnologie-Teams an den Top 10 Funktionen und Fehlerbehebungen.
In November and December 2015, we invited contributors from all Wikimedia projects to submit proposals for what they would like the Community Tech team to work on for the purpose of improving or producing curation and moderation tools for active contributors.
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.
Die Top 10 Wünsche
- Migrate dead external links to archives (111 support votes) -- notes
- Improved diff compare screen (104) -- notes
- Central global repository for templates, gadgets and Lua modules (87) -- notes
- Cross-wiki watchlist (84) -- notes
- Numerical sorting in categories (84) -- notes
- Allow categories in Commons in all languages (78) -- notes
- Pageview Stats tool (70) -- notes
- Global cross-wiki user talk page (66) -- notes
- Improve the plagiarism detection bot (63) -- notes
- Add a user watchlist (62) -- notes
Die vollständige Liste mit Links zu allen Vorschlägen und den Phabricator Anfragen befindet sich auf dieser Seite: Community Wishlist Survey 2015/Results.
Was passiert nun?
The next step is for the team to 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. We'll be talking about the preliminary assessment at the Wikimedia Developer Summit 2016 in the first week of January, and then publish a progress report after the summit.
Manche der Wünsche in der Top 10 scheinen relativ einfach umsetzbar und wir werden im neuen Jahr anfangen an ihnen zu Arbeiten. Andere Wünsche benötigen weitere Untersuchungen und Diskussionen mit anderen Entwicklern, Produkt Teams, Designern und Community Mitgliedern. Es sind vielleicht auch einige dabei, wo der Aufwand zu groß oder unmöglich zu bewältigen ist.
Unsere Analyse untersucht die folgenden Faktoren:
- 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.
- Risiken: Potentielle Nachteile, Konflikte mit der Arbeit anderer Entwickler und negative Effekte auf alle Gruppen von Beiträgern.
Für 2016 ist unser Plan so viele der Top 10 Wünsche zu erfüllen wie möglich. Für die Wünsche der Top 10, die wir nicht fertigstellen können, sind wir für die vollständige Untersuchung dieser und deren Rücksendung zur Analyse verantwortlich.
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.
Für eifrige Verfolger des ganzen Prozesses, den wir entlanggehen werden wir unsere Arbeit in folgenden zwei Plätzen dokumentieren und Notizen machen:
- Auf Meta: 2015 Community Wishlist Survey/Top 10
- In Phabricator: Community-Wunschliste 2015
Was ist mit den anderen 97 Vorschlägen?
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: Community Wishlist Survey 2015/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 Community Tech/News for further Community Tech announcements!
Archive
Du kannst alle Vorschläge für Umfragen und Diskussionen auf den folgenden Seiten sehen:
- Bots and gadgets (4 proposals)
- Categories (7 proposals)
- Commons (6 proposals)
- Editing (15 proposals)
- Miscellaneous (17 proposals)
- Moderation and admin tools (13 proposals)
- Multimedia (5 proposals)
- Notifications (4 proposals)
- Reading (4 proposals)
- Search (5 proposals)
- Special pages (2 proposals)
- Talk pages (3 proposals)
- Templates (3 proposals)
- Watchlists (7 proposals)
- Wikidata (7 proposals)
- Wikisource (6 proposals)
- Wikiversity (1 proposal)
Geschlossene Vorschläge
Closed proposals have been moved to the Community Wishlist Survey 2015/Archive page.