Product Council Sub Groups

Group NameGoals(s)/CharterDate StartedTarget End DateNext Check-InExpected EffortOwnerMembersMeeting Time / LocationWiki
Release Management StakeholdersThe RMS defines FOLIO release schedules for named FOLIO releases as well as service packs that incorporate functionality specify and development milestones as specified by the development teams. The RMS announces the schedule and any changes to the FOLIO community, provides updates on development staffing changes and release status to the PC, TC, and CC. The release schedules are available on the wiki under Releases. The RMS makes determination for the release of a Critical Service Patch, using the process described here.

 




Oleksii Petrenko 
See wiki page for current membership.
Every other Monday, 9 AMFOLIO Release Management Stakeholders
Prioritization & Roadmap Subgroup

See wiki page for current charge

 



1-2 hours/week

See wiki page for current membership

Every other Wednesday, 9 AMFOLIO Prioritization & Roadmap Working Group
PC's support of FOLIO enhancements and improvementsTo be launched in late 2024




See wiki page for current membership
FOLIO Product Council Sub Group Supporting Enhancements and Improvements
Better Sample Data in FOLIO Test EnvironmentsInitial Meeting notes and Scope:  


Charlotte WhittSee wiki page for current membershipvariesBetter Sample Data in FOLIO Test Environments Working Group

Completed Groups

Group NameGoals(s)/CharterDate StartedTarget End DateNext Check-InExpected EffortOwnerMembersMeeting Time / LocationWiki
Re-architecting's impact on PC

https://folio-org.atlassian.net/wiki/x/3ZVb

Became a tri-council group under the Community Council





Jesse Koennecke See wiki page for current membership
FOLIO Product Council Sub Group on the Re-Architecting's Impact
PC Meeting Hygiene and EfficiencySee wiki page 


Alexis Manheimsee wiki page
FOLIO Product Council Sub Group Meeting Hygiene and Efficiency
Structuring SIG reports for the PCSee wiki page



Kristin MartinSee wiki page
FOLIO Product Council Sub Group Structuring SIG Reports
FOLIO Scope Criteria (cross council)
  • determine sustainable and trustworthy process to evaluate functional criteria for accepting new apps/modules into FOLIO
  • Should complement the technical criteria developed by TC
  • Define acceptance criteria for new code to be added:
    • Consistent with community goals
    • Provides desired functionality
    • Will be appropriately supported

Group officially disbanded 2022-09-21. Two new groups created to finalized work:

  • Functional Criteria for Accepting Modules
  • Proposed Vision for Future FOLIO Builds

 



1-2 hours/weekFridays, 8 AM

Cross App Data Synchronization


Representatives from App Interaction, TC, and PC will work on best practices for data synchronization solutions across apps

 


 


Marc Johnson Mondays, 9 AMCross-app data synchronization working group

Functional Criteria for Accepting Modules

The Functional Criteria for Accepting Modules group will determine a functional review process to complement the technical review process so developers today have a process and workflow to be able to have code be accepted into FOLIO. At present time (fall 2022) this means the modules will become part of a Flower Release.

 

 


1-2 hours/weekKristin Martin 

Capacity Planning

Charter needs to be rewritten/reconsidered: Capacity Planning has not had an elected member of the Product Council on it, and that seems odd.  In reformulating this into the release planning team, it would be good to address this.  (Two people that are on the capacity planning group now are also elected members of Technical Council.)  Sharon Wiles-Young, Martina Schildt, and Jesse Koennecke volunteered to sit in on the finalization of the group charter. See: 2022-03-24 Product Council Meeting Notes

Updates from 2022-08-25 Product Council Meeting notes, draft charter not approved, Hkaplanian to provide updated description on the Releases area of the wiki. Group renamed Release Planning Group to better reflect current responsibilities. Group is convened by Oleksii Maksymov to determine schedule for FOLIO releases.

Replaced by Release Management Stakeholders Groups





Hkaplanian Every other Monday, 9 AMFOLIO Release Management Stakeholders
Roadmap Subgroup
  • Update Roadmap to reflect current development priorities for FOLIO
  • Determine appropriate visualization for Roadmap
  • Connect feature development to roadmap priorities
  • Return annually to update Roadmap

 

 

1-2 hours/weekTuesdays, 9 AMFOLIO Roadmap
Priorities for FOLIO Development

With rankings in Jira no longer practical, how do participants provide priorities for development?

  • Environmental scan of other open source projects and products to support rankings and priorities input
  • Gathering SIG input
  • New ways for old "pointing" exercises

 


 

  



Prioritization process working group

FOLIO as an open source product: response to white paper
  • determine how to market FOLIO more successfully as a full-featured open source system
    • Response to white paper issues

 


 


Jesse Koennecke 

Proposed Vision for Future FOLIO Builds

This group will propose visions for future FOLIO builds, including:

  • Not just the architecture and software, but also roles & responsibilities
  • Pros, cons and consequences
  • As many interests as (reasonably) possible into account
  • Non-prescriptive guidance on how to achieve those builds

Group ended without deliverables.

 

 


1-2 hours/weekjulie.bickle 
Proposed vision(s) for future FOLIO builds
Input from the Global Community (Cross-Council)
  • Determine mechanisms to engage with the community across the entire world and global time zones
  • Come up with best practices for holdings meeting and getting input
  • Make sure members across the globe have ways of getting engaged.

Group never got started.

 




Mike Gorrell