Versions Compared

Old Version 1

changes.mady.by.user Ingolf Kuss

Saved on

compared with

New Version 2

changes.mady.by.user Tod Olson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added Support SIG call for members

...

Discussion items

TimeItemWhoNotes
255Support SIG call

Tod Olson 

Support SIG has put out a call for more participation, and would really like another from SysOps as Phil needs to step back. Mondays, 10AM EST.
Biggest requirement may be empathy for staff and some understanding of library workflows.
20Acceptance Criteria for Code Contributions

In the PC meeting there was an update on the cross-council group on high-level criteria for accepting modules/code. Tod agreed to:

bring this back to the TC and suggest that someone from [TC] and/or the Sysops SIG to join the effort in drafting this document. Having about 6 core members with the ability to reach out to others as needed is what is desired.


One observation was that it's not currently clear how to include SysOps concerns in the high-level process. (Though the current TC draft seems to cover some of it.)
So, we have a call for another volunteer to lend a technical voice. Is there anyone here in SysOps who would like to help out?

10FOLIO infrastructure / NFRs

"Grooming": Work on Epic(s) and User Stories & Sub-Stories for those

Work for a subgroup.

Seems to be the proper way forward

77 backend calls to do a checkout.

20FOLIO Integrations

Status of this work ?

5Topics for future meetings


  • Moving reference data between two instances of FOLIO; e.g. circulation rule migration
  • Campus IdM management with FOLIO
  • A mega session about technical debt at the next WolfCon




...