| Decision | Status | Stakeholders | Outcome | Created date | Owner |
|---|---|---|---|---|---|
| Tenant Id and Module Name Restrictions | IN PROGRESS | ||||
| Handle i18n where messages are generated | DECIDED | Back-end modules should handle i18n/l10n of messages provided in responses given a locale preference received in a request, e.g. an Accept-Languages HTTP header. | |||
| Karate API Integration Tests Implementation Guidelines | DONE | All BE developers |
| ||
| Migration of Static Permissions Upon Upgrade | DONE | Static permission removal will use a soft delete to accommodate module downgrades |
| ||
| Back End Module Health Check Protocol | DONE | Back End Developers, System Operators | All back end modules included in 2021 R2 or later must provide a health check endpoint |
| Marc Johnson Oleksandr Dekin (for Spring Way implementation guidance) |
| Check Out Performance | IN PROGRESS | <at-mentions> | <the decision> |
| <at-mention someone> |
| FOLIO secrets management | ON PAUSE | All developers, SysOps, Hosting providers |
| ||
| Localization parameter for back-end | DECIDED | All back-end module developers |
| 2021-06-09 | |
| Deletion of core-module records may leave dangling references from non-core modules | COMPLETE | Front-end and back-end devs of non-core modules that hold references to records in core-modules | UI modules |
| |
| Data consistency and message driven approach | IN PROGRESS | Front-end and back-end devs who meet issues with data consistency |
| ||
| S3/MinIO | IN PROGRESS | Technical Leads, Developers | How to use external object storage |
| |
| FOLIO should define a minimal platform | IN PROGRESS | A "platform-minimal" should be defined which constitutes the absolute bare-minimum set of modules needed to run FOLIO |
| ||
| System and Tenant-level Users | IN PROGRESS | Developers, SysOps, Hosting providers | TBD |
| Jakub Skoczen Mikhail Fokanov |
| How to improve/simplify release proces? | IN PROGRESS | Tech leads | Process changes and tooling to simplify the release process |
| |
| Teams must document deployment requirements in a clear & consistent way | COMPLETE | All developers, SysOps, Hosting providers | Teams must document deployment requirements in a clear & consistent way |
| Craig McNally |
| Apache Kafka usage in inventory-storage | DONE | Apache Kafka will be used directly in inventory-storage as a special case |
| ||
| Teams to implement UI end to end integration tests | NOT STARTED | ||||
| Data export by using Spring Batch (aka Export Manager) | DONE | All the new Data export features should be implemented by using this approach |
| ||
| Use of Testcontainers for test infrastructure | COMPLETE | All developers | The project is embracing the adoption of using testcontainers for integration test infrastructure. |
| Craig McNally |
| Spring Way Equivalent of Edge-common | DONE | Edge API developers | Create a spring way equivalent/port of edge-common, and pull share/common classes/utils into an edge-api-utils library which can be used from both edge-common and the spring way equivalent (edge-common-spring). |
| |
| Optimistic locking support | DONE | Platform team members, interested Tech Leads | Platform team would like to pursue Option 2 of the proposal covered in
| ||
| Optimistic locking support | DONE | Platform team members, interested Tech Leads | Platform team would like to pursue Option 2 of the proposal covered in
| ||
| Should build (pom.xml) changes required by new RMB be considered breaking? | DONE | Build changes (new RMB Maven plugin) will be released as new major RMB release (v33) |
| Jakub Skoczen | |
| Pull Request Guidelines | DONE | All developers | Agreed |
| |
| How to coordinate introducing API compatibility breaking changes? | IN PROGRESS | Tech leads | Process on how the teams should communicate and introduce API breaking changes |
| |
| Log4j2 is the recommended logging library for all core java modules | DONE | Jakub Skoczen Adam Dickmeiss Mikhail Fokanov Taras Spashchenko Teams Leads | It is recommended to move away from Vert.x logger and adopt log4j2 instead for for all core java modules. | ||
| Personal Data Disclosure Process | DONE | All modules must have a completed PERSONAL_DATA_DISCLOSURE.md file at the top-level of their GitHub repository. |
| ||
| Include instance id in the inventory-storage notifications for items | DONE | Instance_id should be added to inventory-storage update notifications for items |
| ||
| UI Testing approach | DONE |
| |||
| Upgrade to JDK 11 | DONE |
|
Additionally, consider the following tickets in JIRA with a "decision" label:
Decision Template
Copy/Paste this snippet into your design documents to log a decision. N.B. Don't forget to also add the "decisions" label to your page so the decisions will also appear above in this aggregated list.