Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Draft update from TC

Date

Meetings are held on Thursdays at 9:30 a.m. Eastern U.S. time (following daylight saving time rules for the Eastern U.S. timezone; see this time in your timezone). Download .ics file to add this meeting to your calendar.


Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/867230970

Or mobile phone one-tap (US Toll):  +14086380968,867230970# or +16465588656,867230970#

Or Telephone:

Dial (for higher quality, dial a number based on your current location)
US Toll: +1 408 638 0968 or +1 646 558 8656
Meeting ID: 867 230 970
International numbers available: https://zoom.us/zoomconference?m=HFOYojqG6P0eOobNily-kmpgCrJ9eJQ_

Discussion items

ItemWhoNotes
Announcements

Council Updates:

Community Council

Technical Council

Product Owners

Capacity Planning updates

Community Council

Technical Council

Technical Reviews: no changes, translation app still waiting on Translations subgroup

Subgroups:

  • Technical Evaluation Process: have solicited feedback on process and incorporated; will conduct retrospective on the group work.
  • TC Goals & Objectives: still collecting pain points, SysOps decided would be best to construct their own pain points document but there have been obstacles to finishing. Still intend to drive architectural topics at WOLFcon. Some pain points have clear costs in terms of time and money, which might help with directing effort to solutions.
  • Translation subgroup: Still having trouble allocating time for this subgroup, will try to recruit more broadly.
  • Controlling AWS costs: no further movement
  • Developer onboarding: intend to contact Marcia B., but no further developments at this time.

FOLIO Scope Criteria presented their work to TC, engaged conversation, broad agreement that the issues raised are important issues for FOLIO to address, with several practical and conceptual particulars.

Tools/Dependency decisions: How do we make decisions about updating required versions of tools/packaged used by the project, e.g. how do we decide to upgrade the version of Java that we use? Considerations are somewhat different between front end and back end. Starting point is to document current versions of software needed by each release and collecting comments on a draft process. (See Officially Supported Technologies and Managing Tools/Frameworks/Dependencies Version - DRAFT VERSION.)

Accepted proposal to formalize conventions for tenant and module names (ADR-000002 - Tenant Id and Module Name Restrictions).

Localization RFC for back end is nearly complete.

Security Team has asked about the support period for Morning Glory and Kiwi. There are older versions running in production who are not ready to upgrade, but the cost to back-port security fixes is high. TC is not the decision maker here. Most recent statement seems to be in the LTS Recommendation document, but it is unclear where this was presented and whether it was accepted by the project. Team will reach out to the authors of the document.

Kafka issues: There was a presentation this week pointing out specific scalability (and security) issues with the way FOLIO is using Kafka, particularly in the way we organize topics. The outcome is that there will be an RFC process to address the scalability issues.

Product Owners

Capacity Planning updates

Browser Support for FOLIO

Owen Stephens

  • What browsers should be supported?
  • How do we determine when a browser is supported?
  • Probably TC Topic as well


Continue discussion from last week.  Note from 6/16: Knowing what we mean by "support" is important for this discussion, as the community itself is not charged with supporting end-users. Product Owners would treat a rendering bug that only happens in Firefox or Safari as at most a priority-2 bug because there is a valid work-around ("Use Chrome").
Future agenda topics

...