Template:Project infrastructure: Difference between revisions

Jump to navigation Jump to search
GitLab is the new place now, and SourceForge the old one
(Use https protocol (mapserver should be removed too, I suppose?))
(GitLab is the new place now, and SourceForge the old one)
Line 1: Line 1:
{{#switch: {{{1|name}}}
{{#switch: {{{1|name}}}
| name = {{#ifeq: {{{link|yes}}} | yes
| name = {{#ifeq: {{{link|yes}}} | yes
           | [{{#if:{{{noprotocol|}}}||https://}}sourceforge.net/projects/flightgear{{#if: {{{urn|}}}|/{{{urn}}}}} {{{text|SourceForge}}}]
           | [{{#if:{{{noprotocol|}}}||https://}}gitlab.com/flightgear{{#if: {{{urn|}}}|/{{{urn}}}}} {{{text|GitLab}}}]
           | SourceForge
           | GitLab
         }}
         }}
| abbrev = gl
| abbrev = gl
Line 187: Line 187:


== Background ==
== 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
Since winter 2024-2025, most of the FlightGear code and data lives at [[GitLab]] (with a notable exception for [[FGAddon]]). Previously, that was at [[SourceForge]] and even before that, at various places like gitorious, googlecode and on private servers. During the (now old!) migration to SourceForge, getting our build server to 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/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35083587/  
   |title  =  <nowiki> Re: [Flightgear-devel] Shall we migrate code from SourceForge to
   |title  =  <nowiki> Re: [Flightgear-devel] Shall we migrate code from SourceForge to
Line 195: Line 195:
   |added  =  May 12th, 2016  
   |added  =  May 12th, 2016  
   |script_version = 0.40  
   |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.
   }}</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/33553643/</ref>. This template helps isolate required changes during such migrations.


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 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>
512

edits

Navigation menu