Skip to content

CoordinatorRole

rml599gh edited this page May 10, 2017 · 15 revisions

Proposed coordinator role split between science and technical

  1. 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).

  2.   Chair and document monthly Committee meetings (chairing and documenting to alternate between Science and Technical Coordinators)
    
  3.   Circulate Monthly CABLE updates via CABLE email list and wiki (Technical Coordinator)
    
  4.   Facilitate community-wide science development via working groups (Science and Technical Coordinators)
    
  5.   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)
    
  6.   Guide up-dates to code documentation, at least by linking to papers. (Science Coordinator)
    
  7.   Processing Tickets. (Technical and Science Coordinators in conjunction with Committee)
    
  8.   Tagging Trunk versions (Technical Coordinator)
    

Back to agenda

Clone this wiki locally