View Source

h2. Technical Coordinator

The current Technical Coordinator for SCAPE is [~pmay] (BL)

h2. The Technical Coordination Committee

In SCAPE, the collaboration of the developers and Testbeds will be related to and governed by the Technical Coordination Committee (TCC), chaired by the project Technical Coordinator. The TCC will

* Ensure technical and architectural consistency of software and research, activities throughout the project, coordinated both internally and with stakeholder communities;
* Provide ongoing technical overview and direction for the project by authoring implementation guidelines and defining the overall project architecture;
* Define interfaces between sub-project software components;
* Ensure quality of software;

Regarding the final point, functional reviews will be carried out every six months; that is, component functionality will be tested against the development roadmap of the sub-project. For example, preservation components will be checked for compliance with project interfaces and Platform requirements. The review of a given sub-project will be carried out by the TCC representative of another sub-project.

h3. Responsibilities

Responsibilities include:

* Running the [Technical Coordination Committee|].
** Warn TCC members the day before via [the mailing list|].
** Afterwards, post summary to [the TCC mailing list|] and to the [SharePoint sub-site as an Announcement|].
* Ensuring the [SCAPE Daily Virtual Stand-Up Technical Meeting|SP:SCAPE Daily Virtual Stand-Up Technical Meeting] takes place.
* Ensuring the [SP:The SCAPE Functional Review Process] is carried out.
* Ensure people have the right access, and are in the right groups:
** If an email address crops up that is not clearly from a partner, query with a contact to make sure the person is genuine.
** Manage membership of the [OPF Labs SCAPE Group|].
** Manage membership of the TCC mailing list (project members only).
** Manage membership of the Techie mailing list (open to the public, but no spammers please\!)