openradar / erad2018 Goto Github PK

We are well converging towards a solution for the upcoming ERAD 2018 short course. Here's a ToDo list which we need to address well before.

The deadline for anything that affects the VM is June 11 2018. After that, the final VM image for the course will be built, and participants will be informed how to download and install.

ToDo VM (deadline: 11/6/2018)

• make sure all required Python intro session notebooks are up and running --> Scott
• make sure all required Py-ART notebooks are up and running --> Scott/Zach/Bobby
• make sure all required BALTRAD notebooks are up and running --> Daniel
• make sure all required wradlib notebooks are up and running --> Maik/Kai

ToDo program (deadline: 1/7/2018)

• finalise open source and open science presentation --> Daniel
• finalise git live demo session (no slides etc., just a demo of fork&pull) --> Maik/Kai

ToDo VM docs (deadline: 11/6/2018)

• revise the openradar/oss_weather_radar_vm/docs in order to make sure that the latest changes (e.g. conda environments!) are well represented in the docs. --> Maik
• build the docs and push to openradar/vm_docs --> Maik

ToDo course website (deadline: 11/6/2018)

The course website (http://openradarscience.org/erad2018/) contains some links through which we can provide additional information for individual course sessions. Could be only one sentence, or could be a detailed instruction, or just a link - it depdends on you. If you are resonsible for a session, you can modify the readme.md files in the subdirectories based on which the webpages will be rendered.

• add minimal info for open-science slot --> Daniel
• add minimal info for launch vm slot --> Maik
• add minimal info for python intro slot --> Scott
• add minimal info for git live demo --> Maik
• add minimal info for Py-ART slot --> Scott/Zach/Bobby
• add minimal info for BALTRAD slot --> Daniel
• add minimal info for wradlib slot --> Maik
• add minimal info for open slot --> Maik

ToDo Gitter (deadline: 15/6/2018)

If was suggested to use Gitter in order to communicate with the participants before the course. We could use the existing openradar/_ERAD2018 channel, if that's fine for you. In that case, we only need to

• inform participants to get a GitHub account and join the openradar/Lobby channel. --> Maik

ToDo openradarscience.org

The short course as well as the OSS keynote would be a good opportunity to advertise our https://openradarscience.org pages. The content basically lives in openradar/openradar-landing-page, so if you want to update anything, please submit a PR, e.g.

• update, extend and beautify https://openradarscience.org