Initial ideas for ecosystem from the working group

[TeresiaOlsson]

We discussed ideas for how an ecosystem could be started to be developed. For inspiration we looked at how it's done in the astropy project https://www.astropy.org/affiliated/index.html.

We said that modularity is important but it's important to keep the balance so it doesn't become too many packages to maintain.

One first step could to move the tuning tools to a separate application package. We discussed if there should be one repository per tuning tool but this is likely too much modularity and at least at this step. Maybe we first start to separate things and then over time the separation could be made further if a package grows to big.

We also discussed dependencies with the idea that the pyaml core package should not depend on any other packages but other packages should depend on the core. We also need to have a plan for in which order packages need to be updated if a modification is made to keep the compatibility.

Then we were looking at how this is done at Sirius https://indico.desy.de/event/43233/contributions/169377/ since they have an ecosystem for their packages. We were also discussing that perhaps a good test case for how the ecosystem could be used to integrate work done at different facilities is to try to see if we could use it to make some applications for Sirius available for other labs similar to the ideas in pyacal.

We also discussed that there might be a need for a coherent naming scheme for packages to make it easier to find packages that belong to the pyaml ecosystem.

An initial idea for how the current pyaml repository could be separated out in different packages: