20180926 - Technical Council Meeting notes
Date
Attendees
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
10 min | Update | team | Quick review of backlog and status/updates:
|
20 min | Definition of Done | Summarize team comments and discussion next steps
| |
20 min | Pull Requests/Repo Management | Discuss the role that the Core Team has in supporting new developers, and how Repos are managed. Discuss proposal by Khalilah Gambrell and John Malconian. KG: We are still experiencing delays with receiving tech design and PR approvals. These delays cause blockers that result in stories being pushed to 1-2 sprints. As a result, the Folijet team and I want to propose the following effective today. We hope this revised approach will ensure a smooth process for the additional epam dev teams joining the FOLIO community.
Tech Design review and approval 1 – Team member/PO will send technical design to reviewers 2- Team member/PO will schedule a meeting within the next 3-4 days to review design and get approval
PR approval 1- Developer will add applicable Core developer(s) to review/approve PR 2- Developer will send a reminder to that Core developer(s) to review/approve PR within the next 24 hours 3- If no feedback by Core developer(s) within 48 hours then the developer will proceed with PR merge Any concerns with this approach? And... JM: I think we might want to implement Github CODEOWNERS for each repository so that developers know who are the best options for approving PRs for each repo. https://help.github.com/articles/about-codeowners/ help.github.com Also, it may make sense to assign an EPAM dev as a co-owner to many of the modules.
Discussion
| |
new business | Agenda for the next meeting:
Many people are out next week; next meeting planned for October 10, 2018. |
Action Items
- Mike Gorrell to follow up with Taras Mankovski re: Stripes 1.0 effort
- Mike Gorrell to follow up with Mark Veksler, Peter Murray about how to operationalize the definition of done