The question addressed in this section is ``who is going to do what.'' The CCSM Software Engineering Group (CSEG) should take a role in managing the process described in this document. However, much of the work will be done in conjuction with the CCSM working groups and rest of the community. The component working groups will be responsible for helping manage repository access, change review, planning, and documentation of individual components. The software engineering working group will continue to oversee the CCSM software engineering process and make recommendations. The applications working groups (Climate Change, Paleoclimate) will be carrying out much of the production runs. As such, they will be granted limited read/write access to the repository like any other development group so production modifications can be archived and possibly merged back if requested and approved. The applications groups also need to play a large role in defining data access policy.
As indicated above, CSEG will play a large role in coordination. Individual tasks in CSEG might include overall coordination, liason to outside collaborations, and repository access monitoring. Individuals will continue to be tasked with component development, documentation, and performance optimization. Significant resources will also be allocated to testing; documentation and web support; and tools support, evaluation, and implementation. CSEG should also play a role in data management. The CSEG liason to a component might also act as gatekeeper or test engineer for that component.