On Mar 9, 2016 12:06, "Matthew Miller" <mattdm@fedoraproject.org> wrote:
>
> On Thu, Feb 11, 2016 at 11:25:24AM -0600, Pete Travis wrote:
> > collaboration, and the quality of the resulting copy.  Without a well
> > established collaborative workflow, a very low barrier to contribution
> > leads to low quality documentation.  We have seen this with both the Fedora
> > wiki and with Ask Fedora.  StackExchange works because users aggressively
> > cull out dupes and poor answers, and that is not happening with Fedora's
>
> This works on Stack Exchange because there's a lot of well-considered
> and constantly tweaked UX design focused on the community moderation
> side. The wiki 5 no understanding of why things are there or what
> they actually do.
>
> > sites.  There is already a general expectation to not be redundant or
> > incorrect on these platforms, and IMO that expectation is not being met.
> > Providing the same kind of platform to the same user base with the same
> > expectations will likely produce the same result.
>
> Yeah, community expectations are important too. I think in Ask Fedora,
> the lack of a "meta" is a crucial part of the pain — and in the Wiki,
> maybe it's correspondingly a lack of a culture of using the Talk pages
> for similar purpose.
>
> This is a tangent from your point, but what you're talking about made
> me realize that any new service made without a clear connection to a
> community communication mechanism is going to fail. (Maybe a new Hub
> for docs would serve? Or, less grandiose, simply prominent connections
> to the hyperkitty interface for this list?)
>
>
> --
> Matthew Miller

I'm personally content with the existing IRC+list channels for Docs meta-discussion, which fits with Hubs as I understand it.  For discussion of implementation  details and back and forth on WIP content, pagure issues would work - a hubs tie-in here would be cool.  I'm not that familiar with Hubs beyond the metaphorical relationship to sliced bread...

The gist of my desire here is a solution and workflow that abstracts away the curating/organizing tasks as much as possible.  Automatically retiring outdated content, automatically organizing content from embedded metadata, etc plus the capability to do more automatic things we haven't thought of yet.  The trapdoor behind 'just do this thing that is easy to describe' has a big spiked pit of 'somebody still has to do all this work' underneath.

--Pete

--Pete