Open milancurcic opened 3 years ago
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.
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:
Having the blogs on Fortran-lang instead of only providing links will give us more control:
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 .
Also for long standing up-to-date material, we should simply write it as a tutorial elsewhere at the website.
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:
Point 3 is especially subjective and difficult to quantify, so review will be important.
Process:
We'll discuss this on the call this week.