Versions Compared

Old Version 1

changes.mady.by.user Craig McNally

Saved on

compared with

New Version 2

changes.mady.by.user Craig McNally

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Translator

...

Attendees 

Discussion items

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

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 

  • CC: Maccabee Levine

    • Welcome to new members. Stephen Pampell (TAMU) volunteered as liaison to TC. Shawn Nicholson (Michigan State) volunteered (prior to meeting) as CC member of AWS Cost Review Group.

    • Developer advocate role. Jeremy summarized work so far. Several members spoke positively. CC will look at budget. Want PC and TC to weigh in on renewal ahead of next CC meeting 8/12.

  • PC: Tod Olson
  • RMS Group: Jakub Skoczen 
    • meetings canceled until 7/29
  • Security Team: Craig McNally 
    • Update on candidates for joining the security team:
      • Met with Jens Heinrich again.  Need to sync up with Kevin Day.
      • Will likely be seeking formal approval from the TC soon.
  • Tri-council Application Formalization: Jenn Colt  
    • No meeting last week
1 minUpcoming MeetingsAll
  •  - Dedicated Discussion: Topic TBD
  •  - Regular TC Meeting
  •  - Dedicated Discussion: Topic TBD
  •  - Regular TC Meeting
5-10 minTCR Board ReviewAll
  • Florian Gleixner - mod-reading-room: Meeting with development team. Got module and functionality presentation. Another meeting after evaluation is soon is planned.
  • Jenn Colt - ui-reading-room  - Jenn started evaluation.
  • TCR-43: mod-marc-migrations: Jeremy Huff will do the evaluation, Tod Olson and Jason Root will help.
5 min

Technical Council Sub-Groups Updates

All


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
15 min/wiki/spaces/DDG/pages/296157187Patrick Pace

From Slack:

Hi TC,

Can I request a 15-minute block of time for this coming Monday's meeting?

On behalf of the documentation subgroup, I'll propose a contribution model and best practices for community contributions to developer documentation. This is intended as a conceptual framework and not practical documentation, so to speak. That is, this document won't go in our documentation, but if approved, its propositions will be used for building such.

Please review the following in preparation for the proposal. And if you have any questions or anything, please let me or any member of the subgroup know. And feel free to comment on the document.

/wiki/spaces/DDG/pages/296157187


15 minPlatform Comparisons, Platform ProposalJulian Ladisch

From Slack:

Yesterday the developer documentation group decided on Confluence as documentation platform (Platform Comparisons, Platform Proposal - still rough draft -). The actual documentation work cannot start until the TC has approved this decision. To remove this blocker as early as possible I suggest to put this on Monday's agenda even if the proposal document is still in rough draft status.

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


Time PermittingReference Data Upgrade

Ingolf Kuss

Jason Root

Craig McNally

Marc Johnson

Julian Ladisch

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:

  • ...


NAZoom Chat



...