---
# System prepended metadata

title: Knowledge Sharing Service Area

---

# Knowledge Sharing Service Area

- People:
   - Jack
   - Radka

- Info:
   - Wiki page: https://github.com/alan-turing-institute/research-engineering-group/wiki/Knowledge-Sharing

## Current work

- The majority of our effort is arranging tech talks:
   - Transition to remote talks
   - Starting new series like the fundamentals  sessions.
   - Encouraging informal discussions (e.g. watch a video together, lightly prepared talks without slides)
   - Giving people nudges to sign up 🙂  

- Support and encourage other activities in the group that aid knowledge sharing  (reading groups,  hack sessions, ...)

## What we could do more of?

-  Snark Hunts - retrospective discussions on projects - have held a few in the past but would be good to make them more frequent.

- Many activities in REG that could be brought under the knowledge sharing heading.
  - Dugnad, newsletter, audit sessions, reading groups, hack sessions, ... 
  - Arrange more "REG events" / REG events calendar / similar.

- Remote/hybrid working/larger team: Finding ways to ensure we're communicating outside our projects.

---

# Researcher Tools Management Service Area

- People:
  - Previously:
    - Oliver
    - Sarah
  - Starting: 
    - Jack 

- Info:
  - [Issue](https://github.com/alan-turing-institute/Hut23/issues/568)
  - [Project board](https://github.com/alan-turing-institute/Hut23/projects/7)

- Managing tools used by researchers at the institute but not administered by IT.
  - Geekbot
  - GitHub
  - Harvest & Forecast
  - Overleaf
  - Travis
  - Zotero

- It minimally involves keeping the various services running:
   - paying for things, adding new users, occasionally answering queries about them from across the Turing, making sure the GitHub organization is running properly and checking out extensions people request

- The more fun side of it: Deciding on new researcher-focused tools to try out, getting funding for them and getting people interested in them.

- A great way to get to know how the Turing works  - it occasionally means talking to IT, Finance, Turing researchers, Data Protection and presenting things at the RCWG (the research computing working group)

- Beyond a few minimal things that need looking after, it can almost certainly be shaped by what you are most enthusiastic about and the time you have to support it, if the above sounds like a lot!


## Plans

- Jack: Only just starting - plan to learn about everything!
- Make a case for Gathertown in the office / explore alternatives.
- Migration from Travis to GitHub actions?
- Increased support licenses for Overleaf and Zotero?

##  How to get involved

-  Would be great to have another person involved! Would give us more resource to push forward beyond "keeping the lights on".

- Contacts:
   - Jack and Oliver

