Versions Compared

Key

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

...

Item

Notes

Next steps

  • DD – I’m thinking about speccing things out, would like to check out openFE stuff but that may be premature.

  • JC – We should see if we can move forward with a plan in which OpenFE components can get shoehorned in later. Though we’re still uncertain

  • JW – Is there an alternative to another round of planning? All I can think of would be to try implementing something to learn if there are other development issues we can derisk

  • JC – We’ve already kinda done an early implementation in the COVID moonshot.

    • DD – We could take what we’ve done in moonshot, pull it into fah-alchemy, and try combining it with current OpenFE software.


  • DN – I’d prefer us to have assembled a discrete task list/backlog from this. Today was largely technical discussion.

  • JW – I think we’re finding that we can’t define what it is we want.

  • DN – So, we should explicitly agree that we will have more meetings to go over user stories.

  • DD – Yes, I think that’s necessary.

  • JW – Current project status and timeline is now unknown - Didn’t have all approvers by this point in the meeting so we couldn’t commit to changing plans. But we are also no longer on our agreed-upon timeline of approving a spec after the third meeting

  • RG – I talked with our governing board and we’d like to become approvers.

    • JW – I think all of the current approvers would agree to that change. Please make sure your nominated approver attend the next such meeting.

Action items

  •  David Dotson will assemble candidate data model for transformation graph in fah-alchemy; use lessons learned from Covid Moonshot, attempt to build on OpenFE network classes
  •  Diego Nolasco (Deactivated) and David Dotson will assemble agenda for next meeting, including updates to project timeline, new approver

...