Anonymous user
PyCon-2015-sprint-wiki: Difference between revisions
Add info about event
imported>Paulproteus (Add info about event) |
|||
Line 143:
List of useful skills: '''"Participating is only feasible for people that can already at least roughly read C-code. Experience in C programming is recommended, but there are also refactoring and code-arrangement and cleanup-tasks that can be done by moving existing code around; that's why reading C-code is already enough for some tasks. In addition to improving C-skills I provide guidance for and insight into Python's C-extension API and also into Jython, how to use it, how it works."'''
== Info about the intro event ==
5:30-5:45 ** Pre-event **
Attendees and mentors trickle in. Mentors update the sprint wiki (see above) as needed, and socialize with attendees.
5:45 - 6:00 ** Intro **
Led by Shauna and Naomi. We'll talk about what the workshop will cover, and what the sprint schedule itself is. We'll be soliciting stories from mentors and others in the audience about past experiences sprinting, to help students picture what the next couple of days will be like.
6:00 - 7:00 ** Tools **
TOOLS Intro by Shauna, then small groups. We'll cover common open source tools, focusing on those mentioned by sprint leaders as useful for contributing to their projects. The first 15 minutes will be spent as a group doing overviews, then for the next 45 minutes we'll break into groups to cover specific topics in more depth.
I'm looking for mentors to cover any topic marked with a ?. Please feel free to add yourself to mentoring groups even if there's already a mentor or two specified. You can also suggest additional topics but I can't promise we'll cover them.
IRC, Issue trackers, and beginning Git - Shauna, with help from Naomi Ceder
Unit tests & testing generally - Ned
Virtualenv - Eeshan Garg & Dustin J. Mitchell
Advanced Git - Trey
HTTP basics - Asheesh Laroia,
Virtualbox or Vagrant? Philip J.
Optional additional topics: ssh,
7:00-7:20/30 **Unsticking Yourself**
Led by Shauna. Group brainstorm of ways you might get stuck and how to unstick yourself. Prompts:
* not being sure what to work on
* not sure where to make changes in the code
* not being sure whether you've satisfied an issue
* your changes break tests
* you can't figure out what an error message means
7:30-end **Project Intros**
Project leads spend 2-5 minutes each describing their project, what they're planning to work on, and what kind of skills sprinters need. Afterwards, leads are encouraged to get dinner with potential sprinters.
Sprint Lunch: 2-3PM tomorrow
| |||