Komunitatearen Nahaien Inguruko 2019 Inkesta

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Community Wishlist Survey 2019 and the translation is 12% complete.


Magic Wand Icon 229981 Color Flipped.svg Amaitu da 2019ko Komunitatearen Gurariei buruzko Inkesta... Magic Wand Icon 229981 Color Flipped.svg
Hementxe 2019ko Komunitatearen Nahien Inguruko Inkestaren emaitzak!

Guztira: 212 proposamen, 1387 lankide, 7282 aldeko boto

Ausazko proposamena

Kategoriak
Klikatu kategoria batean proposamenak ikusteko

Administrariak eta patruilatzaileak
15 proposamen
Jazarpenaren kontra
4 proposamen
Botak eta gadgetak
10 proposamen
Kategoriak
12 proposamen
Aipamenak
13 proposamen
Edizioa
27 proposamen
Mapak
13 proposamen
Askotarikoak
17 proposamen
Mugikorra eta aplikazioak
12 proposamen
Multimedia eta Commons
20 proposamen
Jakinarazpenak
4 proposamen
Programs and events
2 proposamen
Irakurketa
8 proposamen
Bilatu
6 proposamen
Jarraipen zerrendak
12 proposamen
Wikidata
19 proposamen
Wikiturriak
11 proposamen
Wikiztegia
7 proposamen

 

Inkestaren fase guztiak 18:00etan (UTC) hasi eta bukatuko dira.

  • Proposamenak bidali, eztabaidatu eta berrikusi: October 29 to November 11, 2018
  • Community Techek proposamenak berrikusi eta antolatuko ditu: November 13 to November 15, 2018
  • Proposamenei buruz bozkatu: November 16 to November 30, 2018
  • Emaitzak argitaratu: December 3, 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.

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 Community Relations Specialists team.

This is our fourth annual Community Wishlist Survey. See where we are with last year's wishes.

 <div id="What happened to the 2018 wishlist survey?" class="community-wishlist-header">[[#What happened to the 2018 wishlist survey?|What happened to the 2018 wishlist survey?]]

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.

 
The Community Tech mascot: a dog wearing a Santa hat.

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. Proposals should answer the following questions:

  • What is the problem that you want to solve?
  • Which users are affected? (editors, admins, Wikisource editors, etc.)
  • 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.

 
Aldino per Natale.jpg

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.

 

Ohikoa izaten da lehendabiziko 10etan amaitzen duten proposamen gehienak proiektu handienetarako izatea: Wikipedia handiak eta Commons. Aldiz, txikiagoak diren talde ugarik ez dute "bozkatzeko botere" nahikorik beren proposamenak lehendabiziko 10etaraino bultzatzeko, baina lan garrantzitsua egiten ari dira gure mugimendurako.

Gure lantaldeak asmo irmoa du gure talde txikiagoei lagunduko dieten proiektuetan lan egiteko, adibidez, kanpaina eta programa antolatzaileei, GLAMetako parte-hartzaileei, proiektu txikiagoei (hala nola Wikiteka edo Wikiztegia), eta administratzaileei eta CheckUser-ei.

Garrantzizkoa da Komunitatearen Nahien Inguruko Inkestan proiektu txikiagoen proposamenak izatea. Lagundu egiten dio gure lantaldeari eta Wikimedia Fundazioari talde txikiagoetan jendeak oro har zer behar dituen ezagutzen. Beraz, mesedez etorri eta aurkeztu zure proposamenak, baita lehendabiziko 10en artera helduko ez zarela uste baduzu ere!

 

Each proposal should meet the following criteria:

  • The proposal is about a technical change and not for a policy or social change
  • The proposal is about the problem and not necessarily ask for a specific solution
  • The proposal is a well-defined problem and not a mix and match of different unrelated issues
  • 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 or other teams in the past
  • The proposal is within the team's scope

The Community Tech team may decline proposals that fail to meet the above criteria.

 

Aldeko botoen zerrendan, nahi lehenetsien erregistro bat sortzen da, baina Community Techek nahi horiek ebaluatu eta aztertu behar ditu. Bada, bozkatuenak diren nahi guztiak ikertzen ditugu, eta arrisku faktoreei erreparatzen diegu, hala teknikoak nola sozialak/politikari buruzkoak.

Aurka eta Neutral botoak oso lagungarriak dira balizko desabantailei erreparatzeko. Nahiak polemikoak badira, bozketa eta adostasun handiagoko berrikuspen bat, biak baloratzen ditugu.

Adibide baterako, 2015eko inkestan honexek funtzionatu zuen: "erabiltzailearen jarraipen zerrenda gehitzea" aukerak boto ugari jaso zituen, baina baita Aurka boto zintzo batzuk ere. Guk alde guztiak entzun genituen eta erabaki bat hartu genuen, ea proiektua jarraitu edo ez.

 
Every dog that wears a Santa hat works for Community Tech.

…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 “Can I resubmit a proposal from previous surveys?” above.