Skip to content

Commit

Permalink
Merge pull request the-turing-way#3208 from alan-turing-institute/19-…
Browse files Browse the repository at this point in the history
…07-23-notes

archiving notes
  • Loading branch information
aleesteele authored Jul 24, 2023
2 parents 5c7b9d7 + 7fc989c commit 7080173
Show file tree
Hide file tree
Showing 7 changed files with 287 additions and 1 deletion.
1 change: 0 additions & 1 deletion governance/community-calls/20230605-coworking.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,6 @@
* Constrains creativity and options from new members - follow what has been defined by those in power rather than finding what works for them.
* BUT it is important that some leaders do this work otherwise it is too difficult to navigate getting started and seeing how to get to a leadership position.
* What is stopping us - everyone can do anything in the turing way
*

### Advance asynchronous updates

Expand Down
42 changes: 42 additions & 0 deletions governance/community-calls/20230619-coworking.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# Notes 19 July

## Attendees

* Kirstie
* Eirini
* Alex
* Cami
* Emma
* Alden
* Batool Almarzouq
* Esther
* Bastian
* :clock1: (Sophia arriving late)

## Topics/Rooms

* Project Sustainability
* Cami
* Alden
* The Practitioners Hub Events coodination
* Alex (if possible with Malvika) ----> we didn't open it.
* Governance - main room
* Kirstie
* Alex
* Bastian
* Malvika
* Quiet working room?
* Batool (working in documentation for AIM RSF GH Org)
* Esther (getting back on top of things?)
*
* Chatty working room ([repositories chapter for TTW](https://hackmd.io/hIa563koR3Ssdc6B_1Skyw?both))
* Eirini
* Emma

## Advance asynchronous updates

*
*
*
*
*
46 changes: 46 additions & 0 deletions governance/community-calls/20230626-coworking.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Notes 26 June

## Attendees

* Kirstie
* Anne
* Emma
* Vicky
* Bastian
* Gabin
* Eirini
* David
* Alex
* Batool
* Sarah
* Alden
* Sophia

## Topics/Rooms

* Fireside Chat
* Anne (if Alejandro & Alexandra are here!)
* Open Science EU
* (If time) - Emma, Anne, Gabin
* Governance (main room)
* Kirstie
* Alden (Margaret Hamilton)
* Alexandra
* Anne
* Malvika
* Turing research roles case studies (Participatory scientist/researcher) - Emma, Bastian, Georgia, Sophia
* Quiet working
* David will join and catch up on emails and threads
* Sarah
* Batool
* Eirini
* UKRN survey- Vicky


## Advance asynchronous updates

*
*
*
*
*
33 changes: 33 additions & 0 deletions governance/community-calls/20230703-coworking.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Notes 3 July

## Attendees

* Anne
* Malvika
* Gabin
* Batool
* Bastian
* Esther
* Sophia

## Topics/Rooms

* Silent Coworking Room
* Sophia (maybe Esther too)
* Batool (working on the infrastructure of the localisation)
* Gabin (working on NSO shipbuilding review)
* Chatty Coworking
* Bastian
* Linking to Twitter in the Turing way?
* Esther
* Malvika
* Anne
* To avoid broken links:
* Link to the webarchive version of the tweet
* Extract the resources and link directly to those
* Adding a screenshot of the tweet

## Advance asynchronous updates

* New issue regarding the Twitter links [#3212](https://github.com/alan-turing-institute/the-turing-way/issues/3212)
* Esther started with RDM chapter review [3214](https://github.com/alan-turing-institute/the-turing-way/pull/3214) and has updated references in the DMP chapter /o/ (this is going to take forever... :D)
45 changes: 45 additions & 0 deletions governance/community-calls/20230710-coworking.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Notes 10 July

## Attendees

* Sarah Gibson
* Batool Almarzouq
* Emma Karoune
* Eirini Zormpa
* Kirstie Whitaker
* Jen Ding
* Bastian Greshake Tzovaras
* Malvika
* Shakir
* Gabin
* Anne Lee Steele
* Esther (late due to NASA-CERN summit thing)

## Topics/Rooms

* What is the difference between OpenAI, Open AI and Open Source AI?
* Kirstie, Bastian, Jen, Gabin, Anne, Esther
* (all thoughts welcome!)
* "OpenAI" should really be called "SuperShadyLLM Co" +1 +100 +1000!
* YES let's reclaim the phrase open AI!
* Decision made to go for "open AI" in the piece and to define it very expansively. Also to acknowledge the work of the OSI in defining "Open Source AI".
* Health AI standards
* Shakir, Malvika and Owen
* Scoping a project plan for linking up with regulation and corresponding standards in Health - anticipate regulatory requirements at the start
* Quiet room
* Batool: Working on blogpost with the carpentries around localisation
* Sarah: catching up on some docs
* Eirini
* Emma

## Advance asynchronous updates

* Esther: We closed an issue opened in 2020 on error management! [#877](https://github.com/alan-turing-institute/the-turing-way/issues/877). Barbara merged the PR she worked on during this year's bookdash: [#883](https://github.com/alan-turing-institute/the-turing-way/pull/883)


Notes on the TTW booth
* RSF banners are behind the curtain
* TTW - postcards, stickers, book on big screen/slide
* print out the schedule - talk about what we did at AIUK
* brief the people that come along and talk about what went on at AIUK
* how they interact with the TTW.
80 changes: 80 additions & 0 deletions governance/community-calls/20230717-coworking.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
# Notes 17 July

## Attendees

* Susana
* Anne
* Malvika
* Esther
* Kirstie
* Alex
* Eirini
* Jennifer

## Topics/Rooms

* Book dash review (#)
* https://github.com/alan-turing-institute/the-turing-way/issues/3231
* Susana / Anne discussion
* Enrichment Scheme: ALS asked to be a TESC - discussing program & writing transcript here: https://hackmd.io/@aleesteele/rkEKd5f93
* Book Dash Recording
* Will try to record during the second hour of Collaboration Cafe on Wednesday, 19 July
* Book Dash Committee: What is the time commitment for the committee?
* Reviewing this issue: https://github.com/alan-turing-institute/the-turing-way/issues/3210

### Book Dash discussion will be posted here: https://github.com/alan-turing-institute/the-turing-way/issues/3231

* Notes from meeting with @EstherPlomp @KirstieJane @eirini-zormpa @AlexandraAAJ @malvikasharan

Q from Kirstie: Is the committee working as well as it should be?
- Reflection from Esther as a long-term community member:
- It is called a planning committee so it can be unclear what the organisation's role is during the event — we can make responsibilities clearer.
- Chapter has a lot of information in the chapter, but people don't likely read it -- what might be the case? Are there many people assuming the information?
- Malvika sends detailed information, and hence doesn't feel the need to read them. What is the balance between providing sufficient information but then not overwhelming them?

Q Discussion on the chapter:
- The chapter is written by Malvika and maybe the committee doesn't feel the accountability.
- Set expectations for the committee members to read the chapter.

Q Discussion on the planning committee's responsibility:
- How do we pivot
- Some people have taken more responsibility than others, they should be given strategic leadership roles in a 'Book Dash Strategic Committee' that sets a working group
- The working group is constituted by recruiting community members who take on different roles
- Some members of the working group become the Book Dash
- What do we don't want to change?
- Not the restructuring of what we do - new templating and brand new format will bring chaos and stress to the delivery team
- What should they change?
- Evolve with the need of community - e.g. Hub and spoke model that we are working with, anything that they find challenging in the process, updating the community handbook, acting on the feedback from the previous rounds of Book Dash
- Weights of responsibilities are different, how do we address that?
- Create specific roles and create subteams: Go through the issue checklist and tease out the delivery.
- Delivery team: should always have project manager, community manager
- Onboarding the attendees
- GitHub Training
- Reviews applications
- You can be on the working group and delivery team - but full overlap is not needed
- Working group membership should align with other working group expectations/standards (will replace the Book Dash planning committee)
- Onboarding to the working group and delivering
- Chapter updates: Working group (strategic level)
- Facilitating the debrief/feedback from the Book Dash
- Review the rubric for application
- Opens up the applications for Hub, Committee, attendees

Kirstie's notes, possibly overlapping!

* Split the Book Dash Planning Committee into:
* Book Dash Working Group which is responsible for the strategic vision of the Book Dash
* Book Dash Delivery Team which is responsible for delivering a specific Book Dash event (2x per year)
* Turing Way Research Project Manager always a member
* Turing Way Research Community Manager always a member
* Book Dash WG is accountable for the Book Dash DT
* Different responsibilities though!
* For example the Book Dash WG are responsible for making sure that the DT have everything they need
* Book Dash WG members don't have to attend DT meetings, nor the specific book dash itself.
* People are welcome to be members of both WG and DT
* Members of the DT can stay in post for a shorter amount of time than members of the WG, DT should be a pathway to learning more about the Turing Way and having greater strategic understanding and leadership opportunities.

## Advance asynchronous updates

*
*
*
41 changes: 41 additions & 0 deletions governance/community-calls/20230724-coworking.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Notes 24 July

## Attendees

* Anne
* Alex
* Batool
* Jennifer
* Emma
* David
* Danny
* Kirstie
* Malvika


## Topics/Rooms

* Quiet room: Emma, David, Danny
* Saudi Hub - Book Dash (Batool, Anne, Kirstie & Malvika)
* Number of people: 4-5 people, complete beginners in openness & open science, mostly from biology background
* What would funding & support look like?
* BA: to apply for BD hub & committee
* Should this hub be in either Liverpool, London, or Saudi Arabia?
* Networking & talking opportunities to learn from the environment
* Have small funding for travel from Open Collective, IOI funding a possibility as well
* Hub models means not traveling
* Downside of the hub model can be the way it ties to geography
* Where does BA want people to come from?
* Reference to [F.O.R.M. event](https://forumforopenresearch.com/programme/) happening in 22-24 October in autumn
* Can [Open Bioinformatics Foundation](https://www.open-bio.org/) support this work (need to have bioinformatics relationship)
* Book Dash Committee has been split into two groups: Working Group and Delivery Team
* Working Group: Asking questions like: How do hubs interact with each other and online?
* Example of [Mozilla Global Sprint](https://github.com/mozilla/global-sprint): mix of online & in person, with a much larger idea to convene
* The Practitioners Hub Workshop planning:
- Jen and Ale discussion about the panel

## Advance asynchronous updates

*
*
*

0 comments on commit 7080173

Please sign in to comment.