Description
Description
One potential future development path for pyAML is to build a software ecosystem. The idea is that instead of having a single package having a set of compatible packages where facilities can choose which ones they want to use or even develop their own package to add to the ecosystem. The working group should brainstorm how such an ecosystem could look like and come up with a suggestion for the next steps in case the collaboration decides to go in this direction.
Composition
Patrick Madela (SOLEIL)
Teresia Olsson (HZB)
Laurent Nadolski (SOLEIL)
Gayane Amatuni (CANDLE)
Murat Torun (ELI)
Input
- How other research communities have structured their ecosystems
- The existing packages in the pyAML GitHub organisation
- Experience of what might be facility, control system, accelerator type etc specific where different facilities want/need different implementations or functionality
Objectives and deliverables
-
A figure showing the different parts in the ecosystem and how they are connected.
-
A suggestion for how the existing packages can be restructured to facilitate the ecosystem development. What needs to be in a common core, what needs to be more modular, what can be separated out into separate repositories etc.
-
Initial description of the interfaces between packages and an example showing how that can be implemented.