...
- Communication between instructors could have been better
- Some groups were not working together at the beginning
- The participants didn't know what was expected at several practical sessions
- The main integration server was not ideal and was hard to share the work being done with participants
- More time for the project tests and integrations
- Organization of the material
- Communication with participants could be better (goals/expectation)
- Organization, improvisation and consistency of the agenda
- The observatory demonstration (speaking more, showing both the screen and the telescope, explaining the debugging, etc.)
- The CDB repository confused some of the participants
- Virtual machine issues (Problems, not prepared by the partcipants, etc.)
What else can we do?
- Coffee break sessions to know other participants
- Have backup servers to run and connect to ACS
- Review the project (IDLs, communication, etc.)
- Improve documentation (ACS, Workshop, Project, Navigation, etc.)
- ACS workshop as a tutorial
- Invite experienced instructors
- Docker, Vagrant or other virtualization alternative
- REST API (Camera and Telescope + Simulation)
- Increase exercises or quizzes between presentations to improve engagement
- Create alternative projects for the workshop or for after workshop development
- Presentations, exercises as well as opening and closing words
- Improve CDB simulation (dummy image, telescope movement, etc.)
- Add CDB integration to Jenkins
What actions do we identify?
- Improve material
- Review IDL interfaces
- Change CDB repository and improve instructions
- Improve virtual machine
- Workshop agenda as a template in ACS space
- Investigate hardware alternatives or opportunities
- Improve ACS and Project documentation
- Motivate participants before the workshop (prepare and test VMs, etc.)