Page Comparison

• Sent out reminders to the institutions who have not yet paid
• Two more checks have come in
• Checking on one payment that didn't land in the right account
• The TC will review the AWS charges to see if we need everything we're paying for
  • EBSCO had underwritten the bill so far
• Budget  plans will be built on the results
• 4 MOU's still to be signed

Trying to get Juniper released by next week - have lots of unclaimed "smoke tests" due this week... please for help. Messages going out to #general and #folio-implementers

• Juniper release will be at risk if no more testers can be found
• Action item: please reach out to your institutions and ask for volunteers!
  • Volunteers might want to reach out to Anton!

An update on the FOLIO Code of Conduct and a request for consideration of funding for the Community Support Volunteers.

•     Ian Walls
•     Jenn Colt
•     Laura Daniels
•     Peter Murray
•     Sharon Wiles-Young
•     Stephanie Buck 
  
  
• Final version is out on the WIKI page
• Outstanding: follow up and maintenance
  • Group of community support volunteers to follow up any incident in community activities to prevent / stop any unwanted actions
  • Community Council for endorsing sanctions  (meaningful for empoyers as well)
  • Formal reports
• Feedback?
  • Costs for training?
    • 1000/2000 $ for the 6 members of the group - one day webinar with a special consultant
  • Has there been any questions to the group so far?
    • 1 person has asked 3 times to seek advice how to solve certain situations

 The Community Council has created the following subgroups and actions that are in process:

Grants Group

• Have identified grant opportunities
• Upcoming IMLS grant has a deadline of September 24, 2021 for grants to begin August 1, 2022
• We don't have clear communication channels to use. NEXT STEPS: See the Communications Channels topic

New Members Group

• • New members group already drafted a few questions 
  • Organize an offline review in "Discuss"  (Peter will set up a demo for Discuss)  and involve the PC  - (Harry)

1. Discuss forming a team that can reach out to networks and libraries to ask what would make membership worthwhile to them.

• • NEXT STEP - setup a subgroup of librarians, network people : (Kirstin), Simeon, Boaz - need X more volunteers
  • Reach out to next weeks PC to recruit more people

2. Start a discussion with library IT to build a list of concerns and needs that FOLIO must support for approval and adoption.

• • NEXT STEP: setup a subgroup of Technical people:  Ian Ibbotson, Mike G. volunteered - need X More volunteers

Goals and Objectives reviews

• We reviewed the project's list and identified which ones would be driven solely or partially by CC
• NEXT STEP - review list and identify FY22 goals
• Review in Discuss   (Mike G.)

FOLIO WOLFcon planning

• Discussed need for planning well in advance  
• NEXT STEP: form a WOLFcon Planning group. Mike has reached out to PC/TC chairs to have the topic raised at their next meeting. Also asked on the #general channel for planning committee volunteers. He's volunteered to lead the FOLIO WOLFcon Planning Group
  • Meeting this week
  • Built up a FOLIO calenda / agenda 
  • Kathleen, Boaz volunteered

Communication channels

• We have Constant Contact list that is added to when people register for community updates on folio.org
• We have mailing lists as seen at https://ole-lists.openlibraryfoundation.org/ that are self-managed (mostly)
• We have Slack, Twitter and Website(s)
• We don't have a consistent plan for how and when to use each of these
• NEXT STEP: Form a subgroup to map out how each of these may be used. Mike, Tom and Rachel have volunteered

Meeting times and other collaboration protocols

• Given the growing international presence and desire for global engagement we need to rethink some of the initial standard patterns that the project adopted in terms of how decisions get made (in meetings where people are present) and meeting times (typically early New York/Eastern Time).
• Raised the question about how we collaborate and make decisions; can we be more asynchronous; can the Discuss tool be more useful
• A Subgroup was formed to generate ideas
• NEXT STEPS:
  • Explore whether DISCUSS Can use the same authentication as Jira/Wiki - NOT AT THIS TIME
  • setup a DISCUSS conversation on this conversation as a trial
  • Document other potential standards for Councils/SIGs to consider adopting

Onboarding

• Discussed how important this is.
• Did a CC session for the onboarding video series

• NEXT STEPS: Determine what actions are necessary/make sense
• How to address different needs for different people in the onboarding process (Governance, SIG's, developers, PO's ...)?
• Volunteers: Kathleen, ...

• Welcoming commitee - e.g. sub group for this purpose
  • Setup from all parts of the project
  • Additionally mentorship model to accopany newcomers
    • sub group to find the right experienced partner for them
    • different needs - see above
    • Onboarding takes time! 
    • What is the Koha community doing? Or Linux
• Next Steps: 
  • Gain input from TC / PC  in regard to found that group
  • Volunteers: Keven, ...