Jim,<br>I think this is way too much stuff for Update.1. We are in code freeze. We have items 1 and 2 scheduled to go into RC2; I would suggest that we ONLY pick up Spanish, where we really fell short in the current build; I don't agree with holding up this build for either 4 or 5, as this feels like new, untested code - perhaps there is no 'fix' even available at this time (I'd need to see the arguments that this is blocking AND we have a fix); and I agree that we need to look at 'Blocking' bugs that are still open to see if we agree they are still blocking - or move them out.<br>
<br>People can argue otherwise (I'm open to a good discussion), but my recommendation is to get this build out, with all the known issues well documented. <br><br>Kim<br><br><br><div class="gmail_quote">On Jan 31, 2008 10:11 PM, Jim Gettys <<a href="mailto:jg@laptop.org">jg@laptop.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">For comment and discussion, here are the showstoppers I know of for<br>getting Update.1 finished. If you think there are others, please speak<br>
up now (and modify the subject line to start another thread).<br><br>Activity developers: note we'll be asking you to upload updated<br>activities to pick up all the recent flurry of translation work very<br>soon.<br>
<br> 1 - wireless firmware and driver support<br> (to fix problems with WEP and WPA)<br> 2 - q2d11 OFW - to fix battery problems<br> 3 - update activities to pick up translation work, Spanish<br> in particular, but not missing other languages we may need.<br>
4 - UI fix for registration with the school server.<br><a href="http://dev.laptop.org/ticket/6136" target="_blank">http://dev.laptop.org/ticket/6136</a><br> 5 - switch to gabble from salut at school.<br> 6 -testing and fixing anything critical!<br>
<br>If we don't want to hold up an RC2 to pick up translation, then we<br>should anticipate an RC4 might be necessary (as we may have issues that<br>come up with updated activities).<br><br>4 - we previously (without Dave Woodhouse being available to add to the<br>
discussion) thought we could/should punt #6135 and release note.<br>However, talking with him about what we should really fix given his<br>experience in Mongolia, the lack of positive confirmation that the<br>laptop actually was registered is a real issue. The teachers are not<br>
familiar with English (or computers), and the subtlety of a menu entry<br>going away isn't good enough.<br><br>I think we need to seriously discuss about possibly/probably being<br>update.1 fodder is the "kids arrive at school in the morning" problem.<br>
<br>5 - Use of mesh in large, crowded environments<br>If everyone arrives at school running local link and resumed quickly,<br>the network might melt from mdns mesh traffic's interaction with the<br>mesh's implementation of mutlicast. We've upped the multicast bitrate<br>
for multicast as a band aid, until we can dynamically adjust the<br>bitrate. But the fundamental issue comes that in large, dense school<br>environments, can't expect multicast to scale far enough, and should be<br>using unicast to a presence server (jabber in our current case) to<br>
handle this problem.<br><br>Dave Woodhouse has suggested may be to try to get a response to the<br>school server's anycast address, and if we get a response from a school<br>server, switch from Salut to Gabble for presence service automatically.<br>
<br>This is also somewhat mitigated by having working power management, as<br>machines that have suspended due to idle stop sending mdns packets, and<br>the kids presumably will want internet access and switch over when they<br>
arrive. But I'm not very confident that this will always work in large<br>environment.<br><br>Another temporary solution would be to have Ohm ask NM to reconnect if<br>the machine is suspended for more than some interval, say, 30 minutes.<br>
<br>--<br>Jim Gettys<br>One Laptop Per Child<br><br><br>_______________________________________________<br>Devel mailing list<br><a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</blockquote></div><br>