start apex-python-tools repo

[jdries]

bootstrap new open source python project in this github org.

Minimal functionality to start with:

• a data class for an APEx algorithm
• an 'algorithm repo' class that allows to fetch the algorithms (from the repo, can even be hardcoded)

General design docs: https://jdries-vito.quarto.pub/apex-design/algorithm_hosting.html

[soxofaan]

package name (e.g. for users to import in their code)?

• esa_apex
• apexeo
• esa_plaza
• esa_application_hub
• esa_app_hub
• apexhub
• esa_portal
• apex_portal

Should it include "esa" or not? Should it include "apex" or not?

[soxofaan]

Created repo at https://github.com/ESA-APEx/esa-apex-toolbox-python with a package that users can import with import esa_apex_toolbox
Note I went very generic with this naming just to have something to work from. Naming should probably be finetuned later, after feedback of ESA for example

[soxofaan]

• initial data class for an APEx algorithm -> e.g. https://github.com/ESA-APEx/esa-apex-toolbox-python/blob/4f022b6a3a73937f3a8ec47eae9c858a0bef1032/tests/test_algorithms.py#L174-L180
• initial 'algorithm repo' class that allows to fetch the algorithms (from the repo, can even be hardcoded) -> e.g. https://github.com/ESA-APEx/esa-apex-toolbox-python/blob/4f022b6a3a73937f3a8ec47eae9c858a0bef1032/tests/test_algorithms.py#L201-L208

[soxofaan]

to summarize the naming issue, current situation:

• esa-apex-toolbox-python repo name
• esa-apex-toolbox to pip install
• esa_apex_toolbox to import

[soxofaan]

feedback to finetune naming will be received later this week

[soxofaan]

I think we can close this ticket for now (especially given next step #15)