T125439: Create more detailed descriptions of specifically interesting wishlist items might include developers who are already interested. It might be they don't need the descriptions, or could help write them.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Johan | T125659 List Community Wishlist items with interested volunteer developers | |||
| Resolved | Johan | T125439 Create more detailed descriptions of specifically interesting wishlist items | |||
| Resolved | Johan | T125574 Find teams to assess wishlist tasks |
Event Timeline
Comment Actions
There are two ways of achieving more or less the same result that should be explored before starting a new list:
- Organize the #community-wishlist-survey workboard by status (since the classification is already available elsewhere) having columns for i.e. "Developer needed", "Developers interested", "Assigned"... (this is a quickly improvised list, you get the point)
- Add a Status column to the canonical Community Wishlist survey results, documenting there who is interested or working on each project (see my suggestion).
Comment Actions
This task had a bad name. I changed it to better reflect what I'm actually doing, which at the moment is is:
*) Go through the tasks in T119703 and see if they have interested developers.
*) Go through the list of Hackathon attendees and people who have requested scholarships and see if the are interested in wishlist tasks, sorting them into "top ten", "especially suitable for the hackathon" and "other wishlist tasks".
If not or if it seems likely they don't know what they're doing, go forward anyway. If there are interested developers, talk to them. If there are people interested in working on them at the hackathon, wait a bit and see if they are coming and if it's worth talking to them before taking time from other Wikimedia Foundation teams.