2022-02-02 Nolasco/Wagner Check in

Participants

  • @Diego Nolasco (Deactivated)

  • @Jeffrey Wagner

Discussion topics

Item

Notes

Item

Notes

Things to do during meeting

  • Invite to sprint planning

    • (JW invited DN, marked as optional because it is outside of work hours)

  • Get Diego on Trello

    • (JW invited DN, DN made account and got access to board)

    • JW – Please let me know if there’s a way to communicate progress more clearly, or do things differently

    • DN – WIll do. I’ll review this and ask you if I have questions.

  • JW – Plan to give ~10 minute project overview at next all hands? Make a diagram of ongoing efforts at OpenFF and OpenFE based on your understanding. It’s fine to have lots of unknowns (like a box with “?” in it).

    • DN – I can do that. It’ll be a good way to get feedback.

    • JW – It’s important that this diagram at least show the actual current state. After that, it’s fine to show some details of the “proposed state”, but if the team doesn’t think you understand the current state, then people will be unproductive in discussions about the proposed state.

    • DN – Ok. I think people will be welcoming of my attempt to state my understanding, knowing that this is an early view and can be updated.

  • DN – It’s odd that OpenFE doesn’t want to be an approver for F@H project. Maybe this was a miscommunication?

    • JW – Yeah, I was kind of rushed and our communicaiton with OpenFE is relly inconsistent. I’ve messaged Gowers in the shared channel to see if we can clarify this.

    • (JW messaged Gowers in the free-energy-benchmarks channel)

  • Reminder for stakeholders

    • (DN drafted, JW reviewed, DN sent to #developers and #internal)





Action items

Decisions