Kick Off meeting (11 June 2018)

Attendees

  • Christy Wilson
  • John Wise
  • Fiona Ford
  • Alessandro Riccombeni
  • Nick Lynch
  • Marcus Rhenius

Summary / Actions:

How to work together:

  • Build wiki area (David) - Done
  • Investigate Slack (David via Nick)
  • Build a document / reference repository on wiki

Collect references of interest (all) send to David or edit wiki directly (All)


Questions for next meeting:

  • Finding the communities / players
  • Understanding the common problems
  • Build the problem statement:
    • We want to build / run a summer school in the area of x for our members to add value by....

Notes:

General Thoughts and comments:

There might be opportunities for Microsoft or similar to sponsor this

(Fiona) Where are the Microbiome communities globally? Find the pharma, biotech and supplier companies

(Alessandro) Can we find (be?) the interface between smaller (startups) and larger pharma

We should find/be the microbiome community (COI?) - what value would we bring?

(Fiona) From her experience, the Microbiome community appears to be open to sharing data & best knowledge in a way that pharma might not be

(Christy) Would it be a good idea if we share who we know that are players in this area, capture:

  1. Who we know
  2. What they are interested in
  3. Their community or communities they know of / belong to

(Nick) Also find what their common problems are... 

(Marcus) will talk to his colleagues to see Bayer's interest in this space...

Could we put together a questionnaire for distribution (mail and/or linkedin group)

(Christy) - there are a large number of articles out there e.g "the poop lab" - perhaps grab all references of interest and place on the wiki


(John) Longer term as we shape this we have members fo the advisory board interested in this space who may be able to help us (Alan Lewis)


Team Working / Collaboration:

There is a reticence to have to log in (the yet another password syndrome), options:

  • Build a public wiki, if anyone wants to comment they will need to log in
  • There are good password management software that can help with this
  • UX team have had success with Slack, although there were some issues with access through company firewalls when we tried it