Attending: Will, June, Dominik, Frances, Jean-Marie, Mark, Josh, Simon, Jason, Wilma, Petr,
Melissa, Emil, Chris, Kevin,
Start: 2:00 pm
(2-3 minutes each)
prod83 is running (release will constitute the end of migration)
Next release: 3 studies by the end of the month
Microscope to keep it fast.
image.sc discussion instead of office 365 - more testing needed
Processing roi tool feedback
Looking at tileDB, especially Java side. Compare with zarr/n5
(5 min. max; tech. Discussion should be highlighted to relevant people and rescheduled)
(20-25 minutes plus 15 minutes questions max)
thanks to all the work and testing done in preparation, also helped by the presenter / host split. To cover everybody each year without exhausting anybody, I wonder if it could work to have a variety of smaller, more focused meetings, more frequently. For example, each quarter, pick a time of either early or late, get pre-recorded talks in a few days in advance, then have just a couple of half-days scheduled that might not have something for everybody.
more workshops in future.
slack available to answer questions outside of zoom calls.
“intro” workshops useful
bit of a disconnect between the presentations and discussion. Don’t know how to improve that?
Day</u>](https://docs.google.com/spreadsheets/d/1w0oVddpkjgPYIkZS4keXl_6cLu6JucgQOkiOX578ygI/edit#gid=0)” tries to capture several of my general notes:
though it’s perhaps best to show a slide explaining the looseness of that period.
which likely means for the full conference running it over more days.
more frequently, or several of them (3-5) for a full conference.
there was a good deal of interest in having videos of the workshops and discussions. With everything else under our belt, this might be a good one to tackle.
helped me the most would have been a dedicated threaded chat.
binary and metadata</u>**, and perhaps a shorter combined session.
into clear “basic” and “advanced” sessions. Without the visual cues of who is following, more prep and/or pre-registration is likely useful to tune the content to the audience.
calendar. The .ics file could even be shared with the community.
Hard to follow chat in zoom/notes.
Workshop: impossible to see chat or participants (only Dom)
Short videos useful to publish.
Splitting some workshops into basic/advanced of 1h.
two months. How to use iviewer, figure, script, installation etc. It does not have to be new materials every time. We could record them.
usually handled in the chat.
are multiple questions at once it can be quite tricky. Also that people who joined later can’t see the previous chat history is annoying, as one has to repeat things for them (URLs, credentials, etc).
people who miss a workshop.
dealing with letting people in, questions, etc. seems to be enough for a workshop session with ~20-30 people.
have a text chat only during which the OME team are available, either themed or Reddit AMA style, so more like a drop-in session
during Q+A. Many questions had follow-ups, which were done in zoom chat.
participants beforehand that recording will not be made public, but presentations will be available.
Hangouts worked well if people knew each other.
group. Some participants got scared and ran away.
Good, broad community engagement
Workshops very well attended and appreciated.
Not so +’s
Chats are difficult– not sure of the solution.
Beverages or !Beverages
Suggesting additional sessions raises bar on
organisation or participation
Where was ImageJ?
Should spend some time focusing on the positive.
Various private emails have been coming in. Huge success.
Mark: asking participants for feedback?
JRS: would like to construct a survey, focused on this format
E.g. recordings, chat, etc. (Capturing from the above)
JRS: other events I’ve gone to had 3x personnel. In comparison,
we did well.
schedules to suit participants in diverse time zones.
Easiest to start with OME running zoom calls
JM: a lot depends on the schedule / frequency
Chris: More days, less per day.
Mark: late arrivals to workshops had trouble catching up.
Will: late arrivals due to tight schedules
Will: difficult to link Q&A to the slides. Anyway to fix?
JRS: realities of dealing with externals
be harder. Deadlines. Don’t have luxury of massaging on the day.
hand (record and discuss inline)
5 minutes before. Need to get rid of all the last minute changes.
Frances: more technical issues if live.
JRS: if we are too hard-nosed, then we won’t get any content.
Petr: people want to present, but are dragging their feet.
Will: if live, perhaps a call
JRS: see NIH webinar with prep session
Simon: how would the discussion have gone without any talks?
Petr: OME’s talks were crucial. How?
Perhaps napari as well. Few key presentations that were brought up repeatedly. Possibly content would have been brought up anyway.
more weight to the discussion. Found some much clearer than live talks.
JRS: back to the question… no talks?
Simon: at least limiting them to key talks?
Chris: panel-like approach?
we’re doing, but having the community telling
could also pose leading questions for the discussions
then you can just tell someone “next time”
Chris: present it as an opportunity and a privilege.
JRS: want to also see how others are (re-)using our tools
Simon: do it more continually? Once-a-week?
some kind of meeting more regularly, respecting time zones and sampling activity across the globe.
zones can “participate”.
GZD shows it’s hard to serve the entire community with live content.
around for 14 hours. Number of people participating was great. I.e. engagement. Bar is now high.
JRS: really hard to follow chats, gdocs, etc.
Chat leader, Technical leader
different conversations, Don’t know which questions have been dealt with
presentation and a relatively casual discussion. Treat it like any other community.
Chris: e.g. difficult to manage a discord community
But note the number of attendees who don’t know slack.
capturing things that still might need raising verbally.
JRS: Upgrade checks
Topics asked (by bonafide users)
J-m: some expression of integration (KNIME, etc)
Next format(s) & target(s) for digital discussion(s).
Blue box follow-ups.
Focused on topic.