Page Comparison

Library of Congress registration finally complete, ready to send their invoice

• MoU still needs to be signed

Membership renewals sent out last week

• Some FY24 funds already coming in

See FOLIO Code of Conduct for current description

• Mike will check on the group if emails are delivered correctly and the group knows of their tasks (please note: Sharon Wiles-Young has retired) 
• Question: is there a similar group / code of conduct for the OLF? 
  • Christopher: want to ensure that all projects are represented and there is a link for the WOLFCon
• VuFind has a Code of Conduct, and a project team email to contact.  Not necessarily equivalent though.  https://github.com/vufind-org/vufind/blob/dev/CODE_OF_CONDUCT.md

Amount available:   Paula?

• TC suggestions: https://docs.google.com/document/d/1PK57lgZKxLBdpK5fqN55t3nQneid_9Dzdf2s5SCbYxE/edit?usp=sharing 
• PC suggestions 2023-05-22 Meeting notes

Thinking about our funding

• Is this one-time money ($150k-$200k in FY24) or are we planning to have a certain amount to spend each year. If we imagine ongoing, how much should we plan on?

• Funding: ongoing vs. one-time - "ongoing" is not necessarily "continuous"

Staffing for ongoing roles

• Community Developer Advocate (TC, PC, Support SIG)

  • There are 2 goals: where do new developers are pointed to to find their place to work? And then help with their practical onboarding?
  • Developers come to the project with different expectations and interests 
  • Development efforts need to be coordinated and cultivated
  • Onboarding interview to find out what a developer wants to do and where to work and what kind of training is needed
  • Outcome: general agreement from CC about this approach. PC/TC to do some more refinement, how an engagement would look like concretely - which kind of authority such an advocate will have?
    • Refine the scope of work 
    • How to find the first CDA?  → Out of the existing pool of people as an rotating role → How?
    • OLF can only reimburse an institution for its engagement, not hire someone directly
    • How much will this engagement cost? Part-time job is feasible (20 to 50%) 
      • Paula: I'll have firm $$ next meeting of how much we'll have from FY23 to spend. 
• New: Harrys proposal:
  • project needs an analyst to collect requirements
    • e.g. pick up work, that has not been worked on for some while but would be wanted from libraries to be done  → do the pre-work to present a proposal 
  • another need: testing
• Toms proposal: “The List of Things that Could be Better about FOLIO” from October ’22 could be a useful artifact to mine for targets of incremental funding. 

  https://docs.google.com/presentation/d/1x2jON9yjEQboPlXiwFm8pqPT69g0wCDCD_4atR04atw/edit#slide=id.p 

  • Documentation onboarding

• Product Owner (see discussion 2023-05-22 and questions of PO divorced from teams. Product Owners: Available positions)

Ongoing programs/subscriptions

• FOLIO reference environment (TC, staffing and hosting costs)

  • woud be good not to need to maintain reference environments for older versions

• Airtable for prioritization (TC, subscription cost)- Cost not clear yet and also not clear that heavyweight prioritization is best approach

One-time projects

• Security audit (TC)

  • last SA is from 2018
  • Should be done regularly (like every 3 years)  - new scope is added, architecture changes
  • Important for Europe  / Independency

• Privacy assessment working with Privacy SIG (TC)

  • Same as SA

• Github actions migration (TC)

• Innovation grant (TC)

Outcome:

• How much money can we spend?
• Have specific recommendations to vote on (including costs for each position)
• Take forward the Community Developer Advocate back to PC/TC