Talk:Main Page/Archive/2006-2011: Difference between revisions

Jump to navigation Jump to search
m
restructuring and adding link to wikimedia plugin for PDF exports
No edit summary
m (restructuring and adding link to wikimedia plugin for PDF exports)
Line 1: Line 1:
= Initial ramblings=
Sorry, I don't want to junk up the main page with someone's opinion on "the manual" and the wiki documentation.  [[User:Hellosimon|Hellosimon]] 10:41, 5 June 2006 (PDT)
Sorry, I don't want to junk up the main page with someone's opinion on "the manual" and the wiki documentation.  [[User:Hellosimon|Hellosimon]] 10:41, 5 June 2006 (PDT)


Line 7: Line 8:
There's simply a very clear relationship between "The Manual" and "the wiki", if you fail to recognize this, your contribution (that is, this wiki) -even though very much needed and extremely worthwhile- is condemned to fail eventually.  
There's simply a very clear relationship between "The Manual" and "the wiki", if you fail to recognize this, your contribution (that is, this wiki) -even though very much needed and extremely worthwhile- is condemned to fail eventually.  


== Making the manual accessible via wiki software ==
On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.  
On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.  
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).


== Using a dedicated FAQ database ==
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).


Line 17: Line 20:
This assumption is correct. The manual is the center piece of the FlightGear user documentation, so does anyone have a suggestion (one that makes sense) on how to deal with my comments aside from "removing it" or "moving it into negligence/insignificance" ?
This assumption is correct. The manual is the center piece of the FlightGear user documentation, so does anyone have a suggestion (one that makes sense) on how to deal with my comments aside from "removing it" or "moving it into negligence/insignificance" ?
Martin.
Martin.
 
== Using a dedicated bug tracker ==
Martin's text has been placed (not by me) in the paragraphs at the top.  I rather like this compromise and hope it works for everyone.  I agree a bugtracker would be ideal - didn't someone start one?  Also, if anyone wants to grant ftp access to a server, I'll gladly cron a script to upload the backup tarball.  I have it backed up to multiple locations in the meantime.  
Martin's text has been placed (not by me) in the paragraphs at the top.  I rather like this compromise and hope it works for everyone.  I agree a bugtracker would be ideal - didn't someone start one?  Also, if anyone wants to grant ftp access to a server, I'll gladly cron a script to upload the backup tarball.  I have it backed up to multiple locations in the meantime.  
- [[User:Hellosimon|Hellosimon]] 11:36, 11 June 2006 (EDT)
- [[User:Hellosimon|Hellosimon]] 11:36, 11 June 2006 (EDT)


A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)
A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)
= PDF Export Facilities =
* [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF]


Regarding the manual: isn't there a possibility to export wikimedia pages to PDF format? That way, we could maintain the whole manual via this wiki. Any thoughts?--[[User:FlightZilla|FlightZilla]] 18:10, 17 June 2006 (EDT)
Regarding the manual: isn't there a possibility to export wikimedia pages to PDF format? That way, we could maintain the whole manual via this wiki. Any thoughts?--[[User:FlightZilla|FlightZilla]] 18:10, 17 June 2006 (EDT)
Line 34: Line 39:
I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
= Limiting access rights =
* how to define and limit editing rights for certain users?
* how to define and limit editing rights for certain users?


2,561

edits

Navigation menu