---
# System prepended metadata

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

---

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

:::info
* **Time**: 
* **Meeting Information**: 
    


:::

[TOC]

## Agenda

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

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


## Present
* Cass
* Kalle
* Sophie



### Notes

ATI have authorised our repors to sync with hackmd :)

#### Repos!
- ~~https://github.com/alan-turing-institute/innovation-and-impact-hub~~ (new name: **https://github.com/alan-turing-institute/tric-dt-hub**)
- ~~https://github.com/alan-turing-institute/tricdt-hub~~ (new name: **https://github.com/alan-turing-institute/tric-dt-hub-team**)
    - Kalle added note in [README.md](https://github.com/alan-turing-institute/tric-dt-hub-team/blob/main/README.md).
- one external, one internal repo
- tric-dt-hub will be external 
- tric-dt-hub-team will be internal

#### What to model our repo on
- https://github.com/alan-turing-institute/open-research-community-management
- Best practices ideas
    - Start issues with active verb (doing words!) for commit messages and issues :heavy_plus_sign:
- what is our scope of issues? issues should involve at least 2+ 
- Other examples (using project boards)
    - https://github.com/Living-with-machines/MapReader/projects/1
        - "Freezer", "backlog", "upcoming" (set period eg. 2week), "in progress" and "done" lists in project board
        - issues can be linked to each other by mentioning, other option is "cards"
        - issues can be moved along n the project board gui, in the isses itself, or automated (e.g. on close)
- what would be good tags for us to use?


#### Division of teams

- three themes + two RAMs -- complicated!
    - Sharing third / or sharing all.
- Shakir felt that he build portfolio/expertise in a specific field.
    - Pro for splitting up themes
- Frustration could come from having to do the same thing repeatedly
    - Pro for distributed work
- Subsumption architecture is the way forward.
    - Run how you want and need forward. Feed back to Chris when trouble.
    - Figure out ways of resisting feeling of needing to know too much.
    - Risk: pieces of work where you don't need to both be involved.


#### Proposal
- 6 month York project's integration into TRIC.
- General idea: nicer and accessible platform. REG member working now.
- Come 2024, identify three projects with co-directors and themes, start building & testing assurance methodology in three themes + projects.
- Will be integrated into all three themes.
- Writing both of us into grant application? (for Kalle + Sophie to discuss)
- Chris is continuing work on the proposal before sharing wider for feedback
- eventually one project from theme should be proposed to each co-director to serve as test cases for the proposal
- Technology mission fund co-directors started smaller initial projects before tric was announced and these are already completed
- which projects will be relevant to tric?
    - 2 TRIC PDRAs have gone out -- hiring now
    - 1 PDRA (?) for Environment hasn't gone out yet
    - Assurance can then work with those tric-specific projects beginning of 2024 (not necessarily latching onto old ones)

### Action points for follow up 
- [name=Kalle]: set up separate meeting to cover how to use gitHub project boards
    - [name=Cass]: Check who else has been using github project boards to bring them in on this training to nake sure we are aligned and sharing best practice
- [name=Kalle + Sophie] discuss grant proposal for assurance testing
- [name=Kalle + Sophie]: Read [the proposal](https://hackmd.io/@cburr/Hkiqm5at3) -- not a high priority. Tuesday, [name=Chris] will share new revisions on the proposal.


### Next Meeting



### Information and Links  

* 
* 