Overview over documentation to date - organization, available forms of documentation:

Github wiki pages are the entry point- should be kept up-to-date by all contributors with one custodian.
Jupyter notebooks on the PyHEADTAIL playground and SWAN - needs more organisation
ACTION: go through wiki pages and check content and organisation.
ACTION: PyHEADTAIL Playground - include organized repository of examples that can be used as black box - motivate script writers to have a split approach with "input files" and simulation logics in them.
PyHEADTAIL - organize jupyter notebooks in categories - start with Adrian's proposal (ACTION - Adrian to re-organize accordingly); have wiki pages as entry point
Kevin suggests also to have submission script stubs for the different clusters
SWAN usage as showcase - a very first entry point for educational means - can also be used for training means if well prepared (potential ACTION) - online model (--> to date we have no gallery example which uses PySIXTRACK)
Presentation of how to include new notebook into SWAN using pull requests (Adrian will add a short comment that it needs to be forked of course...!)
ACTION - add HB2016 slides onto ATS; have Gianluigi and Elias in CC
Compare with quickstart tutorial from NumPy.
ACTION: Adrian to include a slide on the available documentation existing for PyHEADTAIL.

Next meeting in 2 weeks...

AOB: