I am wondering if I did the best possible job setting up my tasks for the Google code-in. Judging from
http://www.google-melange.com/gci/dashboard/google/gci2012#all_org_tasks it looks like lots of small tasks are most attractive to potential students. I wrote up a little page explaining some possible improvements, each one of which could be considered a task, but on Melange it looks like updating the book is considered one big task. So I'm wondering if that needs to be changed and how to go about it. Whether it as part of the Google code-in or not, I hope to work with the Python Joven and others like them to make an improved version of MYOSA and give them a shot at literary immortality. It isn't fair for me to keep all of it for myself. James Simmons 2. Google Code-In [3] began on Monday. We have 22 mentors [4], 40 > students [5], and 79 out of 132 tasks already completed [6]. (More > tasks are coming on-line soon.) The contest runs for 6 weeks, so it is > not too late to sign up as a mentor [7] and to recruit students to > participate [8]. Some highlights include new tutorials for Turtle Art, > using Sugar in a Virtual Machine, and using Sugar on a Stick; a new > feature: load a background image on the home screen; and numerous > patches in support of internationalization. Some of the usual suspects > are making their usual outstanding contributions, while some new > talent is also emerging. Thanks to everyone (mentors, students, and > Google) for participating. > > [6] > http://www.google-melange.com/gci/dashboard/google/gci2012#all_org_tasks >
_______________________________________________ IAEP -- It's An Education Project (not a laptop project!) [email protected] http://lists.sugarlabs.org/listinfo/iaep
