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

Roles and responsibilities

Role	Responsibilities

Role	Responsibilities
PO	Defines initial user stories and identifies scope Get approval from Spring Force development team & architect for proposed scope Reviews user stories with the team to ensure their completeness and correctness Clarifies requirements before and during development process; provides applicable screenshots and mockups Provides well understood acceptance criteria in each user story Reviews the implementation and if it aligns with acceptance criteria sets user story/bug to Done Note: The work that is only available on a local machine cannot be accepted and user story/bug cannot be closed. Returns user story/bug to In Progress status if an issue is noted
Development team	Work on tech solutions for new features, present to the team and architects to get approval Add missing user stories, bugs and back-end stories on behalf of PO Review and estimate user stories; decide on best approach to turn user stories into working software Develop, code review and test user stories (locally and on test envs) to make sure the acceptance criteria and DoD are met Inform the team about any issues/blockers preventing the team from completing the sprint successfully Help to facilitate Scrum Ceremonies if necessary
Coordinator	Schedules and facilitates Scrum Ceremonies and any ad-hoc meetings Makes sure the process is transparent and Scrum Artifacts available and up-to-date Performs planning based on team’s empirical data Promotes best practices to be applied Analyzes team’s metrics to improve processes and efficiency of the team Provides updates/reports on current status and any risks/impediments known/expected
Solution architect	Provide solution governance Review spikes and results of team investigation for areas with low level of confidence Promotes best development practices to be applied

Tools and instruments for working with Spring

Idea

Eclipse

Maven

Put links to Spring tutorials, Spring-boot tutorials

Questions

1) How to support of OpenAPI at Spring at the same way as at Vert.x? How to support different languages in scope of OpenAPI?

Spring Force

Spring Force Charter

Communication channel

Artifacts

Repo

Templates

Jira project

Jira board

Goal

Scope

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

What could be added to folio-spring-base library

How to contribute to folio-spring-base library

Who is involved?

Base team

Deputy team

Roles and responsibilities

Tools and instruments for working with Spring

Questions

Related content