ADD: Add initial schedule #83
Conversation
|
👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below. |
There was a problem hiding this comment.
I've already got almost 20 replies to the survey. I'll definitely have this on the agenda for next meeting. First impression from the comments, package capabilities should be comprehensive but relatively short. So maybe 20/25 min should be enough for a single package for the morning slot. Baltrad is somewhere in-between as it has no workflow part.
Anyway, good to get this going.
| | 10:30 AM - 11:00 AM | Py-ART/wradlib | Kai Mühlbauer + Bobby Jackson | | ||
| | 11:00 AM - 11:30 AM | Pyrad Introduction | Jordi Figueras i Ventura + Daniel Wolfensberger | | ||
| | 12:00 PM - 12:30 PM | LROSE | Brenda Javornik + Jen DeHart | | ||
| | 12:30 PM - 01:30 PM | Lunch | | |
There was a problem hiding this comment.
I've talked to @ghiggi and we might need 10 to 15 Minutes for a short intro to gpm-api. Not sure where to squeeze this in.
There was a problem hiding this comment.
Can we include that in the project pitches in the afternoon? Or was there interest specifically in the morning?
There was a problem hiding this comment.
It can be in the afternoon, but half an hour and four workflows seems a bit tight. Or LROSE and PyRad do their workflow advertisement in the morning?
There was a problem hiding this comment.
Let's do 15 minutes after BALTRAD - then we can do a "lightning" style for the project pitches. Everyone should advertise their workflow/project ideas throughout the tutorials earlier in the day!
|
@kmuehlbauer - I addressed those suggestions in the latest version 👍 |
|
Thanks @mgrover1! |
Add an initial schedule