Fix views compatibility issues (2.x, 3.x), spin off i18nviews module?

While there's a new branch for development of the views (6.x-3.x) and the i18nviews module has never been fully completed, we've been trapped in the middle of a few security releases for both modules, which resulted in i18nviews trying to be compatible with both views branches and some ugly hacks.

While I wouldn't like to branch the whole i18n, creating a separate i18nviews module with two (2.x, 3.x) branches would be an option and that would allow i18nviews to move faster and keep up with views development.

Ideas / patches / who would like to maintain the new module?