Community Wunschliste/Wie schreibt man einen guten Vorschlag?

This page is a translated version of the page Community Wishlist Survey/How to create a good proposal and the translation is 22% complete.
Outdated translations are marked like this.

Community Wishlist Survey banner FAQ.svg

Was ist ein guter Vorschlag? Diese Anleitung soll sicher stellen, dass die Vorschläge eine gute Chance haben verwirklicht zu werden.

Innerhalb des Community Tech Bereiches

Bei dem Vorschlag sollte es sich um ein technisches Bedürfnis der Wikimedia Editoren (Autoren) handeln. Der Vorschlag sollte Softwareentwicklung benötigen und keine Änderung der Regeln und Richtlinien oder der Umgangsformen.

Antu mail-mark-junk.svg Das Community Tech Team lehnt ab,
wenn die
Antu mail-mark-notjunk.svg Vorschläge, die Softwareentwicklung benötigen, sind
  • Die nur Edits auf Wikis benötigen, sogar wenn es technische Edits sind (in Templates, Modulen, etc.)
  • Sie sind schon bei der Wikimedia Foundation zur Umsetzung geplant
  • Wurden von Community Tech abgelehnt oder von anderen Wikimedia Foundation Teams
  • Anfrage ein Feature, was die Wikimedia Foundation hinzugefügt hat, zu entfernen oder zu deaktivieren
  • Tools für Wikimedia Projekte
  • Identifizieren und Verbessern bestehender Funktionen bestehender Tools
  • Erstellen besserer Dokumentation für diese Tools, sodass sie besser genutzt werden können
  • Erstellen von Gadgets, Bots, und Wizards um Nutzern beim dem zu helfen, was Sie schon tun
  • Erstellen von Tools für WikiProjects
  • Modifizierung bestehender Gadgets und Bots, sodass sie an mehr Projekten arbeiten können
  • Konvertierung von stark genutztem Code, der von der Community geschrieben wurde (Gadgets und User-Skripte), in einen Teil der MediaWiki-Software

Weniger als ein Jahr langes Projekt, mehr als ein Fehler

The Community Wishlist Survey is limited to the capabilities of the Community Tech team.

The team is grateful for "big ideas" for the Foundation and doesn't ignore them. However, some proposals require a dedicated team other than Community Tech.

These proposals will be moved to a separate page and will not be voted upon. Later, the link to that page will be shared with other Wikimedia Foundation teams.

Beispiele:

Antu mail-mark-junk.svg Wiktionary app (too large)
Antu mail-mark-junk.svg Wikivoyage app (too large)
Antu mail-mark-junk.svg Centralization of templates (too large)
Antu mail-mark-notjunk.svg Watchlist item expiration (large-ish)
Antu mail-mark-notjunk.svg Ping users from the edit summary (ideal size)
Antu mail-mark-notjunk.svg Copy and paste from diffs (small-ish but not too small)

Pick one specific problem and describe it in detail

Provide context around why the problem is important for users. A good proposal explains exactly:

  • What the problem is,
  • Who's affected by it.
  • Add screenshots, links, and talk pages detailing the discussion about the problem space, if possible.

This will help Community Tech to understand where to begin their work.

Don't just say that "(x feature) is out of date", "needs to be improved" or "has a lot of bugs". That's not enough information to figure out what needs to be done.

Proposals may be submitted in any language. Community Tech encourages the volunteers to translate them so everyone can read and vote on it more easily. Read more on Review phase.

Beispiele:

Antu mail-mark-junk.svg Add Better Bots (not precise enough and reading between the lines, too large)
Antu mail-mark-junk.svg Make wiki easier for most people (not one problem, but a principle for a lot of changes)
Antu mail-mark-junk.svg Implement Artificial intelligence (not one problem, but a principle for a lot of changes)
Antu mail-mark-notjunk.svg Better diff handling of paragraph splits
Antu mail-mark-notjunk.svg Show all active sessions
Antu mail-mark-notjunk.svg Use Wikidata to improve search

Don't worry about finding the solution

You don't have to suggest ways for resolving the problem. It will be the Community Tech task to find solutions.

Prescribing the solution can sometimes be a constraint. For example, voters could mistakenly support a solution that later in the year could turn out to be impossible to build, and Community Tech would solve the problem differently.

Beispiele:

Antu mail-mark-junk.svg Tags (ala evernote, searchable, catagorizing) (no information on the problem)
Antu mail-mark-junk.svg Bulk upload program (no information on the problem)

Talk to other community members

You may want to bring attention to your idea, and be part of a conversation about the idea happening elsewhere. Gather feedback and share the proposal. You can do this early on, before the voting phase. This way, contributors can know about the problem and remember to participate and vote for it when the time comes.

Also, see our promotional materials. You may use them.

Avoid proposals that were declined in the past

Here's a list of some of the projects that got many votes. Community Tech was committed to work on them but had to decline them. It is unlikely, if not impossible, that the team could work on them this year.

Survey edition Rank in the results Projects Explanation
2019 #2 Dark mode Overlaps with another team's project. The overlapping project is Desktop Improvements. Mehr erfahren.
2019 #6 Put mw.toolbar back The issue had largely been resolved without any Community Tech intervention. Also, it is the Community Tech policy not to undo changes made by other teams. Mehr erfahren.
2019 #8 Article reminders This is too technically complex. Also, it would have to be done by another Wikimedia Foundation team. There are other ways to see the same result. Mehr erfahren.
2019 #10 2FA available for all concerned editors This is too technically complex. Also, it would have to be done by another Wikimedia Foundation team. Mehr erfahren.
2017 #6 Article Alerts for more languages This is too technically complex. Also, the Community Tech is not able to build and maintain such a tool. Mehr erfahren.
2016 #1 Global gadgets This is too technically complex. Also, the Community Tech is not able to build and maintain such a tool.
2015 #3 Central repository for gadgets, templates and Lua modules
2015 #6 Allow categories in Commons in all languages Overlaps with another team's projects. The overlapping projects are Structured Data on Commons and Structured Data Across Wikimedia.
2015 #4 Cross-wiki watchlist This is too technically complex. Mehr erfahren.
2015 #8 Global cross-wiki talk page Overlaps with other teams' projects. The overlapping projects are Flow/Structured Discussions and Cross-wiki notifications. Mehr erfahren.
2015 #10 Add a user watchlist Used in bad faith, this tool could make it easier to harass users. Mehr erfahren.