6,609
edits
FlightGear wiki:Village pump: Difference between revisions
Jump to navigation
Jump to search
Improved the sectioning by bringing all the {{repo link}} sections under one heading.
(→Archived newsletters and dead links?: Navbox bug - indent a navbox and all subsequent text, headings, etc will also be indented until the end of the page?!?) |
(Improved the sectioning by bringing all the {{repo link}} sections under one heading.) |
||
| Line 119: | Line 119: | ||
<references /> | <references /> | ||
== Complete overhaul of the repository link templates == | == The repository link templates == | ||
=== Complete overhaul of the repository link templates === | |||
I have now performed a complete overhaul of the repository link templates (see {{tl|repo link/doc related}}). This was motivated by the incomplete state of these templates, the lack of standardisation, the lack of SourceForge git repository support for {{tl|repo link}}, web-interface only support, etc. I have used a lot of recursive transclusion for standardisation, so that there is a single point for updating for any FlightGear infrastructure changes. This is the master {{tl|repo link}} template. All the other templates are subtemplates which recursively transclude from this master template. I have also created a number of documentation templates for simplifying template maintenance (see {{tl|repo link/doc related}}, {{tl|repo link/doc specific file git}}, {{tl|repo link/doc git clone}}, and {{tl|repo link/doc commit}}). The changes were constrained to maintain backwards compatibility as much as possible. However I would like to break this to allow the following templates to be updated to transclude from the master {{tl|repo link}} template: | I have now performed a complete overhaul of the repository link templates (see {{tl|repo link/doc related}}). This was motivated by the incomplete state of these templates, the lack of standardisation, the lack of SourceForge git repository support for {{tl|repo link}}, web-interface only support, etc. I have used a lot of recursive transclusion for standardisation, so that there is a single point for updating for any FlightGear infrastructure changes. This is the master {{tl|repo link}} template. All the other templates are subtemplates which recursively transclude from this master template. I have also created a number of documentation templates for simplifying template maintenance (see {{tl|repo link/doc related}}, {{tl|repo link/doc specific file git}}, {{tl|repo link/doc git clone}}, and {{tl|repo link/doc commit}}). The changes were constrained to maintain backwards compatibility as much as possible. However I would like to break this to allow the following templates to be updated to transclude from the master {{tl|repo link}} template: | ||
| Line 147: | Line 148: | ||
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:15, 27 February 2016 (EST) | : —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:15, 27 February 2016 (EST) | ||
=== Repository link update === | ==== Repository link update ==== | ||
For those following, I have massively expanded the capabilities of the {{tl|repo link}} template: | For those following, I have massively expanded the capabilities of the {{tl|repo link}} template: | ||
* The SourceForge URLs are now comprehensive. | * The SourceForge URLs are now comprehensive. | ||
| Line 170: | Line 171: | ||
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:53, 8 March 2016 (EST) | [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:53, 8 March 2016 (EST) | ||
== Archived newsletters and dead links? == | === Archived newsletters and dead links? === | ||
Do we have a policy for the dead links in the FlightGear newsletters? It is obviously good to preserve the historic state. But there are many Gitorious links that could be made functional again using the {{tl|gitorious source}} template to point to the historic Gitorious archives (including the official FlightGear repositories, rather than using {{tl|fgdata source}}, for example). The https://gitorious.org links have been converted from URL/path based to query based, so absolutely all of the old links are broken. I am steadily converting all Gitorious links to use the [[Template:repo link/doc related|{{obr}}repo link{{cbr}} family of templates]], with the exception of the newsletters. | Do we have a policy for the dead links in the FlightGear newsletters? It is obviously good to preserve the historic state. But there are many Gitorious links that could be made functional again using the {{tl|gitorious source}} template to point to the historic Gitorious archives (including the official FlightGear repositories, rather than using {{tl|fgdata source}}, for example). The https://gitorious.org links have been converted from URL/path based to query based, so absolutely all of the old links are broken. I am steadily converting all Gitorious links to use the [[Template:repo link/doc related|{{obr}}repo link{{cbr}} family of templates]], with the exception of the newsletters. | ||