make gufe lowercase in docs

[atravitz]

while we're addressing this in the gufe docs overhaul, I thought I'd update in openfe docs as well.

Checklist

• Added a news entry

Developers certificate of origin

• I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.51%. Comparing base (c5d0e58) to head (749fee3).
Report is 94 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1190      +/-   ##
==========================================
- Coverage   94.15%   92.51%   -1.65%     
==========================================
  Files         141      141              
  Lines       10588    10588              
==========================================
- Hits         9969     9795     -174     
- Misses        619      793     +174     

Flag	Coverage Δ
fast-tests	92.51% <ø> (?)
slow-tests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mikemhenry]

Is this settled? Feels like we need a team wide discussion for this, it can be async. @jthorton @hannahbaumann see OpenFreeEnergy/gufe#508

Perhaps without opening the whole can of worms with naming things, I think really the only change in the PR that really changes the "name" is The GUFE package -> Gufe since the other changes I agree with even if it is an acronym (I like lowercase stylistically for software packages). Maybe we could go with gufe in that spot?

This is a minor preference, I am okay with Gufe for now in that spot until we decide what we want to do name wise.

[atravitz]

Is this settled? Feels like we need a team wide discussion for this, it can be async. @jthorton @hannahbaumann see OpenFreeEnergy/gufe#508

I thought this was settled (see "visual style" here)

But if it's just for the package name, that' s fine by me.

[mikemhenry]

AH--sorry, I thought this was motivated with acronym discussion -- my bad!

I would argue then that it should be gufe even if it is the start of a sentence (that is what the visual style says IMHO).

[mikemhenry]

Probably excessive but we can use a macro to not have to copy and paste this note in two places

[atravitz]

once we're >2 then I'll bother with a macro?

[mikemhenry]

That sounds like a good metric, see:
https://xkcd.com/1319/
https://xkcd.com/1205/

[atravitz]

I would argue then that it should be gufe even if it is the start of a sentence (that is what the visual style says IMHO).

thanks! the start of sentence thing was ambiguous to me - I like keeping it lowercase.

[mikemhenry]

I agree it is ambiguous and not clearly stated in the spec, so I would say there is an element of interpretation to it. We've got 2 votes now for gufe to be lower case at the start of a sentence. I'll post a comment on the discussion to see if we can get more consensus on it (I am also fine with merging this in)

[github-actions]

No API break detected ✅

[dotsdl]

I'm partial to lowercase or lowercase for software packages. Thank you for making this change!