On Tue, Nov 09, 2021 at 02:38:59PM +0100, Kamil Paral wrote:
> 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)?
I think the topic titles will be the same as with Common Bugs now, like
"Configured repositories in Discover jump around in the list" or "Clipboard
is not shared with KDE virtual machines".
The site name, "Ask Fedora", makes me _want_ to force them into the form of
a question just... to make it all nice... but in practice most topic tiles
are in the form of a problem summary already. ("Closing the laptop lid does
not turn off the screen", "2-finger scroll occasionally disabled".) So I
think that keeping to the current title format is good.
I can go either way on whether the first post in the topic should also
provide the solution, or whether we should used the answer-solution format.
As I'm reviewing some of the previous wiki pages now, I actually am kind of
inclined to think that it's better to have stronger problem/solution
separation. But I could be convinced either way.
> 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).
I was thinking just move them, yeah.
> 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?
Yes to both. And URLs for topics do not include the category, so moving them
will not break any existing external links.
> 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".
There is a setting "Make new topics wikis by default" which we would enable
for these categories. It doesn't make the post ownerless, though. I think we
could set these expectations reasonably in the description of the category.
And if someone at some point really doesn't want their name attached, we can
always move the Solved check.
> I'm sure I'll have more questions after I think about it a bit more :-)
Sure. :)
> 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.
That does seem like a good idea. Maybe not quite _right away_, but soon.
Would you suggest duplicating the F35 Common Bugs, or making some _possible_
F36 ones based on Rawhide issues?
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
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
