Should we refer to this software as FPM or fpm?

[milancurcic]

They mean the same, but they look and "feel" different. We should have a consistent way to refer to this so it's not confusing to the readers whether they're different things. Especially as we begin to write about these things more publicly?

I've been using both. I don't know which one I prefer. Perhaps 60/40 in favor of fpm.

So, which one should it be?

[certik]

I've been using both also. Let's use lowercase. I think fpm, with `fpm` in markdown. Just like git or markdown. If it is at the beginning of a sentence, let's use Fpm.

…

On Sun, May 10, 2020, at 12:20 PM, Milan Curcic wrote: They mean the same, but they look and "feel" different. We should have a consistent way to refer to this so it's not confusing to the readers whether they're different things. Especially as we begin to write about these things more publicly? I've been using both. I don't know which one I prefer. Perhaps 60/40 in favor of fpm. So, which one should it be? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#77>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFAWDU4C2JEGTK7CN6IJTRQ3V7BANCNFSM4M5LDRPA>.

[certik]

I guess git uses both Git and git: https://git-scm.com/ I think svn also uses both SVN and svn. I am fine either way. We can have a rule to use FPM when referencing the project, but fpm when the executable, and encourage to use fpm where it make sense. But should we write Fortran Package Manager (FPM) or Fortran Package Manager (fpm) at the top of the website? Ondrej

…

On Sun, May 10, 2020, at 12:24 PM, Ondřej Čertík wrote: I've been using both also. Let's use lowercase. I think fpm, with `fpm` in markdown. Just like git or markdown. If it is at the beginning of a sentence, let's use Fpm. On Sun, May 10, 2020, at 12:20 PM, Milan Curcic wrote: > > > They mean the same, but they look and "feel" different. We should have > a consistent way to refer to this so it's not confusing to the readers > whether they're different things. Especially as we begin to write about > these things more publicly? > > I've been using both. I don't know which one I prefer. Perhaps 60/40 in > favor of fpm. > > So, which one should it be? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#77>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAAFAWDU4C2JEGTK7CN6IJTRQ3V7BANCNFSM4M5LDRPA>. >

[milancurcic]

Node Package Manager uses npm universally. Even the company is called "npm, Inc.".

I vote for fpm all the way, and fpm when referring specifically to the command line executable.

[certik]

I also vote fpm all the way.

…

On Sun, May 10, 2020, at 12:59 PM, Milan Curcic wrote: Node Package Manager <https://www.npmjs.com/> uses npm universally. Even the company is called "npm, Inc.". I vote for fpm all the way, and `fpm` when referring specifically to the command line executable. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFAWH4JET6LJBKTX7JHJLRQ32SNANCNFSM4M5LDRPA>.

[everythingfunctional]

I can come up with logical arguments for either.

On the one hand, it's a proper noun, Fortran is capitalized, and it's an acronym, so FPM would make sense.

On the other hand, Fortran is a case insensitive language, and our community style guide seems to be leaning towards all lowercase, so fpm would be consistent with that.

Given that this really is a purely aesthetic choice, and there seems to be a trend in other places towards all lowercase, I have nothing against using fpm everywhere. I'll start doing that.

[milancurcic]

The consensus so far is to use "fpm" everywhere. Closing.