Current situation
Currently we have a OCR-D Organization in GitHub with 55 Repositories.
Most important part seems to be ocr-d all, ocr-d core, specs als documentation.
How it should be
It must be clearly defined which code is to be part of the product, which is to be made available for a long time. Based on this, we can then decide in which way the code should be made available and whether changes are still required to meet the criteria for a sustainable product.
Current situation Currently we have a OCR-D Organization in GitHub with 55 Repositories. Most important part seems to be ocr-d all, ocr-d core, specs als documentation.
How it should be It must be clearly defined which code is to be part of the product, which is to be made available for a long time. Based on this, we can then decide in which way the code should be made available and whether changes are still required to meet the criteria for a sustainable product.
Steps
[ ] Finalize product definition. Basis: Product definition from Clemens: https://hackmd.io/@cneud/ry8DhFqGq
[ ] Present the product definition to the ocr-d community to generate commitment
[ ] Discuss how we can communicate the product to the community
[ ] prepare the presentation of the product draft and the challenges for the Beiratssitzung
[ ] [How to make the product visible to OCR-D users?