On Sat, 11 Feb 2012 23:58:16 -0800, Patrick Reilly preilly@wikimedia.org wrote:
John DuHart has embarked on a complete rewrite of the current Mobile Frontend extension, and has decided to name it 'MobileFrontend2'. While we would prefer it if we could work cooperatively to resolve the existing open issues in the current MobileFrontend extension and maintain continuity. It's understandable why John would prefer to undertake his complete rewrite.
(See Extension_talk:MobileFrontend#Issues_with_MobileFrontend_and_possible_rewrite_11940https://www.mediawiki.org/wiki/Extension_talk:MobileFrontend#Issues_with_MobileFrontend_and_possible_rewrite_11940 )
However, we feel that naming the rewrite 'MobileFrontend2' is problematic as users have already started to confuse it with the current extension.
One thought was to name it to MobileSkin, but it appears that this extension already exists and we quickly reverted that rename attempt. We're curious to hear the rest of the engineering community's perspective and try to gain some consensus as to how best to proceed.
— The Mobile Team
We already have SubPageList, SubPageList2, and SubPageList3 sitting around (SubPageList and SubPageList3 are in SVN, SubPageList is supposed to be the one more up to date then either the 2 or 3) inside MW.org and SVN. Heck it's hard to have as much of a naming mess as we've had with Dynamic Page List. So I see no reason for MobileFrontend2 to be forced to be renamed.
Can we just let John DuHart get on with writing the code so that we can have a working 1:1 replacement, put it through all the testing we need to make it the mobile code used on WMF's cluster, and then replace MobileFrontend/ with MobileFrontend2/'s code.