---
# System prepended metadata

title: Community Call Ideas

---

# Community Call Ideas

If I was a new person deciding to join a research community, part of that decision being attending the first open community call, I would probably like to see the following:

* A summary of the project and successes so far

* A roadmap and a clear way community members can contribute / mould it

* Ways of Working and a Code of Conduct to show inclusivity and community health is a clear priority

* Planned opportunities for collaboration ie. like the Turing Way Calendar

* Calls to action - where does the project really need input now?

* We want to encourage people to: network with likeminded researchers working on similar problems and b) gain some more hands-on experience working on an open source piece of research software.

* Planning issue: https://github.com/alan-turing-institute/DS4S-project-management/issues/68
* Can we add community call members to Turing slack channel?
* We should add the community call details to the GitHub/Readthedocs - or at least get people to email requesting details - The Turing Way has open Zoom link

# Agenda

- Welcome and Ice-Breaker via HackMD (5 min) (Aida)
- Ways of working CoC (Aida) (2 min)
- Intro (Scott) (10min?)
- Discussion (10min)
- Presentation on website and Python package (Ed/Oliver) < 20 mins
- Past, present and future roadmap (Scott/Alan?)
- How to stay in touch and communicate
- Discussion of attendees research and image data challenges (All)

# Promotion
- [Sketch](https://thealanturininstitute.sharepoint.com/:p:/s/scivision/EUxJKlJKgSlPlVQW-MGQcLoB0LARAyA3xYrj9--Wllen1g?e=xP6VDp)

# Notes (managing the session, talk, slides etc)

- Have a HackMd/Google doc people can edit throughout (e.g. name, 'about me', what I'm interested in getting from the session, contact info, whether happy to be contacted by other participants etc)
    - decide how to share (perhaps an edited version with no personal details)

- Some slides on how we're organising ourselves (more than we have done in the past probably, for this group in particular).  To cover:
    - GitHub for development
    - Issues for problems, concrete requests
    - Discussions for ... discussions (!)
    - SCIPs for sharing design ideas
    - ~~The Slack channel for closed/semi-private chatter (have a 'please sign me up to slack' in the docs perhaps?)~~
    - (A few comms channels, probably worth saying it ultimately doesn't really matter, and better to use any of them rather than hold back because you're not sure which one is best)

# Roles
Moderator(s)
Notes
Q&A

# email  draft

Dear all,

If you are receiveing this email, it's because you have expressed an interest in the Scivision project - we invite you to join us for the first ever quarterly Scivision community call on 30 November at 9:30-11:00 UK time. The call will be run remotely on Zoom, sign up to this eventbrite [link](https://www.eventbrite.co.uk/e/scivision-community-call-tickets-467424999757?utm-campaign=social&utm-content=attendeeshare&utm-medium=discovery&utm-term=listing&utm-source=cp&aff=escb).

Scivision is looking for new people to get involved, especially researchers working with image datasets and/or computer vision (CV) algorithms. Scivision aims to become not just a Python package, but a community of researchers spanning different scientific domains and disciplines, with the common thread of applying the latest CV techniques to scientific image analysis. If your research project fits this remit, or you're just interested to hear more about the project, come along!

Attending the call will allow you to:
* Network with likeminded researchers working on similar problems in computer vision
* Find out how you can gain some hands-on experience working on an open source piece of research software.
    
The Agenda for the call will be as follows:

* Introduction and welcome from the Scivision core team
* Presentation from the Scivision team on successes to date and future plans
* Discussion and networking

In the meantime, do check out our [documentation](https://scivision.readthedocs.io/en/latest/) page for the project.

Thanks very much and hope to see you very soon,
The Scivision team

### Slack msg

Dear Turing community,

We invite you to join us for the first ever quarterly Scivision community call on 30 November at 9:30-11:00 UK time. The call will be run remotely on Zoom, sign up to this eventbrite [link](https://www.eventbrite.co.uk/e/scivision-community-call-tickets-467424999757?utm-campaign=social&utm-content=attendeeshare&utm-medium=discovery&utm-term=listing&utm-source=cp&aff=escb).

Scivision is looking for new people to get involved, especially researchers working with image datasets and/or computer vision (CV) algorithms. Scivision aims to become not just a Python package, but a community of researchers spanning different scientific domains and disciplines, with the common thread of applying the latest CV techniques to scientific image analysis. If your research project fits this remit, or you're just interested to hear more about the project, come along!

Attending the call will allow you to:
* Network with likeminded researchers working on similar problems in computer vision
* Find out how you can gain some hands-on experience working on an open source piece of research software.
    
The Agenda for the call will be as follows:

* Introduction and welcome from the Scivision core team
* Presentation from the Scivision team on successes to date and future plans
* Discussion and networking

In the meantime, do check out our [documentation](https://scivision.readthedocs.io/en/latest/) page for the project.

Thanks very much and hope to see you very soon,
The Scivision team

# Strike action email

(Perhaps some wording like this, although not sure what I think of it: "For the benefit of those who signed up already, we will go ahead with the meeting, but it will be a more informal scivision gathering, with our first 'official' community now taking place until January.  Anyone is welcome at both events, and will not miss out if they would prefer only to attend the second.")

# Ways forward - question
Ask people in the call how they would like to engage going forward:
- [ ] co-working calls
- [ ] community calls 


# Actions

- [ ] Aida to create a HackMD 
- [ ] Aida to add all the links into the HackMD
- [ ] ask people how they want to stay in touch - Github Discussions, Slack workspace, Discourse? 
- [ ] We can also have a feedback at the end asking what people would like to have had on the community call
- [ ] list upcoming co-working sessions - and list likely topic 
