OP needs a progressive install

I no longer have OP installed, except on one site.

It is practical to give up, because so many issues don't make it viable. In my situation, I have a large number of sites to maintain and OP site defeats purpose.

I would love to work with OP and through issues over time, but I would really need a backdoor.

By backdoor I mean the ability to drop back incrementally, but with module dependencies that cannot be done.

First I think OP should start as a "clean drupal" similar to Acquia Drupal.

Second, there should be a clearly defined upgrade path for adding to OP functions.

Third, if there are issues you should be able to disable modules to return to working drupal installation.

Fourth, it would be best to use well supported drupal modules where possible in lieu of proprietary modules.

Five, updating has enough issues, but if there are dependencies with modules it can mean your websites can be vulnerable to security problems.
That is, until OP team has altered the OP install to compensate for dependency and provides updates.

Six, you must remember the module developers are working on their own constantly updating and fixing.
It is tough enough for them to keep up with their one module, much less taking on all their stuff and your own.

Seven, Updating should be done as it is with a normal drupal installation. Run status report, cron and then download and install updates.
OP should have a separate update process that doesn't or isn't affected by third party modules when updating.

I realize so much work has gone into OP and I want to be respectful.

My time is at a premium and I just cannot rebuild sites once they are underway when annomalies and issues make the sites unworkable.

I have one site now on OP 2.2, but I have been reluctant to work with it.

It will take several days to get it fully setup and I'm unsure to spend that time.

I can spend the same time on a regular Drupal site, and know I will have a competent working site.

It will not be as full featured, but everything will work.

I do think the OP concept is viable, it just needs to facilitate site developers better.

We face issues with every drupal module we install. We never know issues can associate with them.

IMO, it is best practice to look at the issues queues before installing any module.

By that I mean, if the module isn't being support it is probably best to not install it.

Even now the feeds modlule is giving some people havoc, and it can create some issues within the nornal drupal install.

I had to rebuild a drupal installation just trying to remove it. LOL

I have read where others have viable installs on shared servers, which is my situation.

Please don't be discouraged by this post, you have an excellent idea and your OP will be a very important application when you have worked through problems.

I look forward to that day, but I see it further away with each update of other modules.

Somehow, you have got to insulate OP from dependencies to drupal 3rd party modules (for sure).