Personally I have no interest in a new knowledge-base for EndeavourOS. I’m quite satisfied with the forum, discovery and the great bunch of people who lend a hand when needed giving feedback and their experiences to help others work through the problems themselves with help. That’s how they learn.
1 Like
Yeah! The wonderful community here is the main reason why I am using eOS; I like to use what I’d contribute to.
Since you are looking for collective community engagement, are you aware of 1000 minds and Gather Virtual Office? Are you interested in mechanisms for engaging with a huge number of audience?
I need AI to extract what is discussed here in detail …
Only as an idea.. i had talk with @mostafatouny before and he was talking about Gaming tutorial creation. We have some but the user created it is not here anymore.
With this in general there is no need for a Wiki like the Archwiki, we do not have the manpower to handle this, and it does not make sense at all in addition to recreate something that already exist.
The Idea of Discovery is not to create a complete wiki with everything, its about having tutorials for things directly related to EndeavourOS like Dracut and the installer.
In addition there is the issue that ArchWiki is very straight forward a general information wiki it does not have step-by-step tutorials, Discovery has some of such, for things like setup of virtualbox and others. With this Discovery is maintained by some people, but surely have some parts not 100% on the latest changes. It is always welcome to got hints, what will make it easy for me and the other maintainers to correct Discovery articles, or add info.
Long story short..
It would be a nice addition to have a Gaming Wiki that is open for changes like a real wiki (Discovery is not), I would not agree that this should be open for everything aside Gaming and setup needed for Gaming, nor we should replace Discovery with this.
4 Likes
Yes! Discovery articles could be integrated into “Snippet” knowledge-base, such that
- Snippets contributed cite Discovery articles
- Questions asked by the community, receive citations from snippets, so that a user could navigate them until she reaches Discovery.
- Tracking most cited snippets.
If a snippet is highly cited, then that could be a signal to contribute it as a Discovery article! Also, upon answering a question, if someone raised a snippet needs to be updated, then this coud signal a Discovery article needs update.
As a result, Discovery articles get progressively built and updated, as more users questions are answered.
Maintainers could restrict the kind of contributions “Snippet” knowledge-base receives. We could even use AI for classifying whether a contribution conforms to maintainers selected topics.
The problem with the Arch wiki is that they make it too technical. It doesn’t have to be. They provide information but don’t exactly always explain how to use it and instead provide links to other information for which it is the same. It doesn’t have value if one doesn’t know what is required of the information they are providing. What’s missing is everything in between that the person whose providing this information already knows. The person reading it doesn’t. They don’t have the knowledge, experience, expertise or sometimes and in many cases the basics needed to even understand how to go about using the information provided. The Arch wiki is great for those who have this knowledge and expertise but not so much for the less than average computer user. I myself have gotten used to the Arch wiki but in the beginning i hated it. Now I only cringe when i read stuff that I can’t quite wrap my head around. But i persevere! At least I realize how little I know in the grand scheme of linux and especially all things Arch. 
3 Likes