Project Meeting 2023.07.11 - ActivitySim/activitysim GitHub Wiki
Agenda
- Roadmap Update: Management and Governance
Action Items
- Everyone: review the draft draft management plan document and and any comments or feedback.
Meeting Notes
Presentation: activitsim-roadmap-wip-management-plan-version-2-11-july.pptx
Management Plan
- The deliverable is meant to be a living document that would be updated annually.
- Directors would make the decisions.
- Project management sub-committee would include 3 members, who would rotate off in 3 years (staggered) and primary responsibilities would include administrative things.
- Objectives and Key Results (OKR) sub-committee would include 3 members, who would rotate off in 3 years (staggered) and primary responsibilities include tracking and setting big picture things.
- Engineering Team would include an Engineering Lead, who would set the scope of work, quarterly, for engineer team and directors would approve/revise accoordingly. The Engineer Team would include two members from each bench consultant for which the Engineer Lead is not employed and the bench consultant of the Engineering Lead would include one other member.
- There was some question about the quarterly scopes of work. To clarify, this does not mean that all work needs to start and end in 3 months; it does not mean that there will be a meaningful beta release every 3 months. The quarterly time frame is meant to note incremental milestones and key points for evaluation. Partners will have control on official releases, versions, numbering, etc., not just what can be done technically.
- Engineering sub-committee who be those interested in the engineering work and provide opinions but not direction.
- Community Manager would be a consortium member, who would be the face of ActivitySim, and is currently designated to be Joe C.
Governance
- Most of the drafted governance section was obtained from the current GitHub page.
- That GitHub page included a lot of things that does not pertain to director decision-making (such as code management, which would better fall under the Engineering Team through some developed standards, for example) but was retained in the Appendix.
- A table of actions was updated. This is probably the most important thing to review.