After collecting the community feedback in parent, post a note on the Wishlist discussion page about what we learned from it. It will give the participants a chance to clarify their views if necessary.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Lokal_Profil | T274892 ☂Find other ways of identifying techincal needs arising from the community | |||
| Declined | None | T205247 Ask for community feedback on the 2017+2018 DevSupport wishlist process | |||
| Declined | Alicia_Fagerving_WMSE | T205819 Conduct postmortem of 2018 wishlist | |||
| Resolved | Alicia_Fagerving_WMSE | T206990 Summarize community feedback 2018 | |||
| Declined | None | T206742 Post summary of community feedback |
Event Timeline
Comment Actions
Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.)
Comment Actions
Abandoning this one.
It's been 2 years since we collected the feedback. Instead of posting it on the wishlist the conclusions should be made part of the report in T274892, which in turn should be shared on the wishlist talk page (or other page suitable for the same community)