---
# System prepended metadata

title: 2023-07-23 TRIC-DT Hub - team meeting

---

---
tags: 
description: first all-hands for tric-dt hub!
---

:::info
* **Date**: 2023-07-12 (==note, date in title is incorrect==)
* **Time**: 12:00
* **Meeting Information**: First TRIC-DT HUB meeting
    


:::

[TOC]

## Agenda

* **Theme**: 
* **Chair**: Chris
* **Links & resources:**

### Apologies
> *Please add your name below if you are not able to attend the meeting.*
* 


## Participants
* Chris
* Cass
* Sophie
* Kalle



### Notes
* Psychological safety
    * It is important that we are able to say when we don't know something, and ask questions comfortably among each other. We should also be okay with disagreeing without being disagreeable (or being perceived as disagreeable).
* 
    
#### Ways of working
* Using hackmd for now, but recognise that it might not the the best space for personal data
* TPS Best practices - github, hackmd
    * Will probably work for us, but will need to move to other practices for working with co-directors
    * Private/public repo decisions
        * Sharepoint might be the best place for private material, especially as access is already set up with directors
    * Github accounts set up with gmail and not coming into Turing inbox.
        * [name=Kalle]: You can add the Turing email on your Github account and putting certain notifications there! I can help with that. [Resource here: https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications]
* Working in a team is new for some of us! Our personal preferences will be evolving :) 
    * Should be able to revisit ways of working at future dates.
* Simultaneous note taking duing the meeting
    * This isn't natural for everyone! Very acceptable to revisit notes and compare against those you have taken yourself.
* Explore best practices of existing communities and understand a) why they were deciced upon, and b) how they could be integrated into our ways of working.
* Taking time at the start of the meeting to just say "hello" and acknowledge each other.
* Lets share information about communication preferences, office hours etc.
    * Kalle trying to keep the slack status active so we know whether each of us are available
    * Treat Friday as no-meeting where possible
* Remember that people might be coming into the project later on, so their entry point to our activites/tasks should be accessible. Also what these things might look like in 3 years!
* Need to agree (and stick to) agreed principles for managing tasks and issues through GH +1
* We need to understand eachothers role boundries and division across the TRIC. +1
    * Make them visible and share when we expect that they might be blurred
    * Understand that there may be uncertainties and there will be change - this is good!
* Don't finish meetings on the hour :)
* We need to agree on what we want to do as a team for group meetings. 
    * 10 minute stand-up on Monday and Wednesday
        * "10 before 10"
        * [name=Cass] 10am is often the time "proper" meetings start, so lets have our stand up earlier, e.g. 09:40
            * 09:40 approved!
        * 2.5 min each on what we're doing and what we might need from eachother
    * Tuesday 15:00 team meeting weekly
    * Monthly 15:00-16:00 co-working
* Let's coordinate on when we're coming into the office
    * Let's also plan for a team-away-day-lite, perhaps monthly
    * [name=Sophie] I can set up a hub-calendar to co-ordinate office visits :star: 
* Always make hybrid available (and recording, if possible, for accessibility)
    * Consider where recordings are stored etc. ==Could Sharepoint be a good idea?== [name=Cass] Yes! Teams syncs to sharepoint :)
    * Teams is very effective for call recording (permissions automatically set for sharing) and saving the chat
* We need to build in time/processes for reactivity. 


### Objectives for Programme board 20 July
* [I missed who this is for?] [name=Kalle] Turing leadership
* We need to put together 3-4 objectives to be used as a yard stick for the hub.
* Objectives should be:
    * What is the objective
    * Why it is important
    * How we will measure it
    * Who we are partnering with on this (or partners impacted)
        * NOC, Met Office, CEH (Centre for Ecology and Hydrology)
* Chris will set up a Word doc (to be shared with the co-directors)
    * ACTION: Please provide some objectives into this doc by the end of the week, with a view to finalise by end of Monday 17th.

### Action points for follow up (add this to the contributing guide)
* Set a date for revisiting (regularly?) ways of working?
* Review materials developed by/for TTW, partiularly reviews of tools [name=Cass] I have a link for some resources from Malvika. Will dig them out.
* Discussion and documentation of office ours and communication preference etc. 
* Objective reporting -- final revisions/comments due July 17 COB (internally) —> Janine's collated document (Chris handles this)





### Next Meeting



### Information and Links  

* 
* 