2017.06.13. Developers meeting at SOLEIL

Coordination

• Priority of tasks (tests, abstract classes, documentation)
• Best practices for starting work with mxcube.
• Balance between new features and stable deployment (documentation, tests, abstraction).
• Fast access to the 'starting information'.
• Guidelines for developers.
• Work packages
• Do not accept PR without documentation and link with issues.
• Communication via github.
• Docs camp (Tango collaboration example)? When and where?
• Versioning. Like x.y.z. z: bugfixes, y: features, x: major version

Every Hardware Object

• Abstract Class with docstrings and configuration example
• Mockup Class with tests
• towards 2.3
• Partition of tasks (shared table)
• One example to be done before the developer session ends!

Virtual and face-to-face meetings

• face-to-face coding camps for well defined tasks e.g. -- finalization of clean-up of HardwareObjects -- documentation camp -- ...

Hardware objects and hardwareRepository

• Clean existing hwobj (code, location, etc)
• Add tests (pytest)
• Proper Abstract classes with proper documentation
• Prioritize hwobjs
• Example xml along the code
• Categorize hwobj in directories