---
tags: community
description:
---

:::info
* **Date: 2023-07-25 and 2023-07-28
* **Time**: 14:00
* **Join via**: Zoom
* **Call recording**: not available

:::

[TOC]

## Agenda

* **Theme**: Environment and Sustainability GC WS 2.5: "Foster an open international environmental data science community "
* **Chair**:
* **Links & resources:**

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

## Attendees
* Cass
* Alejandro
* Malvika
* Alden
*
*

### Notes 25-07-23
* [Open Environmental Action](https://www.openenvironmentaldata.org/)
* Set up stage
* Hope to embed some of their practices into TTW
* How can WS2.5 go beyond the EDS Book?
* How can it develop beyond the current offerings
* Example communities
* [Ocean Best Practics System](https://www.oceanbestpractices.org)
* Governance is mapped out
* Community is the centre

* Do we have journals we want to focus on?
* Can we deliver training?

* [TAIAO](https://taiao.ai)
* New Zealand Environmental Data sharing
* [The Eric and Wendy Schmidt Center at Berkeley](https://dse.berkeley.edu)
* E&S SIG
* communication channel
* No clear (documented) scope and values
* Difficult to maintain and grow

* For us
* Want to have a grand vision for WS2.5
* What is the added value that this community can bring?
* International sharing and good practices
* Crossing policy and private sector
* Including citizens
* There is additional focused communities

* TRIC-DT Env / EC GC WS 1 Stakeholder map first draft in mid-August
* New initiatives can accidentally minimise the work of existing ones
* How can we add value to the exicting ecosystem
* EDS book is value addition
* Could scope to see what could be added
* Alejandro has plans to develop in-browser review, which is hard in jupyter book. Considering move to [React](https://react.dev). Note that this should be driven by community need.
* Working towards common practices with this book - this is the hook
* How you convene them is community management (note job profile is UK centric currently)
* ==What is the incentive for people to engage with the book?==
* Could contribute to roadmap
* Target other communities to contribute e.g. via fireside
* Look at other peoples notebooks - see if they can be integrated
* ==Amplifying other communities and peoples work==
* e.g. they may want to share their lobbying work
* Get community involved in building practices => upskilling and contribution to practice development
* KPIs
* 1. Convening around a topic. Understand from existing communities what they want
* 2. All the learnings should be shared, inc to enhance EDS book
* 3. Amplfying

* Beyond notebooks

* EDS book
* Amplify/connect with existing communities OEDP

### Notes 28-07-23
* We have lots of E&S communities which we can reach, but we don't want to spam them!
* SciVision Community calls are in their infancy
* Building up a mailing list
* Call attendees were mostly Turing
* Our biggest interest group is the SIG
* Take EDS book to this group
* Move it organically based on that feedback
* Visibility of EDS group is minimal in SIG
* Presented in January 2023
* Potentially could get spot at October Manchester meeting
* Develop formal community around EDS book
* Work with SCM to refine EDS book and E&S SIG, https://the-turing-way.netlify.app/collaboration/new-community.html#

* KPI, measurable, then SMART goal

### Notes 07-08-23
- Async [name=Alejandro]

**Notes from GDocs**
* Convening: Community (learning from other WS)
* How do we demonstrate that we have been convening?
* Learning: Engagement (how does this feedback into other goals)
* How do we demonstrate that we have been sharing our learning?
* Amplifying: EDS book - platform, different flavours
* How do we demonstrate that we have been using EDS Book as a mechanism to amplify other communities and activity? E.g. incorporate openresearchcalendar

KPIs are motivated by a key performance question.

#### Draft KPIs
**Convening KPIs**

*To what extent are other WS demonstrating interest in collaborating and conduct communnity actitivities using GitHub?*
* KPI: Number of E&S GC scientist and research leadership working on GitHub for share code, data and project management

*To what extent are other WS demonstrating interest in showcasing and sharing their research outputs through computational notebooks?*
* KPI: Number of E&S GC scientists engaging with EDS book, including access to existing notebooks

**Learning KPIs**

*To what extent are other WS demonstrating interest in showcasing and sharing their research outputs through EDS book computational notebooks?*
* KPI: Number of E&S GC scientists engaging with EDS book contributing and testing EDS book

**Amplifying KPIs**

*To what extent is the EDS book being effectively promoted to the public?
* KPI: Number of engagement articles/blogs/social media written by Turing E&S GC and partners comms teams on EDS book

*To what extent is the EDS book vision influencing other communities and activities?
* KPI: Number of notebooks published; total reads of and citations to E&S GC related EDS book notebooks

### Notes 10-08-23
- Sync [name=Alejandro & Chris]

KPI – Short term
• Sustainable Engagement
• Behavioural change / Knowledge base
• Target stakeholders: researchers, partnerships
Traffic,
• Why is this important?
• High quality work
• Use cases
• Generalisable
Metanalysis of comments
• How people comments make differenc

### Notes 11-08-23
- Async [name=Alejandro]

**Convening KPIs**
*To what extent are E&S climate and biodiversity research community demonstrate interest in collaborating?

### Action points for follow up
*
*
*
*

### Next Meeting
*
*
*
*

### Information and Links
*
*
*
*