I
I don't think that's the issue here. The issue is that the current process is as long and dull as the old manual way of doing things. The issue is that this could be so much easier to the point of clicking several buttons and be done within several minutes. Instead you have to ask for permission!?! To use the mod? Why? The mod devs gave their permission when they posted the mod on the forums and said "go ahead and download". Now I do understand if you were going to distribute the mod because then the mod dev may or may not get the credit for it. But in the case of the private packs you aren't doing that. FTB is distributing the mods and they have permission from the devs. So why does the average user need to go to 20 different forum posts to write the same post or maybe pm the dev, asking for permission that may or may not be given?
Because you putting the 'server mod pack' in your Dropbox for your friends is different than the FTB Launcher allowing anyone with the Launcher potential access to it. Your problem is that your server pack can 'go viral' just like Technic did, and end up with the same problems Technic had with not getting permissions and getting people irate about it. When Yogscast hit up the Technic Pack, their usership went from about a dozen to several thousand, practically overnight. Because Yogscast pointed everyone to where they could download the Technic Pack, it became widely distributed to people not on their server, and suddenly it became Not Okay.
If you set it up so that your server pack can be downloaded by anyone with your server code, all it takes is that server code to end up somewhere and your server pack has the potential to have the same thing happen to it, with the same unfortunate drama that ensues. And the FTB Launcher would be tarred with the same brush for being the vehicle of that distribution.
Ownership of the Mods is with the Mod Owners, not with FTB. Granting FTB permission for one, or even a half dozen, Mod Packs does not equate granting them blanket access to any and all mod packs they might ever want to make. Unless every single mod author signs off on a blanket waiver of "The FTB Team has the right to distribute my mod as they see fit in any and all projects they undertake", the FTB team ONLY has permission for those specific mod packs the mod authors signed off on.
Now, I agree, it would be really cool for all the mod authors to sign off on a blanket waiver like that, because it *would* enable the FTB team to do something like what you envision, basically you pick and choose which mods on the 'menu' of available mods which have those blanket permissions granted you would like in your mod pack, then badda-bing, badda-boom, out pops your custom mod pack. Then you could have a variable string which other players could plug into the FTB Launcher to get the exact same one.
However, with that flexibility, there comes a potential problem... Mod Packs are made so everyone is on the 'same page'. If you see a server that says 'We run on the DirePack', then everyone knows what that is, and can use it. Customization on that order would pretty much mean every server has a different mod loadout, meaning everyone has to download yet *another* mod pack to play on that server. Each mod pack being several hundred megs in size... you're quickly adding up into the gigs of data for all these custom packs, rather than a single pack for all. And 'convenience' really wouldn't be very convenient anymore, because you're still having to download everything.
Furthermore, it adds another level of obscurity on the mod authors. For those who followed DW20's Forgecraft Server Let's Play, did you have ANY idea who the guy who handled MCP actually WAS and why his work was so important to EVERY modder out there until it was explained? No? Now take that level of obfuscation and apply it to the mod authors. Now they aren't even getting recognized for their work, except by the FTB team and the 'insiders'. The average joe user won't have a clue, because he won't need one. That also means fewer donations, and fewer adfly hits, which means they won't even be able to afford the hosting fees for their mods anymore. Which means the mods themselves just won't be updated anymore... and we simply won't have those mods anymore. It's already a labor of love, that would just turn it into a labor.
Heck, I've got most of the mods I prefer to play with downloaded into my MultiMC/Mods/1.4.6 folder. I want to make up a custom pack for me to play on, I just refer to that folder and pick out the ones I want. I don't need to re-download any of them. That's what a Config Pack does... and that's why Config Packs are so useful... odds are, you've already GOT most of the mods on your computer already, you just need to point to them. And every one you don't need to download is less bandwidth used, less time downloading crap you already have, and fewer gigs bloating up your hard drive.