Further development on OxGarage
TEIGarage and MEIGarage
Anne Ferger, Daniel Röwenstrunk, Peter Stadler | Universität Paderborn
Slides: anneferger.github.io/MEITEIGarage/further_development_OxGarage/
Motivation
Main Goal
MEIGarage next to the (TEI-)OxGarage with further/different functionality, but the same core (concept, code), while also allowing for updates or bugfixes to the core
Starting Point
- TEIC/oxgarage and Edirom/oxgarage (MEI, fork of OxGarage, branch ‘meigarage’)
- fork of OxGarage was not a perfect solution: problems with harmonizing core changes and new functionality, maintenance
Further Goals
- sustainability of the OxGarage software
- further functionality that can be used by other projects as well (e.g. customization in mei)
- other communities and use cases
Modularization
Modularization
- modularization of code repo
- extracting different parts/modules to their own git repositories while keeping the (git) history of only those parts
- storing artifacts of the modules in GitHub directly
- allowing for merging of bugfixing and further functionality, but not configuration
➞ facilitate development on specific parts only
Structure
Location of the different modules
- Git repositories are located at the TEIC or Edirom Github organizations respectively
- MEIGarage and TEIGarage code structure
Simplification of configuration project
OxGarage to TEIGarage and MEIGarage
- each different use case of the OxGarage needs its own configuration project
- to distinguish from OxGarage: new names TEIGarage and MEIGarage
- Docker images for each of the projects, GUI/webclient can be added
- adaption to other use cases is facilitated
Further development of functionality
From the MEI perspective, useful for TEI community as well
- recognizers for different files (could be useful for other use cases as well)
- simplification of configuration module
- update of dependencies
- supplying stylesheets for conversions in Dockerimage