2022-05-25 Meeting notes

Date

25 May 2022

Attendees

Discussion items

Time	Item	Who	Notes
1 min	Scribe	All	Raman Auramau is next, followed by Dennis Benndorf
5 min	Review outstanding action items	All	No explicit updates
5-10 min	TCR Board Review	All	No updates on Translation app
10-15 min	Technical Council Sub Groups Updates	All	Notes from last week: Craig McNally submitted PR for Acceptance Criteria edits, received good feedback from Marc Johnson . The rest of the TC should review the PR request. Controlling AWS hosting costs - Mark Veksler reports progress. The subgroup plans to document account ownership, lifecycle, and tagging practices to better track the expenses. Suggestion to add it to the TC agenda as a 2-minute line item to flag any cost overruns, trends in increases, and plan to remediate the cost increases. New developer onboarding - Radhakrishnan Gopalakrishnan reports that the document is under review. RFC process adjustments here: RFC Process - Radhakrishnan Gopalakrishnan requests feedback on it. Today: Tech Eval Process Subgr Chulin Meng - target date is mid of June; Radhakrishnan Gopalakrishnan - Cross app data sync is a candidate for presentation; as for the RFC process description - there are no comments there yet Marc Johnson - Cross app data sync decided not to document it as RFC (maybe later but not now); Localization app is another candidate Chulin Meng - the subgroup will be completed by the end of June Marc Johnson expressed concern that the RFC process had not yet worked out in some areas (i.e., Public Review phase) The subgroup position is that it's ok to learn by doing; Marc Johnson insists that it is impossible to learn because the vision of the Public Review Phase is not detalized the discussion continued for some time, but no decision was made... Tech Council Goals - Tod Olson in the process, there are a number of comments, but some of them are very different. From the side of SysOps - there are own interests Translation subgr - Zak Burke no updates Cross-council group - Marc Johnson there a draft process, presented to Comm Council on Mon, to PC/TC later Controlling hosting costs - Steffen Köhler there is already a list of items that one needs to pay attention to Tech documentation - Radhakrishnan Gopalakrishnan no updates
10 min	Localization RFC	Radhakrishnan Gopalakrishnan/All
1-2 min	Elections	All	From Mike Gorrell : Simeon Warner and Harry Kaplanian are running this year’s elections for all councils. Please let them know if anyone from PC or TC wants to help out. Also, they ask that you let them know whether you want to change description/qualifications from last year as well as confirm how many seats will be open (should be 5 for each council but not sure whether anyone has/is stepping down).Reminder that 6 seats on the TC/PC were supposed to be 2 year terms, and 5 seats were supposed to be 1 year terms - those 5 seats are the ones open for election this year. The announcement/request for candidates should go out May 9th. Our timetable is: Call for Nominees May 9, 2022 Nominees due/finalized May 20, 2022 Voting opens May 30, 2022 Voting ends June 17, 2022 Results announce June 20, 2022 New Councils formed/start July 1, 2022 Please let me know if you have any questions. Thanks! Today: Reminder for those planning to run... Nominations are due by May 20 using this nomination form. As of Saturday May 21, there were only 4 nominations for 6 open seats!
5-10 min	Community Update	All	Tentative date: May 27 TC needs to start preparing their update: Accomplishments in Q1 2022, Goals/plan for Q2 2022 Craig McNally will present at next community update Craig McNally has started a thread in the #tc-internal channel, if you have feedback please post it there Today: Any thoughts on Achievements/Goals? Literally no movement in the thread mentioned above.
5-10 min	Updates from PC and CC?	Tod Olson Marc Johnson	No updates Prioritization of features and it will workf
5-10 min	ADRs	Radhakrishnan Gopalakrishnan / Marc Johnson	Decision Records Proposing ADRs with naming conventions preserve decision history including decisions that have been revised/made obsolete Proposal to do this in Confluence (alternate would be Github) where are they most findable. Github is closer to where developers work, wiki is easier to search. When an ADR is related to an RFC, would link to RFC. RFC is the process, ADR is the result. Feedback desired! Today: Radhakrishnan Gopalakrishnan - no new comments. Craig McNally does silence mean acceptance? What about the ADR-1 (Kafka) - does this mean it is accepted? Ingolf Kuss does this ADR mean that Kafka is instead of pubsub? - No Craig McNally Kafka has been introduced but with no formal approval, so this is to avoid ambiguity Marc Johnson provided a brief historical digression in using Kafka on the platform Decision: ADR-00001 can be considered as approved via lazy consensus as there were no explicit objections voiced!
10-15 minutes	Tool/Dependency Versions	All	Question was raised in slack by Marc Johnson How do we make tool version decisions? I’m asking because FOLIO is currently on Java 11. I imagine it could be prudent to move to 17 (the next LTS) at some point.And it seems that the #stripes-architecture group made the decision to move the project from Node 14 to 16 recently.I don’t think there is an equivalent group for the back end. How do we envisage the project making these kinds of decisions? Some feedback was given, but it's probably worth discussing as a group. Should we form a sub-group to define polices/processes? Today: there was some discussion and some comments; in general, the problem is relevant for the backend, frontend, infrastructure. Agreed to make a placeholder for next week, and once again contact in search of volunteers

Attendees

Discussion items

Action Items