Package reorganization for publication

[glopesdev]

Now that we are starting to consolidate the different components of the aeon_mecha API it would be great to start discussing how we would publish these different components in a public package manager like PyPI.

My current feeling is there are potentially three levels of components which are relatively independent and which could be included in separate packages. I propose a name and broad description below:

• aeon-api (the low-level API)
• aeon-datajoint (the DJ ingestion pipeline)
• aeon-analysis (any reusable analysis utilities)

Would be useful to get feedback on this as we prepare to publish the platform paper and more broadly disseminate these tools, it would really help a lot the adoption if the different components could be installed independently.

[glopesdev]

@jkbhagatio we had a brief discussion today on this and one idea which came up is to make aeon_mecha an aggregator of either submodules or other packages, and identify reusable modules which could be moved to a different repo, e.g. the low-level API and modules like io, utils, etc.

My original proposal of generating multiple packages directly from aeon_mecha might require this separation into multiple repos since pip and build tools I believe always generate a single project from the pyproject.toml file.

Examples of other projects with similar organization:

• https://github.com/brainglobe
• https://github.com/openstack/openstack