#acumos-meeting: Architecture Committee

Meeting summary

1. Release status (farheen_att, 14:06:39)
   1. Murali: Licensing issue. (farheen_att, 14:06:57)
   2. Michelle: There is an RTU agreement with the model. I will continue to work with him offline. (farheen_att, 14:07:19)
   3. Michelle: it is just for logging. On a runner side car it tracks the api and provides a file for the logging platform. It is to do some logging and tracking. (farheen_att, 14:07:59)
   4. Manoop: I saw license text that was maintained by Eric. In my opinion this is a false warning. The reason why LF picked up is due to special characters. I think the file got regenerated. I will see if that is the case and verify and email you. (farheen_att, 14:09:06)
   5. Murali: There are 3 issues on the wiki. (farheen_att, 14:09:18)
   6. Manoop: We will discuss after the call. (farheen_att, 14:09:29)
   
   
2. Licensing demo (farheen_att, 14:09:42)
   1. Michelle and Vaibhav sharing demo screen. Murali recording the demo. (farheen_att, 14:10:26)
   
   
3. Murali we are waiting for onboarding sanity tests. (farheen_att, 14:48:37)
   1. Phillippe wants to add to this weeks build (farheen_att, 14:48:54)
   2. Phillippe can provide the build in a few hours. (farheen_att, 14:49:09)
   3. Nat: Is licensing sending us a build? (farheen_att, 14:49:26)
   4. Murali: The licensing issue is not critical (farheen_att, 14:49:55)
   5. Nat if onboarding can send it in the next few hours then the release manager will accept it. (farheen_att, 14:50:37)
   6. if this onboarding causes issues then we will defer it. (farheen_att, 14:50:50)
   7. Nat: as soon as we get sanity tests from the test team move your build to the staging repo. Send your notes to Vasu and Murali. (farheen_att, 14:51:59)
   8. Ken the other thing that is blocking us is onboarding the C++ model. (farheen_att, 14:52:45)
   9. Phillippe Ken C++ is a library. It is not code (farheen_att, 14:52:59)
   10. Manoop: Nat Murali how should we schedule the meetings for the architecture and PTL calls. Do we need architecture and PTL calls every week or alternate weeks? (farheen_att, 14:53:59)
   11. should we use the Tuesday morning call every week or alternate one week architecture call and PTL. (farheen_att, 14:54:35)
   12. every Monday we have TSC. Tuesday we have the PTL and Community call. Wed we do he Architecture. (farheen_att, 14:55:05)
   13. TSC will be every alternate Monday. Every Tuesday we can do one week PTL. One week have the Community call alternate with the PTL call alternate with Architecture meeting. (farheen_att, 14:56:15)
   14. the order should be the community call first then the community call then the architecture every Tuesday. Any issues can be brought to the alternate TSC call. (farheen_att, 14:57:24)
   15. Manoop for the weekly agendas PTLs have to reach out to the community with an agenda. Open calls without agendas are not productive. PTLs should provide the agenda items. (farheen_att, 14:58:12)
   16. Nat: May 26 and June meetings will discuss the point release. (farheen_att, 15:00:51)

Action items

1. (none)

People present (lines said)

1. farheen_att (29)
2. collab-meetbot (3)