Fortran Monthly Call: April 2025

:loudspeaker: Fortran Monthly Call – Relaunch!

After a short hiatus, it’s time to bring back the Fortran monthly call!
We’re aiming for the week after Easter — April 22–25.

:spiral_calendar: Please indicate your availability using the poll below (the time in the poll is GMT +2):
:backhand_index_pointing_right: Fortran Monthly Call: April 2025 | DFN-Terminplaner

The final time slot will be selected on April 16 at 20:00 CEST.

Everyone is welcome — feel free to drop by, say hello, raise topics, share updates, or just listen in. Looking forward to reconnecting with you all!

8 Likes

What timezone are those times in the poll? I can’t figure it out from the website, it doesn’t seem to say, or allow me to select my timezone.

1 Like

GMT+2 (aka CEST)

Sorry about that. I was assuming the app converts into the local timezone. I started with Doodle but it showed too many ads.

The hourly slots in the poll run from 15:00 to 20:00 (GMT+2), which would be

  • Sydney, Australia: 23:00 to 04:00 (GMT+10)
  • New York, USA: 9:00 to 14:00 (GMT-4)
  • San Francisco, USA: 6:00 to 11:00 (GMT-7)
1 Like

Wonderful :slight_smile: , I did miss them. Unfortunately, I will be travelling that week, so I cannot participate.

I should be able to join on the 22nd, but will be travelling later that week. Would be nice to see some of you on screen. :slight_smile:

I accidentally replied twice :frowning:

Won’t have much time that week but will do my best to join :ok_hand:

2 Likes

Great to hear about this initiative. I am planning to attend for the first time, but I have not found a conference link. How will we connect?

I think times are still being decided!

1 Like

We will share a video conference link once the time is selected.

Note: upon request I have added additional times on April 21 and April 28 (both are Mondays).

To edit the poll you can select your name and press the edit button (pen icon), as shown in the following snapshot:

1 Like

Note that there is no edit button for me. I imagine an account is needed for it. Consequently, I filled out a new line with answers that complement previous ones, so there’s no bias.