Regular zarr/n5 community conference calls (Open to all) #1
Comments
|
Following up for on the recent adhoc call, is there any interest in starting this process up (this week?) even if it needs adjustment. Happy to add initial agenda items once @jakirkham's questions are worked out. I've copied them here with some ideas and my (relatively unimportant) preferences:
tl;dr chosen meeting plan
|
|
Thanks @joshmoore. What's the best way of collecting preferences for something like this? Google sheet with a form? Some other voting tool? |
|
Why don't we do what @joshmoore suggested above, unless anyone chimes in that it doesn't work? Day+time is presumably the only real sticking point; if it needs to be put to a vote, Doodle and Google Forms (dumping into a Google Sheet) are good ways to do that, in my experience. |
|
OK, how about this...
Regarding the day/time for the first call, I made a doodle: https://doodle.com/poll/4nwfqqske8bqyh3i |
|
Can I nudge anyone who hasn't completed the doodle poll to add their preferences (@zarr-developers/core-devs). Current best option is Thursday 14th Feb at 20:00 GMT. I've made a google doc for the agenda for the next call, please feel free to propose agenda items. |
|
Sorry for the radio silence. Just recovering from transatlantic travel. 👍 for the doodle (which I've added my preferences to). I'll add the zoom info to the gdoc once a choice has been made. |
alimanfoo
changed the title
|
Just wanted to add that a big part of the driver for getting these calls going was to build links between zarr and n5 communities (both developers and users), and to discuss ways of aligning efforts. Coming from the zarr side I can be a bit too close to the code sometimes, so apologies if at any point I don't seem to be giving enough recognition to this important point. I've change the title of this issue to "zarr/n5 community conference calls", and I've also change the title of the google doc with the agenda to the same. |
|
About the meeting, @rabernat did a great job of chairing the last call, and I was thinking it might be a good idea to rotate the chair round several people so we get a diversity of influences. I'd be happy to chair the meeting this week, but I was then wondering if anyone else might be willing to volunteer to be part of the rotation and chair a future meeting. Personally I would be happy for anyone with an interest in using and/or developing in/on/around zarr/n5 to act as chair. I'd also be happy for whoever is chair to reorder the agenda to reflect their views on priorities. Does anyone have any objections to this idea? |
|
Btw it looks like Wednesday and Thursday are currently tied for best option, I'll close the poll at end of today. |
|
Pinging @WardF to make sure the Unidata folks have a chance to participate. |
|
Thanks for the ping; I'll fill out the doodle poll on our end! |
|
OK, the most popular option is Wednesday (13th) at 20:00 GMT, let's go with that for this week at least. @WardF, @ambrosejcarr, I'm very sorry you can't make that slot, is that day/time always a problem or would you be able to make the following meeting if it was the same day/time (Wednesday 27th at 20:00 GMT)? |
|
It is just a problem this week; internal meeting conflict. I can make the same time on the 27th, no problem! |
|
Very sorry I missed this call. Something came up at the last minute that I had to deal with. Are there notes available? |
|
The call will only start in 20 minutes, won't it? |
|
Damn time zones! You're right, sorry for the confusion! See you all soon. |
|
Thanks again for the call, it was great to meet everyone. I commented on the doc just now suggesting we create a calendar event; consider adding your email here or there if you'd like to be added to that. I'd also weakly vote for reusing the same google doc week after week, and just prepending each new week's agenda (and then minutes) at the top. It's nice for scrollback, searchability, and browser-history recall of the doc when it's time for the call. Obviously whoever's doing the work (thanks Alistair!) should just do what's best for them though. |
|
mdurant at anaconda dot com |
|
Thanks @ryan-williams, good suggestion to create a calendar event, I made a calendar event but ironically don't have your email address :-) Also @funkey I don't have yours either. Also 👍 on re-using the same google doc for agenda and minutes. The next call will be Wednesday 27 Feb at 20:00 GMT. @joshmoore has kindly agreed to chair. The main focus of the call today was how to set up a governance framework so we have a clear process for evolving specs and implementations and for new members of the community to become involved and get recognition for contributing. Pangeo, Jupyter, NumPy and Dask were discussed as possible models. Dask is currently establishing a governance framework and pursuing NumFOCUS affiliation, so there may be relevant discussions there. There was general feeling that we'd like to establish something lightweight and quickly, but we should consider possible models, including those outside the PyData/NumFOCUS space. I proposed we create a zarr-developers/governance repo as a place for governance discussions, and we all took a loose action to read up on relevant governance & process models, with the goal of getting something agreed ASAP. |
|
BTW if anyone ever wants to email me I'm alimanfoo at googlemail dot com. |
|
I think everyone was cool with the idea that we'd have a rotating chair for the calls. I'd like to propose that anyone can add items to the agenda, but it's up to the chair to decide how much time to allocate to which agenda items, and what order to take them in. It's only a 60 min call, so this will probably mean only 1 or 2 substantive agenda items will get covered, but I think that's OK as conversations can also continue in parallel on GitHub around any items that don't get covered. @joshmoore is up to chair next, then I'd like to nominate @jakirkham, @WardF, @axtimwalde, @ryan-williams, @ambrosejcarr, @constantinpape, @martindurant, @rabernat. Please feel free to decline or nominate someone else. Also anyone else please feel free to volunteer. In an ideal world we'd have representation from all zarr/n5 implementations and user groups. The only standing agenda item I'd suggest is that we allow time at the start of the call for anyone joining for the first time to introduce themselves and their interest/involvement with zarr/n5. |
|
I am generally up for chairing a session. |
|
2019-02-27 section has been added to the running document if anyone has agenda items. I've added an "intend to attend" section: I'd suggest that everyone show up a few minutes early for sound check. If you can't get there early, add yourself and we'll wait a bit. |
|
I am confused. I thought the call is on 2019-02-27. Why does the doc say 2019-02-25? Is that a typo? |
|
I think so. We've been doing Wednesdays thus far. @joshmoore, can you please confirm? |
|
Bad math. Very sorry. See everyone this evening. (Note: I've updated the description to include the coordinates so mistakes like mine can be more authoritatively shouted down 😄) |
|
Hi @axtimwalde, @funkey, would either of you be willing to chair the next call? It feels like we created some good momentum to start having technical conversations around the zarr/n5 spec issues raised in the call today, and so I wondered if you'd be willing to lead a continuation of that at the next call? |
|
I won't be here for the next call, sorry :/ |
|
@alimanfoo yes, I will be happy to do that. |
|
I see that the next meeting is on Wednesday, October 7th. Is the time still "8-9pm GMT" (and place still https://zoom.us/j/300670033) as stated in the first message? (Subsequent messages have talked about rescheduling and Doodle polls.) Thanks! (Came here from #33 (comment)) |
|
Yeah that's accurate. We've been editing the OP to stay up-to-date. |
|
Sounds like it was not accurate. I've edited the OP to correct the time. |
|
Updated the zoom link to include the passcode. Note: for other CET'ers, the time is now in UTC which means that it's currently at 2000 Berlin. @ryan-williams has a calendar invite that you can be added to to manage the time shifts. |
|
@ryan-williams, I don't know if this is possible, but would we be able to include a link to the calendar event here and in the notes? If not, no worries. |
|
update: this link doesn't seem to work 😔 I've updated the Zoom link in the cal event to include the pswd query param now as well. @joshmoore reports separately that he's seeing it at an incorrect time on his calendar though, so something still might be off… please chime in if you see anything. Here's how it looks for me: |
|
Thanks Ryan! 😄 When I click the link, Google Calendar opens, but it says "Could not find the requested event." Is there a different link maybe? |
|
that's frustrating. It loads for me in a Chrome profile logged in to google account that I didn't think was affiliated with the event at all, but sure enough from a 3rd google account I see what you are describing. I don't see another way to get a link to the event 😔 sorry, lmk if you have other suggestions. I'm noting this in my previous comment also. |
|
No worries. Tinkered with an event in Google Calendar, but didn't come up with anything either unfortunately 😞 |
|
Just a heads up that we are still having timezone issues. Some people showed up at German 2100. cc: @d70-t and his https://github.com/d70-t/ipfsspec ! |
|
Hey @joshmoore, thanks for having a chat this evening. For the time issue, I think the simplest fix would be to replace
So if local time should stay approximately constant, the time should be defined in any localized time zone. However, as Daylight Saving Time changes at different days depending on country, it will not stay the same wall clock time for everyone at all times, i.e. 14:00 America/New_York is most of the time equal to 19:00 Europe/London, but sometimes (e.g. mid of March) not. |
|
Sorry that this continues to be a problem! Indeed, the calendar event currently says 6-7pm GMT (screenshot) while the OP says 7-8pm UTC (meaning they're off by 1hr; GMT == UTC for our purposes here, afaik). Since most participants are in locales with daylight savings, I like the suggestion to anchor it in someone's local time, that way it will stay at the same local time for everyone (except for the last 2wks of March and the first week of November, when US and Europe are an hour closer, iiuc). I propose changing to 7-8pm UK time, which will keep it at the current calendar-event time for the next several months, will always be 7pm in the UK and 8pm for @joshmoore in Germany, and will almost always be 11am PT / 2pm ET in the US (except right around DST shifts). Give me a 👍/👎 or lmk if I've made a mistake, and I'll update the cal event tmrw if it sg to all. |
|
Just one small addition: when referring to a local zone, I'd recommend to use Area/City based time zone codes from the IANA timezone database file those have well defined semantics and are continuously maintained. In this case, it would be Europe/London in stead of UK. Probably this is going to far, but I spent some time about time in the last weeks... It would also be interesting in which time zone the calender entry is set up under the hood. Usually, calendar tools have one time zone which sets the date of the event and another time zone which is the displayed time. As it can be seen in the table above, setting a recurring event in |
|
Thanks for all the info @d70-t! I've just updated the event (and OP here). I was looking for something like "Europe/London" but the only option I saw in Google Calendar was "(GMT+01:00) United Kingdom Time": Hopefully it will be at a stable local time for most of us now going forward. |
|
Reading this thread I am still not sure of the time of the meeting. Is it 19:00 Europe/London or 20:00 Europe/London? The top two posts with tl;dr are not in agreement. Maybe putting the time of the next meeting at the top of the agenda file would help. |
|
I've updated the second post to agree with the first. |
|
Thanks to @DennisHeimbigner for presenting his slides on filters in nczarr. Plan is to introduce a registry of V2 filters on the numcodecs repo. More details in the notes cc: @alimanfoo @cgohlke A heads up: the next meeting (May 19th) overlaps with the Dask Summit (https://summit.dask.org/schedule) and is therefore cancelled. You can join several of us during Social Event: Quiz Night, for example, if you'd like. |
|
With SciPy going on, it's unlikely anyone will be available for today's community call. Of course, the Zoom is open if anyone needs it. 😉 |
|
All, As discussed during the last call (Dec 15), the Zarr calls are going into hiatus until the new year. We'll be back on the 12th of January (i.e. skipping December 29th). If you didn't see, there's also now a Google calendar (ics) in case you want to subscribe. Regardless, hope everyone has a few safe & restful weeks. |
|
All the info for the meetings is now under https://zarr.dev/#community-meetings 🎉 closing. |
|
Unpinned the issue too. Also submitted PR ( #48 ) to add the meeting information to the README of this repo |
tl;dr:
More information as well as a Google calendar (ics) are available under https://zarr.dev/#community-meetings
Original comment
Raised in issue ( https://github.com/zarr-developers/zarr/issues/291 ) was the idea of having regular conference calls to discuss more complex issues in a high bandwidth setting. Opening here to discuss the logistics (e.g. how often, how long, what day, making agendas, what medium, how to join, etc.).
The text was updated successfully, but these errors were encountered: