SIG reports on activities & priorities
The Product Council seeks two types of regular input from FOLIO Special Interest Groups (SIGs):
(1) Quarterly activity report
Submit by editing this SIG report page
These are brief updates and can include info like meeting frequency or hiatus plans, changes to conveners, recent areas of focus or effort, etc.
A PC liaison in your SIG will provide reminders for upcoming report deadlines
NOTE: SIGs can always reach out to PC outside of this report cycle at any time when special topics or urgent needs arise. Communication between SIGs and PC are not constrained to these reports.
(2) Top 5 development priorities
Presented once per year by SIG conveners or designated SIG representatives at a PC meeting (and added to this PC wiki page)
A PC liaison will assist SIGs with adding their priority presentations to the PC agenda schedule
SIGs should dedicate meeting time to discuss and come to a consensus on the most urgent needs
Any identified development priority should (ideally) be represented by a thoroughly written Jira issue
For tips, see these PC guidelines for creating an effective Jira issue
NOTE: In addition to collecting information from SIGs, the Product Council will host a yearly forum for SIGs on these identified priorities. Watch for announcements and bring your questions/concerns!
How is this information used?
SIG priorities are compiled into a Community Priorities dashboard maintained by the PC for the entire community to use as a reference.
Along with the Community and Technical Councils, PC has a responsibility to ensure the general health and sustainability of the FOLIO project. Feedback from SIGs is crucial to maintaining a high level view of FOLIO functionality, especially when it comes to identifying gaps in that functionality and creating recommended roadmaps for development.
While the PC cannot (and should not!) direct all development decisions, we have an advisory role in the software release development process and we use SIG feedback to provide POs and developer teams with a more cohesive view of implementers’ most immediate needs. The hoped-for outcome is development efforts that are more targeted and intentional.