Maybe we need to clarify exactly what are the base modules vs projects. When I open up the solution, I see the base modules as the only ones with source available.  The project modules appear to be anything in the DesktopModules, there is no codebehind source. 

While I agree that not everyone would need all of the simultaniously, there are developers out there that really would appreciate having a zip of all of the available projects in one master zip.  It's a drag to go to each project and download them seperately, and very time consuming, extra keystrokes and the like.  Now, I'm not saying that it is a must-do thing for everyone, but surely it is an option that is missing.

In my dnn explorations, I find it really beneficial to see how other modules handle certain aspects of development.  Sometimes viewing a different approach sparks a creative burst that gives rise to a new feature or module, reusing code that's been done in one of the projects.  During that creative exploration, I find it distracting to go download another project zip.  Why not just have them all available at the ready?   Now, I have to download all of them in seperate sessions, which takes a lot of extra work, not a whole lot, but you know what I mean.

In my download of the source for DNNv3.2, I got source for the DesktopModules, but in DNNv4.x, we get a split.  So, it's just a bit confusing, and frustrating. (Miss those good old days with access to the Vault. :).

I, also, believe DNN is evolving, but I'm just pointing out that the feature is missing and wondered about how other felt about it.  I'm not saying it needs to be in the dnn version source zip, but a seperate zip with all of the modules.  As long as we are talking about evolving, it would be cool to offer a dropdown list, or enumerate the projects with a checkbox that could be used to assemble a zip of the files desired.  Now, that's evolution!