I have mentioned this before but I really don't think we should have 15+ modules in a basic module pack.. When we say "Basic" that to me says the modules that EVERYONE would use...
These do NOT need to be developed by the core team but they need to be considered as stable and "bug free" as the core does. This can happen over time just as the Protector module, Profile and PM modules have.
I think we should look at these "packs" being much smaller.
The Basic module pack should be something we all will use no matter what. With that in mind If you remove the Gallery and Download modules then I would agree.
Looking at the Modules packs as an Idea I can see we may end up having issues with different packs containing different versions of the same modules unless we standardize the packs to ONLY contain certain modules.
So lets say we figure out we could separate the 25-30 suggested modules into 5 different packs. Some modules really are too specialized to be included in a "pack" but may be something that we really can make use of. Just because they are important modules we shouldn't just attach them to a pack for the sake of sticking it in a pack. Packs should contain related modules that together provide a solution.
So instead of my installing a module pack on my site that contains 20 modules and I have to figure out which modules I need...
I instead want to have an xyz site that to build it is suggested I install packs 1, 3 and 5.
However the idea of a module pack will be obsolete assuming I am successful with what I am working on over the next few months. (Done with my classes and getting back to work on xoops stuff this week.. )
Attending College working towards Bachelors in Software Engineering and Network Security.