Page Comparison

PC Meeting Notes

• update from Dracine
  • honeysuckle is released next week (week of thanksgiving)
  • bugfest update from Anton
  • fewer failed test cases
  • easier release time
  • retrospective of goldenrod release 
    • required many hot-fixes along the way
  • many challenges
  • there was an under-appreciation of some of the bugs
  • dev leads and POs are working alongside tech council to offer better feedback opportunities from SIGs
    • hopes of a more iterative approach to feedback
  • there were some features that other stakeholders viewed as bugs 
  • module dependency (that modules be grouped, like inventory, it seems that splitting things is a bit problematic)
  • talk of app bundles? (or app feature bundling?)
  • no product council meeting next week
• Ann-Marie update
  • thunderjet is working on tags and filters on instance, holding, and item (should be done by the end of next week(
    • will present on these at a later MM SIG meeting
  • data-import meeting
    • index data is doing most of this work
    • they want to be sure that the permission to trigger the OCLC single record import is separate from other imports
    • separate permissions granted to the user (vote for 'yes' of support from the MM SIG)
    • from chat (The use of the magic button, is that separate too, or part of the regular Data Import permissions?) 
      • much liked
      • from chat (

        I think that all permissions need to be more granular and specific. It should be part of the conversation when discussion of new/old features happens.)

      • There is design behind permissions
      • Ann-Marie from chat (FYI - back on permissions - here's a doc that the POs maintain with the permissions for various apps. Each app is on a separate tab. Ask the PO for the particular app if you have questions. https://docs.google.com/spreadsheets/d/1IJnlWvi4k-wFatDNimx9fQ375evHSIIxtGMookHvs-I/edit?usp=sharing )
      • From jackie S in chat (Thanks Ann-Marie. It would be great to be able to translate the permissions here with place in the Users App where permission sets are created/permissions are set. The naming convention is not always easy to parse into what the permission allows or disallows)

Introduction

Vision and strategy paper

Comments and feedback are requested and will be accepted until Friday, November 20, 2020

New Governance Model

Feedback on new governance model

____________________________

Continued from last week

notes:

• What will the User Group or the SIGs be in the future?
  • how will we demonstrate issues and ask for solutions?
    • crowd-sourcing?
  • add comments to the Vision and strategy paper above by November 20, 2020
  • Charlotte asks if a User group would be like a support SIG?
  • How will the implementers SIG or Support SIG evolve?
    • will there need to be some division to avoid one too-large group (might get unwieldy)
  • ref: bywater customers and the other communities they support who may not be their direct customers
  • vendors who want to support folio also will need to get involved in the community
  • Governance model(s)?
    • Product council / community council (which is new)
      • seems to suggest the Community Council will be taking over some of the work the Product Council has been doing de facto
      • Seems to have been working between Product Council and stakeholders group
      • Technical council (TC) is working on technical things
      • Suggests SIGs (like MM SIG) are in the Working Group section
      • SIGs currently report to the Product Council (PC)
      • the managing of the money is also important and is connected through everything
      • How to contribute expertise and money (some will contribute one or the other, not necessarily both)
        • Membership falls under these various lines of contributions of kind or money
      • Asking: do voting members all contribute some kind of money?
        • community is defined as having a Jira account?
        • framed around elections?
        • Policy making takes place elsewhere
        • Big conversation about representation on councils (one seat per council by each institution)
        • how to move governance to the way Koha is governed
        • How is the communty community being defined?
          • how to be open with the awareness that development that tools need resources in the form of $
          • Look at the governance document linked above (feedback deadline, November 20, 2020)