Talk:Troubleshooting problems: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
mNo edit summary
 
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Todo: to be added =
* http://www.flightgear.org/forums/viewtopic.php?t=614
* http://www.flightgear.org/forums/viewtopic.php?t=1448
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16757.html
= KnowledgeBase System? =
Not sure if the purpose of this page wouldn't be better being dealt with if the whole thing would be handled via a database-driven knowledge base, there are really numerous free/open source knowledge base packages available over at freshmeat.net or sourceforge.net. I think we should check out the various existing possibilities (that is, search sourceforge/freshmeat for "knowledgebase", "knowledge base", "support center", "help center" etc) so that we can chose a package that will suit our needs. This would enable us to provide a dynamic frontend for users to have them fill in their data and being presented with possible solution paths, eventually this might in fact end up being pretty comprehensive. Any thoughts? --[[User:FlightZilla|FlightZilla]] 08:38, 18 June 2006 (EDT)
Not sure if the purpose of this page wouldn't be better being dealt with if the whole thing would be handled via a database-driven knowledge base, there are really numerous free/open source knowledge base packages available over at freshmeat.net or sourceforge.net. I think we should check out the various existing possibilities (that is, search sourceforge/freshmeat for "knowledgebase", "knowledge base", "support center", "help center" etc) so that we can chose a package that will suit our needs. This would enable us to provide a dynamic frontend for users to have them fill in their data and being presented with possible solution paths, eventually this might in fact end up being pretty comprehensive. Any thoughts? --[[User:FlightZilla|FlightZilla]] 08:38, 18 June 2006 (EDT)
Background: http://en.wikipedia.org/wiki/Knowledge_base
== Collection of Open Source KnowledgeBase Systems ==
* http://freshmeat.net/projects/knowledgeroot/
* http://freshmeat.net/projects/sitr/
* http://freshmeat.net/projects/zbkb/
* http://freshmeat.net/projects/powl/
* http://freshmeat.net/projects/lore/
* http://freshmeat.net/projects/kbpublisher/
* http://freshmeat.net/projects/mindmeld/
* http://freshmeat.net/projects/pbshelpdesk/
* http://freshmeat.net/projects/daath/
Feel free to suggest other systems, as well as discuss pros & cons of the individual systems.
=== Requirements ===
Let's try to determine what requirements should be met by a KB system for FlightGear-specific issues.
* optional multi-language support
* i18n
* interactive questioning for pre-configurable items (i.e. host, platform, OS, driver version, compiler etc)
* full text search
* nested solution paths
* PDF export for all KB entries
* fully browsable

Latest revision as of 11:49, 10 July 2010

Todo: to be added

KnowledgeBase System?

Not sure if the purpose of this page wouldn't be better being dealt with if the whole thing would be handled via a database-driven knowledge base, there are really numerous free/open source knowledge base packages available over at freshmeat.net or sourceforge.net. I think we should check out the various existing possibilities (that is, search sourceforge/freshmeat for "knowledgebase", "knowledge base", "support center", "help center" etc) so that we can chose a package that will suit our needs. This would enable us to provide a dynamic frontend for users to have them fill in their data and being presented with possible solution paths, eventually this might in fact end up being pretty comprehensive. Any thoughts? --FlightZilla 08:38, 18 June 2006 (EDT)

Background: http://en.wikipedia.org/wiki/Knowledge_base

Collection of Open Source KnowledgeBase Systems

Feel free to suggest other systems, as well as discuss pros & cons of the individual systems.

Requirements

Let's try to determine what requirements should be met by a KB system for FlightGear-specific issues.

  • optional multi-language support
  • i18n
  • interactive questioning for pre-configurable items (i.e. host, platform, OS, driver version, compiler etc)
  • full text search
  • nested solution paths
  • PDF export for all KB entries
  • fully browsable