FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix
JIRA project | Team | Product Owner | Dev Lead/Contact | First Release | Module | BE Framework | Tests repository | DB Usage | Kafka Usage | Platform(Eureka/OKAPI) | ECS(Central/Member/All)/NonECS/Both | Application Sunflower | Application Trillium |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
@Tim Auger | @Alexander Kurash |
| Vert.x |
|
|
|
|
| app-platform-complete |
|
| |||
@Tim Auger | @Alexander Kurash |
| RMB |
| Y |
|
|
| app-platform-complete |
|
| |||
Spring Force |
| @Siarhei Charniak |
| N/A |
|
|
|
|
| ? |
|
| ||
Spring Force |
| @Siarhei Charniak |
| N/A |
|
|
|
|
| ? |
|
| ||
@Jakub Skoczen | @Julian Ladisch |
| Vert.x |
|
|
|
|
|
|
| ||||
@Charlotte Whitt | @Niels Erik Nielsen |
| Vert.x |
|
| N |
|
|
|
| ||||
@Ryan Taylor | @Vijay Gopalakrishnan | Ramsons (R2 2024) | Spring |
|
|
|
|
| app-edge-complete |
|
| |||
EDGUSERS | @Ryan Taylor | @Vijay Gopalakrishnan | Ramsons (R2 2024) | Spring |
|
|
|
|
| ? |
|
| ||
EDGINVENTORY | @Ryan Taylor | @Vijay Gopalakrishnan | Ramsons (R2 2024) | Spring |
|
|
|
|
| ? |
|
| ||
@Tim Auger | @Alexander Kurash |
| Spring |
|
|
|
|
| app-edge-complete |
|
| |||
@Tim Auger | @Alexander Kurash |
| Spring |
|
|
|
|
| app-edge-complete |
|
| |||
@Tim Auger | @Alexander Kurash | Quesnelia (R1 2024) | Spring |
| N | N |
|
| app-dcb |
|
| |||
Athena | @Corrie Hutchinson | @Bobby Sharp | Poppy (R2 2023) | edge-fqm | Spring |
| N | N |
|
| app-edge-complete | app-fqm |
| |
@Tim Auger(Lead) | @Alexander Kurash |
| edge-inn-reach | Spring |
|
|
|
|
| app-in-reach |
|
| ||
@Charlotte Whitt | @Kurt Nordstrom |
| Vert.x |
|
|
|
|
| To be deprecated | To be deprecated |
| |||
FSE | TBD | @Michelle Suranofsky |
| Vert.x |
|
|
|
|
| app-edge-complete |
|
| ||
Athena | @Christine Schultz | @Viachaslau Khandramai |
| Vert.x |
|
|
|
|
| app-oai-pmh |
|
| ||
@Joseph Reimers | @Serhii_Nosko |
| Vert.x |
|
|
|
|
| app-edge-complete |
|
| |||
@Tim Auger | @Alexander Kurash |
| Vert.x |
|
|
|
|
| app-edge-complete |
|
| |||
@Ryan Taylor | @Steve Ellis | Ramsons (R2 2024) | Vert.x |
|
|
|
|
| app-edge-complete |
|
| |||
@Ryan Taylor | @Vijay Gopalakrishnan | Ramsons (R2 2024) | Spring |
|
|
|
|
| app-edge-complete | app-acquisitions |
| |||
K-Int | @Owen Stephens | @Ethan Freestone |
| N/A |
|
|
|
|
| N/A |
|
| ||
K-Int | @Owen Stephens | @Ethan Freestone |
| N/A | Cypress tests: GitHub - folio-org/stripes-erm-testing |
|
|
|
| app-platform-complete | app-agreements |
| ||
K-Int | @Owen Stephens | @Ethan Freestone |
| N/A | Cypress tests: GitHub - folio-org/stripes-erm-testing |
Definition of core vs. complete:
Marc Johnson explained in as Slack thread following distinction/definition:
FOLIO systems (the set of modules included) can be defined as (what folks refers to as) platforms.
Core and complete are examples of platforms that the community has defined. They represent different configurations of FOLIO.Core is intended to be a fairly minimal set of modules (however it has grown over time). Complete is a superset of this that contains most (maybe all) of the modules that the project teams support.Most of the FOLIO environments folks use are based upon the complete platform, as are the regular distributions of FOLIO e.g. 2021 R1The reason it’s important in that list is that the FOLIO project teams use different release schedules for things that are in core vs. complete when we are preparing these regular distributions.I hope that helps, please feel free to ask follow up questions if that doesn’t make sense.