2022-03-23 Mitchell/Wagner Check-in meeting notes

Participants

  • @Jeffrey Wagner

  • @Josh Mitchell

Discussion topics

Item

Notes

Item

Notes

General

  • Org repo index that helps people find solutions, says which repos are maintained, which repos aren't recommended any more

    • JW – We kinda already have this, it’s this page. I’ll update it and ask for your review/add to do items that you can finish

  • Interchange examples update -- Make sure this is on to do, update Thompson on status

    • JW – My mistake, this is on here at high priority.

  • Decision: We’ll keep Interchange user guide in Interchange, give JM direct access for small changes, clear guidelines for medium/large changes

  • Minimum requirements (can always request review and owner will provide it):

    • Small changes (fix typo, wording change of 10 lines or less) → Feel free to merge directly once status is green

    • Medium changes (meanings change but unambiguous improvement) → Give 3 working days after owner is tagged for review, if time window passes with no review or no “I need more time” message, then merge.

    • Large changes (functionality or significant code change) → Requires review

  • JW – We’re also going to do two things:

    • When we review a PR from someone who has direct merge access, we’ll say “here’s whether I think this really required review, and here’s how I could tell”

    • We’re aiming to do a NON ZERO number of PR reverts this year for each other’s work. If we get to the end of 2022 and haven’t reverted any PRs, then we know we’re being too cautious.

Todos

  1. (high) QCSubmit users guide (in progress)

  2. (high) Bespokefit theory docs

  3. (high) Interchange pre-release prep

  4. (medium) Toolkit docs cleanup

  5. (medium) Toolkit revised user guide (+-unifying/centralizing package user guides)

  6. (medium) Come up with “milestones” for making first of three videos this year (like, “first video on covid spike protein and small molecule, filmed this day, edited in that range, etc…”)

  7. (low) “How to cite” section on website

  8. (low) Propose policy for using GH citation machinery

  9. (low) Check main website for broken links

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

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

Action items

Decisions