Skip to end of banner
Go to start of banner

2022-06-01 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Date

Attendees 

Discussion items

TimeItemWhoNotes
1 minScribeAll

Dennis Benndorf  is next, followed by Zak Burke 

5 min

Review outstanding action itemsAll

No explicit updates

1 minTCR Board Review

All

TCR-9 Volunteer/Assignee
5 min

Technical Council Sub Groups Updates

All


Notes from last week:

  • 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., the 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


Today:

10 minLocalization RFC
30 minScope/Criteria Group Update
10-15 minutesTool/Dependency VersionsAll

Notes from last week:

The 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 policies/processes?

Today: there was some discussion and some comments; in general, the problem is relevant for the backend, frontend, and infrastructure. Agreed to make a placeholder for next week, and once again contact in search of volunteers

Today:


Action Items

  • No labels