Skip to end of banner
Go to start of banner

2023-06-26 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Date

Attendees

Paula Sullenger 

Simeon Warner 

Mike Gorrell 

Kirstin Kemner-Heek 

dracine 

Marko Knepper 

Maike Osters 

Hkaplanian 

Ian Ibbotson (Use this one) 

Tom Cramer 

Kathleen Berry 


Guests: Maccabee Levine; (TC rep) Jesse Koennecke (PC rep); Christopher Spalding (new CC member); Ian Walls (ByWater)


Discussion items

ItemWhoNotes
Treasurers ReportPaula Sullenger 

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
Onboarding new CC membersMike Gorrell 

New on CC from July: Christopher Spalding , Edwin Pretz , terms ending: Hkaplanian , keven lw , Leander Seige (2023 Community Council Election)

  • next week: change in chairs to be open for discussion
FOLIO SMLLC Manager roleSimeon Warner 

dracine has graciously agreed to continue for a while but we should identify a new FOLIO SMLLC Manager

  • Jesse Koennecke volunteered to become FOLIO manager and was accepted by CC
Renewing Community Support Volunteers group

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
FY24 Budget Planning – TC and PC suggestions for spending

See 2023-05-22 Meeting notes where we decided to follow up with more discussion, and 2023-06-12 Meeting notes when postponed.

Amount available:   Paula?

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. 


Ongoing programs/subscriptions

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

  • 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)

  • Privacy assessment working with Privacy SIG (TC)

  • Github actions migration (TC)

  • Innovation grant (TC)


Other Business
Release Management Stakeholders Group - meets every other Monday at 9am Esatern: 2023-06-26 Release Management Stakeholder group
  • No labels