-
Notifications
You must be signed in to change notification settings - Fork 89
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
RFC #4: Create more resources for speakers #87
Comments
Great! I know I'd already mentioned this on #86 but part of these resources can include speakers' tooling and not only possible topics to speak about. Thanks, @bencodezen For working on this. 🙏🏽 |
How can we (as organizer or ressource creator) can help with that ? I think a lot of speaker share their presentation and code online. It can be interesting to groups them in one place ? |
@AMontagu Thanks for asking! Organizers and resource creators are more than welcome to file issues with the repo / submit PRs to contribute. As far as centralizing speaker presentations and code, this is a difficult one since we would need to create a fairly complex content management system and guidelines. However, we can certainly consider that in a future roadmap once the events has solidified. Thank you for the suggestion! |
Making a note to also source more CFPs that speakers can apply to: https://twitter.com/obedparla/status/1220995654060793856?s=12 |
A first draft on how to share presentation: |
I feel like this one can be closed since it's old and most of the discussion related was merged. |
Proposal
We currently have a Speakers Handbook, but in order to help encourage and support new & experienced speakers, some ideas include:
Rationale
Public speaking can be intimidating to break into and requires more support than some may admit as it can easily lead to speaker burnout if one is not careful. As a result, we want to create the resources and environment necessary to encourage new speakers to take the stage while also supporting our current speakers.
The text was updated successfully, but these errors were encountered: