...

The PC will track new app submissions that result in new module(s) via a wiki page: Functionality Evaluated by the PC. A recommended timeline for the PC review is 2 weeks. Status updates will appear on the wiki page, including the final decision of the Product Council. This review can occur prior to coding work being completed, so it doesn’t have to extend the development timeline. A PC representative will be in touch with the contributors with the results of the review. The PC may recommend follow-up conversations and put the contributors in touch with the appropriate SIGs. The PC can also help proposals by recruiting subject matter experts to create a new SIG or working group that can support development work, as appropriate. When the module(s) are ready for Technical Council review, the contributors can submit their ticket to have the module(s) reviewed via Jira. The Product Council will indicate by comment that they support inclusion of the new module(s. The TC can verify the PC has reviewed and approved the module by checking on the Functionality Evaluated by the PC page and reach out to the PC for a review. The PC will also reach out to the CC regarding the potential of an MOU (see below). If a new module is purely of a technical nature, the Product Council will indicate in Jira that no PC review is needed. Although the steps are listed sequentially in the diagram, they can happen concurrently to speed the evaluation process.

MOU and Next Steps

Once the module(s) are approved by the Technical Council, the module contributors will need to reach out to The PC will facilitate communication between the module contributors and the Community Council, who will, at their option, supply an MOU detailing their commitment. The FOLIO SMLLC will supply MOU and store the final results. The Community Council will manage the renewal of the MOUs as appropriate.