Database Software

We are planning to deploy a 10g OWB infrastructure. We will have about three people working on OWB to setup sources, target, ETL, deployment etc. There will be separate linux servers for developement, user acceptance and production. The development will be done on the development server, then deployed to the user acceptance server for users to review. If all goes well, it will be deployed to production. What is the best architecture for this scenario? Are there any white papers that describe the best practices?

Here is our current thought process...
* The OWB client software will reside on each user's windows desktop.
* Should there be one repository that will deploy to the runtime environments of TEST, USER ACCEPTANCE and PRODUCTION environments? or should there be three repositories, one for each environment?
* If there is only a single repository that will deploy to all three environments, should it reside on TEST, USER ACCEPTANCE or PRODUCTION server?
* Does OWB have sufficient version control capabilities to drive three environments simultaneously?
* Is it possible to have an additional development repository on a laptop to do remote development of source/target definition, ETL etc and then deploy it to a centralized development repository? Perhaps it is possible to generate OMB+ scripts from the laptop repository and then run them against the centralized repository on the shared server.

Any feedback/direction would be most helpful.
Thanks.