Attendees
Agenda
- Ratify the Technical Charter
- Discuss Pull Requests Approval Process
- Discuss CI/CD Approach
- Discuss and Ratify Architecture View
- Time Permitting...Logo vote link
Minutes
Participants reviewed the TSC representatives who have put their names forward thus far.
Companies HPE, Intel, AMI, TietoEvry, Kubermatic have named a TSC representative.
Therefore, ODIM has formed a TSC with 5 companies represented and any vote of 3 can ratify a decision .
TSC then proceeded to call for a vote to ratify the Technical Charter, which was discussed last week.
TSC approved 5 votes +1 to ratify the Technical Charter, no disapproval, no abstain
Note: we agreed that we would vote in the chat window and capture save the chat for records of votes.
Moved on to discussion of Pull request process- i.e how do we go about submitting and approviing code changes.
We have a github setup for the project and will use Git Issues to post proposed changes and Pull Requests for actual code submissions
We discussed that bigger changes would warrant a "one pager" document proposals on what is the rationale, purpose, high level implementation ,impact etc of the proposed changes.
How would we capture them and archive them?
Jonas proposed the using Git Issues but others did point out that we can always save on the wiki major feature or subsystem proposals and ultimately use GIT Issues to officially submit.
Small changes, with little impact can be done with much less overhead or process-
Developer can create a Git Issue- opens a Feature Branch, complete an implementation, make a Pull Request- Reviewers will review the Pull Request
- Maintainer plus Reviewers (number?) must approve the PR
Discussion around the visibility of the Feature Branch and how this impacts collaboration...
We created a page to capture the process : ODIM Review Process