Any talk of the specific technical solutions needed is probably premature. I apologize for leading the discussion in that direction myself as few posts above. In my experience these discussion quickly devolve into experienced insiders debating the relative merits of existing solutions instead of discussing who the audience is and what their needs are. See past threads for examples:
The real place to start if we want a different outcome is with someone taking on the role of Product Owner and doing the initial work of describing the general problems that should be addressed and how solving those problems will result in a net positive change for the Wikimedia movement. We need to know what problem we are trying to solve and who we are trying to solve it for before deciding on the technical details of how to actually produce the desired result.
|Resolved||• bd808||T171120 [FY17-18] Program 4: Technical community building|
|Resolved||• bd808||T166401 Program 4 Outcome 1: improve documentation|
|Open||Harej||T115650 Create an authoritative and well promoted catalog of Wikimedia tools|
|Resolved||Harej||T183106 [Toolhub Milestone 0] Write up summary of Toolhub for public consumption|
Is there a specific deliverable you would like to see for this task? I've already written up something as part of my research process; I could probably clean it up and put it on a wiki somewhere?
I'm not 100% certain what the "right" document is, but I imagine it is something like a collection of use cases and some sort of strawdog roadmap of what order they should be addressed in.