-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event workflow retrospective #26
Comments
Overall, the planning set up went really well. However, here are some of my comments from #10: Two areas I could work on better (or need accountability for) are:
Regarding R Validation Hub social accounts: Also, our pharmaverse / PHUSE partner comms will likely be smoother next time, meaning we'll have more lead time to share now that we've established our initial connections there. |
Move event materials prepared and trial run to 7 days prior, because thats more realistic and removed the number of times we need to check the items |
Some additional thoughts: I think it would be good to add during/post-event todo items, e.g. record meeting and prepare notes for blog post (to be shared with R consortium marketing team) |
Just kicking off a thread to discuss how we might want to tune the process in the future.
There is a bit of discussion starting in #10 (comment), but in the spirit of having self-contained issues, I'm going to close that one out now that that the event is complete.
@jmanitz, @AARON-CLARK - what did you think about the planning setup?
The text was updated successfully, but these errors were encountered: