Spring Force Charter

Spring Force Charter

Communication channel

#spring-force Private slack channel

#folio-spring-base Public slack channel 

Artifacts

Repo

https://github.com/folio-org/folio-spring-support

https://github.com/folio-org/edge-common-spring

https://github.com/folio-org/edge-api-utils

https://github.com/folio-org/mod-spring-template

Templates

 https://github.com/folio-org/mod-spring-template

Jira project 

https://folio-org.atlassian.net/projects/FOLSPRINGB

Jira board

https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=196

Goal

Maintain project and support features that implemented with Spring framework

Scope

What should not be added to folio-spring-base library

Not to make library heavy. All additional dependency should be moved to business logic modules. Should not introduce duplicated features provided by spring.

What could be added to folio-spring-base library

Standard OKAPI headers to extract UserID

Support for CQL query transformation to jpa criteria

Folio execution context

How to contribute to folio-spring-base library

Create separate Jira ticket and describe required changes. Then assign ticket to PO and team lead to further review.

Who is involved?











Workload, h per sprint

Product Owner

Jakub Skoczen

jakub@indexdata.dk



Coordinator

Oleksii Petrenko

Oleksii_Petrenko1@epam.com



Architect



Viktor Gema

viktor_gema@epam.com



Architect

Viachaslau Khandramai

viachaslau_khandramai@epam.com



Base team

Spitfire

Pavlo Smahin

pavlo_smahin@epam.com



Deputy team

Folijet









Firebird









Vega

Oleksandr Kurash

oleksandr_kurash@epam.com



Volaris

Pavel Filippov

pavel_filippov@epam.com



Leipzig









Eureka

Dmytro Tkachenko

dmytro_tkachenko@epam.com