Le 14/12/2016 à 20:54, Justin W. Flory a écrit :
I think if the big question becomes *what to do with Ask Fedora*, we
should give special consideration to choosing a route forward that
will provide the best user experience for people who are (1) asking
questions, and (2) answering the questions too. I'm not sure of the
process to become integrated with the
+1, there is not much user-facing help at the moment:
The wiki, but no active wiki group for refresh and gardening.
The documentation, but not very active (we know they are changing tools).
And there is Ask.
If Infrastructure team spend too much time (numbers would be great to
understand, I see 11 tickets in 4 years), it's better to pay an
open-source dev for a few days/weeks to investigate and limit the
maintenance costs.
But without clear outreach objectives, it's hard to tell if it is too
much or not.
We should not let this service go without offering something else and
using FOSS technologies is mandatory.
Fedora painfully left Transifex, which is a huge lost for the
translation team, FOSS tool is relevant for contributors.
At the same time, local communities install they own tools. Sometime
they translate wiki, they try to translate documentation (if even
published), etc.
Gather together local contributors to support "user-facing help" in
their language would help wiki, documentation and ask, but today we are
pretty far from having tools to support this.
Would we host our documentation in "Read the docs"?
Would we host our wiki in "Wikia"?
Why would we host our Ask platform anywhere else than in our infrastructure?
I think the problem is not technical, but more about defining what tool
to support which objective.
--
Jean-Baptiste Holcroft
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx