Campus outreach 2011-2012: Difference between revisions
imported>Paulproteus No edit summary |
imported>Paulproteus |
||
| Line 9: | Line 9: | ||
* Join the [http://lists.openhatch.org/mailman/listinfo/events events mailing list] and say who you are and how you want to contribute. We'll get you plugged in. |
* Join the [http://lists.openhatch.org/mailman/listinfo/events events mailing list] and say who you are and how you want to contribute. We'll get you plugged in. |
||
== |
== Doing a P2PU run == |
||
It has been suggested that the curriculum be available as online videos. Also, I want the co-instructors for in-person events to be able to base their lectures/instruction on online videos, so they know ''exactly'' what I would teach in their situation. |
|||
* I want the co-instructors for in-person events to be able to base their lectures/instruction on online videos, so they know ''exactly'' what I would teach in their situation |
|||
One thing we've learned is that practice makes perfect; with the [[Boston Python Workshop]], for example, the more we run it, the more we know how to run it well. |
|||
Therefore, I think we should do a run of the course on the web -- let's say on P2PU, since that's everyone's favorite online learning place. |
|||
We would plan the P2PU course to use the curriculum materials used by the in-person event. This way, we're forced to write them, and we also get feedback before we use them in the in-person events. |
|||
I estimate the course would take 7 weeks (with 8 "meetings", due to the fencepost problem): |
|||
* Day 0: Introductions (why people are here, what they expect to get out of the course) |
|||
* Day 7: Linux and the command line (tar, cd, ls) |
|||
* Day 14: Communication tools (IRC, mailing lists) |
|||
* Day 21: The ethics and history of the movement; and the economics and licensing that support it. |
|||
* Day 28: Getting, modifying, and verifying open source software (getting code; local patching) |
|||
* Day 35: Project organization (getting, building, modifying source code) |
|||
* Day 42: Practice contributing to a project |
|||
* Day 49: Wrap-up |
|||
== Probable places we can take the tour == |
== Probable places we can take the tour == |
||
Revision as of 03:27, 5 October 2011
Here are the things that are planned/true about campus outreach events in the 2011-2012 school year:
Curriculum status
I think that we did a good job with the Penn curriculum. We should polish it up into something unbearably awesome.
How to get involved
- Join the events mailing list and say who you are and how you want to contribute. We'll get you plugged in.
Doing a P2PU run
It has been suggested that the curriculum be available as online videos. Also, I want the co-instructors for in-person events to be able to base their lectures/instruction on online videos, so they know exactly what I would teach in their situation.
One thing we've learned is that practice makes perfect; with the Boston Python Workshop, for example, the more we run it, the more we know how to run it well.
Therefore, I think we should do a run of the course on the web -- let's say on P2PU, since that's everyone's favorite online learning place.
We would plan the P2PU course to use the curriculum materials used by the in-person event. This way, we're forced to write them, and we also get feedback before we use them in the in-person events.
I estimate the course would take 7 weeks (with 8 "meetings", due to the fencepost problem):
- Day 0: Introductions (why people are here, what they expect to get out of the course)
- Day 7: Linux and the command line (tar, cd, ls)
- Day 14: Communication tools (IRC, mailing lists)
- Day 21: The ethics and history of the movement; and the economics and licensing that support it.
- Day 28: Getting, modifying, and verifying open source software (getting code; local patching)
- Day 35: Project organization (getting, building, modifying source code)
- Day 42: Practice contributing to a project
- Day 49: Wrap-up
Probable places we can take the tour
Part of the plan is to have Asheesh roam the country/world
Possible sponsors
In this section, I will speculatively list companies and organizations that might want to help make sure the event can take place.
- Mozilla?
- Red Hat?
- Python Software Foundation?
- WordPress.org?
- Debian's usual funders?