Istraživanje o željama zajednice 2016. godine
Ukupno: 265 prijedloga, 1132 doprinositelja, 5037 glasova podrške
Zanima Vas što će se dogoditi sljedeće? Pogledajte Često postavljana pitanja o Istraživanju o željama zajednice 2016. godine.
- Predloži, diskutiraj i pregledaj prijedloge: Nov. 7–20, 2016
- Tehnički tim Zajednice pregledava i ustrojava prijedloge: Nov. 21–27
- Glasajte za prijedloge: Nov. 28–Dec. 12
- Analiza istraživanja: 13. do 14. prosinca
- Objava rezultata: 15. prosinca
- Community Tech tim provjerava i procjenjuje najtraženije želje: kraj prosinca
- Predstavljanje inicijalne procjene: rani siječanj 2017.
- Rad na željama: siječanj-prosinac 2017.!
Tehnički tim zajednice tim je Zaklade Wikimedija koji se fokusira na potrebe aktivnih suradnika Wikimedije s ciljem izdavanja poboljšanih alata za održavanje i moderaciju. Zajednica Wikimedije kroz godišnje istraživanje o željama zajednice odlučuje na kojim ćemo projektima primarno raditi.
Aktivni suradnici Wikimedije mogu jednom godišnje podnijeti prijedloge funkcija i popravaka za koje smatraju da bi se njima trebao pozabaviti naš tim. Nakon dva tjedna možete glasati za ideje koje Vas najviše zanimaju. Pet najpopularnijih želja istražit će i njima se baviti Tehnički tim zajednice. Možda će se nekim od drugih popularnih želja pozabaviti neki drugi razvojni tim.
Ovaj proces istraživanja razvio je tim Tehničkih želja Wikimedije Njemačka, koji ostvaruje istraživanje želja na wikipediji na njemačkome jeziku. Globalni projekt istraživanja želja podupire tim odnosa sa zajednicama.
Dosta njih! Ovdje se nalazi kratki popis.
- Želja #1: Premještanje mrtvih vanjskih poveznica u arhive -- Community Tech je podržavao volonterski projekt na engleskoj Wikipediji u pisanju i testiranju kôda koji pomaže InternetArchiveBotu detektiranje mrtvih poveznica.
- Želja #2: Poboljšane usporedbe razlika -- Noćna mora u pregledu razlika inačica stranica nastala je stvaranjem male izmjene u velikom odlomku koji je zatim cijeli označen, a razlika je skrivena. Razvijatelj WMF-a ažurirao je engine koji označuje razlike; sada pokazuje što je zapravo izmijenjeno.
- Wish #5: Numerical sorting in categories—Community Tech implemented support for numerical sorting and has deployed the feature to 18 different wikis so far; we're currently offering the feature to any wikis that want to try it.
- Wish #7: Pageview stats tool—Community Tech built the Pageviews Analysis tool, which is now in use on all Wikipedias.
- Wish #9: Improve the plagiarism detection bot—Community Tech built CopyPatrol, a new interface for the plagiarism detection workflow that's attracted more patrollers, and eliminated the backlog of cases.
Community Tech is currently working on wish #4, Cross-wiki watchlist, and there are more wishes that have been addressed by volunteers and other teams.
Neke od top 10 želja nisu bile izvedive zbog različitih razloga; sve želje možete vidjeti na stranici rezultata istraživanja, zajedno s poveznicama na stranice projekata i diskusija.
Razdoblje predlaganja traje prva dva tjedna istraživanja.
Tokom razdoblja predlaganja, doprinositelji iz svakog od projekata i jezičnih izdanja mogu podnositi prijedloge za ostvarenja i popravke koje bi željeli vidjeti u 2016 godini. Prijedlozi mogu biti podneseni na bilo kom jeziku. Ako podnesete prijedlog u nekom drugom jeziku (osim engleskoga), pokušat ćemo priskrbiti prijevod kako bi se svi mogli upoznati s prijedlogom na što jednostavniji način, kao i glasati o njemu.
Prijedlozi bi trebali biti diskretni i dobro definirani zadatci koji će izravno koristiti aktivnim Wikimedijinim suradnicima. Prijedlozi bi trebali odgovoriti na sljedeća pitanja:
- Koji problem želite riješiti?
- Koji su korisnici zahvaćeni ovim problemom? (suradnici, administratori, uređivači Wikizvora, i sl.)
- Kako je ovaj problem trenutno riješen?
- Koja su predložena rješenja? (ako postoje)
Vaš prijedlog trebao bi biti što je više moguće podrobniji, a posebno u definiciji problema. Nemojte napisati samo da "(mogućnost X) nije ažurna", "potrebno je poboljšanje" ili "postoji mnogo programskih grešaka". To nije dovoljno podataka za razaznati što je potrebno učiniti. Dobar prijedlog objašnjava točno što je problem, te tko je pogođen njime. U redu je ako nemate za predložiti neko posebno rješenje, ili ako imate nekoliko mogućih rješenja ali ne znate koje bi bilo najbolje.
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.
Da, definitivno postoje prijedlozi koji prošle godine nisu primili dovoljan broj glasova podrške, ali zaslužuju drugu priliku.
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.
After the proposal phase, we take a break to review the proposals before the voting phase begins.
All active contributors can review and vote for the proposals that they want to support. You can vote for as many different proposals as you want. To ensure fair voting, only registered users can vote, and votes by very new accounts may be removed.
The only votes that are counted are Support votes. The final list of wishes will be ranked in order of the most Support votes. 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.
Note also that the proposals are occasionally rotated to ensure all get fair visibility. This is done by simply moving the top proposal to the bottom.
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 Support-vote rankings create a prioritized backlog of wishes, and the Community Tech team is responsible for evaluating and addressing the popular wishes. To do that, Community Tech investigates 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, Community Tech balances 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. Community Tech listened to all sides, and made a decision on whether to pursue the project or not.
…instead of addressing other wishes from older surveys?
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.
We also want to make sure that older ideas are still wanted. As software evolves, so do the user’s needs. Sometimes a really good wish from last year isn’t so important anymore, or the description has simply become outdated. Conducting the survey annually helps reconfirm what the community needs.
If there are wishes from last year's survey that you think deserve another shot, see “Mogu li ponovo dati prijedlog iz prethodnoga istraživanja?” above.
This page or project is maintained by Community Tech.
Get help:
|