I really appreciate that you spent time in discussing file structure. From the past experience, just by looking at it, it might tell you if a project is going to fail or not.
In your video, you mentioned that you favor organizing by features and not by type. This is very true. You treat each angularJS module as a feature, and inside it you continue use submodule approach. However it's still a mixed model, ex. asset and data folder as well as your common/models folder. It's not 100% by-feature structure.
While this approach may be very effective for very large application which can have submodule inside module. But a typical application might be better in the following way.
First use module to organize functionalities. And we have a folder for all modules (there'll be dependency, but we won't track them by embedding one inside another one).
Inside each module, we'll organize by type, ex. template, script, data, model etc.
This two layer of file structure, by feature first and then by type serves me well for medium size application. For small application, i just organize by type or not organize at all.
This approach also scales well, because it's essentially flat except it's grouped by feature (which is a tag to the type folder inside).