Sorry, @rchhetri, I didn’t get your request until the meeting had already begun. Next time!
Otherwise, That’s a wrap! 
Thanks to the 4 dozen or so of you who joined over the course of the day. (Some joined twice, so thanks 2x.) I’ve locked the meeting notes but they are public if anyone who couldn’t attend wants to take a look. The recordings are currently being uploaded, and I’ll update this thread once they are in place.
A summary write-up of the main conversations like:
- What is “ngff”?
- How to deal with many small files?
- APIs versus file formats
- sparse versus dense
- additions to the multiscale & labeled image specs
- representations for polygons, tabular data, etc.
- storage of flexible metadata
is certainly in order, but I likely won’t get to it for a week or two. But by all means, if anyone wants to add their thoughts, impressions, or generally keep the conversations going, very looking forward to it. If you start a new topic, add the #ome-ngff tag and those who are interested should be able to follow along.
A few procedural decisions were made regarding how future community calls will take place:
- In roughly a month, I’ll kick off another similar topic to see if there’s interest in another meeting. We’ll need to keep #i2k2020 in mind for the scheduling.
- The feeling was that generally organizing the meetings completely within image.sc was successful, but…
- we need to balance the notification to noise ratio. For example, what’s the best way to let everyone express “I’d like to join”? Suggestions welcome.
- For everyone who has already expressed interest, I’ll set up an @ngff group in order to more easily give access to the connection information. Thoughts welcome on how else to make use of that.
- We sadly didn’t choose a better name, so keep your proposals coming!
Thanks to all for taking time out of your crushing schedules. It was great to see everyone.
~Josh