ID | High Level Goal | Description | Ideas for Specific Actions (by X date PC will accomplish Y) | Impacted Subgroups | Relevant Dates | Reference from WOLFCon | Notes |
|---|---|---|---|---|---|---|---|
1 | Revive Community Development | Establish plan to establish models for coordination, funding, and maintenance of community-driven development | would likely need a dedicated subgroup | Quarterly Tri-Council meetings Trillium R2 2025 release scope composition deadline September 2025 - WOLFCon / Umbrellaleaf scope composition (anticipated) | https://easyretro.io/publicboard/0ALmBRbRDFgKpGdILQIAZio6Nvq1/1fbb30b4-8f05-4841-8076-f25dfa8d8cbc | ||
2 | Solicit & analyze community priorities | Define an ongoing process to capture priorities at the SIG, community, and implementing institution level and communicate them back out to the community in an easy to understand, actionable format. | By mid November:
By mid December:
By end of January:
Repeat cycle for Umbrellaleaf scope deadline (assuming this will happen around September) | Quarterly Tri-Council meetings Community Updates Trillium R2 2025 release scope composition deadline September 2025 - WOLFCon / Umbrellaleaf scope composition (anticipated) | Better understanding of what implementers are satisfied with / gaps Help institutions know about each others' plans Ensure investments maximize community value Connect development partners Potential Assessment Subgroup Implement SIG Prioritization Linked data interoperability “What is reporting in FOLIO?..” | ||
3 | Communicate Development priorities and activity to the community | Update existing dashboards and work with POs and SIG conveners to standardize representation of desired and planned development in UXPROD in order to create new dashboards that better reflect scheduled and planned and unscheduled development work. | By mid November:
By mid December:
By end of January:
Repeat cycle for Umbrellaleaf scope deadline (assuming this will happen around September) | Create dashboards Support standardization to improve reporting | |||
4 | Update PC Review Process | Transition from reviewing at the point of scheduling for release, to reviewing at the point of ideation | By end of February, begin scheduling topics for PC meetings based on new functionality surfaced by updated dashboards in #3 | Enhancements & Improvements Subgroup | Re-charge Enhancements & Improvements Subgroup Schedule out PC work Proactively find out about new / planned modules Evaluate Evaluation of New functionality subgroup | ||
5 | Engage with App Formalization | Consult on fixed vs variable functionality
| At the point of review, recommend app as core or extended. Review existing apps and recommend core vs extended (who ultimately decides this?) | would likely need a dedicated subgroup “What is reporting in FOLIO?..” Linked data interoperability | Functional and architectural vision Actively contribute to shaping FOLIO as a product Define standards for cross functional features within core apps (e.g. notes, tags, in app search, accessibility, app interaction / performance considerations) | ||
6 | Develop leadership opportunities within the community | Conduct outreach to implementers to help fill in vacant community roles | Support the community in finding “staff” | ||||
7 | Recommend cross-platform standardization | Develop recommendations for standardizing cross platform functionality that often varies from app to app (search, pop-ups, etc) | Linked data interoperability | Added after reviewing notes from WOLFCon - this was not reflected in the retro |
...