Attendees
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 FOLIO-3060. How does this affect our budget? | |
| WOLFcon Planning update | Review the discussions and current plans for FOLIO at WOLFcon 2022, get feedback from CC. | |
| 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 |