Thanks for organising it @ivanpribec.
@certik, the call was cut off when you were explaining the GSoC mentor decision procedure. I presume there’s room for discussion about it on this discourse, since we have a category for it. Happy to be more involved in it.
1 Like
Sorry about the cutoff. Thanks for joining (on Easter holidays on top)!
My notes:
- GSoC contributor proposal ranking is due soon (April 28, Google Summer of Code 2025 Timeline | Google for Developers)
- several new stdlib features have accumulated; it is time for a new release. @hkvzjal is investigating automation of release notes
- discussion of API stability guarantees for stdlib
- new fpm packages in the making (MPFR fpm package, fpm-deps)
- CI/CD: sanitizers (probably worth it), CodeCoverage (try and evaluate)
- steady progress in LFortran (TODO for beta · Issue #3806 · lfortran/lfortran · GitHub); more testing from the community welcome
Unfortunately I couldn’t record the meeting this time (I forgot my apartment keys 500 km away, hence I had to join from the public university campus).
3 Likes
I couldn’t attend either, did the recording work?
What do you mean by cut off, is it a Teams restriction? If so, maybe consider using Jitsi for the Monthy Calls. You could even integrate Jitsi into discourse:
I have zoom pro bougie so I can host the next ones, even if I am not attending due to timing reasons !