I do believe it may be time for DNN to stop trying to be the single stop application and divide into more configuration specific versions (leaner and meaner). For instance, any Intranet implimentation may have no need for payment processing or maybe even localization. Or maybe the authentication mechanism be completey modular with the choice of which one to use (Asp.net or DNN or AD) without any specific version tied to the core. I'm in favor of asp.net membership tied together with AD since it can be used from other applications.  I'm sure that would require even more resources  to support though.