Add the FortranCon2020 community abstract #3
Conversation
milancurcic
requested review from
certik,
everythingfunctional,
jvdp1,
ivan-pi and
LKedward
|
Aside from the one grammar mistake I think it looks great. |
|
It seems interesting. I would be happy to help if I can. |
Co-authored-by: Brad Richardson <[email protected]>
There was a problem hiding this comment.
I think that looks good. I don't know if you want to put the following in the abstract, or we'll put it in the presentation:
We believe that for any language to be thriving in the modern era, it needs a central place on the internet with quality discussion forums, tutorials and documentation, community and commercial compilers, standard library, package manager, rich ecosystem of packages and libraries, standards committee and perhaps most importantly a thriving community that is supporting and developing all of the above and is ready to welcome newcomers and to answer questions.
Co-authored-by: Ondřej Čertík <[email protected]>
|
Thank you all. The author list so far is Curcic, Certik, Magnin, Richardson, Vandenplas. Others, please let me know if you'd like to be a co-author and help in any way. I'll be submitting tomorrow afternoon. |
|
@certik Yes, good idea, I will include this later today, probably in a condensed form so that it flows with the rest of the text. |
|
@certik There was a lot of overlap between your suggestion and sentences 6 and 7 in the abstract. So I cherry-picked some of your suggestions that I originally missed, and edited sentences 5, 6, and 7 to include them. I hope it works. |
|
I just left a minor formatting suggestion, otherwise looks good to me. Thanks! |
Co-authored-by: Ondřej Čertík <[email protected]>
Co-authored-by: Ondřej Čertík <[email protected]>
|
I cut 17 words to fit the 200-word limit. @certik, sorry, dropping the spaces around em dashes gave us 4 words, so I let them go. |
|
It's now submitted, thank you all! |
|
@milancurcic thanks! That's a great trick to use |
|
Make sure you commit the final version that you submitted. |
|
My other comment is: currently the title is "Toward a thriving open source Fortran community". One thing to consider is changing it to "fortran-lang.org: Toward a thriving open source Fortran community". I am not 100% sure myself --- the argument pro is that it shows where the community is, right from the title, makes it clear where you are coming from and for what "project" you are arguing. The con is that perhaps we want to convey a message that is wider than fortran-lang, and while we of course want fortran-lang to be the place, and it is mentioned in the abstract, we want the title to be wider. So I am just putting this idea up here for consideration. Also, I am not a native speaker --- shouldn't |
|
Thank you, Ondrej! Good idea about fortran-lang.org in the title and my reasoning about pros and cons is the same as yours. Another con in my view is that it makes the title longer. But most importantly, "fortran-lang.org" has a connotation (and first impression) of a website, and of course what we're presenting is greater than just the website. I vote to keep the title as is.
Both are correct, toward is more common in American English and towards is more common in British English. The version merged into master is the one that was submitted. |
|
Good point, what we do is much greater than just a website, so let's leave it as it is. Regarding Toward, yes, leave it as it is, we want the American spelling. I guess there are lots of resources on this topic out there: https://www.merriam-webster.com/words-at-play/toward-towards-usage I had no idea. |
Any suggestions welcome!