I've been following along but trying to avoid getting cast on either of sides of the trenchline on this - mostly because it has expanded to four fronts, two insurrections, one well-organized resistance, and a smoldering guerilla war - but also because I am really of the opinion that something DOES need to be done here.
However, for completely academic purposes...
** At what point is a rule set changed enough that it's no longer "Improved Touring?"
** Is it necessary that a new class to address the policy issues Ron opened with be called "Improved Touring?" What if it creates additional problems - organizational, philosophical, or cultural - by doing so? Is it worth the cost?
** To what degree are the benefits of a new class balanced against the inevitable down-sides? What ARE some of the potential unanticipated outcomes of the addition of Class X?
How about setting free some of the preconceived notions for the sake of brainstorming what this class SHOULD be, if it could be anything it wanted? Don't hem anyone in at this point by having to address the IT wheel rules or anything else.
What would it look like?
I understand the logic - and it's good logic - of not trying to create a whole new category, instead "simply" creating a new class within IT. However, there might be sufficient smaller issues that need to be resolved, that trying to put it under the IT tent might be counterproductive - giving people too many things to worry about.
K
However, for completely academic purposes...
** At what point is a rule set changed enough that it's no longer "Improved Touring?"
** Is it necessary that a new class to address the policy issues Ron opened with be called "Improved Touring?" What if it creates additional problems - organizational, philosophical, or cultural - by doing so? Is it worth the cost?
** To what degree are the benefits of a new class balanced against the inevitable down-sides? What ARE some of the potential unanticipated outcomes of the addition of Class X?
How about setting free some of the preconceived notions for the sake of brainstorming what this class SHOULD be, if it could be anything it wanted? Don't hem anyone in at this point by having to address the IT wheel rules or anything else.
What would it look like?
I understand the logic - and it's good logic - of not trying to create a whole new category, instead "simply" creating a new class within IT. However, there might be sufficient smaller issues that need to be resolved, that trying to put it under the IT tent might be counterproductive - giving people too many things to worry about.
K