Mike,<br><br>Thanks, this kind of feeback from each project would definitely be helpful. One specific way to ask for help: we are after all taking part in Google Summer of Code. Please add new project ideas,or offer to mentor, on our Summer of Code page:
<br> <a href="http://wiki.laptop.org/go/Summer_of_Code">http://wiki.laptop.org/go/Summer_of_Code</a><br><br>As you come across project needs or potential mentors over the coming few days, please add them there or on the discussion page. We would like to get some great applications in over the next few days. This is also a good way to tackle the question of where to work within the project -- where people with experience in other projects can jump in and do some good with limited time.
<br><br>Cheers,<br> SJ<br><br><br><div><span class="gmail_quote">On 3/23/07, <b class="gmail_sendername">Mike C. Fletcher</b> <<a href="mailto:mcfletch@vrplumber.com">mcfletch@vrplumber.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As I start the developer outreach work I'm getting (quite a few)<br>developers asking me the question:<br><br> Where should I work within the project.<br><br>and I'm coming up against the question of how I can know what the
<br>project priorities/needs are. Over time I will hopefully become<br>pseudo-omniscient (work on that later ;) ) but in the meantime I'm<br>tossing around some ideas.<br><br>So far my answers are of the character:<br>
<br> * We desperately need documentation<br> o Mel is beginning work on that with Marco now<br> * We desperately need (documented) sample code for:<br> o Hippo, particularly for activities, particularly more
<br> advanced layouts showing both how and *why*<br> o Telepathy, we need sample code for "how to share activity<br> state among multiple participants"<br> o Hardware access from Python (for all special hardware)
<br><br>and I *think* those answers are probably the right answers *today* (and<br>there's more in the wiki on the developer's images pages), but that's<br>all just *me* thinking up what needs to be done. What I need to be
<br>effective is requests from the various project leads, things like:<br><br> * We need someone to build an X activity with an associated set of<br> simple experiments<br> * We need someone to document X API(s) or processes
<br> * We need someone to figure out how to do X<br> * We need someone to run X subproject, they need to be able to do<br> this, that and the other thing<br><br>If at all possible, some prioritisation would be helpful (is this
<br>blocking your project, going to speed it up, or just a nicety). I'll<br>probably look into getting such things posted to a wiki page somewhere<br>(or maybe something with an RSS feed).<br><br>Or does someone have a better idea? Project-wide ticket-tracker for
<br>"hiring"? Simple mailing list with announces of needs and offers?<br><br>There are thousands of developers willing to work, where do we need them<br>tomorrow,<br>Mike<br><br>--<br>________________________________________________
<br> Mike C. Fletcher<br> Designer, VR Plumber, Coder<br> <a href="http://www.vrplumber.com">http://www.vrplumber.com</a><br> <a href="http://blog.vrplumber.com">http://blog.vrplumber.com</a><br><br>_______________________________________________
<br>Sugar mailing list<br><a href="mailto:Sugar@laptop.org">Sugar@laptop.org</a><br><a href="http://mailman.laptop.org/mailman/listinfo/sugar">http://mailman.laptop.org/mailman/listinfo/sugar</a><br></blockquote></div><br>