# Fortran Monthly Call - September 2026

**URL:** <https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075>\
**Category:** Announcements\
**Created:** [August 31, 2026, 4:12pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075 "2026-08-31T16:12:21Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [August 31, 2026, 4:12pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/1 "2026-08-31T16:12:21Z")

</div>

After a long hiatus, let’s restart the fortran-lang community call.

This session will focus on the status of the ecosystem: fpm, stdlib, lfortran, etc. Feel free to propose additional discussion priorities, upcoming releases, etc.

Time is fixed at **8:00 AM Pacific / 15:00 UTC / 17:00 CEST** ; please mark which **days** work for you in the poll: [Fortran Monthly Call - September 2026](https://app.rallly.co/poll/a751YFvb2LZ7)

Options: Wed Sept 9 · Thu Sept 10 · Fri Sept 11 · Mon Sept 14 · Wed Sept 16 · Mon Sept 21

The final date will be announced here on or before the evening of **Sunday, September 6**. The call will be held on MS Teams (link posted here once the date is set) and recorded as usual. Propose agenda items below!

Hope to see you there,  
Federico

---

<div class="post-metadata">

**Author:** ![hkvzjal](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/hkvzjal/32/3055_2.png) [@hkvzjal](https://fortran-lang.discourse.group/u/hkvzjal)\
**Post date:** [August 31, 2026, 4:59pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/2 "2026-08-31T16:59:18Z")

</div>

What about the status of the fpm registry ?

---

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [August 31, 2026, 5:06pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/3 "2026-08-31T17:06:54Z")

</div>

Good question - That’s exactly the kind of thing the call is for: figuring out where each piece of the ecosystem stands and who’s driving it.

Adding it to the agenda - I’ve never been involved in the registry development myself, but it would be great if someone who worked on it, or wants to pick it up, could give a short status update during the call. Or post one here in the thread, and I’ll share it during the call.

---

<div class="post-metadata">

**Author:** ![Arjen](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@Arjen](https://fortran-lang.discourse.group/u/Arjen)\
**Post date:** [September 1, 2026, 10:03am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/4 "2026-09-01T10:03:43Z")

</div>

I really appreciate the initiative, but 5 o’clock is not the most convenient time for me 😊. I have marked a few dates as possible.

---

<div class="post-metadata">

**Author:** ![fxm](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fxm/32/5726_2.png) [@fxm](https://fortran-lang.discourse.group/u/fxm)\
**Post date:** [September 1, 2026, 2:27pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/5 "2026-09-01T14:27:55Z")

</div>

Thanks for the initiative! I’m away (from desks and computers) most dates, but may be able to make one, as indicated.

---

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [September 6, 2026, 7:09pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/6 "2026-09-06T19:09:15Z")

</div>

Thanks everyone for filling in the poll. **Monday, September 21, 17:00 CEST / 8:00 AM PDT** works for all 8 respondents, so that’s the date.

**Teams link:** [Join conversation](https://teams.microsoft.com/meet/349879131932160?p=tkM2myGVqA6NArxVVM)  
Duration: 1 hour. No registration needed; the lobby is open.

Draft agenda:

- state of the ecosystem
- Open PRs, release planning, and maintenance
- Anything you want to bring - reply in this thread with agenda items.

See you there!

---

<div class="post-metadata">

**Author:** ![Arjen](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@Arjen](https://fortran-lang.discourse.group/u/Arjen)\
**Post date:** [September 17, 2026, 7:07am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/7 "2026-09-17T07:07:52Z")

</div>

Unfortunately, I cannot make it - another meeting overruled this one.

---

<div class="post-metadata">

**Author:** ![Arjen](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@Arjen](https://fortran-lang.discourse.group/u/Arjen)\
**Post date:** [September 17, 2026, 11:49am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/8 "2026-09-17T11:49:18Z")

</div>

Well, that meeting has been changed, so I can indeed attend 😊

---

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [September 21, 2026, 2:57pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/9 "2026-09-21T14:57:49Z")

</div>

Hello all, a few quick items to discuss during today’s call (link above, 17:00 CEST / 8:00 AM PDT). Bring anything else you’d like to raise to the open floor.

- **fpm update** (Federico): v0.13 features & profiles - conditional compilation, per-compiler/OS flags, optional dependencies. (@hkvzjal, others) discussion on the registry status/implementation. What’s next? LFortran support status; PR backlog.
- **Ecosystem update** : maintainer effort, funding status, opportunity for contracts and grants.
- **Free AI/compute credits for open source** : several providers run OSS credit programs - worth applying for fortran-lang projects?
- **AI policy for fortran-lang projects** : do we accept AI-assisted PRs, and with what disclosure? How do we handle low-quality AI-generated PRs/issues? AI in docs and review triage. Proposal: a short written policy for the org.
- **Open floor and next steps** : owners, dates, next call.

---

<div class="post-metadata">

**Author:** ![fxm](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fxm/32/5726_2.png) [@fxm](https://fortran-lang.discourse.group/u/fxm)\
**Post date:** [September 22, 2026, 9:25pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/10 "2026-09-22T21:25:09Z")

</div>

Hey, did you manage to record it so we can catch up? (I couldn’t make it in the end, unfortunately).

---

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [September 23, 2026, 7:15am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/11 "2026-09-23T07:15:56Z")

</div>

Yes, the meeting was recorded - I’ll post it on the fortran-lang YouTube channel (getting access sorted) and link it here, together with notes and next steps in the next day or two.

---

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [September 24, 2026, 1:46pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/12 "2026-09-24T13:46:25Z")

</div>

Thanks to everyone who joined on Monday!

The recording is now up on the fortran-lang YouTube channel, with chapters in the description:

🎥

[![](https://global.discourse-cdn.com/free1/uploads/fortran_lang/original/2X/6/6d7721b59652f44b0615d928fa22fa13e481a0c3.jpeg "Fortran Monthly Call: September 2026") ](https://www.youtube.com/watch?v=7JOOtNV-dtI)

---

<div class="post-metadata">

**Author:** ![arainer](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/arainer/32/7535_2.png) [@arainer](https://fortran-lang.discourse.group/u/arainer)\
**Post date:** [October 1, 2026, 11:02am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/13 "2026-10-01T11:02:32Z")

</div>

Thanks @FedericoPerini for organising the call and, with @certik , for sharing a recording here (which I have just finished watching) and to those who participated in the call. I’d like to respond to a few items.

One of the items discussed in the call was funding, particularly in relation to fpm. I’m leading on the [FortranFuture](https://www.fortranfuture.net) project, in the UK, which is funded by a UK research council. FortranFuture includes flexible funding to support others, though mostly this will need to be ‘ring-fenced’ to the UK. More generally, I wonder whether there might be opportunities for some of the flexible funding to ‘seed fund’ other opportunities, perhaps fpm but other activities too (of which one I mention below). Happy to discuss sometime with people who are interested.

Another item discussed was AI. Broadly speaking, my sense was that the discussion covered two areas: 1) policies and good practice around using AI in one’s Fortran development, e.g., in relation to further developing fpm; and 2) the behaviour of AIs (LLMs) and how to ‘control’ that behaviour. People may be interested to know that item 1) was discussed in various sessions at the UK’s [RSECon26](https://rsecon26.society-rse.org/) recently. Slides are on their [Zenodo](https://zenodo.org/communities/rsecon26/records?q=&l=list&p=1&s=10&sort=newest) space and videos are on their [YouTube space](https://www.youtube.com/@SocRSE). Then, for items 1) and 2), people might be interested to watch James Kermode’s talk on the use of Agentic AI in scientific computing which includes some discussion of Fortran. A post is on [LinkedIn](https://lnkd.in/p/eHKnGidn), with slides and materials on [GitHub](https://github.com/jameskermode/agentic-coding-seminar) . James talks about patterns and anti-patterns when using agentic AI and provides advice, experience and worked examples too. Without prejudging anything, I wonder whether FortranFuture could use flexible funding to extend/deepen the work he has done to provide advice in relation to items 1) and 2) for Fortran. Again, happy to discuss with those who are interested.

It was interesting to hear too about continuing innovations, e.g., @Beliavsky 's work on a Python to Fortran transpiler, serving as an exemplar of how Fortran can continue to contribute. Not everything need be, or should be, a one-way street away from Fortran.

Finally, I agree with closing comments about the value of establishing a recurring meeting.

Thanks again to you all,

Austen

---

<div class="post-metadata">

**Author:** ![Beliavsky](https://avatars.discourse-cdn.com/v4/letter/b/ba8739/32.png) [@Beliavsky](https://fortran-lang.discourse.group/u/Beliavsky)\
**Post date:** [October 1, 2026, 12:07pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/14 "2026-10-01T12:07:21Z")

</div>

> [@arainer](#):
>
> It was interesting to hear too about continuing innovations, e.g., @Beliavsky 's work on a Python to Fortran transpiler, serving as an exemplar of how Fortran can continue to contribute. Not everything need be, or should be, a one-way street away from Fortran.

Yes, and even if the target language is C, Fortran can play a role, since the mapping from NumPy to Fortran has been done by Pyccel and my transpiler, and since there is a [modern Fortran to C transpiler](https://github.com/Beliavsky/Fortran-to-C) (which I need to improve).

---

<div class="post-metadata">

**Author:** ![everythingfunctional](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/everythingfunctional/32/176_2.png) [@everythingfunctional](https://fortran-lang.discourse.group/u/everythingfunctional)\
**Post date:** [October 1, 2026, 12:42pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-september-2026/11075/15 "2026-10-01T12:42:56Z")

</div>

I had taken the action item to write down some ideas for the further design of fpm features. I’ve done so if anybody would like to chime in:

> **[Design For Transitive Features · fortran-lang fpm · Discussion #1324](https://github.com/fortran-lang/fpm/discussions/1324)**
>
> In the recent Fortran-Lang Monthly Call, @perazz and I discussed a bit about how to design, using the \[features\] feature, how to conveniently depend on a package that has optional features. The cur...
