Code tour guide needed
Nov. 10th, 2010 09:36 pm![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
I'm running late with the update this week (unsurprisingly) and need a code tour tour guide! Rather than browbeat ask someone in irc, I figured I'd throw it out there and see if someone's been interested in doing one but hasn't known how to ask!
(For the record, the way the code tour usually gets assigned is: Wednesday afternoon/evening, I realize oh crap, I need to do the update, and then turn to irc and keep begging people until someone says that they will do it. If you ever want to do one, just drop me a line Tuesday night/Wednesday morning and ask if anyone's claimed it yet.)
There are 17 bugs on this week's tour, which means it will be a quick one. You can check previous code tours for an example of how they should read (although everyone's different!)
You don't need to be a programmer to do one -- just be able to read the description of what the bug is for and put it into plain English. And, if you don't understand what a particular bug does, fixes, covers, etc, you can totally ask, and someone will explain it for you so that you can then explain it for everyone else!
(I will also happily look over your draft before you post it, if you'd like some reassurance that you have not just asserted that the moon is made of green cheese.)
If you are interested, comment to say that you're taking it. I'd prefer to have the code tour posted by tomorrow afternoonish/early evening (EST).
(For the record, the way the code tour usually gets assigned is: Wednesday afternoon/evening, I realize oh crap, I need to do the update, and then turn to irc and keep begging people until someone says that they will do it. If you ever want to do one, just drop me a line Tuesday night/Wednesday morning and ask if anyone's claimed it yet.)
There are 17 bugs on this week's tour, which means it will be a quick one. You can check previous code tours for an example of how they should read (although everyone's different!)
You don't need to be a programmer to do one -- just be able to read the description of what the bug is for and put it into plain English. And, if you don't understand what a particular bug does, fixes, covers, etc, you can totally ask, and someone will explain it for you so that you can then explain it for everyone else!
(I will also happily look over your draft before you post it, if you'd like some reassurance that you have not just asserted that the moon is made of green cheese.)
If you are interested, comment to say that you're taking it. I'd prefer to have the code tour posted by tomorrow afternoonish/early evening (EST).