Brugerundersøgelse om fællesskabets ønskeliste 2019
Samlet: 212 forslag, 1387 bidragsydere, 7282 stemmer for
Alle faser af brugerundersøgelsen starter og slutter kl. 18:00 UTC.
- Indsend, diskuter og revidere forslag: 29. oktober til 11. november, 2018
- Community tech gennemgår og organiserer forslag: 13. november til 15. november, 2018
- Afstemning på forslag: 16. november til 30. november, 2018
- Resultater lagt op: 3. december, 2018
The Community Tech team is a Wikimedia Foundation team focused on the needs of active Wikimedia contributors for improved curation and moderation tools. The projects that we primarily work on are decided by the Wikimedia community, through the annual Community Wishlist Survey.
Once a year active Wikimedia contributors can submit proposals for features and fixes that you'd like our team to work on. After two weeks, you can vote on the ideas that you're most interested in. The top 10 wishes will be investigated and addressed by the Community Tech team. Some of the other top wishes may be addressed by other development teams.
This survey process was developed by Wikimedia Deutschland's Technical Wishes team, who run a wishlist survey on German Wikipedia. The international wishlist process is supported by the Technical Collaboration team.
Dette er fjerde udgave af den årlige brugerundersøgelse om fællesskabets ønskeliste. Se [[Special:MyLanguage/Community Wishlist Survey 2017/Results|]].
Every year we hold the survey at the end of the year but we work on the wishes during the next year and sometimes these wishes may even trail into the year after. It can be a cause of confusion to people when they hear we are working on wishes from the 2016 or 2017 Wishlist Survey when we are well into 2018. To eliminate this confusion and to make ourselves feel better about doing work that was meant for the current year, we decided to rename the survey to state the year during which we intend to work on the wishes instead of the year in which the survey is held.
Forslags fasen er brugerundersøgelsens første to uger.
In the proposal phase, contributors from every project and language can submit proposals for features and fixes that you'd like to see in 2019. Proposals may be submitted in any language. If you submit a proposal in a language other than English, we will attempt to get it translated so everyone can read and vote on it more easily.
Proposals should be discrete, well-defined tasks that will directly benefit active Wikimedia contributors. Forslag bør besvare følgende spørgsmål:
- Hvilket problem prøver du at løse?
- Hvilke brugere bliver påvirket? (skribenter, administratorer, COmmons brugere, Wikipedia brugere, osv.)
- How is this problem being addressed now?
- What are the proposed solutions? (if there are any ideas)
Your proposal should be as specific as possible, especially in the problem statement. 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. A good proposal explains exactly what the problem is, and who's affected by it. It's okay if you don't have a specific solution to propose, or if you have a few possible solutions and you don't know which is best.
Submitting a proposal is just the beginning of the process. The two-week proposal phase is a time that the community can collaboratively work on a proposal that presents the idea in a way that's most likely to succeed in the voting phase. When a proposal is submitted, everyone is invited to comment on that proposal, and help to make it better — asking questions, and suggesting changes. Similar proposals can be combined; very broad proposals should be split up into more specific ideas. The goal is to create the best possible proposal for the voting phase.
The person who submits a proposal should expect to be active in that discussion, and help to make changes along the way. Because of that, we're going to limit proposals to three per account. If you post more than three proposals, we'll ask you to narrow it down to three. Bring your best ideas!
Similarly, only registered users can make proposals to ensure they can watchlist the discussion and respond to questions. Just as with voting, you should be an active editor on at least one Wikimedia project. If you do not meet this criteria, or you have hit your proposal limit but have more ideas, you can seek other users to adopt your proposals.
One more note: Proposals that call for removing or disabling a feature that a WMF product team has worked on are outside of Community Tech's possible scope. They won't be in the voting phase.
Yes, you may submit some proposals that didn't get enough support votes in past years, and deserve a second try.
If you decide to copy a proposal from the old survey into the new survey, we expect you to "adopt" that proposal — meaning that you'll be actively participating in the discussion about that idea, and willing to make changes to the proposal in order to make it a stronger idea when it moves to the voting phase. As we said above, there's a limit of three proposals per person, and posting a proposal from last year counts.
It's helpful if you want to post a link to the previous discussion, but please don't copy over the votes and discussion from last year. If there are good points that people made in last year's discussions, include the suggestions or caveats in the new proposal.
Efter forslags fasen tager vi en pause for at gennemgå forslagene inden afstemnings fasen begynder.
Alle aktive bidragsydere kan gennemlæse og stemme på de forslag de ønsker at støtte. Du kan stemme på så mange forskellige forslag du ønsker. For at sikre en fair afstemning kan kun registrerede brugere stemme, og stemmer fra helt nye kontoer kan blive fjernet.
De eneste stemmer der tæller er For stemmerne. Den endelig liste af ønsker vil blive rangeret i rækkefølge efter de fleste for stemmer. If you are the proposer, a support vote is automatically counted for your proposal.
However, lively discussion is encouraged during the voting phase. If you want to post an Oppose or Neutral vote with a comment, then feel free to do so. These discussions can help people to make up their mind about whether they want to vote for the proposals. The discussions also provide useful input to guide the work that will happen through the year.
A reasonable amount of canvassing is acceptable. You've got an opportunity to sell your idea to as many people as you can reach. Feel free to reach out to other people in your project, WikiProject or user group. Obviously, this shouldn't involve sockpuppets, or badgering people to vote or to change their vote. But a good-faith "get out the vote" campaign is absolutely okay.
It's common that most of the proposals that end up in the top 10 are for the biggest projects — the big Wikipedias, and Commons. There are many smaller groups and projects that don't have enough "voting power" to boost their proposal into the top 10, but are doing important work for our movement.
Vores team har en forpligtekse til at arbejde på projekter der hjælper mindre grupper, dette inkluderer organisatører af kampagner og programmer, folk der deltager i GLAM, mindre projekter som Wikisource og Wiktionary, og forvaltere og tjekbrugere.
Having smaller projects' proposals in the Wishlist Survey is important — it helps our team and the Wikimedia Foundation broadly know what people in smaller groups need. So yes, please come and post your proposals, even if you don't think you'll get into the top 10!
Community tech teamet kan afvise forslag hvis de ikke opfylder følgende kriterier:
- Forslaget skal være om en teknisk ændring og ikke en politisk eller social ændring
- Forslaget skal være om problemet og ikke nødvendigvis bede om en bestemt løsning
- Forslaget skal være et veldefineret problem og ikke en blanding af forskellige urelaterede problemer
- Mængden af arbejde der skal puttes i forslaget er passende til at Community Tech teamet kan arbejde på de andre ønsker der er på listen over de 10 mest populære ønsker samtidig
- Forslaget er ikke allerede på et andet teams roadmap eller er ikke tidligere blevet afvist af andre teams
- Forslaget er ikke tidligere blevet afvist af Community Tech
- Forslaget skal være indenfor teamets arbejdsområde
The Support-vote rankings create a prioritized backlog of wishes, and the Community Tech team is responsible for evaluating and addressing the top 10 wishes. To do that, we investigate all of the top wishes, and look at both the technical and social/policy risk factors.
The Oppose and Neutral votes are very helpful in raising potential downsides. For controversial wishes, we balance the voting with a more consensus-based review. As an example, this worked in the 2015 survey: The wish to "add a user watchlist" received a lot of votes but also some heartfelt Oppose votes. We listened to all sides, and made a decision on whether to pursue the project or not.
... istedet for at rette hvert punkt under de ti mest populære fra sidste års brugerundersøgelse?
The main reason why we're making the survey an annual event is that we want to include more people! More people know about the team and the survey now, and after a year where many of the top wishes were completed, we're expecting that people will be even more interested and excited about participating. We want to give everyone a chance to bring new ideas.
If there are wishes from last year's survey that you think deserve another shot, see "Can I resubmit a proposal from previous surveys?" above.