Attendees
Ian Ibbotson (Use this one)(notes)
- Former user (Deleted)
- Hkaplanian
- Ian Walls
- Kathleen Berry
- keven lw
- Kirstin Kemner-Heek
- Marko Knepper
- Simeon Warner
- Tom Cramer
- Boaz Nadav Manes
Discussion items
Item | Who | Notes |
---|---|---|
AWS Credits | Per Peter Murray: New news! AWS granted us a $62k in credits as part of their Open Source support program. In case you don't know, this is the second year I've applied for AWS credits on behalf of the FOLIO project. Details in |
How does this affect our budget? --- MDG reported AWS USD62K credits for the project II: Are the AWS credits usable for reserved instances or only for on-demand. MDG to find out. HK: What's the progress on tagging in AWS and more granular costs. MDG will link up with TC and report back. | ||
WOLFcon Planning update | Review the discussions and current plans for FOLIO at WOLFcon 2022, get feedback from CC. MDG updated on venu - Bucerius law school. The date needs to push back to fit with dates available to the venue. new date 31st Sept. For FOLIO needs - see google doc above for details. KKH: Does the CC need to plan some meetings to curate an agenda or structure well ahead of time to encourage attendance and structure the outcome. DH: Will there be an OLF round table? TC: Conference will be Worldwide - and conversations about content design for timezones are ongoing. Discussions about asynchronous broadcast options are ongoing. DH: Lets coordinate a tri-council meeting for the conference HK: Conference is important as a way to rebuild working relationships. Lets organise an in person meeting - Budget discussions KKH: Lets bring together communities that don't often get face to face time - Technical folks and library staff. II: Can we propose an innovation lab (TC) or find other ways to curate conversations that gets technical folks talking to library staff. BN: Future vision conversations? | |
Guidelines for Private Slack channels | Propose the following guidelines: FOLIO is an open project and transparent discourse and decision making is the foundation of a trusting and collaborative community. Many conversations and project decisions are made using the group-chat tool Slack. This is why the default for Slack channels is to be public. However, the community council recognizes that there are situations in which a private channel is appropriate - a channel that's intended for "internal" conversations of a team, or a topic that needs more development before being exposed to the rest of the community, or other financial or sensitive topics. This is why Private channels are allowed. The recommendation of the FOLIO Community Council is that the default in creating a Slack channel is to have it be Public, but allow for the creator of the channel to use their discretion to make it private if that is appropriate. Since this is the current default, the only action 'required' would be to communicate this to the #general #folio-product-council #tech-council and #folio-community-council channels. | |
Upcoming Topics: | Update on Web site Journey Map |