Template talk:Repo link: Difference between revisions

Jump to navigation Jump to search
m
Topic header, link, grammer
(→‎Todo list: Clean up mess, finalize {{repo link}} list.)
m (Topic header, link, grammer)
Line 1: Line 1:
== needs to be updated for different protocols ==
== Supporting different protocols ==
 
Specifically for <nowiki>git://</nowiki> - which will help centralize all repo URLs - e.g. to replace all URLs with a corresponding template, instead of having  <code>git://git.code.sf.net/p/flightgear/simgear</code> everywhere - we should probably introduce a <code>proto</code> parameter that defaults to http/https and which can be overridden so that "git" can be specified. We want to avoid having to manually update all related articles in the future (if/when another repository needs to be moved) - e.g. [http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Linux&curid=1323&diff=83168&oldid=71205].
specifically for <nowiki>git://</nowiki> - which will help centralize all repo URLs - e.g. to replace all URLs with a corresponding template, instead of having  <code>git://git.code.sf.net/p/flightgear/simgear</code> everywhere - we should probably introduce a <code>proto</code> parameter that defaults to http/https and which can be overridden so that "git" can be specified. We want to avoid having to manually update all related articles in the future (if/when another repository needs to be moved) - e.g. [http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Linux&curid=1323&diff=83168&oldid=71205].


--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:10, 4 April 2015 (EDT)
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:10, 4 April 2015 (EDT)
Line 26: Line 25:
:: Once we adapt the new repo link template, we could easily use that for also maintaining everything easily. And the corresponding clone/checkout/push and pull templates could also contain instructions for different front-ends (think git command line vs. TortoiseGit), to help generalize our docs, especially for people on Windows/Mac OSX not as familiar with CLI environments.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:59, 5 April 2015 (EDT)
:: Once we adapt the new repo link template, we could easily use that for also maintaining everything easily. And the corresponding clone/checkout/push and pull templates could also contain instructions for different front-ends (think git command line vs. TortoiseGit), to help generalize our docs, especially for people on Windows/Mac OSX not as familiar with CLI environments.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:59, 5 April 2015 (EDT)


== FlightGear have completed the move from Gitorious ==
== FlightGear has completed the move from Gitorious ==
{{FGCquote
{{FGCquote
   |FlightGear has completely moved all its gitorious based material over to< sourceforge.  But it's nice to know a historical record will remain at gitorious.org as well as several other public locations not to mention on a myriad of personal computers.
   |FlightGear has completely moved all its gitorious based material over to< sourceforge.  But it's nice to know a historical record will remain at gitorious.org as well as several other public locations not to mention on a myriad of personal computers.
Line 107: Line 106:
'''To do'''
'''To do'''
* {{tl|Repo link}}
* {{tl|Repo link}}
** Protocols (e.g., <code><nowiki>git://</nowiki></code>, see [[#needs_to_be_updated_for_different_protocols|above]])
** Protocols (e.g., <code><nowiki>git://</nowiki></code>, see [[#Supporting different protocols|above]])
** Add Mercurial to repo types
** Add Mercurial to repo types
** GitLab option
** GitLab option

Navigation menu