2022-08-31 Meeting notes (at WOLFcon with remote)

Introductions (if necessary)

Discussion - What FOLIO activities should be funded centrally through member dues?

Mike/Simeon/ all

ebsco funds go to hosting.

Paula has the final account.

OLF has a reserve fund, and Paula suggests that we also have one. Suggests we start with a 3 month reserve, with a goal towards 6.

Membership dues are coming in, will compile August funding when returns home.

Kirstin suggests that there is reserves for Wolfcon, so that there can be funds on hand for unexpected circumstances. Could OLF set this money aside or should FOLIO?

Funding:

• AWS costs

• One developer

• github, testrail, equinix

What should we consider funding?

• Documentation

• More developers

• team that is responsible for raising/coordinating resources

  • a contact point to help institutions get involved, show them how they can contribute

  • Actively reaching out to our members

  • track our needs, and take action to fill them

  • individuals from invested institutions and vendors as they are committed

• Samvera - community manager (this could be a model to consider)

  • Tom points out that this role is common in open source US projects

  • A person to hold the project overview- match maker and consensus builder

  • We'd have to manage position carefully so they don't get all the problems and work dumped on them

  • Ian I: a "reality check" for teams- make sure that groups are accountable for thinking through their testing, documentation, instead of making it others (or their) problem

  • Tom: no one person can solve our organizational problems. We need to review and address these before. identify levers are available to get things done.

• Fundraising manager

• Ian W: Koha elects a "release manager" That sets the goal for the release and then manages the work to achieve the release

Future work for this group:

Other updates