Közösségi kívánságlista 2019
Összesen: 212 javaslat, 1387 közreműködő, 7282 támogató szavazat
A kívánságlista összes szakasza magyar (téli) idő szerint este 7-kor (18:00 UTC) kezdődik és végződik.
- Javaslatok készítése, megbeszélése és átdolgozása: 2018. október 29. – november 11.
- A Community Tech átnézi és rendezi a javaslatokat: 2018. november 13–15.
- Szavazás a javaslatokról: 2018. november 16–30.
- Eredmények közzététele: 2018. december 3.
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.
Ez a negyedik éves közösségi kívánságlistánk. Így állunk a tavalyi kérésekkel.
Minden kívánságlista év végén van, és a kívánságokon a következő évben, néha még a rákövetkező évben is dolgozunk. Összezavarhatja az embereket, amikor azt hallják, hogy a 2016-os vagy 2017-es kívánságlista kívánságain dolgozunk, mikor már bőven benne járunk a 2018-ban. Hogy megszüntessük a kavarodást, és jobban érezzük magunkat azáltal, hogy idei feladatokon dolgozunk, úgy döntöttünk, hogy átnevezzük a kívánságlistát, így mostantól az az év szerepel a címében, amelyikben a kívánságok megvalósítását tervezzük, nem az, amikor a felmérést tartjuk.
The proposal phase is the first two weeks of the survey.
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. A javaslatoknak meg kell válaszolniuk a következő kérdéseket:
- Milyen problémát szeretnél megoldani?
- Which users are affected? (editors, admins, Commons users, Wikipedia users, etc.)
- How is this problem being addressed now?
- Mik a javasolt megoldások? (ha van bármi ötleted)
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.
A javaslati szakasz után tartunk egy kis szünetet, amíg átnézzük a javaslatokat a szavazási szakasz előtt.
Az összes aktív szerkesztő átnézheti a javaslatokat, és szavazhat azokra, amiket támogatni szeretne. Annyi javaslatra szavazhatsz, amennyire csak akarsz. A tisztességes szavazás érdekében csak regisztrált szerkesztők szavazhatnak, és a nagyon új fiókokból leadott szavazatokat eltávolíthatjuk.
Csak a támogató szavazatok számítanak. A kívánságok végleges listája a támogató szavazatok szerint lesz csökkenően rendezve. Ha te javasoltad az ötletet, egy támogató szavazatot automatikusan beszámítunk.
Azonban biztatunk az élénk megbeszélésre a szavazási szakasz alatt. Ha szeretnél ellenző vagy semleges szavazatot leadni indoklással, nyugodtan tedd meg. Ezek a megbeszélések segíthetnek másoknak eldönteni, hogy szavazzanak-e egy javaslatra. Értékes véleményt is jelentenek az év során végzendő munka során.
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.
Our team has a commitment to work on projects that help out smaller groups, including campaign and program organizers, GLAM participants, smaller projects like Wikisource and Wiktionary, and stewards and CheckUsers.
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!
The Community Tech team may decline proposals which do not meet the following criteria:
- The proposal should be about a technical change and not for a policy or social change
- The proposal should be about the problem and not necessarily ask for a specific solution
- The proposal should be a well-defined problem and not a mix and match of different unrelated issues
- The amount of work in the proposal is appropriate for the Community Tech team to work on along with the other wishes in the top 10
- The proposal is not already in another team's roadmap or has not been declined by other teams in the past
- The proposal has not been declined by Community Tech in the past
- The proposal should be within the team's scope
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.
... instead of addressing every item below the top 10 from last year's survey?
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.