Inhlolovo Yohlu Lwezifiso Lomphakathi/Ukubeka Eqhulwini
Lesi sihloko sibhalelwe amavolontiya, abathanda i-Community Wishlist Survey kanye nabanikeli abathuthukile. Thina, Community Tech, sifuna ukuchaza ukuthi siwuhlela kanjani umsebenzi wethu ngeziphakamiso ngemva kokuphela kwesigaba sokuvota. Sithemba ukuchaza izinqubo zethu zokuthuthukiswa kwesofthiwe. Siyayamukela impendulo mayelana nokucaca kwalo mbhalo.
Njengomphumela wohlelo ngalunye lwe Community Wishlist Survey, kunohlu olusha lweziphakamiso oluhlelwa ngenani lamavoti. Ngokuhamba kweminyaka sifunde ukuthi ukuzibophezela ekusebenzeni kwabayi-10 akuwona umqondo omuhle kakhulu.
Kunalokho, senze indlela yokubeka phambili iziphakamiso. Sizihlola ngokuhlelekile nangokusobala. Ukubeka phambili kusisiza ukuthi sinqume ukuthi sizosebenza kanjani ukuze sikwazi ukuqedela iziphakamiso eziningi ngangokunokwenzeka. Kunemibono embalwa:
- Ukuduma kwesiphakamiso kufanele kube yinto ebaluleke kakhulu esinqumweni sethu sokukhetha, kodwa kungabi sodwa.
- Kungcono ukusebenzela iziphakamiso ngokulandelana kwesu futhi ugcwalise eziningi ngangokunokwenzeka.
- Onjiniyela nabaqambi kufanele bakwazi ukusebenzisana ngaphandle kokuvimbana. Isibonelo, njengoba umklami ecwaninga isiphakamiso futhi ekhiqiza izingxenye ezibukwayo zeziphakamiso, onjiniyela bagxila eziphakamisweni ezinobuchwepheshe nje.
- Kungcono ukuxhumana ngokusobala nemiphakathi kunokufihla imininingwane. Ukubonakala kwakha ukwethembana nengxoxo.
Isifinyezo semibandela
Uma sibeka phambili, sibuyekeza iziphakamiso ezingu-30 ezaziwa kakhulu. Asibuyekezi noma yiziphi iziphakamiso ngezansi kwalokho, ngoba asikwazi ukunikeza izifiso ezingaphezu kuka-30 ngonyaka. Sizuza iziphakamiso ngokusekelwe ekudumeni, ubuchwepheshe kanye nobunkimbinkimbi bomkhiqizo & nomklamo, kanye nomthelela womphakathi. Okulandelayo kufinyeza imibandela:
Uma zonke iziphakamiso sezitholiwe, siyazilinganisa futhi sisebenze ngokwalesi simo. Kulapho kuphela lapho singakwazi khona:
- Sebenzela inani elikhulu kakhulu lezifiso ngezinsiza esinazo.
- Khetha ukwenza umthelela omkhulu ngenkathi ucabangela ukulungiswa nokuba yinkimbinkimbi.
Siphinde sixoxisane namanye amathimba eSisekelo, futhi siphenye ukuthi ngabe abevele esebenza kumaphrojekthi ahlobene neziphakamiso.
Inkimbinkimbi Yobuchwepheshe
Imibandela
Our engineers estimate how much effort they would need to put into granting a wish. They prioritize less complex (more workable) projects. Whenever something is not clear, they try to overestimate rather than underestimate.
- Technical dependency – we check if the work requires interactions with other Wikimedia Foundation teams. It could be that part of the work needs to be on other teams' roadmap or that we need other teams' input or feedback before we can complete the wish. Examples of these are schema changes, security reviews, adding a new extension, and upgrading third-party libraries.
- Technical research – we ask ourselves if we know how to approach a particular problem. Sometimes we need to evaluate and consider our options before we can start thinking about a solution. Sometimes we need to confirm that what needs to be done can be done or is within what the platform we are working on can handle.
- Technical effort – we ask ourselves how familiar we are with the underlying code and how big or complex the task can be. A high-effort score could also mean that the code we'll be working with is old, brittle, or has some degree of technical debt that will have to be dealt with before we can start working on our actual task.
Isikali
Ngayinye yalezi ibalwa esikalini esingu-1-6:
| 1 - Ubulukhuni obuphansi kakhulu |
|
|---|---|
| 2 - I-Low Medium Complexity |
|
| 3 - I-Medium Complexity |
|
| 4 - I-Medium Eyinkimbinkimbi Enkulu |
|
| 5 - Ubunzima obukhulu |
|
| 6 - I-Complexity enkulu kakhulu |
|
Inkimbinkimbi Yomkhiqizo Nomklamo
Imibandela
Similarly to the assessments above, our designer estimates what effort should be made to complete a project. They prioritize less complex (more workable) projects. Whenever something is not clear, they tries to overestimate rather than underestimate.
- Design research effort – we seek to understand the level of research needed for each proposal. In this case, the research involves understanding the problem, either at the very beginning through initial discovery work (the scope and details of the project, surveys or interviews with community members), or later in the process through community discussions and usability testing (e.g. how do users contribute with and without this new feature).
- Visual design effort – a significant number of proposals require changes in the user interface of Wikimedia projects. Therefore, we check to estimate the change of the user interface, how many elements need to be designed and their complexity. For instance, using existing components from our design system or creating new ones, keeping in mind how many states or warnings need to be conceived to help guide users, including newcomers.
- Workflow complexity – we ask ourselves how does this particular problem interfere with the current workflows or steps in the user experience of editors. For example, a high score here would mean that there are a lot of different scenarios or places in the user interface where contributors might interact with a new feature. It can also mean that we might have to design for different user groups, advanced and newcomers alike.
Isikali
Ngayinye yalezi ibalwa esikalini esingu-1-6:
| 1 - Ubulukhuni obuphansi kakhulu |
|
|---|---|
| 2 - I-Low Medium Complexity |
|
| 3 - I-Medium Complexity |
|
| 4 - I-Medium Eyinkimbinkimbi Enkulu |
|
| 5 - Ubunzima obukhulu |
|
| I-6 - Ukuxaka Okukhulu Kakhulu |
|
Umthelela Womphakathi
In contrast to the two perspectives described above, this part is about equity. Practically, it's about ensuring that the majorities aren't the only ones whose needs we work on.
Depending on this score, proposals with similar numbers of votes and similar degrees of complexity are more or less likely to be prioritized. If a given criterion is met, the proposal gets +1. The more intersections, the higher the score. This assessment was added by our Community Relations Specialist.
- Not only for Wikipedia – proposals related to various projects and project-neutral proposals, are ranked higher than projects dedicated only to Wikipedia. [[Community Wishlist Survey 2022/Editing/Autosave edited or new unpublished article|Autosave edited or new unpublished article]] is an example of a prioritized proposal.
- Sister projects and smaller wikis – we additionally prioritize proposals about the undersupported projects (like Wikisource or Wiktionary). We counted Wikimedia Commons as one of these. [[Community Wishlist Survey 2022/Bots and gadgets/Tool that reviews new uploads for potential copyright violations|Tool that reviews new uploads for potential copyright violations]] is an example of a prioritized proposal.
- Critical supporting groups – we prioritize proposals dedicated to stewards, CheckUsers, admins, and similar groups serving and technically supporting the broader community. [[Community Wishlist Survey 2022/Admins and patrollers/Show recent block history for IPs and ranges|Show recent block history for IPs and ranges]] is an example of a prioritized proposal.
- Reading experience – we prioritize proposals improving the experience of the largest group of users – the readers. [[Community Wishlist Survey 2022/Editing/Select preview image|Select preview image]] is an example of a prioritized proposal.
- Non-textual content and structured data – we prioritize proposals related to multimedia, graphs, etc. [[Community Wishlist Survey 2022/Multimedia and Commons/Mass uploader|Mass uploader]] is an example of a prioritized proposal.
- Urgency – we prioritize perennial bugs, recurring proposals, and changes which would make contributing significantly smoother. [[Community Wishlist Survey 2022/Wikisource/Fix search and replace in the Page namespace editor|Fix search and replace in the Page namespace editor]] is an example of a prioritized proposal.
- Barrier for entry – we prioritize proposals about communication and those which would help to make the first contributions. [[Community Wishlist Survey 2022/Mobile and apps/Show editnotices on mobile|Show editnotices on mobile]] is an example of a prioritized proposal.
2022 Imiphumela ibalwa nge-Prioritization Score
These scores may change when we start working on the proposals. As we explained above, we have tried to overestimate rather than underestimate. Check out the proposals, in order of prioritization:
| Wish | Popularity Rank | Votes | Engineering Score | Product and Design Score | Community Impact Score | Prioritization Score |
|---|---|---|---|---|---|---|
| [[Community Wishlist Survey 2022/Editing/Autosave edited or new unpublished article|Autosave edited or new unpublished article]] | 29 | 69 | 1.0 | 0.3 | 2 | 2.66 |
| [[Community Wishlist Survey 2022/Miscellaneous/Get WhatLinksHere's lists in alphabetical order|Get WhatLinksHere's lists in alphabetical order]] | 22 | 74 | 1.3 | 0.3 | 2 | 2.63 |
| [[Community Wishlist Survey 2022/Search/Enable negation for tag filters|Enable negation for tag filters]] | 26 | 71 | 2.0 | 0.3 | 2 | 2.47 |
| [[Community Wishlist Survey 2022/Wikisource/Fix search and replace in the Page namespace editor|Fix search and replace in the Page namespace editor]] | 11 | 93 | 2.3 | 0.7 | 2 | 2.47 |
| [[Community Wishlist Survey 2022/Multimedia and Commons/Improve SVG rendering|Improve SVG rendering]] | 5 | 108 | 4.0 | 0.8 | 3 | 2.44 |
| [[Community Wishlist Survey 2022/Anti-harassment/Notifications for user page edits|Notifications for user page edits]] | 2 | 123 | 1.3 | 1.7 | 1 | 2.38 |
| [[Community Wishlist Survey 2022/Miscellaneous/Check if a page exists without populating WhatLinksHere|Check if a page exists without populating WhatLinksHere]] | 14 | 89 | 2.7 | 0.7 | 2 | 2.38 |
| [[Community Wishlist Survey 2022/Bots and gadgets/Tool that reviews new uploads for potential copyright violations|Tool that reviews new uploads for potential copyright violations]] | 4 | 109 | 4.3 | 2.7 | 4 | 2.21 |
| [[Community Wishlist Survey 2022/Reading/IPA audio renderer|IPA audio renderer]] | 9 | 97 | 3.0 | 2.7 | 3 | 2.15 |
| [[Community Wishlist Survey 2022/Reading/floating table headers|floating table headers]] | 24 | 73 | 1.0 | 2.7 | 2 | 2.14 |
| [[Community Wishlist Survey 2022/Admins and patrollers/Mass-delete to offer drop-down of standard reasons, or templated reasons.|Mass-delete to offer drop-down of standard reasons, or templated reasons.]] | 25 | 72 | 1.0 | 2.7 | 2 | 2.14 |
| [[Community Wishlist Survey 2022/Editing/Formatting columns in table|Formatting columns in table]] | 19 | 77 | 4.0 | 0.3 | 2 | 2.11 |
| [[Community Wishlist Survey 2022/Editing/Select preview image|Select preview image]] | 8 | 100 | 3.0 | 2.0 | 2 | 2.07 |
| [[Community Wishlist Survey 2022/Translation/Add DeepL as a machine translation option in ContentTranslation|Add DeepL as a machine translation option in ContentTranslation]] | 20 | 75 | 3.3 | 0.0 | 1 | 2.06 |
| [[Community Wishlist Survey 2022/Search/Change default number of search results displayed|Change default number of search results displayed]] | 12 | 92 | 2.0 | 1.7 | 1 | 2.05 |
| [[Community Wishlist Survey 2022/Editing/Better diff handling of paragraph splits|Better diff handling of paragraph splits]] | 1 | 157 | 3.3 | 2.3 | 1 | 2.04 |
| [[Community Wishlist Survey 2022/Mobile and apps/Table sorting on mobile|Table sorting on mobile]] | 17 | 83 | 2.3 | 1.7 | 1 | 1.92 |
| [[Community Wishlist Survey 2022/Miscellaneous/Enhanced Move Logs|Enhanced Move Logs]] | 10 | 96 | 2.7 | 2.3 | 1 | 1.79 |
| [[Community Wishlist Survey 2022/Bots and gadgets/Gadget: Who is active|Gadget: Who is active]] | 26 | 71 | 1.3 | 4.0 | 2 | 1.76 |
| [[Community Wishlist Survey 2022/Admins and patrollers/Show recent block history for IPs and ranges|Show recent block history for IPs and ranges]] | 3 | 120 | 4.0 | 3.7 | 2 | 1.61 |
| [[Community Wishlist Survey 2022/Admins and patrollers/Reminders or edit notifications after block expiration|Reminders or edit notifications after block expiration]] | 20 | 75 | 3.3 | 3.2 | 2 | 1.57 |
| [[Community Wishlist Survey 2022/Wikidata/Autosuggest linking Wikidata item after creating an article|Autosuggest linking Wikidata item after creating an article]] | 12 | 92 | 3.3 | 3.8 | 2 | 1.53 |
| [[Community Wishlist Survey 2022/Mobile and apps/Full page editing|Full page editing]] | 30 | 67 | 2.0 | 3.7 | 1 | 1.42 |
| [[Community Wishlist Survey 2022/Miscellaneous/Allow filtering of WhatLinksHere to remove links from templates|Allow filtering of WhatLinksHere to remove links from templates]] | 6 | 106 | 5.0 | 3.3 | 2 | 1.40 |
| [[Community Wishlist Survey 2022/Citations/Automatic duplicate citation finder|Automatic duplicate citation finder]] | 6 | 106 | 3.0 | 4.2 | 1 | 1.36 |
| [[Community Wishlist Survey 2022/Editing/VisualEditor should use human-like names for references|VisualEditor should use human-like names for references]] | 22 | 74 | 3.3 | 4.0 | 1 | 1.12 |
In addition, if you are interested in viewing a more granular version of the sub-components that make the prioritization scores, we've made the individual sub-components public:
These are proposals which we found will be worked on by other teams at the WMF or third-party open source when we went through the process of estimating their complexities:
| Wish | Popularity Rank |
|---|---|
| [[Community Wishlist Survey 2022/Anti-harassment/Deal with Google Chrome User-Agent deprecation|Deal with Google Chrome User-Agent deprecation]] | 15 |
| [[Community Wishlist Survey 2022/Mobile and apps/Show editnotices on mobile|Show editnotices on mobile]] | 15 |
| [[Community Wishlist Survey 2022/Mobile and apps/Categories in mobile app|Categories in mobile app]] | 18 |
| [[Community Wishlist Survey 2022/Multimedia and Commons/Mass uploader|Mass uploader]] | 28 |
Amagama Awusizo
Ucwaningo lwabasebenzisi olungalinganiselwe
Sisebenzisa ithuluzi elifana ne-UserTesting.com ukuze senze “izinto ezihlekisayo” zezinguquko ezihlongozwayo zedizayini yethu futhi sibone ukuthi siyayiklama yini isixazululo sesifiso esifanele-- kubizwa ngokuthi “akulinganiswanga” ngoba sivumela abasebenzisi ukuthi bachofoze babone imiklamo yethu inengqondo ngaphandle kokuchaza. kubo
Iqoqo ledatha lenani
Inqubo yokuqoqa idatha ukuze kuqondwe ukuthi abasebenzisi basebenzisana kanjani ne-UI yamanje ukuze baqonde amaphuzu obuhlungu besifiso -- kungaba idatha emayelana nokuchofoza, ukuvakasha, ukudawuniloda, izikhathi njll. Idatha ivamise ukukhawulelwa lapho siqala ukubhekana nesifiso ngenxa yokuntuleka ukuyilandela ngaphambi kokufisa, noma idatha engekho ngenxa yezizathu zobumfihlo
Ukuqoqwa kwedatha okufanelekile
Ukuqonda indawo yenkinga yesifiso ngokukhuluma ngqo nabasebenzisi, kungaba izingxoxo noma ngenhlolovo ekuqaleni kwesifiso sokuqonda amaphuzu obuhlungu nokucacisa indlela yokubhekana nesixazululo
'Abasebenzisi
Inqubo yokuthola abasebenzisi abanolwazi oludingekayo ukuze babambe iqhaza ezivivinyweni zethu zabasebenzisi futhi isinikeze ulwazi esiludingayo ukuze siluqonde uma izinqumo zethu zedizayini nemikhiqizo ziqondiswe endleleni efanele. Ezinye izifiso ezabasebenzisi abathuthukile, okunzima ukuzithola futhi ezingatholakali kumathuluzi afana ne-UserTesting.com
Ukwenza kabusha ikhodi
Inqubo yokwenza ikhodi ekhona igcineke kakhudlwana ukuze abanye abantu bafake isandla kukhodi, kanye nokususa isikweletu sobuchwepheshe neziphazamisi.
I-database schema iyashintsha
Ukuguqulwa kweqoqo lezakhiwo ezinengqondo zazo zonke noma ingxenye yesizindalwazi esihlobene. Uma kudingeka ushintsho kusizindalwazi esikhona, kufanele siklanywe bese sigunyazwa ithimba elingaphandle le-CommTech. Lokhu ngokuvamile kuthatha isikhathi esiningi futhi kwengeza ubunkimbinkimbi besakhiwo kuphrojekthi.
Ikhodi yomuntu wesithathu
Ikhodi ebhalwe ngaphandle kwethimba le-Community Tech, izibonelo zifaka ama-API noma amalabhulali.