Split the project in parts

[simoneliuzzo]

May be at this stage of the project we could think of splitting in several parts.

For example:

• Documentation
• Configuration
• Core
• Tuning Tools
• Backend 1
• Backend ...
• Backend N
• virtual accelerator
• ...

The project is already mostly separated as above.

Each of these parts could have one person responsible with "last word" decisional power.

Each of these parts could be handled by a different lab.

The responsibility would be reassessed (on an yearly basis?) among labs and people contributing to the project.

This proposal makes sense if the separation makes sense. For example if Core and Configuration are too difficult to separate, then they would remain a single topic.

[gubaidulinvadim]

Could we do this after the workshop at ESRF? There are still parts of the project that need to be implemented (unit conversion, a standardised way to do measurements, etc), and I would not like to introduce yet another refurbishment, moving things around and rewriting tests.

Also, we have very few people actively working on the project. If we assign a responsible person for each repository, it will quickly come to one person being responsible for many things. We should first aim to attract more developers.