[General Omni Discussion] pulser_g2:
I shall now try to reply to as many posts as I can :)

My view is that we try to fix as much as we can - I suspect Google will release another iteration of AOSP before big-time launch, hopefully to resolve some of the issues. Most of the crashes aren't insurmountable. In terms of moving to the more modern, material-inspired design (hopefully minus the badly matched colours they seem to love), that's going to take time and effort. That's where the more help we can get, the better.

Every ROM will benefit if we, as a community, can get a proper, material-designed SMS app sorted out - stock is, as I gather, still left on the old UI. Same for browser etc. Talking of browser, it really needs a complete overhaul now that Google prefers their own Chrome browser.

Omni with prebuilt kernel - Google hadn't released the blobs or sources at that point, and the 4.4 one wasn't good enough to get it booting. Hopefully soon they will.

Yeah, but I will still abbreviate it to L, and I suspect a lot of others will as well. L is a nice, convenient name :) It's one single key-stroke. :)

Presumably it doesn't have a device maintainer working on it - Omni is entirely a community ROM, but that does mean we rely on the community to port it to new devices, and then maintain these ports.

Unfortunately one of the main reasons for devices going unsupported with L will be lack of maintainer attention. If there's no maintainer that is participating, it's difficult for them to do things, and keep their device up to the standards expected of a stable ROM. Omni aims to be (and from comments everywhere, certainly appears to achieve) incredibly stable, despite bringing forward new features.

See reply above.

I didn't say those words at any point in my post, though? Actually, something I've been quite keen to encourage is greater collaboration between ROMs. Unfortunately not many are interested, but going forwards, with Google apparently intent on closing down Android, it would be beneficial for people to realise this is not a case of petty squabbling, rather that they can do better than Google.

Omni isn't about trying to add more buttons or switches than another ROM - it's not in competition with another ROM. It's about making something that is more stable, and reliable, than AOSP. It's about taking AOSP, and making it usable on a day-to-day basis. It does that while being an unfunded community project, contributed to by developers in their spare time.

Actually, it's quite nice to see the number of developers from other ROM projects that drop in to chat about things, and bounce ideas around. :) Given the number of devices likely to be cast off by Android 5.0, I think there's a lot of scope to have a supported Android 4.4 long-term support branch. These things would all need significant cross-ROM cooperation, which is something we're very keen to encourage.

That isn't necessarily the "roadmap" as such - that's just basics that max was writing up. Here's a rough example of "roadmap" kind of ideas with regard solely to security - http://docs.omnirom.org/Security_features. The ideas are there, but it's very difficult to get motivated people involved.

It's scary that these days, iOS8 is actually ahead of Android in terms of protecting user privacy in a number of ways.

Well, the general consensus on the bump towards 5.0 is that user experience is key. This isn't about quickly porting forward features, rather about carefully considering the best way to make them fit in with the new way of Android 5.0. For example, Quiet Hours is now not the way forward - there's a system-level do-not-disturb. Omni's goal remains about taking stock Android, and making it more usable, while remaining rock-solid on stability. No crash is acceptable, no regression should go unchecked. It's about taking AOSP, fixing the things they didn't get right, making it more usable, adding customisation where needed, and making it work on all devices, like Android should be.