Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Discussion topics

Item

Notes

General updates

  • JW – Thanks for quick feedback on FAQ updates!

  • JW – Would it help to have my eyes on bespokefit/qcsubmit docs?

    • JM – Yeah, it’d be great if you did an initial review of the bespokefit docs.

    • JW will review

      Github link macro
      linkhttps://github.com/openforcefield/bespoke-fit/pull/85

    • JM – Building on RTD is waiting for the repo name to change from bespoke-fit to openff-bespokefit, since the repo name will become part of the URL when it’s created.

    • We posted on Slack to see if SB or JH have any objections to changing the repo name

  • JM – There was a problem with the website and height padding

    Github link macro
    linkhttps://github.com/openforcefield/openforcefield.org/pull/375

    • JW – Looks great. Approved.

  • JM – We could put our docs under the http://openforcefield.org domain.

    • JW – Would this be easy/secure?

    • JM – Yes, it should be straightforward and it will look professional. We can also nest all our projects under one group.

    • JW – This would also be nice in the event that we moved to GH pages, since the same URLs would work before and after the switch.

    • JM will try switching our project docs to be accessed through openforcefield.org urls

To dos

  • (high) Bespokefit users guide (in progress)

  • (high) QCSubmit users guide

  • (medium) Spec migration PR part 2

  • (medium) ELF10 thing

  • (low) Check main website for broken links

  • (low) migrate docs to be under openforcefield.org domain (openforcefield/status would be base project repo)

  • (low) Conda env yamls for each release (automated inside of Toolkit’s single-file-installer action)

Action items

  •  

Decisions