Split up hostmaster_plus into several modules and use this namespace for an install profile

May be able to all the modules in this project are independent you although enabling all of them gives you full functionality.

Yea I can do that, This was sort of a sandbox project to get things to a somewhat stable state, so that i could see issues easier, ill look into breaking them out. I have got some feedback from i think it was anacrat that I may want to use another namespace besides hostmaster_ any ideas or suggestions on it would be helpful.

I guess the aegir name space is protected/privileged too... but I am testing out the idea of Aegir Ecology .. I have aegirecology.org/.com and would consider some kind of community project .. dunno

@cmcintosh - i thought the "hostmaster_plus" name was non-sensical, in general. if you make your own custom install profile, call it "hostmaster_chris" or something, or us a more descriptive name, not "doubleplusgood". ;)

As for the modules, I agree with sfyn they should be split out, so that people can build their own distribution. What if, for example, I wanted the services API but not the bandwidth stuff? Then I would need to implement my own "hosting_resources" module, and bang, i'm screwed because the module is installed and I have a namespace conflict.

If unrelated functionality is merged together here, I think it should be in the official core repositories (provision/hostmaster). Contrib should try to stick with the UNIX philosophy (do one thing and do it well).

Furthermore, there is a specific namespace problem already - modules should be named hosting_foo. It's only profiles that should be named hostmaster_bar. If you write code for the backend (e.g. the stuff you have in _drush/hostmaster_resources.drush.inc), it should be prefixed with provision_ (so that would be provision_resources.drush.inc, and you wouldn't need to have a silly _drush directory there :).

Also note that backend/frontend stuff is usually separated in different repositories, or at least directories so that the backend will not pickup the frontend .drush.inc commands (and vice versa).

@niccolo not sure what you want to do with that domain of yours, isn't the community site and drupal.org enough to share and discuss contrib module and the aegir ecology?

I just did a huge cleanup of the contrib section of the wiki, let me know what you think!

http://community.aegirproject.org/contrib

hey anarcat,

thanks for all this AWESOME documentation, the contrib section rocks

the idea for aegir ecology emerged in contrast to the drupal gardens. I have no solid plans, just ideas, which I am floating as Aegir Crazy Ideas

I was thinking that the Aegir Ecology is a name for an existing ecosystem of projects, hosts, people around the Aegir Project and its a business model as well as a product

compare the open source business model of Aegir Ecology with the Drupal Gardens stack and you've got some complimentary and some competing areas.

I guess its a matter of, do you want Fair Trade Biodynamic Organic Shade Grown Aegir Ecology ? or do you want McGaia Drupal Gardens ?

dunno really, an Aegir Crazy Idea, was going to do a presentation in Davis about it
http://community.aegirproject.org/discuss/aegir-ecology-vs-drupal-garden...

Hi cmcintosh,

I'd like to echo sfyn's and anarcat's suggestions to split this into separate projects. More modularity should make it easier for others to test, use and hopefully enhance those components they feel are most useful to them. A case in point being Koumbit's interest in your Services API work. Furthermore, though I'm not a maintainer of Aegir core, I suspect that better isolation of functionality would increase the likelihood of some components being integrated directly into Aegir core.

You could then pull the components together into a "wembassy" install profile, or the like.

@niccolo: I think such discussions are vital for the ongoing growth of the community, though I'd prefer to see them within the Aegir community at this point. Take, for example, the importance of standardizing backup formats, to ensure site/platform portability and avoid vendor lock-in. Without the participation of Aegir contributors and maintainers in such discussions, the chances of implementing such things is virtually nil.

That said, I strongly support innovation at the business model level. BTW, I'll be the presenter of Aegir-based Business Models at DrupalCon London (assuming it gets chosen).

I've been keeping my conversations within the community, so far I've been talking to myself. Like most crazy people I guess. http://community.aegirproject.org/users/niccolo

+1 subscribe
https://github.com/sfyn/hosting_services

excellent ! subscribing

Sounds fair to start a new branch for each of these projects sorry I have not responded as I am in the middle of moving and for some reason not getting updates from drupal.org about these things. @sfyn would love to do co-maintenance with you.

@ergonlogic sounds great wish i could make the london drupalcon, however stuck moving for the moment, would be willing to give you some of my experiences and what I am doing at the moment on my own. I have been looking without much luck for some partners as far as building something like Drupal Gardens, but also with a built in Job board that could help beginning devs find work as well as promote drupal as a serious business product.

I gave a presentation called Aegir Ecology vs Drupal Gardens at the Sacromento Drupal Camp

a couple of Drupal luminaries where in attendance, which was nice (and daunting)

http://sacdrupal.org/program/sessions/aegir-ecology-vs-drupal-gardens
http://sacdrupal.org/sites/default/files/slides/aegir-ecology-vs-drupal-...

@niccolo: I encourage you to post your slidedeck here: http://community.aegirproject.org/presentation/slidedecks

I have been doing some recent work with aegir again along the line of development platforms and integrating git so that you can use git to spawn up new platforms from a branch/tag/etc. I would appreciate whenever you mention this project or Aegir Services taht you mention my project over at wembassy.com as well.

Thanks,