The fact that features are tested in Plone core IS the selling point in having them in core. You can know they are stable and well tested. With add-ons, you run the risk that they are of poor quality.
Additionally, how do you ever attract new comers. If near releases have no real new features? We're a CMS, not a framework. So let's do CMS-like things OOTB.
You should have that merged. Just have to fix tests. We've all been there fixing broken tests. It happens with lots of merges--not a big deal. Just need to fix. I will also mention, it's very easy to run the whole test-suite against a pull request now with jenkins.
Hi again @jaroel , I've just got time to try this out, and I'm glad to report that it does seem to play nicely with plone.app.multilingual. I just simply choose not to enable the Multi Language behavior.
It's always to see things in github collective, but I don't see an immediate need for changes
(though there's a typo here it should say "login form" not "homepage")