On Mon, Mar 24, 2008 at 12:37 PM, Samuel Klein <<a href="mailto:meta.sj@gmail.com">meta.sj@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We could use more mentors specifically for projects integrating with sugar, networking and other core services -- many students have been applying to create their own standalone code or activities from scratch, but that does not give them much of a chance to learn about collaborating on a larger project.</blockquote>
<div><br>What about treating several of the proposed activities as a one large project? We would create a
SoC "activity team" of 4-8 students and 2-3 mentors, and then have these students
develop several of the activity ideas over the summer.<br>
<br>Developing activities involves so much similar code that I think it would be wasteful for individuals to have to learn everything separately. And there is an opportunity for students to learn about working as part of a team in different roles.<br>
<br>For example if we were to tackle a subset of these activities:<br><br>Typing Tutor<br>Flash Cards<br>Finance<br>Connect*<br>Mastermind*<br>Deducto*<br>Chess*<br>Checkers*<br>Othello*<br>Mancala*<br>Classroom Tools<br>
<br>*These are so similar that they could be developed by one team in parallel.<br><br>We would assign the members of our team one or more of the following roles:<br><br>Interface coder - Responsible for the activity user interface. Includes PyGTK toolbars, custom widgets and event handling.<br>
<br>Model coder - Responsible for the activity state machine and logic. Includes implementing application states & transitions between them, data processing algorithms, serialization (journal interaction).<br><br>Collaboration coder - Responsible for activity sharing and collaboration. Includes protocol design & implementation, DBUS & tubes programming.<br>
<br>This project would require the following supprt from the OLPC organization:<br><br>Mentors - At least 2 programming mentors (myself, manu, tomeu, morgs, cjb, anyone else?) and one organization mentor (mel, sj?). The programmers would divide responsibility for the different parts of each activity, and develop as many as possible to a polished state over the course of the summer.<br>
<br>Support Artist - A volunteer artist with a lot of spare time to develop toolbar and activity icons as well as bitmapped graphics for game pieces.<br><br>This is kind of a prototype of my Activity Development Portal proposal at <a href="http://wiki.laptop.org/go/Talk:Activities">http://wiki.laptop.org/go/Talk:Activities</a>.<br>
<br>Anyone interested?<br><br>Regards,<br><br>Wade<br>
<br>
<br><br>View<br>
For example, students could be divided between collaboration,
UI design and implementation, <br></div></div><br>