# Fortran Monthly Call: March 2021

**URL:** <https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807>\
**Category:** Announcements\
**Created:** [March 11, 2021, 8:24am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807 "2021-03-11T08:24:26Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [March 11, 2021, 8:24am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/1 "2021-03-11T08:24:26Z")

</div>

Dear all,  
It’s again time to organise our next monthly call which will be in the week of March 22-26; please see the following doodle poll to mark your availability:

### [Doodle: Fortran Monthly Call: March 2021](https://doodle.com/poll/paamwe29ixru7akr?utm_source=poll&utm_medium=link)

The final time slot will be selected and announced on the evening (European time) of **Sunday March 21, please complete the poll before then**.

If there are specific topics or issues you would like to raise, even if you are unable to attend the call, please post them in the thread here.  
As usual, we will record this call and make it available online.

All the best,

Jeremie

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 11, 2021, 2:16pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/2 "2021-03-11T14:16:18Z")

</div>

Thank you for organizing these, @jeremie.vandenplas

I have a small proposal for scheduling to help avoid time conflicts.

Problem: Currently, we give ample time for people to indicate availability in Doodle, and then we have a potentially very short notice when a decision about the meeting time is made. Specifically, Doodle is now open for the next 10 days, which is plenty of time. But we will make a meeting time decision on Sunday evening, for a meeting that could in theory be on Monday morning.

When I mark my availability, I look at my calendar for that week and provide all my available time slots. But in the meantime, I’m also scheduling other meetings. So it becomes a game of chance whether I will schedule some meeting at an overlapping time with a Fortran call.

So, I suggest the following:

- This month, we decide on the meeting time a bit sooner, perhaps at the end of the work week, Friday evening (March 19)
- In the future, we follow this pattern:
  - Scheduling in Doodle happens during the 1st week of the month
  - Fortran call occurs in the 3rd week of the month (except during events like FortranCon, J3 meetings, and similar, if they occur in the same week).

That way, we will have one week between the meeting time being set, and the meeting itself.

What do you think?

---

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [March 11, 2021, 9:31pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/3 "2021-03-11T21:31:36Z")

</div>

This sounds good to me. A fixed day (e.g, at 8pm (European time) on Tuesdaty of each third week of a month) could be decided too. People could then block this slot in their agenda in advance.We can briefly discuss it during the next call.

For this month, I will follow @milancurcic 's proposition: **the final time slot will be selected and announced on the evening (European time) of Friday March 19**, instead of March 21.

---

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [March 19, 2021, 3:12pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/4 "2021-03-19T15:12:29Z")

</div>

Our next monthly call will be on **Wednesday, March 24 at 6pm CET (Amsterdam)**.

9:00 - 10:00 PDT (California)  
17:00 - 18:00 GMT (London)  
18:00 - 19:00 CET (Central Europe)

As previously, the meeting will be recorded for those who cannot attend. Please continue to use this thread for topics you would like discussed at the meeting. A Zoom invitation will follow soon.

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 19, 2021, 3:20pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/5 "2021-03-19T15:20:44Z")

</div>

Thanks @jeremie.vandenplas, here’s the Zoom info:

Topic: Fortran Monthly Call: March 2021  
Time: Mar 24, 2021 12:00 PM Eastern Time (US and Canada)

Join Zoom Meeting

> **[Join our Cloud HD Video Meeting](https://miami.zoom.us/j/93549172763?pwd=VkVMRTJVMUlyRlFudWlpOW0zeWtIdz09)**
>
> Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webinars across mobile, desktop, and room systems. Zoom Rooms is the original software-based conference...

Meeting ID: 935 4917 2763  
Passcode: 727898  
One tap mobile  
+16465588656,93549172763#,\*727898# US (New York)

Dial by your location  
+1 646 558 8656 US (New York)  
+39 021 241 28 823 Italy  
+39 069 480 6488 Italy  
+39 020 066 7245 Italy  
Meeting ID: 935 4917 2763  
Passcode: 727898  
Find your local number: [https://miami.zoom.us/u/aec1v9kb2i](https://miami.zoom.us/u/aec1v9kb2i)

Join by SIP  
[93549172763@zoomcrc.com](mailto:93549172763@zoomcrc.com)

Join by H.323  
162.255.37.11 (US West)  
162.255.36.11 (US East)  
213.19.144.110 (Amsterdam Netherlands)  
213.244.140.110 (Germany)  
103.122.166.55 (Australia Sydney)  
103.122.167.55 (Australia Melbourne)  
64.211.144.160 (Brazil)  
69.174.57.160 (Canada Toronto)  
65.39.152.160 (Canada Vancouver)  
Meeting ID: 935 4917 2763  
Passcode: 727898

---

<div class="post-metadata">

**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\
**Post date:** [March 20, 2021, 3:14pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/6 "2021-03-20T15:14:27Z")

</div>

Note: These calls are open for anyone to join! We have not been very good at communicating this. We are doing these calls to provide a venue for the wide Fortran community to be able to talk. Anyone who is interested is welcome to join.

---

<div class="post-metadata">

**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\
**Post date:** [March 23, 2021, 8:17pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/7 "2021-03-23T20:17:03Z")

</div>

I want to add some items on the agenda for tomorrow, mostly stdlib related and about documentation:

1. git workflow/strategy recommendations for fortran-lang repos  
[Preferred git strategy · Discussion #358 · fortran-lang/stdlib · GitHub](https://github.com/fortran-lang/stdlib/discussions/358)
2. Updating the style guide / workflow for the stdlib infrastructure (build files, CI workflows, …)  
[Summarize build toolchain workflow and implied rules by awvwgk · Pull Request #360 · fortran-lang/stdlib · GitHub](https://github.com/fortran-lang/stdlib/pull/360)
3. The versioning issue, next steps to actually get started  
[Is stdlib versioned? · Issue #292 · fortran-lang/stdlib · GitHub](https://github.com/fortran-lang/stdlib/issues/292)

---

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [March 23, 2021, 9:05pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/8 "2021-03-23T21:05:12Z")

</div>

I realize that the times mentioned earlier might wrong (due to daylight saving time).

Here should be the correct times:

Our next monthly call will be on **Wednesday, March 24 at 17:00 UTC**.

**10:00 - 11:00 PDT (California)**  
17:00 - 18:00 GMT (London)  
18:00 - 19:00 CET (Central Europe)  
**13:00 - 14:00 EDT**

@milancurcic I think the time for the Zoom meeting is wrong. Could you check please?

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 23, 2021, 9:24pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/9 "2021-03-23T21:24:16Z")

</div>

@jeremie.vandenplas Can you write the meeting time in UTC? That way we’ll be sure, and we’ll be using UTC going forward. Zoom link will work regardless of the time. People just need to know when to show up.

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 23, 2021, 9:35pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/10 "2021-03-23T21:35:46Z")

</div>

Okay, I see, **17:00 UTC**.

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 23, 2021, 10:41pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/11 "2021-03-23T22:41:06Z")

</div>

~~Unfortunately I won’t be able to join tomorrow. I will make you the host, @jeremie.vandenplas.~~

---

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [March 24, 2021, 2:11pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/12 "2021-03-24T14:11:20Z")

</div>

Edited with Milan 's suggestions.

Here is the current agenda:

1. Fortran-lang projects

- git workflow/strategy recommendations for fortran-lang repos @awvwgk [Preferred git strategy · Discussion #358 · fortran-lang/stdlib · GitHub](https://github.com/fortran-lang/stdlib/discussions/358)

1. stdlib

- Updating the style guide / workflow for the stdlib infrastructure (build files, CI workflows, …) @awvwgk [Summarize build toolchain workflow and implied rules by awvwgk · Pull Request #360 · fortran-lang/stdlib · GitHub](https://github.com/fortran-lang/stdlib/pull/360)
- The versioning issue, next steps to actually get started @awvwgk[Is stdlib versioned? · Issue #292 · fortran-lang/stdlib · GitHub](https://github.com/fortran-lang/stdlib/issues/292)
- @arjenmarkus’s module for tolerant comparisons. [PR](https://github.com/fortran-lang/stdlib/pull/353).

1. fpm

- @urbanjost’s fpm plugin design and implementation. @milancurcic[Discussion](https://github.com/fortran-lang/fpm/discussions/361) | [PR](https://github.com/fortran-lang/fpm/pull/364).

Don’t hesitate to add topics to this agenda.

I would like to remember that everyone is welcome to join this call.

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 24, 2021, 2:58pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/13 "2021-03-24T14:58:39Z")

</div>

I’d like to present and get feedback on @urbanjost’s fpm plugin design and implementation. [Discussion](https://github.com/fortran-lang/fpm/discussions/361) | [PR](https://github.com/fortran-lang/fpm/pull/364).

I’d also like to get feedback on @arjenmarkus’s module for tolerant comparisons. [PR](https://github.com/fortran-lang/stdlib/pull/353).

---

<div class="post-metadata">

**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\
**Post date:** [March 26, 2021, 6:29pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-march-2021/807/14 "2021-03-26T18:29:45Z")

</div>

[![](https://global.discourse-cdn.com/free1/uploads/fortran_lang/original/1X/eb2db809851292038c6877e7fb01db6f34b34dcf.jpeg "Fortran monthly call March2021") ](https://www.youtube.com/watch?v=cxDF2Sa3nvU)
