Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FUND] Preconfigured, easy to install package for testing and documentation purposes #5968

Open
Erikmitk opened this issue Mar 1, 2024 · 2 comments
Labels
development fund 2024 A candidate for the Kitodo e.V. development fund.

Comments

@Erikmitk
Copy link
Member

Erikmitk commented Mar 1, 2024

Description

To facilitate software testing for new releases, we need a flexible test environment. This environment should include yet-to-be-defined sets of diverse sample projects, processes, workflows, configurations and users. It must be reproducible, preconfigured, and easy to install. Additionally, it should support dynamic creation with parametrizable software versions, allowing configuration of specific development versions of Kitodo.Production such as tags or branches. Furthermore, comprehensive documentation is essential to ensure the usefulness of this environment.

Related Issues

A prerequisite for this is the definition of baseline functionality and standardized sets of sample data by the Community Board.

Expected Benefits of this Development

By establishing a standardized environment, developers and release managers can communicate changes more effectively. Having a preconfigured version of Kitodo.Production simplifies testing for those new to the software. This benefits developers, release managers, and anyone looking to explore or test Kitodo.Production.

In the long run, this environment could serve as the foundation for testing Kitodo.Production's core features. By automating testing against this baseline, it cuts down on the need for manual testing. This means institutions can concentrate on their own customizations, confident that the established environment always works reliably. Moreover, the documentation provided for users can be done via this environment, ensuring seamless integration of software and documentation independent from the institution that is using it.

Estimated Costs and Complexity

I estimate the cost as medium as there are already unofficial prototypical solutions (https://github.com/slub/kitodo-production-docker).

@Erikmitk Erikmitk added the development fund 2023 A candidate for the Kitodo e.V. development fund. label Mar 1, 2024
@Erikmitk
Copy link
Member Author

Erikmitk commented Mar 1, 2024

@solth Can you change the label to 2024? I used the issue template and that contains the wrong year. :)

@solth solth added development fund 2024 A candidate for the Kitodo e.V. development fund. and removed development fund 2023 A candidate for the Kitodo e.V. development fund. labels Mar 1, 2024
@solth
Copy link
Member

solth commented Mar 18, 2024

Votes: 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development fund 2024 A candidate for the Kitodo e.V. development fund.
Projects
None yet
Development

No branches or pull requests

2 participants