The top 10 highest voted proposals of the 2017 wishlist are:
Let's try to find an owner (or group of owners) for each of these, either by getting them some team's quarterly goals list, or getting them accepted as outreach projects, or by finding volunteers who commit to spending regular time on them!
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T158148 Promote Developer Wishlist 2017 proposals | |||
| Declined | None | T158149 Find an owner for top 10 Developer Wishlist 2017 proposals |
Re T45: @mmodell and I are talking about making it a goal/activity for next fiscal. We might be able to start on it before then, but I don't want to rush it and we have other things to do in the near term.
Also, to be clear, I don't think we need to make this a "contract upstream to do it" task. @mmodel plans to follow a similar path that we used for ElasticSearch support: us (him) writing the support with feedback from upstream in upstream's Differential.
@mmodell, let me know if I got any of that wrong.
I have pinged the top 10 tasks listed above asking for their current status. The fact that all of therm are unassigned and most of them with low or no priority is telling.
While theoretically Developer-Advocacy could have been done promoting these tasks and nagging volunteer developers, in practice we face two problems:
If we organize a new edition, we need to have some guarantees from WMF Technology & Audiences that (some of) the top wishes will be addressed. Someone will remember that we were warned exactly about this important missing factor while planning the first edition. Sure, this was a clear risk clearly demonstrated now. Still, I think it was a good idea and a good decision. We have learned a lot, and we still have an interesting wishlist that is relevant.
I don't see this as something in scope of the Developer-Advocacy team, hence I'm boldly removing that tag.
(I also don't really get the difference to T158148.)