13,208
edits
Talk:Main Page/Archive/2006-2011: Difference between revisions
Jump to navigation
Jump to search
Talk:Main Page/Archive/2006-2011 (view source)
Revision as of 11:57, 9 February 2012
, 9 February 2012Gone through the entire history, signing unsigned comments and adding indentation at a few places, intending to later sort the sections chronologically after first posting. A few posts slipped between.
(Gone through the entire history, signing unsigned comments and adding indentation at a few places, intending to later sort the sections chronologically after first posting. A few posts slipped between.) |
|||
| Line 2: | Line 2: | ||
Every day a new spam are edit on this WIKI, It's so Boring. Personnaly i havn't right to delete account, and can only delete the Spam. | Every day a new spam are edit on this WIKI, It's so Boring. Personnaly i havn't right to delete account, and can only delete the Spam. | ||
But if administrator of the wiki can install some of this extension to prevent spamming, it could be very nice... I know there some Capcha installed, apparently is not enough | But if administrator of the wiki can install some of this extension to prevent spamming, it could be very nice... I know there some Capcha installed, apparently is not enough | ||
* http://www.mediawiki.org/wiki/Anti-spam_features | * http://www.mediawiki.org/wiki/Anti-spam_features | ||
and please read this page http://www.mediawiki.org/wiki/Manual:Combating_spam | and please read this page http://www.mediawiki.org/wiki/Manual:Combating_spam | ||
Thanks. --[[User:Lolalilo|Lolalilo]] 01:58, 11 February 2011 (EST) | |||
= MediaWiki Extension Requests = | = MediaWiki Extension Requests = | ||
| Line 10: | Line 12: | ||
* 02/2010: http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi - syntax highlighting (for XML, C, C++, Nasal) | * 02/2010: http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi - syntax highlighting (for XML, C, C++, Nasal) | ||
* 02/2010: http://www.mediawiki.org/wiki/Extension:Drafts - allow users to save drafts of articles | * 02/2010: http://www.mediawiki.org/wiki/Extension:Drafts - allow users to save drafts of articles | ||
{{unsigned2|17:01, 20 February 2010|MILSTD}} | |||
= CVS vs. Addon-aircraft = | = CVS vs. Addon-aircraft = | ||
| Line 30: | Line 33: | ||
= Translating the wiki (10/2009) = | = Translating the wiki (10/2009) = | ||
There needs to be a dedicated article about translating individual articles, especially about prioritizing certain articles (based on the [http://wiki.flightgear.org/index.php/Special:Statistics stats]) and about translation strategies. Also, there should probably be a couple of new templates specifically to be used for translation efforts, such as "translation request" and "translation in progress", as well as "translation help or review required".--[[User:MILSTD|MILSTD]] 18:10, 1 October 2009 (UTC) | There needs to be a dedicated article about translating individual articles, especially about prioritizing certain articles (based on the [http://wiki.flightgear.org/index.php/Special:Statistics stats]) and about translation strategies. Also, there should probably be a couple of new templates specifically to be used for translation efforts, such as "translation request" and "translation in progress", as well as "translation help or review required".--[[User:MILSTD|MILSTD]] 18:10, 1 October 2009 (UTC) | ||
Also see: http://www.mediawiki.org/wiki/Extension:Translate | Ok, apparently there's something in the works [[Help:Translate]] {{unsigned2|18:12, 1 October 2009|MILSTD}} | ||
Also see: http://www.mediawiki.org/wiki/Extension:Translate {{unsigned2|17:01, 20 February 2010|MILSTD}} | |||
= Planned Wiki Changes & Todo = | = Planned Wiki Changes & Todo = | ||
Please see [[Wiki Plans and Todo]] | Please see [[Wiki Plans and Todo]] {{unsigned2|15:45, 8 April 2009|MILSTD}} | ||
= Making the manual accessible via wiki software = | = Making the manual accessible via wiki software = | ||
| Line 41: | Line 45: | ||
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/). | ||
As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST) | :As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST) | ||
= Using a dedicated FAQ database = | = Using a dedicated FAQ database = | ||
| Line 49: | Line 53: | ||
= Using a dedicated bug tracker = | = Using a dedicated bug tracker = | ||
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) | ||
:It's better to have one consolidated source of information for both bugs and descriptions. For now, user has to search through mailing lists, forums, user manuals (even not a single user manual, but several) and this wiki. It's absolutely not convinient for both users (they spend lot's of time searching required information) and developers (they spend lot's of time updating and syncronizing certain information in various sources). | |||
:This wiki is suitable for bug tracking too. Users can provide feedback in a convinient form. They just open the corresponding page and add their bug to the list. Developers can respond to the posted bugs right away. Mailing lists are a lot less user-friendly and effective and a lot less popular among users (not developers) in this regard, this is the reason why some bugs may stay unreported and why many users forget about FlightGear as soon as they run into a problem. | |||
:Unfortunately, it seems to me, this wiki is not popular among developers and users. -- [[User:Alfozavr|Alfozavr]] 06:59, 17 June 2007 (EDT) | |||
::10/2009: Bug tracking has -again- become an issue [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23799.html] {{unsigned2|18:13, 1 October 2009|MILSTD}} | |||
:::NOTE: As of 02/2010, a google code tracker is used for bug tracking: http://code.google.com/p/flightgear-bugs/issues/list | |||
:::Also, see this wikimedia extension: http://www.mediawiki.org/wiki/Extension:IssueTracker | |||
:::{{unsigned2|17:01, 20 February 2010|MILSTD}} | |||
= Backups = | = Backups = | ||
| Line 68: | Line 71: | ||
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST) | --[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST) | ||
Yes, there are daily backups of the [http://hellosimon.org/backups code] and of the [http://hellosimon.org/backups/mysql database]. We also have off-site backups. [[User:Hellosimon|Hellosimon]] 17:04, 4 February 2008 (EST) | :Yes, there are daily backups of the [http://hellosimon.org/backups code] and of the [http://hellosimon.org/backups/mysql database]. We also have off-site backups. [[User:Hellosimon|Hellosimon]] 17:04, 4 February 2008 (EST) | ||
= Updates = | = Updates = | ||
| Line 86: | Line 88: | ||
* needs screenshots | * needs screenshots | ||
* needs better layout | * needs better layout | ||
{{unsigned2|03:32, 16 May 2009|MILSTD}} | |||
Also a template for the FlightGear news would be perfect to keep them synchronized on the different pages (especially the translations of the Main Page) | :Also a template for the FlightGear news would be perfect to keep them synchronized on the different pages (especially the translations of the Main Page) {{unsigned2|21:42, 17 September 2011|Hamster}} | ||
:I've just created a [[Template:News|news template]] and added it to all main pages. Please check for your own language whether this works and is up to date (some are not). For the other templates, we do have [[Template:Cleanup]]. And I just created [[Template:Image requested]] and added a "reason" variable to the cleanup template (where you can say it needs a spelling check) | ::I've just created a [[Template:News|news template]] and added it to all main pages. Please check for your own language whether this works and is up to date (some are not). For the other templates, we do have [[Template:Cleanup]]. And I just created [[Template:Image requested]] and added a "reason" variable to the cleanup template (where you can say it needs a spelling check) | ||
:[[User:Gijs|Gijs]] 07:12, 18 September 2011 (EDT) | ::[[User:Gijs|Gijs]] 07:12, 18 September 2011 (EDT) | ||
:PS: Please sign your messages on talk pages with <nowiki>~~~~</nowiki> | ::PS: Please sign your messages on talk pages with <nowiki>~~~~</nowiki> | ||
== Syntax Highlighting == | == Syntax Highlighting == | ||
* what about some sort of true syntax-highlighting module, that would properly highlight XML & C++ ? | * what about some sort of true syntax-highlighting module, that would properly highlight XML & C++ ? {{unsigned2|15:43, 10 March 2008|MILSTD}} | ||
: This can be achieved using the [http://qbnz.com/highlighter/ GeSHi] syntax highlighting module for php. {{unsigned2|09:12, 13 October 2008|MILSTD}} | |||
:: With XML, C, C++ and Nasal source code being increasingly used on various wiki pages, this would be an important and huge step towards improving this wiki! {{unsigned2|03:30, 16 May 2009|MILSTD}} | |||
== PDF Export == | == PDF Export == | ||
* PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF] | * PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF] {{unsigned2|14:38, 31 January 2008|MILSTD}} | ||
* http://www.mediawiki.org/wiki/Extension:WikiPDF - WikiPDF is an extension for MediaWiki, which converts MediaWiki-articles to LaTeX or PDF. | :* http://www.mediawiki.org/wiki/Extension:WikiPDF - WikiPDF is an extension for MediaWiki, which converts MediaWiki-articles to LaTeX or PDF. {{unsigned2|15:07, 28 December 2009|MILSTD}} | ||
| Line 114: | Line 117: | ||
* 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? | ||
07/2009: Even more talk about the merits of supporting PDF exports for wiki articles: [http://flightgear.org/forums/viewtopic.php?f=6&t=5201&p=39847#p39847] | :07/2009: Even more talk about the merits of supporting PDF exports for wiki articles: [http://flightgear.org/forums/viewtopic.php?f=6&t=5201&p=39847#p39847] {{unsigned2|14:36, 9 July 2009|MILSTD}} | ||
12/2009: Also see [http://www.mediawiki.org/wiki/DocBook_XML_export] for details about exporting to docbook/XML | ::12/2009: Also see [http://www.mediawiki.org/wiki/DocBook_XML_export] for details about exporting to docbook/XML {{unsigned2|15:05, 28 December 2009|MILSTD}} | ||
= Issues = | = Issues = | ||