Page Comparison

Farewell to md331 (Deactivated)

Mark is leaving FOLIO .  Thank you for your contributions to the project.  Best of luck! 

Regarding a replacement...

Here's what our Governance Model says:

Any council may appoint members to fill vacant seats (up to the maximum) on the council, if necessary. When possible, individuals who were the next highest vote getters in the previous election should be selected. The CC will ratify any appointment to ensure that it doesn’t violate any council membership rules.

Chulin Meng (Lehigh) was the next highest vote getter.

• We should probably:
  • Reach out to him to see if he's still interested and able to join.
  • Assuming he is, 
    • Update the TC member history and home page.
    • Get him the meeting details, part of the slack channel, etc.
    • Anything else?

Dennis Benndorf

• Dennis Benndorfdescribed a scenario where they moved tenants between database servers, attachments to agreements were not moved with the rest of the data due to how they were stored
• To mitigate this Knowledge Integration proposed the adoption of min.io for file storage
• Philip Robinson advised that the Scout have already chosen to use it for the Bursar work
• Philip Robinson asked if there are any security considerations?
• Jeremy Huff asked if this relies on AWS? It was advised that it does not
• VBar raised a concern about min.io using the AGPL v3 licence which may not be compatible with FOLIO e.g. client libraries
• Dennis Benndorf suggested that Ian Ibbotson (Use this one)be invited to the next TC meeting to explain the choice
• Marc Johnson advised that Ian Ibbotson (Use this one) intended to be here however could not 
• Marc Johnson advised that the proposition was likely based upon
• VBar advised that the min.io client libraries are licensed under Apache 2.0, Marc Johnson advised that the AWS S3 libraries (used by data export) are also licensed under Apache 2.0
• Dennis Benndorf Is the decision to include min.io in the platform or provide it?
• Jeremy Huff proposed that we write a file storage module that could integrate with S3 or min.io
• Marc Johnson suggested that we even if we build that module, it may not change the decision today
• Dennis Benndorf suggested that we decide to use the S3 APIs and hosting providers can use their choice of server e.g. AWS, min.io
• Philip Robinson suggested that we should use S3 APIs as that could allow folks to use other infrastructure e.g. Azure
• Ian Walls suggested that using standards is a good approach
• Marc Johnson asked if the S3 APIs are a standard?
• Ian Walls suggested it was an industry standard rather than an ISO standard
• Jeremy Huffproposes that we have a file storage interface and module that uses min.io, S3 etc
• VBar Suggests there are two decisions here:
  • Which client library should the project standardise on?
  • Should there be a centralised file storage abstraction?
• VBar suggested that there would be a performance overhead to a centralised model, particular with FOLIO's architecture Jeremy Huff suggests it can be mitigated with changes to the architecture
• Marc Johnson suggested that we go with the decision that modules should use the S3
• It was decided that we schedule a resumption to this next week and make a decision on whether FOLIO should adopt the S3 APIs and related questions

• Jeremy Huff asked if we have any examples of the TC resolving conflicts? Tod Olson cited the reference record upgrades work as an example of this
• The group decided that documentation of decisions (with reasoning) in the meeting notes is sufficient documentation for conflict resolution. With reservation for publishing a separate document when appropriate.