The Developer Wishlist is a voluntary effort, so its success depends on promoting it to the people can make those wishes true. This might include:
* volunteer developers (many are reachable through wikitech-l; are there other channels that could be used to reach more people without being perceived as spammy?)
* WMF teams (make sure the people doing annual and quarterly planning have heard about the wishlist)
* outreach projects (see which proposals are suitable as Outreachy or GSoC projects and propose them as such; find smaller proposals which might be suitable as microtasks)
* hackathon projects (make sure the wishlist is advertized to the participants)
== Microtasks
| # | Task | Langauges | Familiarity with | Comment
| #9 | {T123218} | JS | | need to grep extensions/skins/vendors and make a task list
| #14 | {T156788} | PHP | | needs someone familiar with MW authorization to know where to look & make a list
== Small tasks
(1-2 days for an experienced developer)
| # | Task | Langauges | Familiarity with | Comment |
| #1 | {T45} | PHP | Phabricator | upstream is willing to add an interface, some needs to write a plugin that uses it
| #5 | {T111731} | PHP | basic extension writing | make `MWExceptionRenderer` replaceable & write an extension to replace it
| #8 | {T156048} | PHP, HTML, CSS | | this sounds like small display tweaks
| #10 | {T156695} | PHP | MW caching layers | a simple maintenance script
| #13 | {T156568} | PHP, JS | basic extension writing | not hard, but needs experienced people to know what should go into it
| #15 | {T126500} | | | just curate a list of things that need their documentation improved?
| #18 | {T156847} | PHP | WMF config? MobileFrontend? |
| #20 | {T128149} | PHP, SQL | MW upgrade system? |
| #21 | {T96041} | PHP, SQL | MW special pages |
| #22 | {T156500} | wiki templates | |
| #23 | {T101659} | | | just curate a list of things that need their documentation improved?
| #24 | {T117661} | PHP | | mostly done
| #28 | {T135245} | | gerrit | maybe done already?
| #30 | {T135186} | ? | Phabricator |
== Big tasks
| # | Task | Langauges | Familiarity with | Comment
| #2 | {T90687} | CSS | responsive design |
| #4 | {T115650} | ? | | easy-ish programming task + lots of cat-herding
| #6 | {T155567} | JS | OOUI, HTMLForm | write a `HTMLForm`-like descriptor-array-to-form converter in JS
| #7 | {T155473} | | OOUI |
| #12 | {T37497} | ? | git, gerrit |
| #16 | {T50826} | PHP, JS | basic extension writing, editing internals? |
| #25 | {T156231} | PHP | | maybe blocked by {T128351}?
| #26 | {T156872} | PHP | | maybe already exists?
| #29 | {T147545} | | | probably needs funding & staff time
== Consensus needed
| # | Task | Langauges | Familiarity with | Comment
| #3 | {T71445} | PHP? | git? | need to decide on on-wiki vs off-wiki solution
| #11 | {T155029} | PHP, Python? | | need to decide where to store infobox data
| #17 | {T156873} | Java? | the chosen IDE | need to pick a target
| #19 | {T107561} | JS | package managers | need to pick a tool
| #27 | {T156640} | | | this is mostly about creating policy and getting buy-in from maintainers