13,212
edits
Template talk:Project infrastructure: Difference between revisions
Jump to navigation
Jump to search
Template talk:Project infrastructure (view source)
Revision as of 21:26, 27 February 2016
, 27 February 2016→Some suggestions: Go step by step; the mode parameter, its name parameter; and a slight variation of the current template implementation.
(→forum) |
(→Some suggestions: Go step by step; the mode parameter, its name parameter; and a slight variation of the current template implementation.) |
||
| Line 7: | Line 7: | ||
yes, that was the idea - I was just expecting to spend a few weeks doing this, and not to come back realizing that you finished the whole thing in a few hours. So, thank you very much for doing this. It is good for us to learn from the sourceforge transition and try to prevent certain issues in the future.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 06:43, 26 February 2016 (EST) | yes, that was the idea - I was just expecting to spend a few weeks doing this, and not to come back realizing that you finished the whole thing in a few hours. So, thank you very much for doing this. It is good for us to learn from the sourceforge transition and try to prevent certain issues in the future.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 06:43, 26 February 2016 (EST) | ||
== | == Forum == | ||
probably need to extend the template a little to support this use-case: http://wiki.flightgear.org/index.php?title=Template:Forum&action=history | probably need to extend the template a little to support this use-case: http://wiki.flightgear.org/index.php?title=Template:Forum&action=history | ||
| Line 21: | Line 21: | ||
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 08:38, 26 February 2016 (EST) | :: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 08:38, 26 February 2016 (EST) | ||
== | == Other URLs == | ||
* scenemodels.flightgear.org | * scenemodels.flightgear.org | ||
| Line 27: | Line 27: | ||
* multiplayer map | * multiplayer map | ||
* add ticket/issue tracker template here ? | * add ticket/issue tracker template here ? | ||
== Some suggestions == | |||
First off, implement this step by step, and think the architecture through during the process. Do not lock yourself in early. | |||
I still have frustrations with annoying inconsistencies and non user friendly naming schemes in the FlightGear screenshot categories due to "flash-implementing" early ideas before thinking them through thoroughly. | |||
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:26, 27 February 2016 (EST) | |||
=== The mode parameter === | |||
I think the '''mode''' parameter is slightly ambiguous and maybe misleading. I would expect it to be something like for example '''type''' or '''infrastructure''' rather than '''mode'''. | |||
As this is an unnamed parameter this is merely a change in the documentation. | |||
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:26, 27 February 2016 (EST) | |||
=== The name value of the mode parameter === | |||
I would say that even though it is an important ''part'' of the project infrastructure SourceForge is merely the host of the main repositories. | |||
Here I would probably rather expect something like for example '''host''' or '''main-repo''' rather than '''name'''. | |||
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:26, 27 February 2016 (EST) | |||
=== Slight variation of the current architecture === | |||
This might make for a slightly more complex template, but consider this: | |||
{{obr}}project infrastructure|''infrastructure''|''attribute''{{cbr}} | |||
All parameters would be optional optional. If none is given it could e.g. default to the URL of the project page at SourceForge. | |||
:; infrastructure: Name of the infrastucture, e.g. '''forum''', '''wiki''', '''main-repo''', '''scenedb''' or '''website'''. Could e.g. default to '''main-repo''' | |||
:; attribute: One of several attributes associated with the infrastructure, e.g. '''name''', '''abbreviation''', '''url''', '''host''' etc. Could e.g. default to '''url''' | |||
I think the template would be slightly more flexible this way. | |||
It could be implemented with two levels of <code><nowiki>{{#switch: }}</nowiki></code> parser functions and use the <code><nowiki>#default =</nowiki></code> case to catch most errors. Something like: | |||
<nowiki>{{#switch: {{{1|main-repo}}} | |||
| wiki = {{#switch: {{{2|url}}} | |||
| name = FlightGear wiki | |||
| short-name = wiki | |||
| url = http://wiki.flightgear.org | |||
| #default = {{error|Attribute '''{{{2}}}''' invalid for infrastructure '''wiki'''|project infrastructure}} | |||
}} | |||
| main-repo = {{#switch: {{{2|url}}} | |||
| name = Main FlightGear repository | |||
| short-name = main repo | |||
| host-name = SourceForge | |||
| host-short-name = SF | |||
| host-url = http://www.sourceforge.com | |||
| url = http://sourceforge.net/projects/flightgear/ | |||
| #default = {{error|Attribute '''{{{2}}}''' invalid for infrastructure '''main-repo'''|project infrastructure}} | |||
}} | |||
| #default = {{error|Invalid '''infrastructure''' parameter|project infrastructure}} | |||
}}</nowiki> | |||
The template documentation should probably be complemented by a table of available infrastructure and attribute combinations. | |||
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:26, 27 February 2016 (EST) | |||