-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #846 from coderefinery/rkdarst/blog-next-workshop
2024-03-25-next-cr-workshop-help-needed: Blog post to prepare for next workshop
- Loading branch information
Showing
1 changed file
with
55 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
+++ | ||
title = 'Help us do the next CodeRefinery workshop (2024 H2)' | ||
slug = "2024/03/25/next-cr-workshop-help-needed" | ||
description = "Our workshop in 2024 March went well. But we need help if we want to do this again." | ||
|
||
[extra] | ||
authors = "Richard Darst" | ||
+++ | ||
|
||
As usual, our workshop in 2024 March has worked very well, and our | ||
feedback is as positive as ever. The technical setup worked smoothly, | ||
and [we are working to share our livestreaming technique with | ||
others](@/blog/2024-03-17-streaming-training-workshop.md). But | ||
there's another thing we need: the mere fact we have hundreds of | ||
registrations, multiple partners, and more than 10 instructors means | ||
**we need more help to keep these going**. | ||
|
||
**We won't schedule another very large CodeRefinery workshop until we can be sure | ||
we have enough people to distribute the load widely enough to make it | ||
worth it. If we don't get that, we'll scale down to what is | ||
manageable. Your help is essential. We give an initial deadline of | ||
the end of April to figure out our status and do rough timetabling.** | ||
|
||
The good thing is that instructors and helpers are not what is in | ||
short supply, but something more about bigger picture stuff. We've | ||
developed good processes and pretty well know what works, but as we | ||
move to the sustainability phase, we can't do everything ourselves. | ||
For example, we would be happy to have: | ||
|
||
* **Instructor coordinator**, who can keep track of all of our | ||
instructors and make sure the necessary onboarding and all is done. | ||
|
||
* **Registration coordinator**, who can help manage all of the | ||
registrations and communication. | ||
|
||
* **Partner coordinator** who can help with outreach to partners | ||
(other universities for example) who advertise our workshop and | ||
organize local sessions. | ||
|
||
None of these are exactly hard, and we can help you learn what is | ||
needed (but also there is a lot that can be improved for the future - | ||
new visions are welcome). | ||
|
||
Our vision is that our commonly shareable online, live-streamed course | ||
can be used by as many organizations and learners as possible. We | ||
have the base and now we need the communication and outreach to make | ||
that possible. (If you can't help directly, but want to be part of | ||
this vision, also let us know) Whoever joins would basically become | ||
part of CodeRefinery for the purposes of organization - your voice | ||
would matter as much as anyone else. | ||
|
||
TODO who to contact. | ||
|
||
See also | ||
* (manuals links? website links?) |