Questions and Decisions, Asking and Reaching

The first means of contact should always be to enter a Git issue.

However, deciding what repo to submit a Git issue in is not always straightforward.

If your question is about a particular text, submit the issue in the appropriate canonical repo. If the file or text is not yet on Github, the appropriate canonical repo is the repository that reflects the original language of the text. If there's not yet a canonical repository reflecting the original language of your text, please submit an issue in the perseids_docs repository.

If your question is about conversion routines to CTS and EpiDoc compliance, submit the issue in the tei-conversion-tools repo.

There are a number of projects in the Perseus ecosystem, many of which have Github repositories that also serve as pathways to communication. These include:

• The Open Philology Project, including repositories for Greek OCR.

• The Alpheios Project, including the Arethusa annotation environment.

• The Perseids Project, including the perseids_docs wiki of developer documentation.

• Capitains CTS services, including a Capitains.github.io publication of documentation.

• The Open Greek and Latin Project with more text and image data in various states.

Please don't hesitate to submit Git issues with questions, but also please perform due diligence to make sure your question or problem doesn't already exist. Whenever possible, please be general in your phrasing. For example, "textgroup X has Y problem", where Y problem isn't something in the tracking files, instead of submitting issues for Y problem for each text in textgroup X.

The final decision-maker for all markup questions is @lcerrato for Perseus Digital Library texts and @ThomasK81 for all Open Philology texts.

Please do be patient. Your issue may not be one that can be rapidly resolved.