13,212
edits
Template talk:Ticket: Difference between revisions
Jump to navigation
Jump to search
→encapsulate registration/ticket creation ?: I think I will add the templates I mentioned soonish. Yep, templates simplifies maintenance
mNo edit summary |
(→encapsulate registration/ticket creation ?: I think I will add the templates I mentioned soonish. Yep, templates simplifies maintenance) |
||
| Line 3: | Line 3: | ||
== encapsulate registration/ticket creation ? == | == encapsulate registration/ticket creation ? == | ||
we could easily support all main use-cases by combining related templates, e.g. <nowiki>{{Issue Tracker}}</nowiki>, which also encapsulates the registration and ticket creation processes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:00, 1 April 2015 (EDT) | we could easily support all main use-cases by combining related templates, e.g. <nowiki>{{Issue Tracker}}</nowiki>, which also encapsulates the registration and ticket creation processes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:00, 1 April 2015 (EDT) | ||
| Line 16: | Line 15: | ||
:: thank you for your cleanup and documentation work, much appreciated ! Also thanks for your feedback - I am not opposed to handling this the way you say, I just figured that it makes sense to keep everything in a single place - i.e. for better maintenance, the reason being that updating stuff later on takes usually many months (if not even years). So by having dedicated templates for these things, updating should become easier hopefully. I was also hoping that similar templates could be used for "encapsulating" processes related to mailing list subscription, forum signup/participation, or even wiki registration - i.e. if there's ever the need to update things for some reason, there's only a single place/template involved. I do think that the Git link/repo link work has demonstrated remarkably well that it pays off to follow the DRY principle - which is what I was trying to do here, too. If we had done that with our fgdata docs (on using gitorious/git), it would now be much easier to update things for svn/fgaddon - which would be one of my long-term goals to ensure that we don't have to update dozens of articles manually --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:39, 1 April 2015 (EDT) | :: thank you for your cleanup and documentation work, much appreciated ! Also thanks for your feedback - I am not opposed to handling this the way you say, I just figured that it makes sense to keep everything in a single place - i.e. for better maintenance, the reason being that updating stuff later on takes usually many months (if not even years). So by having dedicated templates for these things, updating should become easier hopefully. I was also hoping that similar templates could be used for "encapsulating" processes related to mailing list subscription, forum signup/participation, or even wiki registration - i.e. if there's ever the need to update things for some reason, there's only a single place/template involved. I do think that the Git link/repo link work has demonstrated remarkably well that it pays off to follow the DRY principle - which is what I was trying to do here, too. If we had done that with our fgdata docs (on using gitorious/git), it would now be much easier to update things for svn/fgaddon - which would be one of my long-term goals to ensure that we don't have to update dozens of articles manually --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:39, 1 April 2015 (EDT) | ||
::: You are most welcome. :-) | |||
::: I think I will have a try at implementing the ideas in my post above in the upcoming days. | |||
::: Indeed, using templates, in particular for often used stuff will help maintenance a lot. In addition, the easier the maintenance is, the more likely it will be done. ;-) | |||
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:02, 2 April 2015 (EDT) | |||