Patlisiso ea Lenane la Litakatso la Sechaba/Ho bea pele
Sengoliloeng sena se ngoletsoe baithaopi ba chesehelang Community Wishlist Survey le batšehetsi ba tsoetseng pele Rona, Community Tech, re batla ho hlalosa hore na re rera mosebetsi wa rona jwang mabapi le ditshisinyo kamora hore mokgahlelo wa ho vouta o fele Re tšepa ho hlalosa mekhoa ea rona ea ntlafatso ea software Re amohela maikutlo mabapi le ho hlaka ha tokomane ena.
Ka lebaka la khatiso e ngoe le e ngoe ea Patlisiso ea Lenane la Litakatso tsa Sechaba ho na le lethathamo le lecha la litlhahiso tse hlophisitsoeng ka palo ea likhetho Ho theosa le lilemo re ithutile hore ho itlama ho sebetsa ho ba 10 ba holimo ha se mohopolo o motle ka ho fetisisa.
Ho e-na le hoo re thehile mokhoa oa ho beha litlhahiso pele Re li hlahloba ka mokhoa o hlophisitsoeng le ka mokhoa o hlakileng Ho beha lintho tse tlang pele ho re thusa ho etsa qeto ea ho sebetsa e le hore re ka phethela litlhahiso tse ngata kamoo ho ka khonehang. Ho na le likhakanyo tse 'maloa:
- Ho tsebahala ha tlhahiso e lokela ho ba ntlha ea bohlokoa haholo qetong ea rona ea khetho, empa eseng eona feela.
- Ho molemo ho sebetsa ka litlhahiso ka tatellano ea leano le ho tlatsa tse ngata kamoo ho ka khonehang.
- Baenjiniere le baqapi ba lokela ho khona ho sebetsa hammoho ntle le ho thibelana Mohlala ha moqapi a ntse a etsa lipatlisiso ka tlhahiso mme a hlahisa likarolo tse bonoang bakeng sa litlhahiso lienjineri li shebana le litlhahiso tseo e leng tsa tekheniki feela.
- Ho molemo ho buisana ka bolokolohi le sechaba ho e-na le ho pata lintlha. Ponahalo e haha tšepo le lipuisano.
Kakaretso ea litekanyetso
Ha re beha pele, re hlahloba litlhahiso tse 30 tse tsebahalang haholo. Ha re hlahlobe litlhahiso tse ka tlase ho moo, hobane ha re khone ho fana ka litakatso tse fetang 30 ka selemo. Re fana ka lintlha ho ipapisitse le botumo, botekgeniki le sehlahisoa & ho rarahana ha moralo, hammoho le tšusumetso ea sechaba. Lintlha tse latelang li akaretsa litekanyetso:
Hang ha tlhahiso e ngoe le e ngoe e se e fumanehile, rea e beha maemong me re sebetsa ho latela boemo bona Ke ka hona feela re ka khonang:
- Sebetsa ho palo e kholo ea litakatso ka lisebelisoa tseo re nang le tsona
- Khetha ho ba le tšusumetso e kholo ha u ntse u ela hloko tlhokomelo le ho rarahana.
Re boetse re buisana le lihlopha tse ling tsa Motheo, le ho etsa lipatlisiso hore na li ne li se li ntse li sebetsa mererong e amanang le litlhahiso.
Mathata a Theknoloji
Litekanyetso
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.
Sekala
E 'ngoe le e' ngoe ea tsona e behiloe ka tekanyo ea 1-6:
| 1 - Mathata a tlase ka ho Fetisisa |
|
|---|---|
| 2 - Ho rarahana ha Bohareng ho Tlase |
|
| 3 - Mathata a Mahareng |
|
| 4 - Mathata a Mahare a Maholo |
|
| 5 - Ho rarahana ho hoholo |
|
| 6 - Ho rarahana ho eketsehileng |
|
Mathata a Sehlahiswa le Moralo
Litekanyetso
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.
Sekala
E 'ngoe le e' ngoe ea tsona e behiloe ka tekanyo ea 1-6:
| 1 - Mathata a tlase ka ho Fetisisa |
|
|---|---|
| 2 - Ho rarahana ha Bohareng ho Tlase |
|
| 3 - Mathata a Mahareng |
|
| 4 - Mathata a Mahare a Maholo |
|
| 5 - Ho rarahana ho hoholo |
|
| 6 - Mathata a Eketsehileng a Maholo |
|
Tšusumetso ea Sechaba
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.
Liphetho tsa 2022 li behiloe ka 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 |
Mareo a Thusang
Patlisiso e sa lekanyetsoang ea basebelisi
Ho sebelisa sesebelisoa se kang UserTesting.com ho tsamaisa "metlae" ea liphetoho tse reriloeng tsa moralo le ho bona hore na re rala tharollo e nepahetseng ea takatso-- e bitsoa "e sa lekanngoeng" hobane re lumella basebelisi ho tobetsa ho pota-pota le ho bona meralo ea rona e utloahala ntle le ho tlameha ho hlalosa. ho bona
Pokello ea lintlha tse ngata
Mokhoa oa ho bokella datha ho utloisisa hore na basebelisi ba sebelisana joang le UI ea hajoale ho utloisisa lintlha tse bohloko tsa takatso -- e ka ba lintlha tse mabapi le ho tobetsa, ho etela, ho khoasolla, mananeo, joalo-joalo. Lintlha hangata li na le moeli ha re qala ho sebetsana le takatso ka lebaka la ho hloka ho e sala morao pele ho takatso, kapa data e sieo ka lebaka la mabaka a lekunutu
Pokello ea lintlha tsa boleng
Ho utloisisa sebaka sa bothata ba takatso ka ho bua ka kotloloho le basebelisi, e ka ba lipuisano kapa ka lipatlisiso qalong ea takatso ea ho utloisisa lintlha tsa bohloko le ho hlakisa mokhoa oa ho sebetsana le tharollo.
Basebelisi ba "ho fumana"
Mokhoa oa ho fumana basebelisi ba nang le tsebo e hlokahalang ho kenya letsoho litekong tsa basebelisi ba rona le ho re fa leseli leo re le hlokang ho utloisisa haeba liqeto tsa rona tsa moralo le sehlahisoa li lebisitsoe tseleng e nepahetseng Litakatso tse ling ke tsa basebelisi ba tsoetseng pele tseo ho leng thata ho li fumana ebile ha li fumanehe lisebelisoa tse kang UserTesting.com
'Code refactoring
Mokhoa oa ho etsa hore khoutu e teng e bolokehe haholoanyane e le hore batho ba bang ba ka kenya letsoho ho khoutu, hammoho le ho tlosa likoloto tsa tekheniki le likokoana-hloko.
schema sa database se fetoha
Phetoho ho pokello ea meaho e utloahalang ea tsohle kapa karolo ea polokelo ea litaba tse amanang. Ha ho hlokahala phetoho ho database e seng e ntse e le teng, e tlameha ho raloa ebe e amoheloa ke sehlopha se kantle ho CommTech. Hangata sena se nka nako e eketsehileng mme se eketsa ho rarahana ha moralo morerong.
Khoutu ea motho oa boraro
Khoutu e ngotsoeng kantle ho sehlopha sa Community Tech, mehlala e kenyelletsa li-API kapa lilaeborari.