woooah... Let's back up a little bit here. As previously stated, William, your enthusiasm is great and we all appreciate/enjoy it, but I believe your naivety is causing you to race ahead of us.
Let's not create problems or controversy before there are actually problems. If the community embraces the project as we think they will, there's nothing to worry about but making our project better for everyone.
Secondly, those involved with Open Source and Joomla are not against making money. If your start hosting Joomla sites, that's a perfectly reputable business/service that I doubt anyone is going to have a problem with.
Hopefully I've understood you correctly, William.
Anyway back on track here:
Rogue4ngel, you mentioned some excellent ideas:
Having a central repository on the web so we don't necessarily have to package the components with the program itself, but have it pull them on the installation as necessary. This way we can do one update and guarantee that one someone does run the installation, they'll be getting all of the latest versions of what they need.
This is my ideal setup as well. I'm not sure what programming level you're at, but I would like to collaborate and share ideas of a practical way to accomplish this using PHP/MySQL/XML/etc. Just thinking about it without putting it on paper, I have a few ideas that may a good start.
This might be overreaching a bit, but perhaps we don't have to distribute any software. Could we run a site that allows users to go through a series of questions, which then in turn connects to their site and installs everything for them. They wouldn't even necessarily need a separate program, ftp program, or anything else.
Not overreaching at all! In fact, I think it's a valuable idea. If you've ever noticed how many people use JoomlaPlug's remote installer, it's quite shocking. Big time saver for a lot people.
That said, however, I don't think it is something that would need to be implemented immediately. First things first: develop a stable system that packages Joomla along with 3PD elements (templates, extensions, etc).1.0 vs 1.5
Again, just thinking about it, I don't believe it would be a major challenge to have 1.0 and 1.5 Joomla bundles built using the system. We'll have the logic in place, updating table names and file names and locations shouldn't be difficult.
Also, let's remember that a good majority of extensions aren't even 1.5 compatible yet. So, even when 1.5 is officially released, it will take some time for everyone to migrate over their extensions and websites. Supporting both versions is a good way to get community support, IMO.Another Idea
Here's an idea that's inline with William's focus... Offer "Optimized Joomla hosting" as a service that can be added at some point during the process where users are "building" their bundles. This gives them the option to build a package and a) download it or b) have it setup and hosted on an "optimized server". The idea needs refining, but I think you see where I'm going with it
That's all for now