Skip to content

Project Meeting 2023.11.07

kadannemiller edited this page Nov 7, 2023 · 4 revisions

Agenda

  • Roadmap Review and Finalization
  • Strategic Development and Contribution Plan
  • Revisit the following from previous meeting:
    • Roadmap Documentation: What does the consortium want to do in the next year? How will we allocate our resources to meet those goals?
    • Testing and contribution management discussion.

Meeting Notes

Admin

  • IRFP released. Responses requested by December 1st.

Roadmap Review and Finalization

  • Not enough input to consider today.

Strategic Development and Contribution Plan

  • Resuscitated due to discussion surrounding the BayDAG update.
  • Not enough input to consider today.

Testing and Contribution Management Discussion

  • Are there other open source community-based projects which could provide any direction for the consortium?
    • Not much documentation. Much uncertainty about the extent to which contributions be made and how difficult it may be to integrate these contributions into the main code branch. A public-facing website is too passive – we need more information upfront.
    • MATSim is struggling with similar issues. Although, they are not in the business of maintaining certain applications. Their endeavor is strictly focused on the code. However, it may still be helpful to speak with folks from MATSim.
  • The Roadmap will provide a trajectory for the consortium. If the person triage-ing comes up with an idea which aligns with the Roadmap’s goals, their ideas should be added to the document for the consortium to confirm/give feedback. Reminder: Although the Roadmap is a living document, the document will also need active management.
  • Brainstorm Ideas:
    • A core group of people to begin sub-conversations regarding final pieces before completion.
    • For the next 6 weeks, utilize weekly Thursday time slots to discuss funding, contribution, and testing, and further partner understanding of the Roadmap.
    • Build reliability into the system by digging into the code and testing into smaller, discrete chunks - catch the corner cases. Although testing will cost (in both time and money), the cost to maintain in the long run is much less.

Going Forward

  • Contact folks from MATSim.
  • Joe to schedule weekly meetings for sub-group.
  • BayDAG pull request.
Clone this wiki locally