Release Process:
- CCDA service build complexity
- Suggestion: one-day freeze prior to patch release to merge security fixes?
Banner module:
- Have a mechanism to rapidly highlight the need to upgrade OpenEMR to get security fixes (possibly powered by an RSS feed or similar)
- Having a certified instance may need a up-to-date check to remain legally compliant
Docs:
- What can we do to best keep the wiki up to date? Does the wiki even make sense as the documentation mechanism these days?
Misc:
- Could one of the various security classes help set up automated scanning? Would be very beneficial for real-world knowledge for students and help the project
- Bootstrap UI update - basically imminent!
Action items:
- Figure out (async) who should own the update checking and banner module things being discussed. There’s a technical design side as well as implementation.
Next Week:
- Prescriptions issues after upgrading
- MySQL strict mode?
- Continue packaging/upgrading/runtime requirements discussion