Versions Compared

Old Version 2

changes.mady.by.user Jenn Colt

Saved on

compared with

New Version Current

changes.mady.by.user Maccabee Levine

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: meeting notes


Date

22

Attendees 

Discussion items

TimeItemWhoNotes
1 minScribeAll
Maccabee Levine will scribe
Marc Johnson is next, followed by Ingolf Kuss (on vacation until ), then skip Julian Ladisch as he filled in on  

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

5-10 minLiaison Updates

Maccabee Levine

Tod Olson

Jakub Skoczen

Craig McNally

Jenn Colt 

1 minUpcoming MeetingsAll
  •  - Dedicated Discussion: Officially Supported Technologies
  •  - Regular TC Meeting
  • 07 August 2024 Dedicated Discussion: RFC retro part 'n' and Tod Olson's suggestion
  • Regular TC Meeting
5-15 minTCR Board ReviewAll
  • Florian Gleixner - mod-reading-room:
    • Met with development team.  Impetus was LOC, to control access to the reading rooms for individual users.
    • Self-evaluation was correct, nothing wrongly checked.
    • Logs are kept without expiration date.  EU GDPR would not support this, should be documented.  Legal issue, not technical.  Recommend possibility to clear the logs, or to not record them.  Send that recommendation to the development team.
      • Craig McNally Makes sense to document this and create a UX-PROD to address.  And if it should be handled for all modules, should be added to criteria for all modules, not just this one.
      • Jenn Colt Privacy SIG has been quiet, but PC could ask them to take this up.  Should be part of the product.
      • Jens Heinrich This should be documented in the personal data disclosure form.  And maybe that should be enhanced with timescales info, i.e. the timing of how long the data is stored.
      • Maccabee Levine Agree it passes the TC criterion since the disclosure form is accurate.  It's a product issue if we want timescale reported or changed.
      • Jeremy Huff Agree.  But it's not an accident that this came up in a technical review, privacy sometimes requires technical investigation.  Interplay between TC and PC, not sure what that would look like.
    • TC voted, module approved.
  • Jenn Colt - ui-reading-room .
    • Working on it, no update yet, will have on soon.
  • TCR-43: mod-marc-migrations: Jeremy Huff
    • Planning to make headway this week
5 min

Technical Council Sub-Groups Updates

All

Developer Docs

  • proposal later on agenda
  • Jeremy Huff Going well thanks to Patrick's productivity.
1 minRFCs

All

Reminder(s)

  • Go RFC still open - admin action required, only a PoC - nothing formal required other than closing the pull request.
  • Still Need Decision Log record for application formalization, Go, configuration RFCs
10 minSecurity Team Personnel changesCraig McNally
  •  The Security Team is seeking formal approval to add Jens Heinrich and Kevin Day as members.
  • Jens Heinrich Works at IdM working group for German FOLIO project.  Designing how to sync FOLIO and current identity solutions.  Moving from implementing work to mostly security.  Security critical for libraries and libraries for universities.
    • Craig McNally Jens was also participated in API fuzzing to discover vulnerability, by network security operations group.
    • Jens Heinrich Modern tooling expects OpenAPI spec not RAML.  Got stuck behind higher priorities but could start again with conversion to OpenAPI spec.  Also on GDPR conformity part of HEBIS.
  • Craig McNally Kevin Day (TAMU) has been a full-stack dev.  Workflow, camunda modules.
    • Jeremy Huff He is tech lead for the workflow work.  Work at TAMU not just FOLIO.  Very security-minded, involved in different technical communities' security concerns.
  • TC approved new personnel by lazy consensus.
15 minProposed structure for developer manualPatrick Pace (Unlicensed)
  • /wiki/spaces/DDG/pages/283934733
  • Patrick Pace (Unlicensed) If approved, it will serve as the initial form.  Planned to be fluid.  But should be logical & organized so a new developer could read through the manual, be ready to develop.  Veteran can find exactly what they're looking for rather than only depending on search.
    • Logical progression of major sections
      • Introduction to FOLIO.  Expectation of a development background, but not FOLIO.
      • How to Use This Manual.  And how to contribute.
      • Accessing the FOLIO Toolstack.
      • Core Technical Concepts (4) and Advanced Technical Concepts (6) have balancing.  But the idea is not to get deep very quick.  Have conceptual stuff precede the practical stuff.
      • Development in Practice.  I.e. style guide.  Finding an issue, starting to contribute.
      • Advanced Technical Topics.  All the detail we want.  So developers can do so "well".
      • Tips, Tutorials, Examples and Templates.  Building on the technical details.  Things that can be re-used.
      • Reference.  Like source code map, API documentation.
      • Appendices.  Anything that doesn't have a place elsewhere.
  • Jens Heinrich First section is about FOLIO as a project?
  • Jeremy Huff The version of FOLIO that the document relates to should be clear.
    • Patrick Pace (Unlicensed) Functional docs group does that, so precedence.  Need input on that.
    • Jens Heinrich How much of the documentation is release dependent?  Seems not much.  Only 6 and upwards very dependent on the release.
    • Jeremy Huff Esp with application formalization, sections 4-6 may change a lot.
    • Maccabee Levine Suggest focus on the current version, perhaps callouts / sidebars with "Prior to release X, something different".
  • Jeremy Huff Does TC need a process in place for significant changes to the manual in the future?
    • Patrick Pace (Unlicensed) Hopefully there will continuously be incidental changes.  Dev documentation group would have regular reviews.
  • Jenn Colt Comfortable accepting this, knowing it can evolve and dev documentation group can manage the changes.
  • Approved by lazy consensus.
1 minDecision LogAll

Need to log decisions for the following:  (see above)

  • Decentralized configuration - Florian is working on this, will come back around next week. Write-up in draft
  • Go programming language
  • Application formalization - Craig will update next week


Time Permitting

Officially Supported Technologies (OST)

All

Check Recurring Calendar

  • Message to channels about RFCs.  Due end of next week.  Craig McNally and Jenn Colt will confer about posting to the listed channels.  Maybe find automation.
Time PermittingReference Data Upgrade

Ingolf Kuss

Jason Root

Craig McNally

Marc Johnson

Julian Ladisch

Hold until after Aug 2.

In the Sys Ops SIG meeting the topic of Reference Data Upgrades came up. The SIG thinks that the solution of this problem for mod-inventory-storage is not enough, but that this problem needs to be solved in a general way, for all modules.

There has been a long discussion 3-4 years ago about how FOLIO should handle reference data upon upgrades. See these links for background:

Previous Notes:

Marc Johnson points out he remembers a difference set of formal processes for this from the previous subgroup

Jason R. asks if the issue is that you cannot specify per-module what type of data to load, or that no matter what is specified the upgrade process overrides it

Marc mentions that the proposal to correct this by Vince is a very involved and complex workflow. There has been no developer resources allocated to correct this issue and address the proposal

No easy solution to this problem because the original default data is lost to time and change

Will reach out to Julian Ladisch when he returns

Notes:

Ingolf Kuss is on vacation.  Lets wait until Julian and Ingolf are both here.

Today:

  • Maccabee Levine Is this the same as the PC subgroup working to improve sample data?
    • Marc Johnson Not sure.
    • Tod Olson Thought we were taking about the same thing as the group a lot of people were on for a while.
    • Craig McNally Reference data working group a couple years ago is what sysops is taking about.  Not sure if it's the same as the sample data group.
    • Tod Olson Was much more involved the last time.
    • Maccabee Levine Just make sure the two groups are aware of each other.
  • When Ingolf Kuss returns, can get more info.
  • Tod Olson This new PC group is about sample data.  Years ago data was contributed.  Now new functionality, there are no sample data test cases.
  • Maccabee Levine Example, in snapshot there are no orders connected to any invoices.
  • Tod Olson Reference data can be customized (i.e. material types) or added to, but often is not.  Some stable conventions are needed for the reference environments.  It's a fuzzy boundary.
NAZoom Chat



...