Page MenuHomePhabricator

Find an owner for top 10 Developer Wishlist 2017 proposals
Open, LowPublic

Related Objects

Event Timeline

Tgr created this task.Feb 15 2017, 2:11 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 15 2017, 2:11 AM
Rical added a subscriber: Rical.Feb 15 2017, 11:28 AM
Tgr updated the task description. (Show Details)Feb 28 2017, 1:53 AM
Tgr added a subscriber: bd808.
Volker_E updated the task description. (Show Details)Mar 1 2017, 2:38 AM
Volker_E added a subscriber: Volker_E.
Qgil updated the task description. (Show Details)Mar 1 2017, 4:47 PM
Qgil added subscribers: greg, Qgil.
greg added a subscriber: mmodell.Mar 3 2017, 12:04 AM

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.

Qgil updated the task description. (Show Details)Mar 13 2017, 5:08 PM
Rical removed a subscriber: Rical.Jul 21 2017, 9:55 AM
Qgil triaged this task as Medium priority.Sep 12 2017, 8:43 AM

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:

  1. most of these tasks are not suitable and/or not motivating for the average volunteer
  2. since this Developer Wishlist was agreed and completed, Developer Relations has concentrated on a focus for onboarding new developers, where this wishlist doesn't quite fit.

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.

Aklapper updated the task description. (Show Details)Mar 2 2018, 9:37 AM
Aklapper added a subscriber: Harej.
Aklapper lowered the priority of this task from Medium to Low.Mar 2 2018, 9:40 AM
Aklapper updated the task description. (Show Details)

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.)