-
Notifications
You must be signed in to change notification settings - Fork 0
CoordinatorRole
rml599gh edited this page May 10, 2017
·
15 revisions
-
Ensure reporting needs on CABLE are met via a biennial (6 monthly) report which will serve as (i) communication to managers (CSIRO e.g. CSC director and/or group leader, Unis e.g. ARCCSS/CE director , BoM) and (ii) a record of code developments and acknowledgement of contributors, based on closed Tickets. (Science Coordinator).
-
Chair and document monthly Committee meetings (chairing and documenting to alternate between Science and Technical Coordinators)
-
Circulate Monthly CABLE updates via CABLE email list and wiki (Technical Coordinator)
-
Facilitate community-wide science development via working groups (Science and Technical Coordinators)
-
Guide broad research directions by communicating CABLE deficiencies (Appendix to Annual report) and by shepherding CABLE developments, particularly by encouraging early ticketing and communication between developers with common/interacting developments (Science Coordinator)
-
Guide up-dates to code documentation, at least by linking to papers. (Science Coordinator)
-
Processing Tickets. (Technical and Science Coordinators in conjunction with Committee)
-
Tagging Trunk versions (Technical Coordinator)