I created a new topic, to help new users to see the importance, of transmitting us the correct information about their systems.
The observation I made is that we do get a lot of new users every day. I also realized that we repeatedly ask the same thing how to give us the correct information to help them. It would really be handy when we just can write:
Please give us the necessary information to help you: Have a look here #inxi
I am sure that this will simply fie the live of a lot of helpers here in Discourse.
For the moment it is OK if it not forwards to the specific topic. Just showing the #taged topic would help. If we do have a single tag, I will try to keep order with it
Now we have to search for guidefyi. I guess with pining and using just the #inxi tag we could keep it simple and easy for helpers and users which search for help.
P.S.
We already talked once to install inxi by default. I do understand if it is not included by default, because of a lot of Perl dependencies we not like to relay on. So, for a uniform communication, I guess, such a topic with tag wold help us!
Shouldnāt we make a documentation page somewhere with the common commands we request for troubleshooting and the info to install them so that we can points to it instead?
I guess you not get the problem. We are almost twice a day telling the users that they should give us the correct information in the correct format.
When I can say āplease read the instructions about #inxi to help you betterā then I do not have to link the doc every-time. It creates a link like , see example #start -> ( Ask Fedora > Start Here ) Already there it has a lot of information which is not really helpful for an average request. inxi -Fzxx on the other hand gives enough information we can work to find out what the issue could be.
This tag should be for support only, that we do have it easier and not have to ask every time the same:
Please give us more information like inxi -Fzxx and past it here as pre-formatet text </>
Making a doc will not really make a difference but a tag will.
If people would read the docs, we would not have to repeat all this instructions every day!
If someone wants to write a doc quick-doc long-doc etc. feel free to do so. I will not.
Feel free to tell me the correct instructions and I will add it to the doc I made, Or you can write it as an answer and I will link like:
Instructions for Atomic Desktops see here:
In my experience, users who ask here either donāt know about the docs or donāt want to read them for some reason. Iām not entirely sure if the inxi command is useful specifically for Atomic Desktops, but I was also thinking of creating a dedicated page in the Atomic Desktops docs with frequently required by us troubleshooting commands. This will at least save us a lot of typing the same commands over and over again and hopefully point people to the answers in the docs.
It is known that we already have fpaste, which can to some degree match the information provided by inxi. E.g.fpaste --sysinfo-short --printonly vs inxi -Fzxx.
Granted inxi presents the information in a more compact way, which might be one of the reasons why those providing support here on the forums prefer inxi over fpaste.
It is known that we already have fpaste, which can to some degree match the information provided by inxi. E.g.fpaste --sysinfo--short --printonly vs inxi -Fzxx.
Note that fpastes arenāt kept around too longā¦ I think itās a day or
two.
Granted inxi presents the information in a more compact way, which might be one of the reasons why those providing support here on the forums prefer inxi over fpaste.
Iām not sure this should be a tag though? I mean, if we just want to
point someone at a āplease provide this infoā it should just be a
(probibly wiki) post we refer to? if itās a tag, people could just add
it to all kinds of other things and confuse new folks as to what info is
helpful.
Sure, itās 24h max, I know that, thanks. Thatās why I was referring to the --sysinfo-short flag for a shorter output, and for the --printonly flag, so that the user requesting help would post the output in the post instead of uploading it to the pastebin server. I find the server upload relevant when the user cannot boot into a graphical session, and has to use a different PC to post here on the forums.
I wouldnāt want to comment on the usefullness of a tag as this was the idea of @ilikelinux, not mine.
TBH, I would rather see a higher adoption of the tools available in the base installs (either fpaste, or the tools that provide specific, non-aggregated info), and by that avoiding to ask the users to install a package plus dependencies in order to provide the necessary system information (be that for a traditional or atomic desktop).
It is a restricted area the Ask Fedora > Start Here section. The problem of posting there will not exist, because the tag is just for there.
It should be simply a shortcut to help us simplify, not to tell all the time the same things.
But it looks like that this is a general problem, that people not read exactly and prefer to talk about a issue. To question every thing just to keep talking ;-). Especially what others should do.
However if the fear exists of miss using the tag, it is best we do redirect into the topic direct.
Iām sure we can make it invisible for selection.
https://discussion.fedoraproject.org/tag/inxi redirect to ->
https://discussion.fedoraproject.org/t/inxi-the-help-to-help-your-selves/180413
This way if we do mention #inxi it will kreate a link in the topic and by clicking on it it opens the topic.
If we need to talk about what exactly we want to tell the user in this topic, we can do this in the moderation coordination together.
It is a restricted area the Ask Fedora > Start Here section. The problem of posting there will not exist, because the tag is just for there.
It should be simply a shortcut to help us simplify, not to tell all the time the same things.
ok. I perhaps misunderstand thenā¦
But it looks like that this is a general problem, that people not read exactly and prefer to talk about a issue. To question every thing just to keep talking ;-). Especially what others should do.
Well, the post you are replying to is the only one I have made in this
thread.
However if the fear exists of miss using the tag, it is best we do redirect into the topic direct.
Iām sure we can make it invisible for selection.
https://discussion.fedoraproject.org/tag/inxi redirect to ->
https://discussion.fedoraproject.org/t/inxi-the-help-to-help-your-selves/180413
This way if we do mention #inxi it will kreate a link in the topic and by clicking on it it opens the topic.
Sure. Sounds fine as long as that works.
If we need to talk about what exactly we want to tell the user in this topic, we can do this in the moderation coordination together.
I do see the purposeā¦ I think thats fine. I just thought a tag will be
something that could have more posts tagged into it and redirect to all
the posts in the tagā¦ ie, if I open the kde tag:
That is true. As we do not have a shorten service URL for fedora i thought this is the easiest way to achieve.
It is also correct that we should document software in a Manual. However when we link to the manual for such a thing, It gets to much information and then it looks like the time we told the users to RTFM.
To tell them on a more friendly way, please give us more infoās so we can try to help you, I proposed a tag. Otherwise we have to go thru a catalogue of questions for every user which likes assistance. As Ask Fedora is more a Questions and Answers, we depend on a basic set of information just to catalogue the issue and point them to a solution or bug which causes the issue.
According to the linked page, the Discourse Canned Replies plugin is deprecated, and Discourse Templates should be used instead (which should already be installed, only setup needed). The Private Templates feature could be of help here maybe?
Thanks for your Answer. That is the way I would now it works. We already had once a tag which pointed into a document, which was a forward. I just do not know if you can hide it to use as a selector for topics?
It is really meant to explain in a few lines that Windows and Linux not work the same way and that Drivers are included in the Kernel as long as they are available and open.
Inxi -Fzxx would be a standardized way to gather a overall info to find out what the issue can be.
I think we can say that inxi is a āstandardā we established for the first steps.
You are talking from Inixi as a package, perl get pulled as dependency, right? On atomic would it need to be layered? The procedure for support in Atomic would be different anyway.
If you have a view instructions steps I could add this to the inxi document?
It not has to be and substitute a manual. It is just to gather the basic infoās that we do have a overview what is going on with the system.
