Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
“Once the module(s) are approved by the Technical Council, the module contributors will need to reach out to the Community Council, who will, at their option, supply the 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. “
Outstanding question from PC
How does the CC want to be informed about new modules and the state of the procedure?
CC review: after the TC approves it
Review the last year by CC as well (last one or two releases)
Follow up: how to review by CC → topic for next meeting
see process as an enhancement - not a “go / no go”
Mike will ensure the follow up, maybe we need a subgroup to get this done
Discussion:
@Kristin Martin notes that CC have not been involved in the approval process so far, do we want to be involved in future reviews? @Mike Gorrell asks whether there is a good part in the process. @Kristin Martin notes that there is a Jira and if the CC chairs get notified/included then can add to CC agenda
@Christopher Spalding: Suggestion that MOUs should be incleded in the repos of the code involved, demonstrating commitments