Versions Compared

Old Version 3

changes.mady.by.user Ingolf Kuss

Saved on

compared with

New Version Current

changes.mady.by.user Tod Olson

Saved on

Key

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

Date

Attendees

Tod Olson Axel Dörrer  Anton Emelianov (Deactivated) Brandon Tharp Florian Gleixner Florian Kreft Ian Walls James Fuller jpnelson jroot 

...

TimeItemWhoNotes
5Support 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.

  • Anton Emelianov (Deactivated) is attending, useful to have more representation because support issues include getting fixes out, which has deployment/operations implications. Anton is willing to also look after SysOps interests.
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?

  • Anton has been hit by this when running BugFest with requests for new modules late in the game. TC has technical requirements already, but there are also needs to be clear on how this affects deployment/SysOps concerns. Argues for SysOps criteria/approval process.
  • Important that the process in clear, do not want surprises at deployment time; new requirements have implications.
  • Anton Emelianov (Deactivated) volunteers to participate
  • See also New Module Technical Evaluation Processes
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

  • Intend to put together a working group to groom epics and user stories for NFRs from
Operational and SysOps needs

77 backend calls to do a checkout.

  • Intersects with Roadmap, see
  • jpnelson volunteers for subgroup
20FOLIO Integrations

Status of this work ?


SWOT analysis
FOLIO Product Council, introduced the idea of a SWOT survey for the FOLIO Community. They have invited any implemented library – or any soon-to-be-implemented library – to participate at https://forms.office.com/r/XDi2pEJtzU.   The form linked above is designed so that multiple people from a single institution can fill it out – multiple times if desired! There are no demographic questions included in the form, but you may self-identify if you wish.   Please participate by November 30th to ensure that your institution’s voice is heard!   If you’re interested in viewing the discussion from November 2nd, a meeting recording can be found here: https://drive.google.com/file/d/1mVUmi2o1ki61_HhV7TpCow0hahDENOJq/view?usp=sharing
5Topics for future meetings


  • Moving reference data between two instances of FOLIO; e.g. circulation rule migration
  • Campus IdM management with FOLIO
  • WolfCon 2022: Call to action for SIGs and Councils is out
    • WolfCon Hamburg, Germany, 31.08 - 02.09., Bucerius Law School
      Widget Connector
      urlhttps://docs.google.com/presentation/d/1w3o_wHjpgtqNKVSMiIWgZ46wQEnAopsKruv1ikk32yk/edit#slide=id.g1014119ffe9_0_10

      "Skeleton Agenda until 31.12.2021"
      "Detailed Agenda until  31.03.2021"
      Call to action: SIGs and Councils
      Add items to this page wiki/CC/Folio+at+WOLFcon until 01.12.2021 !!
    • A mega SysOps session about technical debt at the next WolfCon




...