Writing articles / blog posts on fortran-lang.org

[milancurcic]

So far we've only posted newsletters. However, it'd be of great value to establish a process for members of the community to publish Fortran-related blog posts. This would be good case for people who don't have their own blog, or people who want a wider audience than their own blog, or for any article that is especially relevant for readers of fortran-lang.org.

Ondrej and I discussed this via email some time ago, and came up with a first stab of criteria and process. Here they are:

Criteria:

1. Relevant: The article should be about Fortran, or at least interesting to Fortran programmers.
2. Original: The article should not have been published elsewhere, but adaptation from GitHub, Discourse, or Twitter threads is fine.
3. High quality: The article provides meaningful and useful information, does not advertise a product or service, and is generally aligned with the Fortran-lang community.

Point 3 is especially subjective and difficult to quantify, so review will be important.

Process:

1. The Author opens an issue to propose an article, with a tentative title and short description.
2. If there are thumbs ups / go aheads at step 1, open a PR with the article, and request 3 reviewers.
3. Reviewers review and approve the article. Once published, it's distributed on usual channels (Discourse, mailing list, Twitter)

We'll discuss this on the call this week.

[certik]

I think this would be great. The other thing we discussed is conflict of interest (say somebody submits an article about compiler comparison and I would like them to mention LFortran which I am also the main developer of), which we can resolve by the person (e.g. me) being able to participate / provide feedback, but would not count as a reviewer.

[HaoZeke]

As discussed in the monthly meeting, it might be a good idea to have a sort of "time bound" which will trigger a re-review / update of each of the tutorials / articles.

Fleshing this out a little, I'd propose having a sort of archive and current set:

• Article is written and reviewed --> current
• Not updated / re-reviewed --> moved to the archive

[arjenmarkus]

Having the blogs on Fortran-lang instead of only providing links will give us more control:

• Like @Rohit Goswami @.***> says, an opportunity to re-review them or update them
• They will not disappear without notice, as so often happens to links

Op do 22 apr. 2021 om 20:03 schreef Rohit Goswami @.***

:

As discussed in the monthly meeting, it might be a good idea to have a sort of "time bound" which will trigger a re-review / update of each of the tutorials / articles.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fortran-lang/webpage/issues/76, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN6YR3TTR6IMULMMMO3QHLTKBQIZANCNFSM43IKYZQQ .

[certik]

Also for long standing up-to-date material, we should simply write it as a tutorial elsewhere at the website.