[Matt wrote] ---- ... I think we also need to think about breaking "core" into more modules as well and start thinking about the modules as a way to compose a target application that includes the pieces it needs. For instance, the username& password management infrastructure, while incredibly valuable to some, is something that we have no need for internally and I would like to find a way to split that out into a separate security module.
One caution: we will have to be careful of is an explosion of modules and should logically compose them so that they are easy to understand and work with. ---- I would add that an explosion of modules might be a *very* good thing if: - an ecosystem exists to promote, share, and co-develop useful modules (while filtering out the useless ones)... think App Store, but without Apple at the cash register ;) - dependencies between modules can be declared (e.g., I want to use a module that enforces password strength requirements - but it needs the password authentication module in order to operate) - a workable module format is established in advance (+1 on Matt's point on logical composition) - the core remains lightweight - which it should, if the "optional" features are separated out Stan Drozdetski MITRE
