Selection of 10 most voted suitable tasks.

What is the status of this selection? If it is not completed yet, I bet it deserves its own subtask. If it is completed, please share the tasks selected here.

(Summarizing my conversation with Nick)

Alright, now there are 8 tasks mentioned in the description. The desired scenario is to have the 10 that we believe are a good fit for volunteers.

If a task is taken by a WMF developer (or WMDE, any professional dev) but they are taking it not as part of their team backlog, goal, etc, but on their own time and at their own risk, that also counts as a task driven by a volunteer.

And also:

On the latter, there is an open (although currently silent) discussion about promoting CW tasks to WMF devs as pet projects / 20% time kind of thing. Nothing solid (at all) at this point, but who knows what might happen during FY 2016-17.

It would be useful to keep a record in the description of the position of the tasks in the CW. Also a record of the tasks that were considered but discarded. Example:

(and etc until #10)

Desc says "Selection of 10 most voted suitable tasks" which is followed by "Technical and social feasibility assessment".
So I guess it's an acceptable potential assessment result that a task is suitable but not feasible and it is still "counted" as one of Technical-Collaboration's ten tasks.

For example, surely "Improve SVG rendering" is a suitable task for anybody knowing C but visible success might end up being blocked on external issues (upstream patch review; downstream package deployment).

Regarding the three tasks that I initially proposed,

• #16: I think that T112987: Separating infoboxes and navboxes from article content is not suitable for volunteers, due to T112987#1655990 or T112987#1656036 describing both technical and social obstacles. So I'd remove that from "my" list. It looks very unlikely that I could help driving this forward at all, or that some volunteer could actually work on such a complex task.
• #17: Status: I need to clarify the scope in T120746: Improve SVG rendering plus at some point talk to upstream. I'm confident there can be some results but not sure if/when they will actually reach Wikimedia servers due to T112421 and very limited upstream resources.
• #18: Status: In T2738: Ability to watch section levels of pages I've asked for both clarification of expectations when it comes to types of pages, plus a technical update on Parsing plans. (Likely need to go to mailing lists if no reply.)
• #25: As I "lost" one task above, looking for another one, T120788: Tool to use Google OCRs in Indic language Wikisource sounds suitable. There has already been a volunteer working on it (not sure how active currently), and I'd be happy to help sorting out the next steps there. I've asked in the task for some update.

Related: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_report_2#Technical_Collaboration

10 tasks are in development, and a number of others are in various stages of investigation, planning, or people-nudging.
The updates to this task were not as clear or frequent as I/we wanted, but I/we intend to keep pushing forward on as many of the wishlist (and related) tasks as feasible, over the coming months.

Outreachy round 12 will be announced on September 12, at it would be very good to have by then a landing page featuring Community Wishlist projects with mentors aligned.

@Quiddity can we have the top 10 tasks listed here asap, please? This will allow @01tonythomas @Sumit and Developer-Advocacy to start the search for mentors also asap.

For the records, Outreachy round 13 (which you meant) has a landing page now (T144816). Edits welcome...

I've been going through the top 60 again, pinging "in development" owners for status updates and to confirm they're still working on the things and aren't blocked, and confirming the difficulty of the others.
These are the only tasks that I believe have a possible chance of Outreachy/GSoC development.

• T88781: Create a Timer based reminder for workflows (#32)
• T28059: Add support for KML/KMZ filetype (#34) - Possibly Putnik is working on this? I've emailed him asking for update.
• T120437: Category suggestions based on filename, description and location (#54)

I've added Possible-Tech-Projects to those.
I will keep going through the list from 60 on down.

I've also added:

• T120748: Make Special:Listfiles show the quantity of globalusage for a file

Thank you very much @Quiddity for all the research and pinging and more research and more pinging!

@Sumit @01tonythomas feel free to send an Outreachy invitation to at least the open tasks among the top 10 list. The developers working on them might welcome help from an Outreachy intern, and they would be the default candidates for mentoring.