Topic on Talk:Developer Wishlist

As discussed at WikiDev, we probably should split the list into sections to make it easier for people to review existing proposals before submitting new ones, and to make sure important areas affecting less tech people (e.g. operations) also get some visibility. Here is an initial suggestion (based on what kind of skill is required to implement proposals):

• Frontend
• Backend
• API (ie. wishes by developers who make API calls)
• [Dev]Ops (does this make sense?)
• Documentation
• Enviroment (IDE integration, Vagrant etc)
• Contribution workflow (Phab, gerrit, CI)

Yes, categories will be useful. Do we need to decide them beforehand, or can we create them based on the proposals received? They could be columns in a Phabricator board.

Creating them up-front will probably help people think of their concerns. Next iteration we can tweak the columns. Maybe have an "Other" for other suggestions?

OK, please check https://phabricator.wikimedia.org/project/board/2436/.

"Frontend" and "Backend"... are these clear concepts in the context of the developer wishlist? Are we talking about... technical debt?

We need to be cautious about people perceiving that they can propose i.e. "power user frontend features" or anything in that direction.

Technical debt and tooling.

I don't think mistaken submissions are particularly problematic, just remove the wishlist project and treat them as normal feature requests.

OK, makes sense.