FlightGear wiki - User contributions [en]

FlightGear wiki:Village pump

2025-11-13T22:06:29Z

Bugman: /* Default text in Template:Repo link */

__NEWSECTIONLINK__
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

__TOC__

== MediaWiki updated to 1.39.6 ==

We have updated MediaWiki to its latest LTS version 1.39.6 today. Although we've tested the update, chances are that we've missed certain scenarios or features. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:31, 30 January 2024 (UTC)

== Embedded YouTube videos broken ==

It seems that the [[mw:Extension:EmbedVideo|EmbedVideo extension]] was removed at some point. Consequently, pages such as [[Howto:Creating FlightGear Promo Videos]] are broken. At present, the best replacements seems to be [[mw:Extension:EmbedVideo_(fork)|a fork]] and [[mw:Extension:YouTube|Extension:YouTube]].

—'''''[[User:Red Leader|Red Leader]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 19:21, 30 January 2024 (UTC)

: Hi,
: Thanks for the report. It was introduced by today's update, but should be fixed now.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 21:21, 30 January 2024 (UTC)

:: Confirmed, thanks. And I’d completely forgotten about {{[[Template:Wikipedia|wikipedia]]}}. 😅
:: '''''[[User:Red Leader|Red Leader]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 21:57, 30 January 2024 (UTC)

== Forum registration problem ==

Hello,
I would like to register on the forum, but I tried several times without success. I sent an email to the administrator some time ago, but it seems to have been lost. I don't know what to do, is there somebody here who could help? Please tell me if you need additional information.
Thanks very much in advance. [[User:Kestrel|Kestrel]] ([[User talk:Kestrel|talk]]) 13:14, 25 March 2024 (UTC)

: Hi,
: That's unfortunate! You can find my email address at https://forum.flightgear.org/contact.php Please try again if you've done that before, I'll actively monitor the address for any incoming messages, and let me know if you don't get a reply.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:01, 25 March 2024 (UTC) (forum admin)

== Sidebar link for "Build server" is broken ==

Hello,

Just wanted to bring to someones attention that the URL for "Build server" currently 404s. Not sure if this resource still exists or if its URL has changed.

Cheers!
-Joshua

: Hi Joshua,
: The URL is still correct, but the build server is temporarily down due to a server failure. It's being worked on, so should be back up "soon".
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:29, 3 September 2024 (UTC)

== FlightGear Wikipedia article image needs correctly sourced Flightgear wiki screenshot ==
https://en.wikipedia.org/wiki/FlightGear

The image used for the Flightgear Wikipedia article appears to have been deleted, because it was sourced from the following Flightgear-wiki screenshot page:

[[:File:Bo 105 over Sint Marteen.png]]

which referred to an imgur link instead of the following thread, which gives a CC license based on a google search of the file name:

https://forum.flightgear.org/viewtopic.php?f=88&t=32163&start=0

Discussion on Wikipedia:

https://en.wikipedia.org/wiki/Wikipedia:Files_for_discussion/2024_December_7#File:FlightGear_Flight_Sim_Bo_105_over_Sint_Marteen.png

> ''Subsequent comments should be made on the appropriate discussion page (such as the file's talk page or in a [https://en.wikipedia.org/wiki/Wikipedia:Deletion_review deletion review]).''

The person who uploaded it, or someone from the wiki, should ideally fix the FlightGear wiki page, and do a deletion review for the Wikipedia file. The file may have been used in multiple pages since screenshots are uncommon on Wikipedia due to proprietary apps. Feel free to remove this comment once it's taken care of. Good luck

== Issues with three templates ==

Hi,

The [[Template:Fgmeta_commit|fgmeta commit]] template appears to be broken. It used to work in the first ''Note'' [[Scripted_Compilation_on_Linux_Debian/Ubuntu#For_the_curious:_the_SSH_way|here]] (see the URL).

Also, I tried to use [[Template:Repo_link#Site:_Generic]] to create a link to the [https://gitlab.kitware.com/cmake/cmake.git CMake repo], but didn't manage: IIRC, the link text was empty.

Finally, [[Template:Fgmeta_source]] doesn't seem to to what the doc. says for ''simplepath'': with
<pre><nowiki>{{fgmeta source
| path = download_and_compile.sh
| simplepath = 1
}}</nowiki></pre>

the link text starts with a slash, so I used
<pre><nowiki>{{fgmeta source
| path = download_and_compile.sh
| text = download_and_compile.sh
}}</nowiki></pre>
which is of course more redundant.

Thanks for considering! :-)

[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

: Good catch. I need to look into that one. I may not have coded the commit part of GitLab into the master {{tl|repo_link}} template.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:41, 13 March 2025 (UTC)

:: All fixed. It was quite simple - the {{tl|fgmeta_source}} template was missing the <code>proj</code> parameter. I've also fixed {{tl|fgmeta_clone}}.

:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:53, 13 March 2025 (UTC)

::: Thanks for the reply and fixes, Bugman! (And sorry for the delay, I didn't see any notification...) I see the first item is indeed addressed. Regarding the second item, well, I see no place where I'd really want to use this now on the d&c page, so didn't test it. As for the third one, I still get <code>/download_and_compile.sh</code> in the Preview when I try the above {{tl|fgmeta_source}} snippet with <code>simplepath = 1</code>.

::: I looked at {{tl|fgmeta_clone}} too; it looks nice but seems to default to the <code>git://</code> protocol. Would it be possible to make it default to using <code>https://</code>? Thanks again. :-)

::: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

:::: Not a problem. For the <code>simplepath</code> parameter, that is the designed behaviour in the {{tl|repo link}} template. In most cases our repositories have complex directory structures and the desired output is the absolute file path, removing the protocol and URL parts of the path. Do you wish to simply have the file name there? No one had asked for that before, so I never added an option for that. In the case of the source repositories, you often want to remove the first part of the absolute path so that for example in SimGear, {{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|simplepath=1}} (<nowiki>{{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|simplepath=1}}</nowiki>) would be shown as {{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|text=scene/util/QuadTreeBuilder.hxx}} (<nowiki>{{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|text=scene/util/QuadTreeBuilder.hxx}}</nowiki>. This is not scriptable in MediaWiki so I left it all for the text parameter.

:::: For the protocol, I have now added the <code>protocol</code> parameter. E.g. <nowiki>{{fgmeta clone | protocol = https}}</nowiki>. That will give <code>{{fgmeta clone | protocol = https}}</code> (as of today generated as <code><nowiki>git clone https://gitlab.com/flightgear/fgmeta.git</nowiki></code>).

:::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 08:51, 24 March 2025 (UTC)

::::: Thanks Bugman, I've updated the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|download_and_compile.sh page]] to use <code><nowiki>{{fgmeta clone | protocol = https}}</nowiki></code> as you proposed; it works great. For the link to download_and_compile.sh, I can continue to use <code><nowiki>{{fgmeta source | path = download_and_compile.sh | text = download_and_compile.sh}}</nowiki></code>, no problem.

::::: As far as I'm concerned, everything is resolved here, so this thread/section can be deleted if someone wants to “clean up”.

::::: ''Other subject:'' the only remaining thing is that I didn't receive any notification, neither for your replies here nor for the January changes by [[User:Jebba|Jebba]] to the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|download_and_compile.sh page]] that is on my watchlist. I used to receive email notifications for these things years ago, haven't changed my preferences regarding this and don't see any setting that would explain why I don't receive these notifications anymore. Maybe email sending by the wiki software is not quite well configured according to current standards (SPF, DKIM, DMARC)?

::::: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

== Improve the 'simgear clone', 'flightgear clone' and 'fgdata clone' templates ==

Hi,

In order to improve [[Fedora_Packages_and_Compiling]], it would be nice to have the <code><nowiki>{{simgear clone}}</nowiki></code>, <code><nowiki>{{flightgear clone}}</nowiki></code> and <code><nowiki>{{fgdata clone}}</nowiki></code> templates on par with <code><nowiki>{{fgmeta clone}}</nowiki></code> (support for the <code>protocol</code> parameter, etc.). I tried

<nowiki>{{simgear clone | protocol = https | opt = --single-branch --branch release/2024.1 | post = simgear}}</nowiki>

but it doesn't seem to work, as the preview shows this:

<nowiki>git clone --single-branch --branch release/2024.1 git://gitlab.com simgear</nowiki>

(ditto with <code>flightear clone</code> and <code>fgdata clone</code>). Thanks in advance :-)

[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

: I needed a while to work out the best strategy for these changes. I've now gone through all of the {{tl|repo link}} cloning subtemplates listed on {{tl|repo link/doc related}} and added the <code>project</code> parameter to the templates and the optional <code>protocol</code> parameter. These changes were required as the <code>gl</code> section of the {{tl|repo_link}} template is constructed differently to the <code>sf</code> section. I've also updated the git cloning documentation {{tl|repo link/doc git clone}}. I hope this covers everything you need.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 07:48, 1 April 2025 (UTC)

:: Thanks a lot, Bugman, this works great! Your changes allowed me to perform [https://wiki.flightgear.org/w/index.php?title=Fedora_Packages_and_Compiling&type=revision&diff=141687&oldid=141513 this edit] in [[Fedora_Packages_and_Compiling]]. The only remaining <code>git clone</code> command written in full on that page is for FG's fork of OpenSceneGraph at GitLab. I understand that choosing a proper name for an applicable <code><nowiki>{{... clone}}</nowiki></code> template probably requires some careful thinking... ;-)

:: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

== Default text in Template:Repo link ==

Hi,

The default ''text'' in {{tl|Repo link}} gives somewhat pleasant link texts such as
flightgear/flightgear/src/Scripting/NasalSys.cxx
when the ''site'' is <code>sourceforge</code>, however the result looks like a bug for other sites (though I understand this may be as intended). To be clear, the URLs are correct but the default link texts look weird because they start with the unqualified site name rather than the fully-qualified domain name. For instance,
{{obr}}fgmeta source{{cbr}}
yields [https://gitlab.com/flightgear/fgmeta gitlab/flightgear/fgmeta/next] rather than [https://gitlab.com/flightgear/fgmeta gitlab.com/flightgear/fgmeta/next]. I suggest to replace <code>gitlab</code> with <code>gitlab.com</code> in the default text (where the HTML comment says “Site advertising”) and do the same for <code>github</code>.

Note: the Gitorious web site doesn't exist anymore, maybe that should be removed from the template?

Thanks for considering; I can do the replacement if you wish.

[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 10:38, 12 November 2025 (UTC)

: Sounds sensible, so please go ahead!
: Regarding Gitorious, it may be nice to link to an archived version of the repos, such as https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://gitorious.org/flightgear/fgdata.git&visit_type=git Altough this only makes sense for repos or branches that are not part of our current GitLab...
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:58, 12 November 2025 (UTC)

:: [https://wiki.flightgear.org/w/index.php?title=Template:Repo_link&action=history Done], thanks Gijs!
::

:: One should be careful using this, though, because the resulting link ''texts'' may be non-existing URLs (after prepending the protocol) despite looking like valid ones, as shown by the first example in [[User:Rominet/Sandbox#FGMeta-Python repo templates]]!

:: So, to avoid people getting trapped by this, maybe the default link text should start with something like <code>[GitLab]/...</code> rather than the <code>gitlab.com/...</code> I just put (to make it clear that such link texts are not supposed to be “Internet addresses”).
:: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 16:20, 12 November 2025 (UTC)

: That's a good idea. Note for Gitorious - I added this because there are a number of historical documents/pages that refer to developments that occurred on Gitorious which were not migrated to SourceForge. I originally made the Gitorious links work by pointing to the archive by the Internet Archive (see [[Gitorious]]). However that archive has been offline for a few years now. The Internet Archive are storing all the data so it may return one day.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 22:06, 13 November 2025 (UTC)

FlightGear wiki:Village pump

2025-04-01T07:48:39Z

Bugman: /* Improve the 'simgear clone', 'flightgear clone' and 'fgdata clone' templates */

Template:Terrafs clone

2025-04-01T07:38:20Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = terrafs
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = TerraFS
| repo = terrafs
| post = terrafs
}}

</noinclude>

Template:Terragear clone

2025-04-01T07:37:20Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = terragear
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = TerraGear
| repo = terragear
| post = terragear
}}

</noinclude>

Template:Sceneryweb clone

2025-04-01T07:37:07Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = sceneryweb
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = SceneryWeb
| repo = sceneryweb
| post = sceneryweb
}}

</noinclude>

Template:Openradar clone

2025-04-01T07:36:56Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = openradar
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = OpenRadar
| repo = openradar
| post = openradar
}}

</noinclude>

Template:Fgcom clone

2025-04-01T07:36:32Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = fgcom
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FGCom
| repo = fgcom
| post = fgcom
}}

</noinclude>

Template:Fgaddon co

2025-04-01T07:35:38Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = sf
| cmd = svn co
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol = {{#if: {{{login|}}} | svn+ssh | https}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type = svn
| proj = flightgear
| repo = fgaddon
| branch{{#if:{{{branch|{{{b|{{{1|}}}}}}}}}||NULL}} = {{{branch|{{{b|{{{1}}}}}}}}}
| path{{#if:{{{path|{{{f|{{{2|}}}}}}}}}||NULL}} = {{{path|{{{f|{{{2}}}}}}}}}
| post = {{{post|fgaddon}}}
| full = 1
}}}}<noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
To provide a consistent representation of the command to checkout the FGAddon subversion repository.

{{repo link/doc usage
| template = fgaddon co
| value_cmd = svn co
| opt = 1
| login = 1
| branch = 1 | short_branch = b | pos_branch = 1
| path = 1 | short_path = f | pos_path = 2
| post = 1 | default_post = fgaddon
| sf = 1
| svn = 1
| break = 0
}}

{{repo link/doc plain text}}

== Examples ==
=== Checkout of trunk with user name ===
{{obr}}fgaddon co
{{!}} opt = --username <username>
{{!}} post = fgaddon
{{cbr}}

{{fgaddon co
| opt = --username <username>
| post = fgaddon
}}

=== Checkout of aircraft from a branch ===
{{obr}}fgaddon co
{{!}} branch = branches/release-3.4.0
{{!}} path = Aircraft/V22-Osprey
{{!}} post =
{{cbr}}

{{fgaddon co
| branch = branches/release-3.4.0
| path = Aircraft/V22-Osprey
| post =
}}

=== Checkout of aircraft as a user ===
{{obr}}fgaddon co
{{!}} login = <username>
{{!}} path = Aircraft/wrightFlyer1903
{{!}} post =
{{cbr}}

{{fgaddon co
| login = <username>
| path = Aircraft/wrightFlyer1903
| post =
}}

=== Aliased parameters ===
{{obr}}fgaddon co
{{!}} b = branches/release-3.2.0
{{!}} f = Aircraft/V22-Osprey
{{cbr}}.

{{fgaddon co
| b = branches/release-3.2.0
| f = Aircraft/V22-Osprey
}}.

=== Numbered parameters ===
{{obr}}fgaddon co {{!}} branches/release-3.2.0 {{!}} Aircraft/V22-Osprey {{cbr}}.

{{fgaddon co | branches/release-3.2.0 | Aircraft/V22-Osprey }}.

== Related templates ==
{{repo link/doc related}}

}}

[[Category:SCM Instruction Templates]]
</noinclude>

Template:Fgdata clone

2025-04-01T07:35:01Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = fgdata
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FGData
| repo = fgdata
| post = fgdata
}}

</noinclude>

Template:Simgear clone

2025-04-01T07:34:43Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = simgear
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = SimGear
| repo = simgear
| post = simgear
}}

</noinclude>

Template:Windows-3rd-party clone

2025-04-01T07:33:05Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = windows-3rd-party
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = Windows-3rd-party
| repo = windows-3rd-party
| post = windows-3rd-party
}}

</noinclude>

Template:Terrafs clone

2025-04-01T07:32:26Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = terrafs
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = TerraFS
| repo = terrafs
| post = terrafs
}}

</noinclude>

Template:Terragear clone

2025-04-01T07:31:44Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = terragear
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = TerraGear
| repo = terragear
| post = terragear
}}

</noinclude>

Template:Sceneryweb clone

2025-04-01T07:31:10Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = sceneryweb
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = SceneryWeb
| repo = sceneryweb
| post = sceneryweb
}}

</noinclude>

Template:Openradar clone

2025-04-01T07:30:26Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = openradar
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = OpenRadar
| repo = openradar
| post = openradar
}}

</noinclude>

Template:Fgcom clone

2025-04-01T07:29:30Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = fgcom
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FGCom
| repo = fgcom
| post = fgcom
}}

</noinclude>

Template:Fgdata clone

2025-04-01T07:28:04Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = fgdata
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FGData
| repo = fgdata
| post = fgdata
}}

</noinclude>

Template:Simgear clone

2025-04-01T07:27:15Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = simgear
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = SimGear
| repo = simgear
| post = simgear
}}

</noinclude>

Template:Repo link/doc git clone

2025-04-01T07:24:44Z

Bugman: Updated the documentation to include the protocol parameter.

{{Informative template|1=
__NOTOC__
== Goal ==
To provide a consistent representation of the command to clone the [[{{{label|MISSING}}}]] git repository. It is a subtemplate of the master {{tl|repo link}} template designed to be specific for the FlightGear repository.

{{repo link/doc usage
| template = {{{repo|MISSING}}} clone
| value_cmd = git clone
| opt = 1
| protocol = 1
| post = 1
| break = 0
}}

{{repo link/doc plain text}}

== Examples ==
{{obr}}{{{repo|MISSING}}} clone
{{!}} opt = {{{opt|-v}}}
{{!}} post = {{{post|MISSING}}}
{{cbr}}

{{{{{repo|MISSING}}} clone
| opt = {{{opt|-v}}}
| post = {{{post|MISSING}}}
}}

Specifying the <code>git</code> protocol:
{{obr}}{{{repo|MISSING}}} clone
{{!}} opt = {{{opt|-v}}}
{{!}} protocol = git
{{!}} post = {{{post|MISSING}}}
{{cbr}}

{{{{{repo|MISSING}}} clone
| opt = {{{opt|-v}}}
| protocol = git
| post = {{{post|MISSING}}}
}}

Specifying the <code>https</code> protocol:
{{obr}}{{{repo|MISSING}}} clone
{{!}} opt = {{{opt|-v}}}
{{!}} protocol = https
{{!}} post = {{{post|MISSING}}}
{{cbr}}

{{{{{repo|MISSING}}} clone
| opt = {{{opt|-v}}}
| protocol = https
| post = {{{post|MISSING}}}
}}

== Related templates ==
{{repo link/doc related}}

}}

[[Category:Repository link templates]]
[[Category:SCM Instruction Templates]]

Template:Flightgear clone

2025-04-01T07:14:39Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = flightgear
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FlightGear
| repo = flightgear
| post = flightgear
}}

</noinclude>

Template:Flightgear clone

2025-04-01T07:00:30Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| repo = flightgear
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FlightGear
| repo = flightgear
| post = flightgear
}}

</noinclude>

FlightGear wiki:Village pump

2025-03-24T08:51:29Z

Bugman:

Template:Fgmeta clone

2025-03-24T08:49:17Z

Bugman: Addition of the protocol parameter to chose between https:// and git://

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| type = git
| proj = flightgear
| repo = fgmeta
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FGMeta
| repo = fgmeta
| opt = --recursive
| post = fgmeta
}}

</noinclude>

FlightGear wiki:Village pump

2025-03-13T15:53:57Z

Bugman: /* Issues with three templates */

Template:Fgmeta clone

2025-03-13T15:50:28Z

Bugman: Added the missing project parameter.

{{#tag:nowiki|{{repo link
| site = {{project infrastructure|abbrev}}
| cmd = git clone
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol = git
| type = git
| proj = flightgear
| repo = fgmeta
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| full = 1
}}}}<noinclude>

{{repo link/doc git clone
| label = FGMeta
| repo = fgmeta
| opt = --recursive
| post = fgmeta
}}

</noinclude>

Template:Fgmeta commit

2025-03-13T15:48:24Z

Bugman: Added the missing project parameter.

{{repo link
| site = {{project infrastructure|abbrev}}
| proj = flightgear
| repo = fgmeta
| commit = {{{1|next}}}
| view = commit
| text = {{#if: {{{1|}}}
| {{{text|{{{t|{{{2|FGMeta commit {{{1}}} }}} }}} }}}
| <big style="color:red;">Missing parameter '''commit'''</big>
}}
}}<noinclude>

{{repo link/doc commit
| label = FGMeta
| repo = fgmeta
| git = 1
| svn = 0
| eg1commit = c19096
| eg2intro = The
| eg2commit = 0cd467
| eg2text = FlightGear 2016.2.0 release
| eg2post = has now been tagged
}}

</noinclude>

FlightGear wiki:Village pump

2025-03-13T15:41:28Z

Bugman: /* Issues with three templates */

Template:Flightgear source

2025-02-14T10:19:35Z

Bugman: Reverted edits by Gijs (talk) to last revision by Bugman

{{repo link
| site = {{project infrastructure|abbrev}}
| cmd{{#if:{{{cmd|}}}||NULL}} = {{{cmd}}}
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type{{#if:{{{type|}}}||NULL}} = {{{type}}}
| proj = flightgear
| repo = flightgear
| branch{{#if:{{{branch|{{{b|}}}}}}||NULL}} = {{{branch|{{{b}}}}}}
| tag{{#if:{{{tag|}}}||NULL}} = {{{tag}}}
| path{{#if:{{{path|{{{f|{{{1|}}}}}}}}}||NULL}} = {{{path|{{{f|{{{1}}}}}}}}}
| commit{{#if:{{{commit|{{{c|}}}}}}||NULL}} = {{{commit|{{{c}}}}}}
| line{{#if:{{{line|{{{l|}}}}}}||NULL}} = {{{line|{{{l}}}}}}
| view{{#if:{{{view|{{{v|}}}}}}||NULL}} = {{{view|{{{v}}}}}}
| text{{#if:{{{text|{{{t|}}}}}}||NULL}} = {{{text|{{{t}}}}}}
| pre{{#if:{{{pre|}}}||NULL}} = {{{pre}}}
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| simplepath{{#if:{{{simplepath|}}}||NULL}} = {{{simplepath}}}
| full{{#if:{{{full|}}}||NULL}} = {{{full}}}
}}<noinclude>

{{repo link/doc git source
| label = FlightGear
| repo = flightgear
| examples =
=== No parameters ===
{{obr}}flightgear source{{cbr}}
{{flightgear source}}

=== The repository ===
{{obr}}flightgear source
{{!}} text = The flightgear source repository
{{cbr}}

{{flightgear source
| text = The flightgear source repository
}}

=== File ===
{{obr}}flightgear source
{{!}} path = src/Main/fg_init.cxx
{{cbr}}

{{flightgear source
| path = src/Main/fg_init.cxx
}}

=== File and a branch ===

{{obr}}flightgear source
{{!}} path = src/Main/fg_init.cxx
{{!}} branch = release/2016.1/~
{{cbr}}

{{flightgear source
| path = src/Main/fg_init.cxx
| branch = release/2016.1/~
}}

=== File and a tag ===
{{obr}}flightgear source
{{!}} path = src/Main/fg_init.cxx
{{!}} tag = version/2016.1.1/~
{{cbr}}

{{flightgear source
| path = src/Main/fg_init.cxx
| tag = version/2016.1.1/~
}}

=== File and a commit ===
{{obr}}flightgear source
{{!}} path = src/Main/fg_init.cxx
{{!}} commit = c40040
{{cbr}}

{{flightgear source
| path = src/Main/fg_init.cxx
| commit = c40040
}}

{{obr}}flightgear source
{{!}} path = src/Main/fg_init.cxx
{{!}} commit = c400405b0a4c63debe7fea0dfc9ec6e5343b0fba
{{cbr}}

{{flightgear source
| path = src/Main/fg_init.cxx
| commit = c400405b0a4c63debe7fea0dfc9ec6e5343b0fba
}}

=== Commit ===
{{obr}}flightgear source
{{!}} commit = 2af076
{{!}} view = commit
{{cbr}}

{{flightgear source
| commit = 2af076
| view = commit
}}

=== File and line number ===
{{obr}}flightgear source
{{!}} path = src/Environment/environment_mgr.hxx
{{!}} line = 39
{{cbr}}

{{flightgear source
| path = src/Environment/environment_mgr.hxx
| line = 39
}}

=== File, line number, and commit ===
{{obr}}flightgear source
{{!}} path = src/Environment/environment_mgr.cxx
{{!}} commit = e42a8f597c84d65a66978af76cfbb3aae02abf63
{{!}} line = 47
{{cbr}}

{{flightgear source
| path = src/Environment/environment_mgr.cxx
| commit = e42a8f597c84d65a66978af76cfbb3aae02abf63
| line = 47
}}

=== Custom label given ===
{{obr}}flightgear source
{{!}} path = src/Environment/environment_mgr.hxx
{{!}} text = The newest code for the environment manager
{{cbr}}

{{flightgear source
| path = src/Environment/environment_mgr.hxx
| text = The newest code for the environment manager
}}

=== Prefix of $FLIGHTGEAR_SRC ===
{{obr}}flightgear source
{{!}} path = src/Environment/environment_mgr.hxx
{{!}} pre = $FLIGHTGEAR_SRC
{{cbr}}

{{flightgear source
| path = src/Environment/environment_mgr.hxx
| pre = $FLIGHTGEAR_SRC
}}

=== Full path ===
{{obr}}flightgear source
{{!}} path = src/Environment/environment_mgr.cxx
{{!}} commit = e42a8f597c84d65a66978af76cfbb3aae02abf63
{{!}} line = 47
{{!}} full = 1
{{cbr}}

{{flightgear source
| path = src/Environment/environment_mgr.hxx
| commit = e42a8f597c84d65a66978af76cfbb3aae02abf63
| line = 47
| full = 1
}}

=== Git clone ===
This is for <code><nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear</nowiki></code>.

{{obr}}#tag:code{{!}}{{obr}}#tag:nowiki{{!}}{{obr}}flightgear source
{{!}} cmd = git clone
{{!}} protocol = git
{{!}} type = git
{{!}} full = 1
{{cbr}}{{cbr}}{{cbr}}.

{{#tag:code|{{#tag:nowiki|{{flightgear source
| cmd = git clone
| protocol = git
| type = git
| full = 1
}}}}}}.

=== Aliased parameters ===
This is for https://sourceforge.net/p/flightgear/flightgear/ci/version/2016.1.1/~/tree/src/Main/fg_init.cxx.

{{obr}}flightgear source
{{!}} f = src/Main/fg_init.cxx
{{!}} b = version/2016.1.1/~
{{!}} full = 1
{{cbr}}

{{flightgear source
| f = src/Main/fg_init.cxx
| b = version/2016.1.1/~
| full = 1
}}

=== Numbered parameters ===
This is for https://sourceforge.net/p/flightgear/flightgear/ci/version/2016.1.1/~/tree/src/Main/fg_init.cxx.

{{obr}}flightgear source {{!}} src/Main/fg_init.cxx {{!}} b = version/2016.1.1/~ {{!}} full = 1 {{cbr}}

{{flightgear source | src/Main/fg_init.cxx | b = version/2016.1.1/~ | full = 1 }}

}}</noinclude>

Template:Fgaddon co

2025-02-14T10:15:43Z

Bugman: FG has migrated repositories to GL, but FGAddon remains on SF. Switch required as the project_infrastructure template has changed.

{{#tag:nowiki|{{repo link
| site = sf
| cmd = svn co
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol = {{#if: {{{login|}}} | svn+ssh | https}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type = svn
| repo = fgaddon
| branch{{#if:{{{branch|{{{b|{{{1|}}}}}}}}}||NULL}} = {{{branch|{{{b|{{{1}}}}}}}}}
| path{{#if:{{{path|{{{f|{{{2|}}}}}}}}}||NULL}} = {{{path|{{{f|{{{2}}}}}}}}}
| post = {{{post|fgaddon}}}
| full = 1
}}}}<noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
To provide a consistent representation of the command to checkout the FGAddon subversion repository.

{{repo link/doc usage
| template = fgaddon co
| value_cmd = svn co
| opt = 1
| login = 1
| branch = 1 | short_branch = b | pos_branch = 1
| path = 1 | short_path = f | pos_path = 2
| post = 1 | default_post = fgaddon
| sf = 1
| svn = 1
| break = 0
}}

{{repo link/doc plain text}}

== Examples ==
=== Checkout of trunk with user name ===
{{obr}}fgaddon co
{{!}} opt = --username <username>
{{!}} post = fgaddon
{{cbr}}

{{fgaddon co
| opt = --username <username>
| post = fgaddon
}}

=== Checkout of aircraft from a branch ===
{{obr}}fgaddon co
{{!}} branch = branches/release-3.4.0
{{!}} path = Aircraft/V22-Osprey
{{!}} post =
{{cbr}}

{{fgaddon co
| branch = branches/release-3.4.0
| path = Aircraft/V22-Osprey
| post =
}}

=== Checkout of aircraft as a user ===
{{obr}}fgaddon co
{{!}} login = <username>
{{!}} path = Aircraft/wrightFlyer1903
{{!}} post =
{{cbr}}

{{fgaddon co
| login = <username>
| path = Aircraft/wrightFlyer1903
| post =
}}

=== Aliased parameters ===
{{obr}}fgaddon co
{{!}} b = branches/release-3.2.0
{{!}} f = Aircraft/V22-Osprey
{{cbr}}.

{{fgaddon co
| b = branches/release-3.2.0
| f = Aircraft/V22-Osprey
}}.

=== Numbered parameters ===
{{obr}}fgaddon co {{!}} branches/release-3.2.0 {{!}} Aircraft/V22-Osprey {{cbr}}.

{{fgaddon co | branches/release-3.2.0 | Aircraft/V22-Osprey }}.

== Related templates ==
{{repo link/doc related}}

}}

[[Category:SCM Instruction Templates]]
</noinclude>

Template:Fgaddon commit

2025-02-14T10:15:17Z

Bugman: FG has migrated repositories to GL, but FGAddon remains on SF. Switch required as the project_infrastructure template has changed.

{{repo link
| site = sf
| repo = fgaddon
| type = svn web
| commit = {{{1|HEAD}}}
| view = commit
| text = {{#if: {{{1|}}}
| {{{text|{{{t|{{{2|FGAddon commit r{{strip whitespace|{{{1}}}}} }}} }}} }}}
| {{error|Missing parameter '''commit'''|fgaddon commit}}
}}
}}<noinclude>

{{repo link/doc commit
| label = FGAddon
| repo = fgaddon
| git = 0
| svn = 1
| type = svn
| eg1commit = 1020
| eg2intro = Maintenance such as
| eg2commit = 1001
| eg2text = removing Windows Thumbs.db files
| eg2post = should not be needed
}}

</noinclude>

Template:Fgaddon url

2025-02-14T10:14:58Z

Bugman: FG has migrated repositories to GL, but FGAddon remains on SF. Switch required as the project_infrastructure template has changed.

Template:Fgaddon aircraft source

2025-02-14T10:14:50Z

Bugman: FG has migrated repositories to GL, but FGAddon remains on SF. Switch required as the project_infrastructure template has changed.

{{repo link
| site = sf
| cmd{{#if:{{{cmd|}}}||NULL}} = {{{cmd}}}
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type = {{{type|svn web}}}
| proj = flightgear
| repo = fgaddon
| branch{{#if:{{{branch|{{{b|}}}}}}||NULL}} = {{{branch|{{{b}}}}}}
| path = Aircraft{{#if: {{{1|}}}
|/{{strip whitespace|{{{1}}}}}{{#if: {{{2|}}}
|/{{strip whitespace|{{{2}}}}}
}}
}}
| commit{{#if:{{{commit|{{{c|{{{r|}}}}}}}}}||NULL}} = {{{commit|{{{c|{{{r}}}}}}}}}
| line{{#if:{{{line|{{{l|}}}}}}||NULL}} = {{{line|{{{l}}}}}}
| view{{#if:{{{view|{{{v|}}}}}}||NULL}} = {{{view|{{{v}}}}}}
| text{{#if:{{{text|{{{t}}}}}}||NULL}} = {{{text|
{{{t|
{{#ifeq: {{{full|}}} | 1
|
| {{#if: {{{1|}}}
|{{strip whitespace|{{{1}}}}}{{#if: {{{2|}}} |/{{strip whitespace|{{{2}}}}}}}
| FGAddon aircraft
}}
}}
}}}
}}}
| pre{{#if:{{{pre|}}}||NULL}} = {{{pre}}}
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| simplepath{{#if:{{{simplepath|}}}||NULL}} = {{{simplepath}}}
| full{{#if:{{{full|}}}||NULL}} = {{{full}}}
}}<noinclude>

{{Informative template|1=
__NOTOC__
== Goal ==
This template is for creating Mediawiki links or URLs for files in the [[FGAddon]] svn version control repository. It is a subtemplate of the master {{tl|repo link}} template designed to simplify the interface by being specific for the [[FGAddon]] repository and avoiding the need to supply the <code>Aircraft/</code> directory.

{{repo link/doc usage
| template = fgaddon aircraft source
| param1 = 1 | name1 = aircraft | type1 = num | pos1 = 1 | desc1 = The aircraft directory name. The path is constructed as <code><nowiki><branch>/Aircraft/<aircraft></nowiki></code>. If empty, the path of <code><branch>/Aircraft/</code> will be used.
| param2 = 1 | name2 = path | type2 = num | pos2 = 2 | desc2 = The file path following from the aircraft directory name. The full file path will be constructed as <code><nowiki><branch>/Aircraft/<aircraft>/<path></nowiki></code>.
| cmd = 1 | eg_cmd = svn co
| opt = 1
| protocol = 1
| login = 1
| type = 1 | default_type = svn web
| branch = 1 | short_branch = b
| commit = 1 | short_commit = c {{!}} r
| line = 1 | short_line = l
| post = 1
| view = 1 | short_view = v
| text = 1 | short_text = t
| pre = 1
| simplepath = 1
| full = 1
| intro = The {{param|aircraft}}, {{param|path}}, and {{param|file}} parameters are unique to this template and are used to construct the parent {{tl|repo link}} template {{param|path}} and {{param|text}} parameters. Note that the {{param|text}} parameter overrides {{param|file}}, if supplied.
| sf = 1
| svn = 1
}}

{{repo link/doc plain text}}

== Examples ==
=== No parameters ===
{{obr}}fgaddon aircraft source{{cbr}}
{{fgaddon aircraft source}}

=== Aircraft given ===
{{obr}}fgaddon aircraft source{{!}}737-200{{cbr}}
{{fgaddon aircraft source|737-200}}

=== Revision number given ===
{{obr}}fgaddon aircraft source{{!}}ec135{{!}}c=560{{cbr}}
{{fgaddon aircraft source|ec135|c=560}}

=== Branch name given ===
{{obr}}fgaddon aircraft source{{!}}B-1B{{!}}b=release-3.6.0{{cbr}}
{{fgaddon aircraft source|B-1B|b=branches/release-3.6.0}}

=== Path and line number given ===
{{obr}}fgaddon aircraft source{{!}}F-15{{!}}Nasal/fox2.nas{{cbr}}
{{fgaddon aircraft source|F-15|Nasal/fox2.nas}}

{{obr}}fgaddon aircraft source{{!}}F-15{{!}}f15c-set.xml{{!}}l=8{{cbr}}
{{fgaddon aircraft source|F-15|f15c-set.xml|l=8}}

=== Custom text ===
{{obr}}fgaddon aircraft source{{!}}F-15{{!}}Nasal/fox2.nas{{!}}text=The F-15's missile system{{cbr}}
{{fgaddon aircraft source|F-15|Nasal/fox2.nas|text=The F-15's missile system}}

=== URL ===
{{note|Preferably, the {{tl|fgaddon aircraft url}} template should be used instead.}}
{{obr}}fgaddon aircraft source{{!}}F-15{{!}}Nasal/fox2.nas{{!}}full=1{{cbr}}
{{fgaddon aircraft source|F-15|Nasal/fox2.nas|full=1}}

=== The repository ===
{{obr}}fgaddon aircraft source
{{!}} text = The official FGAddon aircraft repository
{{cbr}}

{{fgaddon aircraft source
| text = The official FGAddon aircraft repository
}}

=== File ===
{{obr}}fgaddon aircraft source
{{!}} wrightFlyer1903
{{!}} wrightFlyer1903-set.xml
{{cbr}}

{{fgaddon aircraft source
| wrightFlyer1903
| wrightFlyer1903-set.xml
}}

=== File and a branch ===
{{obr}}fgaddon aircraft source
{{!}} wrightFlyer1903
{{!}} wrightFlyer1903-set.xml
{{!}} branch = branches/release-2016.1
{{cbr}}

{{fgaddon aircraft source
| wrightFlyer1903
| wrightFlyer1903-set.xml
| branch = branches/release-2016.1
}}

=== File and a commit ===
{{obr}}fgaddon aircraft source
{{!}} 787-8
{{!}} Nasal/systems.nas
{{!}} commit = 1333
{{cbr}}

{{fgaddon aircraft source
| 787-8
| Nasal/systems.nas
| commit = 1333
}}

=== File and line number ===
{{obr}}fgaddon aircraft source
{{!}} ornithopter
{{!}} ornithopter-set.xml
{{!}} line = 13
{{cbr}}

{{fgaddon aircraft source
| ornithopter
| ornithopter-set.xml
| line = 13
}}

=== File, line number, and commit ===
{{obr}}fgaddon aircraft source
{{!}} ornithopter
{{!}} ornithopter-set.xml
{{!}} commit = 3
{{!}} line = 10
{{cbr}}

{{fgaddon aircraft source
| ornithopter
| ornithopter-set.xml
| commit = 3
| line = 10
}}

=== Custom label given ===
{{obr}}fgaddon aircraft source
{{!}} mirage2000
{{!}} mirage2000-set.xml
{{!}} text = The Mirage 2000 *-set.xml file
{{cbr}}

{{fgaddon aircraft source
| mirage2000
| mirage2000-set.xml
| text = The Mirage 2000 *-set.xml file
}}

=== Prefix of $FG_AIRCRAFT ===
{{obr}}fgaddon aircraft source
{{!}} SpaceShuttle
{{!}} Sounds/SpaceShuttle-Sounds.xml
{{!}} pre = $FG_AIRCRAFT
{{cbr}}

{{fgaddon aircraft source
| SpaceShuttle
| Sounds/SpaceShuttle-Sounds.xml
| pre = $FG_AIRCRAFT
}}

=== Full path ===
{{obr}}fgaddon aircraft source
{{!}} CRJ700-family
{{!}} CRJ900-set.xml
{{!}} commit = 1418
{{!}} line = 10
{{cbr}}

{{fgaddon aircraft source
| CRJ700-family
| CRJ900-set.xml
| commit = 1418
| line = 10
}}

== Related templates ==
{{repo link/doc related}}

}}

[[Category:Repository link templates]]
</noinclude>

Template:Fgaddon source

2025-02-14T10:14:40Z

Bugman: FG has migrated repositories to GL, but FGAddon remains on SF. Switch required as the project_infrastructure template has changed.

{{repo link
| site = sf
| cmd{{#if:{{{cmd|}}}||NULL}} = {{{cmd}}}
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type = {{{type|svn web}}}
| proj = flightgear
| repo = fgaddon
| branch{{#if:{{{branch|{{{b|}}}}}}||NULL}} = {{{branch|{{{b}}}}}}
| tag{{#if:{{{tag|}}}||NULL}} = {{{tag}}}
| path{{#if:{{{path|{{{f|{{{1|}}}}}}}}}||NULL}} = {{{path|{{{f|{{{1}}}}}}}}}
| commit{{#if:{{{commit|{{{c|}}}}}}||NULL}} = {{{commit|{{{c}}}}}}
| line{{#if:{{{line|{{{l|}}}}}}||NULL}} = {{{line|{{{l}}}}}}
| view{{#if:{{{view|{{{v|}}}}}}||NULL}} = {{{view|{{{v}}}}}}
| text{{#if:{{{text|{{{t|}}}}}}||NULL}} = {{{text|{{{t}}}}}}
| pre{{#if:{{{pre|}}}||NULL}} = {{{pre}}}
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| simplepath{{#if:{{{simplepath|}}}||NULL}} = {{{simplepath}}}
| full{{#if:{{{full|}}}||NULL}} = {{{full}}}
}}<noinclude>

{{repo link/doc svn source
| label = FGAddon
| repo = fgaddon
| examples =
=== No parameters ===
{{obr}}fgaddon source{{cbr}}
{{fgaddon source}}

=== The repository ===
{{obr}}fgaddon source
{{!}} text = The official FGAddon aircraft repository
{{cbr}}

{{fgaddon source
| text = The official FGAddon aircraft repository
}}

=== File ===
{{obr}}fgaddon source
{{!}} path = Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml
{{cbr}}

{{fgaddon source
| path = Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml
}}

=== File and a branch ===
{{obr}}fgaddon source
{{!}} path = Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml
{{!}} branch = branches/release-2016.1
{{cbr}}

{{fgaddon source
| path = Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml
| branch = branches/release-2016.1
}}

=== File and a commit ===
{{obr}}fgaddon source
{{!}} path = Aircraft/787-8/Nasal/systems.nas
{{!}} commit = 1333
{{cbr}}

{{fgaddon source
| path = Aircraft/787-8/Nasal/systems.nas
| commit = 1333
}}

=== Commit ===
{{obr}}fgaddon source
{{!}} commit = 1552
{{!}} view = commit
{{cbr}}

{{fgaddon source
| commit = 1552
| view = commit
}}

=== File and line number ===
{{obr}}fgaddon source
{{!}} path = Aircraft/ornithopter/ornithopter-set.xml
{{!}} line = 13
{{cbr}}

{{fgaddon source
| path = Aircraft/ornithopter/ornithopter-set.xml
| line = 13
}}

=== File, line number, and commit ===
{{obr}}fgaddon source
{{!}} path = Aircraft/ornithopter/ornithopter-set.xml
{{!}} commit = 3
{{!}} line = 10
{{cbr}}

{{fgaddon source
| path = Aircraft/ornithopter/ornithopter-set.xml
| commit = 3
| line = 10
}}

=== Custom label given ===
{{obr}}fgaddon source
{{!}} path = Aircraft/mirage2000/mirage2000-set.xml
{{!}} text = The Mirage 2000 *-set.xml file
{{cbr}}

{{fgaddon source
| path = Aircraft/mirage2000/mirage2000-set.xml
| text = The Mirage 2000 *-set.xml file
}}

=== Prefix of $FG_AIRCRAFT ===
{{obr}}fgaddon source
{{!}} path = Aircraft/SpaceShuttle/Sounds/SpaceShuttle-Sounds.xml
{{!}} pre = $FG_AIRCRAFT
{{cbr}}

{{fgaddon source
| path = Aircraft/SpaceShuttle/Sounds/SpaceShuttle-Sounds.xml
| pre = $FG_AIRCRAFT
}}

=== Full path ===
{{obr}}fgaddon source
{{!}} path = Aircraft/CRJ700-family/CRJ900-set.xml
{{!}} commit = 1418
{{!}} line = 10
{{!}} full = 1
{{cbr}}

{{fgaddon source
| path = Aircraft/CRJ700-family/CRJ900-set.xml
| commit = 1418
| line = 10
| full = 1
}}

=== svn import ===
This should give:
<syntaxhighlight lang="bash">
svn import DaSH/ svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/ -m "Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&t=24495 ."
</syntaxhighlight>

{{obr}}#tag:syntaxhighlight{{!}}
{{obr}}fgaddon source
{{!}} cmd = svn import DaSH/
{{!}} protocol = svn+ssh
{{!}} login = <username>
{{!}} type = svn
{{!}} path = Aircraft/
{{!}} post = -m "Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at <nowiki>http://forum.flightgear.org/viewtopic.php?f=4&t=24495</nowiki> ."
{{!}} full = 1
{{cbr}}
{{!}} lang = "sh"
{{cbr}}

{{#tag:syntaxhighlight|
{{fgaddon source
| cmd = svn import DaSH/
| protocol = svn+ssh
| login = <username>
| type = svn
| path = Aircraft/
| post = -m "Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&t=24495 ."
| full = 1
}}
| lang = "sh"
}}

=== Aliased parameters ===
This is for https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/branches/release-2016.1/Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml.

{{obr}}fgaddon source
{{!}} f = Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml
{{!}} b = branches/release-2016.1
{{!}} full = 1
{{cbr}}.

{{fgaddon source
| f = Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml
| b = branches/release-2016.1
| full = 1
}}.

=== Numbered parameters ===
This is for https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/branches/release-2016.1/Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml.

{{obr}}fgaddon source {{!}} Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml {{!}} b = branches/release-2016.1 {{!}} full = 1 {{cbr}}.

{{fgaddon source | Aircraft/wrightFlyer1903/wrightFlyer1903-set.xml | b = branches/release-2016.1 | full = 1 }}.

}}</noinclude>

Template:Project infrastructure

2025-02-14T10:11:40Z

Bugman: Switch to a default abbreviation of 'gl'. This is mainly for the repo_link subtemplates.

{{#switch: {{{1|name}}}
| name = {{#ifeq: {{{link|yes}}} | yes
| [{{#if:{{{noprotocol|}}}||http://}}sourceforge.net/projects/flightgear{{#if: {{{urn|}}}|/{{{urn}}}}} {{{text|SourceForge}}}]
| SourceForge
}}
| abbrev = gl
| buildserver =
{{project infrastructure option
| link = {{{link|yes}}}
| url = {{#if:{{{noprotocol|}}}||http://}}build.flightgear.org:8080
| desc = {{LangSwitch
| en = FlightGear Build Server
}}
}}
| nightlies =
{{project infrastructure option
| link = {{{link|yes}}}
| url = {{#if:{{{noprotocol|}}}||https://}}sourceforge.net/projects/flightgear/files/unstable
| desc = {{{text
| {{LangSwitch
| en = Nightly builds
}}
}}}
}}
| mapserver =
{{project infrastructure option
| link{{#if:{{{link|}}}||NULL}} = {{{link}}}
| link = {{{link}}}
| url = {{#if:{{{noprotocol|}}}||http://}}mapserver.flightgear.org
| desc = {{{text
| {{LangSwitch
| en = FlightGear mapserver
}}
}}}
}}
| forum =
{{project infrastructure option
| link{{#if:{{{link|}}}||NULL}} = {{{link}}}
| url = {{#if:{{{noprotocol|}}}||https://}}forum.flightgear.org
| urn{{#if:{{{urn|}}}||NULL}} = {{{urn}}}
| desc = {{{text
| {{LangSwitch
| en = FlightGear Forum
}}
}}}
}}
| mailing lists =
{{project infrastructure option
| link{{#if:{{{link|}}}||NULL}} = {{{link}}}
| url = {{#if:{{{noprotocol|}}}||https://}}sourceforge.net/p/flightgear/mailman
| urn{{#if:{{{urn|}}}||NULL}} = {{{urn}}}
| desc = {{{text
| {{LangSwitch
| en = FlightGear Mailing Lists
}}
}}}
}}
| scenery =
{{project infrastructure option
| link{{#if:{{{link|}}}||NULL}} = {{{link}}}
| url = {{#if:{{{noprotocol|}}}||https://}}scenery.flightgear.org
| urn{{#if:{{{urn|}}}||NULL}} = {{{urn}}}
| desc = {{{text
| {{LangSwitch
| en = FlightGear Scenery Website
}}
}}}
}}
| website =
{{project infrastructure option
| link{{#if:{{{link|}}}||NULL}} = {{{link}}}
| url = {{#if:{{{noprotocol|}}}||https://}}flightgear.org
| urn{{#if:{{{urn|}}}||NULL}} = {{{urn}}}
| desc = {{{text
| {{LangSwitch
| en = website
}}
}}}
}}
| wiki =
{{project infrastructure option
| link{{#if:{{{link|}}}||NULL}} = {{{link}}}
| url = {{#if:{{{noprotocol|}}}||https://}}wiki.flightgear.org
| urn{{#if:{{{urn|}}}||NULL}} = {{{urn}}}
| desc = {{{text
| {{LangSwitch
| en = FlightGear wiki
}}
}}}
}}
| liveries =
{{project infrastructure option
| link = {{{link|yes}}}
| url = {{#if:{{{noprotocol|}}}||https://}}liveries.flightgear.org
| desc = {{LangSwitch
| en = FlightGear Livery Database
}}
}}
}}<noinclude>

{{Informative template|1=
== Goal ==
This is an universal template for referencing the current open source infrastructure used by the FlightGear project.

Ideally other templates this will use this template for URNs and links, so that this will be the only template that need to be changed if parts of the FlightGear infrastructure move from one host to another (for details of why, see the [[#Background|Background]] section below).

__TOC__

== Usage ==
{{obr}}'''project infrastructure
{{!}} mode
{{!}} ''urn'' =
{{!}} ''link'' =
{{!}} ''text'' =
{{!}} ''noprotocol'' =
{{cbr}}

; mode: The type of infrastructure. This defaults to {{param||name}}, but can be one of:

:; name: The name of the hosting infrastructure.
:; abbrev: An abbreviation for the hosting infrastructure, mainly for use in other templates (no link, and current returns '''sf''').
:; nightlies: nightly builds
:; buildserver: The FlightGear build server
:; forum: The FlightGear forum.
:; scenery: The FlightGear scenery website.
:; website: The FlightGear website.
:; wiki: The FlightGear wiki.
:; mailing lists: The FlightGear mailing lists.

; urn: The optional [https://en.wikipedia.org/wiki/Uniform_Resource_Name uniform resource name], the part of the [https://en.wikipedia.org/wiki/Uniform_Resource_Locator URL] after the domain name.

; link: If set to {{param||yes}}, then a MediaWiki link will be created, when appropriate. The value of {{param||no}} will cause plain text to be returned. This defaults to {{param||yes}}.

; text: The optional custom text to use for the link.

; noprotocol: If set, then the protocol part of the URL will not be added. This is, for example, '''https://'''.

== Examples ==
=== Name ===
{{obr}}project infrastructure{{!}}name{{cbr}}

{{project infrastructure|name}}

{{obr}}project infrastructure{{!}}name{{!}}link=no{{cbr}}

{{project infrastructure|name|link=no}}

{{obr}}project infrastructure{{!}}nightlies{{cbr}}

{{project infrastructure|nightlies}}

=== Abbreviation ===
{{obr}}project infrastructure{{!}}abbrev{{cbr}}

{{project infrastructure|abbrev}}

=== Build Server ===
{{obr}}project infrastructure{{!}}buildserver{{cbr}}

{{project infrastructure|buildserver}}

=== Forum ===
{{obr}}project infrastructure{{!}}forum{{cbr}}

{{project infrastructure|forum}}

{{obr}}project infrastructure{{!}}forum{{!}}urn=search.php{{!}}text=Search the forum{{cbr}}

{{project infrastructure|forum|urn=search.php|text=Search the forum}}

{{obr}}project infrastructure{{!}}forum{{!}}link=no{{cbr}}

{{project infrastructure|forum|link=no}}

site:{{obr}}project infrastructure{{!}}forum{{!}}link=no{{!}}noprotocol=yes{{cbr}}

site:{{project infrastructure|forum|link=no|noprotocol=yes}}

=== Scenery ===
{{obr}}project infrastructure{{!}}scenery{{cbr}}

{{project infrastructure|scenery}}

=== Website ===
{{obr}}project infrastructure{{!}}website{{cbr}}

{{project infrastructure|website}}

{{obr}}project infrastructure{{!}}website{{!}}link=no{{cbr}}

{{project infrastructure|website|link=no}}

=== Wiki ===
{{obr}}project infrastructure{{!}}wiki{{cbr}}

{{project infrastructure|wiki}}

{{obr}}project infrastructure{{!}}wiki{{!}}link=no{{cbr}}

{{project infrastructure|wiki|link=no}}

== Background ==
Currently all our code and data lives on SourceForge. Collecting everything from gitorious, googlecode and private servers, getting our build server work with the new locations was not a trivial task, took months to complete and was everything but a pleasant job.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35083587/
|title = <nowiki> Re: [Flightgear-devel] Shall we migrate code from SourceForge to
GitLab? </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = May 12th, 2016
|added = May 12th, 2016
|script_version = 0.40
}}</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/33553643/</ref> However, should the project (or any of its associated websites) ever need to be moved again (a discussion that keeps coming up, and is even raised by former core developers,<ref>https://sourceforge.net/p/flightgear/mailman/message/35054466</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/35083528/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/33510482/</ref>) this template will help isolate required changes.

The creation of this template was motivated by the workload caused by the shutdown of gitorious (to become gitlab) and subsequent migration of all repositories to sourceforge.<ref>[[FlightGear Newsletter April 2015#FlightGear now lives at SourceForge]]</ref> Shortly afterwards, Sourceforge and Slashdot were sold, where most of the FlightGear project's infrastructure had moved at the time.<ref>https://forum.flightgear.org/viewtopic.php?f=42&p=277816#p277816</ref>

The wiki admins back then realized that the workload due to having to update dozens, if not even hundreds, of articles could be greatly reduced if a common set of templates were to be used for "encapsulating" (hiding) such details.
In particular, the creation of the repo link (respectively git/svn link) templates (started by {{usr|Red Leader}} and {{usr|Johan G}}) will greatly help isolate and reduce the amount of work needed to maintain our wiki articles up to date.

== Related templates ==

{{tl|project infrastructure option}}

}}
{{Appendix}}
[[Category:Templates]]
[[Category:Link templates]]
</noinclude>

User:Bugman/Bot sandbox

2024-02-21T10:01:51Z

Bugman: Initial sandbox testing page.

Links for bots to fix:

* https://forum.flightgear.org/viewtopic.php?f=42&t=42097&p=419217#p419217
* https://forum.flightgear.org/viewtopic.php?t=42097&p=419217#p419217
* https://forum.flightgear.org/viewtopic.php?f=42&p=419217#p419217
* https://forum.flightgear.org/viewtopic.php?p=419217#p419217
* https://forum.flightgear.org/viewtopic.php?f=42&t=42097#p419217

User:Bugman

2024-02-20T09:07:17Z

Bugman: /* Wiki template work */

{{warning|I have to warn you {{caution|to be cautious {{note|because I am {{tip|currently a stub {{stub}} }} }} }} }}

== Wiki template work ==

* Creation of the repository link template family: [[:Category:Repository link templates]].
* Writing and maintaining the [[FGAddon]] wiki page.
* Aircraft infoboxes: {{tl|infobox aircraft}}.
** Sandbox: [[User:Bugman/Infobox Aircraft]].
** Hangar support: {{tl|hangar banner}}.
** Conversion of all [[:Category:Controllable craft]] pages to use the new features: {{progressbar|60}}
* Template help:
** Sandbox: [[User:Bugman/Finding_the_correct_template]].

== FlightGear repositories ==

* Subsystem API standardisation and robustness: [[User:Bugman/subsystems]]
* Work for finding and restoring the FGData and FGAddon model dependencies: [[User:Bugman/model_dependencies]]

[[fr:User:Bugman]]

== Subpages ==

For self reference, this is a listing of all my subpages:

{{Special:Prefixindex/User:Bugman/}}

User:Bugman/Finding the correct template

2024-02-20T08:48:12Z

Bugman: Initial mock-up page

{{Wiki help navbar}}

== Information boxes ==

If you would like to present important information to the reader, please see:

* [[Help:Gallery of messagebox templates]]

== Aicraft infoboxes ==

When creating a page for an aircraft, always start with the aircraft infobox template:

* {{tl|infobox aircraft}}

== Avoiding hard-coded URLs and future dead links ==

{{warning|URLs to the official and 3rd-party FlightGear infrastructure should never be hard-coded, as these will inevitably change in the future and become dead links on the Wiki.}}

To help the FlightGear project survive many decades from now, URLs, links, and descriptions to the official and 3rd party FlightGear infrastructure should always be provided via templates.

=== Forum link templates ===

For the FlightGear forum, we have three main templates:

* {{tl|forum}}
* {{tl|forum link}}
* {{tl|forum url}}

=== Repository link templates ===

URLs to the official and 3rd-party FlightGear repositories should, in all cases, be provided by one template from the family of repository link templates:

{{repo link/doc related}}

=== Project infrastructure details ===

For links, names, and descriptions of the FlightGear project infrastructure, please consider using the {{tl|Project infrastructure}} template.

Template:SVN link

2024-02-19T13:25:13Z

Bugman: Undo revision 139144 by Bugman (talk)

{{Repo link
|site = sourceforge
|proj = {{{reponame|flightgear/fgaddon}}}
|rev = {{{rev|HEAD}}}
|path = {{{path|Aircraft}}}
|lines = {{{line|}}}
|text = {{{text|}}}
|pre = {{{pre|}}}
}}<noinclude>
{{Informative template|1=

{{historical|reason=This template is kept for the last few pages that link to it. It is not functional and the links it produces are broken. Please use the {{tl|repo link}} family of templates instead.|date=8 March 2016}}

== Goal ==
__NOTOC__
This template allows easy links to SVN-managed files or projects located at [https://sourceforge.net SourceForge].

{{inote|Using this '''will''' add an external link; make sure to enter the appropriate security question after hitting "Save page", or your changes will be lost.}}

== Usage ==
<nowiki>{{</nowiki>'''SVN link'''
<nowiki>|</nowiki> ''path'' =
<nowiki>|</nowiki> ''reponame'' =
<nowiki>|</nowiki> ''rev'' =
<nowiki>|</nowiki> ''line'' =
<nowiki>|</nowiki> ''text'' =
<nowiki>|</nowiki> ''pre'' =
<nowiki>}}</nowiki>

All parameters are optional. If no parameters are given, the template will link to the <code>Aircraft</code> folder of [[FGAddon]].

; path
: Path to the file or directory.

; reponame
: Path to the repository. Defaults to '''flightgear/fgaddon'''.

; rev
: Revision number. Defaults to '''HEAD'''.

; line
: Line to go to on the page.

; text
: Alternative label for the link text. Will override all other parameters.

; pre
: Prefix for the links label. Defaults to '''flightgear/fgaddon'''.

== Examples ==
<nowiki>{{SVN link}}</nowiki>
{{SVN link}}

<nowiki>{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|pre=$FGDATA}}</nowiki>
{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|pre=$FGDATA}}

<nowiki>{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|line=7|text=Line 7 of the Mirage 2000-5's set.xml file}}</nowiki>
{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|line=7|text=Line 7 of the Mirage 2000-5's set.xml file}}

== Known issues ==
It appears that '''line''' does not work with files on Sourceforge that are not XML. This seems to be a problem with SourceForge. See the below example and the second example above for illustration.
<nowiki>{{SVN link|path=Aircraft/Mirage-2000/Nasal/missile.nas|line=7|text=missile.nas - line7}}</nowiki>
{{SVN link|path=Aircraft/Mirage-2000/Nasal/missile.nas|line=7|text=missile.nas - line7}}

== Related templates ==
{{repo link/doc related}}

}}

</noinclude>

Template:SVN link

2024-02-19T13:24:53Z

Bugman: {{[[Template

{{Repo link
|site = sourceforge
|proj = {{{reponame|flightgear/fgaddon}}}
|rev = {{{rev|HEAD}}}
|path = {{{path|Aircraft}}}
|lines = {{{line|}}}
|text = {{{text|}}}
|pre = {{{pre|}}}
}}<noinclude>
{{Informative template|1=

{{historical|reason=This template is kept for the last few pages that link to it. It is not functional and the links it produces are broken. Please use the {{tl|repo link}} family of templates instead.|date=8 March 2016}}

== Goal ==
__NOTOC__
This template allows easy links to SVN-managed files or projects located at [https://sourceforge.net SourceForge].

{{inote|Using this '''will''' add an external link; make sure to enter the appropriate security question after hitting "Save page", or your changes will be lost.}}
x
== Usage ==
<nowiki>{{</nowiki>'''SVN link'''
<nowiki>|</nowiki> ''path'' =
<nowiki>|</nowiki> ''reponame'' =
<nowiki>|</nowiki> ''rev'' =
<nowiki>|</nowiki> ''line'' =
<nowiki>|</nowiki> ''text'' =
<nowiki>|</nowiki> ''pre'' =
<nowiki>}}</nowiki>

All parameters are optional. If no parameters are given, the template will link to the <code>Aircraft</code> folder of [[FGAddon]].

; path
: Path to the file or directory.

; reponame
: Path to the repository. Defaults to '''flightgear/fgaddon'''.

; rev
: Revision number. Defaults to '''HEAD'''.

; line
: Line to go to on the page.

; text
: Alternative label for the link text. Will override all other parameters.

; pre
: Prefix for the links label. Defaults to '''flightgear/fgaddon'''.

== Examples ==
<nowiki>{{SVN link}}</nowiki>
{{SVN link}}

<nowiki>{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|pre=$FGDATA}}</nowiki>
{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|pre=$FGDATA}}

<nowiki>{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|line=7|text=Line 7 of the Mirage 2000-5's set.xml file}}</nowiki>
{{SVN link|path=Aircraft/Mirage-2000/m2000-5-set.xml|line=7|text=Line 7 of the Mirage 2000-5's set.xml file}}

== Known issues ==
It appears that '''line''' does not work with files on Sourceforge that are not XML. This seems to be a problem with SourceForge. See the below example and the second example above for illustration.
<nowiki>{{SVN link|path=Aircraft/Mirage-2000/Nasal/missile.nas|line=7|text=missile.nas - line7}}</nowiki>
{{SVN link|path=Aircraft/Mirage-2000/Nasal/missile.nas|line=7|text=missile.nas - line7}}

== Related templates ==
{{repo link/doc related}}

}}

</noinclude>

Talk:Main Page

2022-11-20T22:39:37Z

Bugman: Reverted edits by Buy-tramadol-online (talk) to last revision by Gijs

{{Archives|[[/Archive/2006-2011|2006-2011]]}}

:''Please sign your comments with using tildes (<nowiki>~~~~</nowiki>) or the signature button (second from right above the text edit box). Add new sections to the bottom or by using the "+" tab. You are also encouraged to add a summary of your comment to the edit summary (below the text edit box).''

= 2012 =
== Issues and regressions ==

== Planned changes ==
== Extension requests ==
how can I add the slovenian flag to the others on the top right corner ?
[[User:Laserman|Laserman]] ([[User talk:Laserman|talk]]) 04:51, 27 December 2015 (EST)

: {{done}}
: [[:File:Sl.gif]] was uploaded and added to [[:Category:Flag icons]] and the {{tl|Main page/Languages}} template where the flag icons are added to the main page.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:07, 27 December 2015 (EST)

Thank you! [[User:Laserman|Laserman]] ([[User talk:Laserman|talk]]) 12:40, 27 December 2015 (EST)

== Deleting versus archiving ==

I have archived an earlier version of this page [http://wiki.flightgear.org/index.php?title=Talk:Main_Page/Archive/2006-2011&oldid=40427 here].

I believe that for the sake transparency and keeping a accessible record of the progressing history of the wiki and what is done to it, and I am not talking about the page history, it would be better if comments instead of being deleted get marked off as completed, obsoleted or what seems appropriate. When the page once in a while gets uncomfortably long it should be archived.

I noted when I went through the entire history of the now archived page that a lot of the comments was unsigned and many of the longer ones later on was cut into pieces by headings, later on to be partially deleted. That makes it very difficult and time consuming to follow what is done and what people laid forth what ideas etc. I am a bit frustrated, although not angry, about that. Luckily there was only a few hundred edits, making it possible to attribute the surviving parts of the comments to an individual author and edit.

As for now I have not used any "fancy" templates when archiving the page, but if needed that can be added later.
[[User:Johan G|Johan G]] 11:21, 9 February 2012 (EST)

: I am sorry, you are probably right: it's the better solution. It just didn't occur to me that people might still be interested in stuff that's no longer an issue, i.e. because it was solved. Also, some of the comments were from people who haven't done any wiki editing in years. My next step would have been to go trough the list of "open" issues and suggestions and migrate them over to 2012. What do you think?--[[User:Hooray|Hooray]] 11:42, 9 February 2012 (EST)

::There is no need to be sorry. :-) My frustrations are more related to the entangled edit history than specifically what you deleted, even though it add to it. As for the open issues I agree, it is probably a good idea to copy them over here. [[User:Johan G|Johan G]] 12:22, 9 February 2012 (EST)

FlightGear wiki:Village pump

2022-07-05T10:22:21Z

Bugman: Favicon not visible.

FlightGear wiki:Village pump

2022-07-05T10:17:15Z

Bugman: Shifted the 2021 content to FlightGear wiki:Village pump/Archive 2021.

FlightGear wiki:Village pump/Archive 2021

2022-07-05T10:14:38Z

Bugman: 2021 content of FlightGear_wiki:Village_pump.

{{talk archive}}

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

:: Hm, I cannot reproduce that here. Did it happen at a specific page? Can you try to reproduce it and provide a recipe?
::[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

: Oh, just one thing if this is possible, can we have a [https://www.mediawiki.org/wiki/Manual:$wgFavicon favicon] set like the forum and the [https://flightgear.org main website]?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:23, 16 February 2021 (UTC)

:: Good one, done!
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Basic question sub page/sandbox ==

Hi,
New to the wiki here and hoping to contribute in some small way. I don't see any instructions (or menu options) on how to crate a sub page or sandbox in order to start drafting an article. I'll also aim to update the wiki on how to crate a sub page as it might help others with the same question.
Many thanks
[[User:Volador|Volador]] ([[User talk:Volador|talk]]) 08:33, 7 April 2021 (UTC)

== MediaWiki updated to 1.35.3 ==
We have updated MediaWiki to its latest version 1.35.3 today. Although we've tested the update, chances are that we've missed certain scenarios. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:45, 23 July 2021 (UTC)

Talk:Suggested aircraft

2022-06-19T20:07:45Z

Bugman: Shift NPOV content to a user subpage.

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 14:08, 28 May 2022 (UTC) Well, maybe someone should write WHY they are good, because only suggesting is not changing anything

== Goal of the page ==

Hi,

I'm not exactly sure what the goal of this page is. We definitely do not want to suggest the average FlightGear user to use a development repository to get their aircraft from with high risk of issues and bugs. Especially not in cases where the authors actively push releases to FGAddon when they reach a stable state (e.g., the Space Shuttle, c172 etc.). For those interested in finding the latest development version of an aircraft, each aircraft page on the wiki has (or can have) a "repository" link in the infobox behind this icon [[File:Preferences-system_32x32.png|16px]]. This makes me wonder what the added value of this page is in its current form?

Also note that linking to FGMembers is definitely a no-go [https://www.flightgear.org/fgmembers-statement/ per our statement].

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:03, 31 May 2022 (UTC)

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:14, 31 May 2022 (UTC) Yes, this have no sense of doing it. Well, suggesting aircrafts is nothing bad but someone should write why they are good, and not just spam links on possibly bugged version on usually FGLauncher ones. FGMembers ones need to be deleted, because fgmembers, i didn't wanted to deleted that fgmembers link that SidarDeha posted here, because i knew that there is no other version than FGmembers, so i wrote warning on start of the page. And yes, That what FGMembers did was not stupid, but they did it wrong. They maked one hangar with all aricrafts what can be added to launcher. But there are also license problems, especially for the FGMembers-nonGPL(what the hell is that). I think that page is not contributing anything to FG, may make some users experience bug with 3rd party aircrafts, and should be category of wiki pages with good aircrafts instead of few github links here

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:07, 4 June 2022 (UTC) Also, adding something that you found on github, turned on and saw good cockpit is very bad thing. some aircrafts look nice, fly nice, and are unrealistic

== Shift to a user subpage ==

The content of this article is not [[w:Wikipedia:Neutral point of view|NPOV]], it is the opinion of the user [[User:SidarDeha|SidarDeha]]. The content should be moved either to the user's page [[User:SidarDeha]] or a dedicated subpage such as [[User:SidarDeha/Suggested_aircraft]]. FlightGear's well established rating system for aircraft is how aircraft are judged by users and how the project suggests aircraft to users.

[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 20:07, 19 June 2022 (UTC)

User talk:PlayeRom

2021-10-18T12:43:53Z

Bugman:

{{Template:Welcome to the wiki|realName=|name=PlayeRom}}

-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 19:46, 21 March 2021 (UTC)

== Aircraft infobox ==

Hi PlayeRom! I noticed you added Polish translations to the [[Cessna 172P/info]] page. Note that the {{param|type}}, {{param|config}}, {{param|propulsion}}, and {{param|manufacturer}} parameters should not be translated in the aircraft specific infobox. Instead, please see the instructions at [[Template:Infobox aircraft#Full translation]]. The translation of these subtemplates will allow all aircraft to access your Polish translations. Cheers!

[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:43, 18 October 2021 (UTC)

FlightGear wiki:Village pump

2021-02-16T21:23:00Z

Bugman: /* MediaWiki updated to 1.35.1 */

{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

: Oh, just one thing if this is possible, can we have a [https://www.mediawiki.org/wiki/Manual:$wgFavicon favicon] set like the forum and the [https://flightgear.org main website]?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:23, 16 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

FlightGear wiki:Village pump

2021-02-16T21:12:54Z

Bugman: /* MediaWiki updated to 1.35.1 */

{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

Howto talk:Start core development

2020-11-23T10:28:03Z

Bugman: /* Use of "repo" links in wiki pages. */

= Open questions =
* merge requests (post follow-up to mailing list and file review via issue tracker)

= Planned improvements =
* navigating the source trees (FG + SG)
* FG entry point (bootstrap.cxx)
* the FG main loop
* FG subsystems
* adding new fgcommands
* adding new network protocols
* adding new telnet/props commands
* adding new startup options (options.cxx)
* adding new subsystems
* networking
* scripting
* GUI code
* instruments
* list of FG related projects (URLs, type of software)
* list of FG related websites
* list of FG related people (i.e. developers)
* gdb, valgrind, gprof, gcov

== Use of "repo" links in wiki pages. ==

I'm not sure there's much advantage to using the "repo" link system. It's an abstraction that protects us against something that happens extremely rarely (changing of the main git repositories) at the cost of an obscure macro-like thing in the wiki text. Personally i'm with the Python philosophy of "Explicit is better than implicit" in this case. Apart from anything else, the most likely change to repositories is not a simple move to different location, but a merging of flightgear and simgear into a single repository, for which the repo macro is useless. [[User:Cgdae|Cgdae]] ([[User talk:Cgdae|talk]]) 10:34, 22 November 2020 (EST)

: It was agreed on by the people involved in updating the wiki after the last migration, and given that another migration is currently being discussed, it might not be such a bad idea. I do think that the existing macros could be adapted to reflect a merged repository (if the need arises). If in doubt, Johan and bugman were primarily involved in establishing these "link templates", but it seemed other wiki admins were also convinced it's a good idea, here's the original context: http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=87148#Repository_link_templates --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:09, 22 November 2020 (EST)

:: I manually did the large part of that migration myself. The pain is insane! The changes could not be scripted - my attempts ended in a large proportion of dead links. There is too much variability and redundancy in the PHP query strings. I dealt with something like 5000 dead gitorious links manually, one by one. It took me weeks, and innumerable hours of work. If there is another infrastructure change, now with the {{tl|repo link}} family of templates I can migrate all of those 5000 links within seconds. Or if SourceForge, GitHub, GitLab, or the Gitorious archive change their URLs or PHP query string interface, I can fix all links within a single location. In 20 years we will still have the wiki and we would probably have gone through one or two infrastructure migrations, just as we have been through 3 different infrastructures in the previous 20 years (Curt's CVS server, Gitorious, and SourceForge). So there is a very big advantage for the long term viability of the wiki.

:: A merged repository is also no problem for these templates. Just as I experimented with creating that merged repository, I also looked into what is required for the templates, and this is trivial (either for a merged repository, a submodule, or a subtree).

:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 16:32, 22 November 2020 (EST)

::: Agreed, I am entirely with bugman on this ...wiki admins (and hosting providers) come and go, but we don't really have many people interested in doing such tedious work. In fact, I wish there were more people with the privileges that Simon and Gijs have, so this mediawiki installation itself could be better maintained here. For instance, these template are enormously helpful, but obviously it could really go a long way if such helper templates were properly integrated in the WYSIWYG editor/interface - this, and many similar requests have been made over the years, but were rarely implemented by our server admins. Thus, templates like these are a compromise obviously, but I'd rather use these than have no option at all. So, thank you bugman for all your work here !! (to be fair, {{Usr|Red Leader}} did have an instrumental role in the development of the original idea. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:40, 22 November 2020 (EST)

:::: To be fair, you'd need to have seen it or looked at the {{tl|repo link}} history to know that I did some major work on that template. From its history it is clear that {{usr|Red Leader}} started these templates. I only extended the family and the dealt with the direct and dead link Gitorious mess.

:::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 16:55, 22 November 2020 (EST)

Ok, fair enough, thanks everyone for explaining things.

Is there more information about the repository links system somewhere? I couldn't see anything in [[Special:SpecialPages]] for example?

[[User:Cgdae|Cgdae]] ([[User talk:Cgdae|talk]]) 05:22, 23 November 2020 (EST)

: Everything is reachable from [[:Category:Repository_link_templates]], and each template is documented. Maybe the table in {{tl|Repo link/doc related}} could be better documented?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 05:27, 23 November 2020 (EST)

Howto talk:Start core development

2020-11-22T21:56:02Z

Bugman: /* Use of "repo" links in wiki pages. */

Howto talk:Start core development

2020-11-22T21:55:35Z

Bugman: /* Use of "repo" links in wiki pages. */

= Open questions =
* merge requests (post follow-up to mailing list and file review via issue tracker)

= Planned improvements =
* navigating the source trees (FG + SG)
* FG entry point (bootstrap.cxx)
* the FG main loop
* FG subsystems
* adding new fgcommands
* adding new network protocols
* adding new telnet/props commands
* adding new startup options (options.cxx)
* adding new subsystems
* networking
* scripting
* GUI code
* instruments
* list of FG related projects (URLs, type of software)
* list of FG related websites
* list of FG related people (i.e. developers)
* gdb, valgrind, gprof, gcov

== Use of "repo" links in wiki pages. ==

I'm not sure there's much advantage to using the "repo" link system. It's an abstraction that protects us against something that happens extremely rarely (changing of the main git repositories) at the cost of an obscure macro-like thing in the wiki text. Personally i'm with the Python philosophy of "Explicit is better than implicit" in this case. Apart from anything else, the most likely change to repositories is not a simple move to different location, but a merging of flightgear and simgear into a single repository, for which the repo macro is useless. [[User:Cgdae|Cgdae]] ([[User talk:Cgdae|talk]]) 10:34, 22 November 2020 (EST)

: It was agreed on by the people involved in updating the wiki after the last migration, and given that another migration is currently being discussed, it might not be such a bad idea. I do think that the existing macros could be adapted to reflect a merged repository (if the need arises). If in doubt, Johan and bugman were primarily involved in establishing these "link templates", but it seemed other wiki admins were also convinced it's a good idea, here's the original context: http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=87148#Repository_link_templates --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:09, 22 November 2020 (EST)

:: I manually did the large part of that migration myself. The pain is insane! The changes could not be scripted - my attempts ended in a large proportion of dead links. There is too much variability and redundancy in the PHP query strings. I dealt with something like 5000 dead gitorious links manually, one by one. It took me weeks, and innumerable hours of work. If there is another infrastructure change, now with the {{tl|repo link}} family of templates I can migrate all of those 5000 links within seconds. Or if SourceForge, GitHub, GitLab, or the Gitorious archive change their URLs or PHP query string interface, I can fix all links within a single location. In 20 years we will still have the wiki and we would probably have gone through one or two infrastructure migrations, just as we have been through 3 different infrastructures in the previous 20 years (Curt's CVS server, Gitorious, and SourceForge). So there is a very big advantage for the long term viability of the wiki.

:: A merged repository is also no problem for these templates. Just as I experimented with creating that merged repository, I also looked into what is required for the templates, and this is trivial (either for a merged repository, a submodule, or a subtree).

:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 16:32, 22 November 2020 (EST)

::: Agreed, I am entirely with bugman on this ...wiki admins (and hosting providers) come and go, but we don't really have many people interested in doing such tedious work. In fact, I wish there were more people with the privileges that Simon and Gijs have, so this mediawiki installation itself could be better maintained here. For instance, these template are enormously helpful, but obviously it could really go a long way if such helper templates were properly integrated in the WYSIWYG editor/interface - this, and many similar requests have been made over the years, but were rarely implemented by our server admins. Thus, templates like these are a compromise obviously, but I'd rather use these than have no option at all. So, thank you bugman for all your work here !! (to be fair, {{Usr|Red Leader}} did have an instrumental role in the development of the original idea. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:40, 22 November 2020 (EST)

:::: To be fair, you'd need to have seen it or looked at the {{tl|repo link}} history to know that I did some major work on that template. From its history it is clear that {{use|Red Leader}} started these templates. I only extended the family and the dealt with the direct and dead link Gitorious mess.

:::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 16:55, 22 November 2020 (EST)