Attendees
Guests: Andre Schueller-Zwierlein Jesse Koennecke Rachel Fadlon
Discussion items
| Item | Who | Notes |
|---|
| Recap last week's meeting and Retrospective | | Reviewed financial situation: Bottom line is we are good for this FY. Ideally we can grow revenue (member subscriptions) so that we can fund more activity. Retrospective: - Several things that have gone well over the last 8 months:
- We were able to create an organization separate from OLE with 3 councils and a treasurer and it’s up and running.
- We had successful Elections
- We did a successful membership campaign
- We are continuing to define and clarify CC’s role in our community
- The CC has been “pretty” engaged
- Taken strides towards setting up regular communications with the community
- We’ve laid the foundation for regular processes - we’ve started a lot of stuff
- Able to live within our budget and pay our bills
- Things that could be improved:
- Participation in this group is not as even as it could be amongst members
- We haven’t finished a lot of things
- We could have more open community members participating in the council’s meetings and activities
- We need more direct communications with member organizations (examples - not communicated to Texas A&M’s interim Dean, not communicated with chinese members/prospects)
- CC tends to be more reactive than proactive; we have a big gap with being able to have individuals and/or groups champion communication and speak/represent FOLIO proactively.
- We need more people doing things
- We are not, in general, seeing more community development contributions - in fact may have decreased
- Is there a “FOLIO fatigue” for developers and others?
- We should have more balance amongst organizations contributing development; more than EBSCO
- We could have a better argument for membership
- We should spend more time doing the projects and less time with governance and other matters
- Possible to enhance the membership/operation model is to have development support for specific modules
- Actions:
- Develop an articulated framework for maintenance
- Craft the membership drive this year around our actual needs (i.e. specific roles, costs, etc.)
- Review and redesign the MoUs to be more reflective of our current needs
- Define which costs should be “FOLIO” costs and which things should we strategically define as contributed - a theory of resourcing and how it is applied.
- Should we consider hiring someone professional to raise funding?
- Can we define more roles defined within the CC rather than everything being volunteer-based or delegated to subgroups.
- Review the FOLIO Manager definition (single person vs group)
|
| Roadmap from Product Council | | Present PC's Roadmap - https://docs.google.com/spreadsheets/d/1e0ydj6vcjKNGFBdit0X4FioLmV9z6XgubOfwN2h_ZfE/edit#gid=2142006984
-
| type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
- Discussion
- Harry: great work - are orphaned applications considered as well?
- Could be a roadmap theme - but due to "cone of uncertainty" its unclear, who will pick that up
- Visualisation to produce overviews about topics that are addressed / not addressed
- Filtering process
- Ian I.: great agreement - this was asked out of different contexts!
- Roadmap could be used for necessary gap analysis as base for libraries
- And full overview for customers view, support RFP
- Advantage: overarching language - addresses functional and technical people
- Dracine: documentation and its versioning in it could work to help gaining overview
- Mike: How can people participate in this process to drive the discussion forward?
- Please comment in the document
- Maybe simplyfied view on document could be a goal
- Kirstin: use document for review purposes on a regular base - gain overview and direct resources
|
| OLF Board Seat Nominee | | Annually the OLF selects a Roundtable Representative to the OLF Board of Directors for a one year term. Paula Sullenger filled that role last year and would like to do so again. Are there any objections to nominating Paula again this year? - CC agrees!
Details of this Roundtable Representative
|
| Membership Drive | | Review Calendar, proposed plans and existing thoughts Proposed specific efforts: - Letter to existing Members to be sent in early February
- Letter to orgs active in FOLIO but not yet members - to be sent in early February
- Letter to orgs who signed up for the FOLIO Newsletter but who have not yet shown up in the community
Thoughts? - Agreement on sending 3 letters to address the different key groups
- Be more specific about the needs?
- Harry: start with "thankyou", add more information what was done with the money, and then add specific needs
- Dracine and Boaz added a document:
- Harry: mention much more innovative projects of FOLIO and things that have been done
- large number of EBSCO customer libraries are looking at EBSCO being their sustainable vendor in the project
- Please add more comments!
|
| Web Site review | | Proposed outline, some of proposed text - Hearing back from EBSCO design team → Rachel
- Please review the documents
|
| Information - any questions? |
|
|
| | February 11th @ 10:00am Eastern - agenda: - CC update - 12 minutes (MDG)
- PC Update - 12 minutes (Jesse/Kristin)
- TC update - 12 minutes (Craig/Jeremy)
- WOLFcon update - 12 minutes (MDG)
- FOLIO.ORG Website update - 12 minutes (MDG)
- Invitation goes out today
- Announce new web side
|
- LTS Discussion is happening
| | |