20,741
edits
Template:Project infrastructure: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
__NOTOC__ | __NOTOC__ | ||
== Goal == | == Goal == | ||
To be a universal template for referencing the current open source infrastructure used by the FlightGear project. Should the project 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>), 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>http://wiki.flightgear.org/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>. | To be a universal template for referencing the current open source infrastructure used by the FlightGear project. 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, tooks months to complete and was everything but a nice 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> | |||
Should the project 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>), 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>http://wiki.flightgear.org/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. | 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 reduce the amount of work needed to maintain our wiki articles up to date. | 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 reduce the amount of work needed to maintain our wiki articles up to date. | ||