Newsletter draft for June 2022

[milancurcic]

• Newsletter draft
• GitHub stats data
• Flang updates @AlexisPerry
• LFortran updates @certik @HaoZeke @czgdp1807

Please review and edit if I missed any notable events or updates.

Let's merge on Friday, June 10, to allow time for compiler updates.

Thank you!

[henilp105]

@milancurcic @awvwgk

Respected Sir,
In light of the future transition to Sphinx+MyST parser, I just wanted to request a few points for further newsletters.

• please make the main heading in H1 as myst parser raises errors. ( Example: # fortran-lang )
• please add date to the blog post.

Example:
date: 2020-02-28
title: J3 February 2020 Meeting
category: newsletter
author: Ondřej Čertík and Zach Jibben

This is for the future transition to sphinx+myst parser. application of all the above stated changes has been implemented at my fork.Please Refer my Github fork's source folder for Sphinx Implementation of the site. I have also raised an Issue for the same #407.

Thanks and Regards,
Henil Shalin Panchal

[milancurcic]

@henilp105 Thanks for the heads up, will do!

[AlexisPerry]

Please see PR milancurcic#10 for Flang updates. Thank you!

[milancurcic]

#build_preview

[github-actions]

This PR has been built with Jekyll and can be previewed at: https://fortran-lang.org/pr/406/

[milancurcic]

#delete_preview

[milancurcic]

#build_preview

[github-actions]

The preview build for this PR has now been deleted.

[github-actions]

This PR has been built with Jekyll and can be previewed at: https://fortran-lang.org/pr/406/

[certik]

I think the formatting doesn't work, good catch. I think I have to put * at the beginning of each line, let me fix that.

[milancurcic]

I got it already, just haven't pushed yet, so don't worry about that part.

[certik]

Thanks! I noticed when I couldn't push into your branch. :)

[milancurcic]

@henilp105 If we change the level of headings from 2 to 1, we also need to adjust the heading selector in assets/js/page_nav.js. This will let the TOC work for this newsletter, but it will break the TOCs in past newsletters. We'd then need to fix all past newsletter headings.

I suggest to keep the headings here as is for now, and if it's beneficial we can address the headings in all newsletters in a separate PR. I added the date field.

[milancurcic]

#build_preview

[github-actions]

This PR has been built with Jekyll and can be previewed at: https://fortran-lang.org/pr/406/

[henilp105]

@milancurcic
Yes sir , sure we can address the headings later in a separate pr later, Thanks for adding the date field.

Thanks and Regards,
Henil Shalin Panchal

[milancurcic]

Thanks all, I'll go head and merge.

[milancurcic]

#delete_preview

[github-actions]

The preview build for this PR has now been deleted.