On Thu, Nov 4, 2021 at 4:43 PM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
Specifics
---------
We’d create a new top-level category, “Common Issues”. Posting directly
in the category would not be allowed. Instead, there would be a
*subcategory*, “Proposed Common Issues”.
New topics in “Proposed Common Issues” would use the template feature,
prompting for the necessarily information and keeping the format
consistent. Unfortunately, there are no macros to do the fancy things
the current wiki process uses, which I will freely admit is a drawback.
Each topic would be tagged with the release that it corresponds to
(and, ideally other tags, like the installation / upgrade / workstation
/ etc. sections on the wiki — we could make that mandatory or just by
convention).
Members of the QA team (based on group membership, automatically once
[Does `sso overrides groups` work with Oauth2? - sso - Discourse
Meta][4] is fixed upstream) and possibly other volunteers will be
marked as category moderators, and so can promote topics to the
higher-level “Common Issues” after vetting them.
And, we’d turn on voting, and ask people to vote for issues that they
have also experienced. Not scientific, but gives a measure that we
don’t have now.
1. In the Proposed Common Issues category, how are the topics intended to look like? Will the initial topic description be a question ("my sound is broken, how do I fix it?") and then somebody will provide a solution which will get marked as such, or will the initial topic description be already a solution (i.e. a similar text to what is currently on the CommonBugs wiki)?
2. In the Common Issues category, will the topics look the same as in 1) (we'll simply re-tag them there), or differently? (e.g. a question-style in Proposed, a solution-style in actual Common Issues).
3. Can we easily move a topic (or add a tag to it) into the Proposed Common Issues category, when it is currently in a completely different one? And similarly, we can easily move out a topic from Proposed Common Issues to some generic "Ask" category?
4. The solution text often needs maintenance. Some clarifications, newly discovered workarounds, etc. If the original solution text was created by a community member, is it expected that we'll simply edit his/her post? Or what do we do? On wiki, it is owner-less, which avoids the problem "somebody edited my post, and it's still displayed under my name, but those aren't my words, and I don't like it".
I'm sure I'll have more questions after I think about it a bit more :-)
Overall, I don't have strong opinions on the proposal. A wiki is easier for us, but otoh more community involvement would definitely be nice. We could try a different approach as an experiment. If we do, it might be good to start it right away, so that some initial problems are resolved before the F36 cycle runs in full swing.
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
