To do that, we would first need to orphan {{term}}, as the parameters are not compatible. And at that point there is no need for a redirect anyway, is there? —CodeCat20:03, 12 September 2014 (UTC)[reply]
We should aim at there being one template in the mainspace. We should aim at at least a semblance of professionalism. Keeping term with old parameter order to make old revision legible is fine. --Dan Polansky (talk) 20:13, 12 September 2014 (UTC)[reply]
Support — It's better to have one term (whichever) than two - since the newbie suspects there's a subtle difference between them. Since most will look for an example (like me) either would do, but m is shorter — Saltmarshαπάντηση19:30, 5 November 2014 (UTC)[reply]
Weak support — I can agree that "term" is more descriptive than "m", which can be confusing. On the other hand, not needing a named language parameter makes things a lot easier. ObsequiousNewt (ἔβαζα|ἐτλέλεσα) 00:14, 25 November 2014 (UTC)[reply]
Support "term" does not mean what it says, and it's NOT more descriptive; it's misleading, beside being longer. "m" would force the newbies to read the docs, which is eventually a good thing, because by seeing "term" they probably think that they already know what the template does, while they usually don't. --Z10:07, 1 December 2014 (UTC)[reply]
Support. {{m}} is much easier to use and should be the default. I agree with Wikitiki89, though, that it's best to leave {{term}} functional, since it's been in use for so long, and because we should go as easy as possible on casual editors. I think the best course of action is to swap out current uses of {{term}} to reduce confusion and encourage the use of {{m}}, but not to introduce any overt obstacles to use of {{term}} by those who want to use it (hidden tracking categories should be ok). I can understand the resentment of many here for the way the changes in behavior of some templates with respect to omitted language codes was handled, but, on balance, I think this is a better course of action. Chuck Entz (talk) 20:15, 3 January 2015 (UTC)[reply]
Oppose No user will ever guess what {{m}} means, while the meaning of {{term}} is rather obvious. We need to think about non-regulars and casual contributors too. -- Liliana•18:05, 29 August 2014 (UTC)[reply]
At least the name of {{m}} is intriguing while term is misleading - one may take it for only a decorating template (like I did until recently xD).--Dixtosa (talk) 19:07, 29 August 2014 (UTC)[reply]
Oppose. The name term is more comprehensible. The old revision histories will be clearer (not that that's a strong argument in my opinion, but it's worth something). And even if all were equal (m and term were equally good), there'd be no reason to specifically change from one to the other. I have no opposition, however, to reordering the parameters of either template to match those of the other, provided that that's done without introducing errors.—msh210℠ (talk) 16:35, 18 September 2014 (UTC)[reply]
Oppose – I read the ‘rationale’ but can't see any explanation…does this new template do something different? If not, why can't we just change how {{term}} works? And why ‘m’?! Basically, no. Ƿidsiþ08:15, 17 November 2014 (UTC)[reply]
@Renard Migrant I don't think so. The disagreement seems to be about the template name. I don't see anyone insisting that term should be used like {{term|...|lang=en}} instead of {{term|en|...}}. --Dan Polansky (talk) 18:59, 7 December 2014 (UTC)[reply]
For completeness: Mr. Granger said "oppose deleting Template:term. No opinion regarding any other action", so migrating the template without deleting {{term}} has 14-9-3 = 60.9% support. That is still "no consensus". --Dan Polansky (talk) 10:01, 1 March 2015 (UTC)[reply]