2,732
edits
(→Todo list: Added linking to "Template:Fgaddon aircraft url") |
Red Leader (talk | contribs) (→Todo list: Reply to Johan G) |
||
Line 159: | Line 159: | ||
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:27, 26 May 2015 (EDT) | : —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:27, 26 May 2015 (EDT) | ||
:: Hi Johan, | |||
:: Sorry for the delayed reply. | |||
:: Just checking, am I right in saying that you're suggesting that there should be a template for Git repos and a separate one for FGAddon (an SVN repo)? It's just a bit hard to read what you mean above. Anyway, apart from that, here's my feedback: | |||
::* '''Oft used parameters:''' Using unnamed parameters is good idea. The parameters that would commonly be used would be <code>site</code>, <code>proj</code>, and <code>path</code>. I don't think <code>commit</code> is used as much, though. | |||
::* '''Defaulting:''' Where possible, it's probably best to use defaulting, rather than throwing errors. | |||
::* '''Aircraft URL templates:''' Another good idea. | |||
::** We should probably link to info page URL. Linking directly to download may catch users out when it automatically starts downloading. | |||
::** http://forum.flightgear.org/viewtopic.php?f=42&t=26167 ;) | |||
::* '''New category:''' Agree. | |||
::* '''Upper/lowercase names:''' Yeah, we should use lowercase names, especially in the documentation. | |||
::* '''Name suggestions''' I think ''repo'' instead of ''source'' should be used. It's less typing and a bit more descriptive. Also, {{obr}}fgaddon repo{{cbr}}? URL template names are fine to me, though. | |||
:: Also, do you have any suggestions for link styling above? | |||
:: Regards, | |||
:: [[User:Red_Leader|<span style="color:red">'''''Red Leader'''''</span>]] ([[User_talk:Red_Leader|Talk]], [[Special:Contributions/Red_Leader|contribs]]) 06:03, 31 May 2015 (EDT) |