<HTML dir=ltr><HEAD><TITLE>Sugar Digest, Vol 20, Issue 7</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText18040 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><A href="http://info.seattleacademy.org/saas/parent_reps/parent_reps.php">http://info.seattleacademy.org/saas/parent_reps/parent_reps.php</A></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>We'll need to add a link to the site, I guess....sorry!</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sugar-bounces@lists.laptop.org on behalf of sugar-request@lists.laptop.org<BR><B>Sent:</B> Mon 2/4/2008 1:02 PM<BR><B>To:</B> sugar@lists.laptop.org<BR><B>Subject:</B> Sugar Digest, Vol 20, Issue 7<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Send Sugar mailing list submissions to<BR> sugar@lists.laptop.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR> <A href="http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/listinfo/sugar</A><BR>or, via email, send a message with subject or body 'help' to<BR> sugar-request@lists.laptop.org<BR><BR>You can reach the person managing the list at<BR> sugar-owner@lists.laptop.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of Sugar digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. Re: What's left for Update.1 (C. Scott Ananian)<BR> 2. Re: What's left for Update.1 (Sayamindu Dasgupta)<BR> 3. Re: What's left for Update.1 (Sayamindu Dasgupta)<BR> 4. Update.1. When What How and Why ('Caperton, Idit')<BR> 5. Re: Update.1. When What How and Why (drew einhorn)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Mon, 4 Feb 2008 12:01:01 -0500<BR>From: "C. Scott Ananian" <cscott@laptop.org><BR>Subject: Re: [sugar] What's left for Update.1<BR>To: "Sayamindu Dasgupta" <sayamindu@gmail.com><BR>Cc: Kim Quirk <kim@laptop.org>, Sugar List <sugar@laptop.org>, OLPC<BR> Developer's List <devel@laptop.org><BR>Message-ID:<BR> <c6d9bea0802040901y69e02e2foa227dd2830578099@mail.gmail.com><BR>Content-Type: text/plain; charset=ISO-8859-1<BR><BR>On Feb 4, 2008 11:50 AM, Sayamindu Dasgupta <sayamindu@gmail.com> wrote:<BR>> 2008/2/4 Kim Quirk <kim@laptop.org>:<BR>> > I think this is way too much stuff for Update.1. We are in code freeze. We<BR>> > have items 1 and 2 scheduled to go into RC2; I would suggest that we ONLY<BR>> > pick up Spanish, where we really fell short in the current build; I don't<BR>> > agree with holding up this build for either 4 or 5, as this feels like new,<BR>> > untested code - perhaps there is no 'fix' even available at this time (I'd<BR>> > need to see the arguments that this is blocking AND we have a fix); and I<BR>> > agree that we need to look at 'Blocking' bugs that are still open to see if<BR>> > we agree they are still blocking - or move them out.<BR><BR>Hear, hear.<BR><BR>> For translations, I would also probably push Mongolian in, along with<BR>> Spanish. I am currently making those two sets of translations go<BR><BR>I really believe that we will need an update.1.1 for Mongolia, so I<BR>(for one) would not be sad to see the Mongolian translations not make<BR>it for update.1. By the time we can solve the networking issues for<BR>Mongolia, we should have translations well in hand as well.<BR><BR>Mongolia will likely not get updated again until there is another<BR>opportunity to use the bulk multicast update technique again, so it<BR>doesn't make too much sense to rush the Mongolian translations.<BR> --scott<BR><BR>--<BR> ( <A href="http://cscott.net/">http://cscott.net/</A> )<BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Mon, 4 Feb 2008 23:06:44 +0530<BR>From: "Sayamindu Dasgupta" <sayamindu@gmail.com><BR>Subject: Re: [sugar] What's left for Update.1<BR>To: "Tomeu Vizoso" <tomeu@tomeuvizoso.net><BR>Cc: Sugar List <sugar@laptop.org><BR>Message-ID:<BR> <a1314bfe0802040936l25364e32j35eab3d961917343@mail.gmail.com><BR>Content-Type: text/plain; charset=UTF-8<BR><BR>On Feb 4, 2008 10:29 PM, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:<BR>> On Mon, 2008-02-04 at 22:20 +0530, Sayamindu Dasgupta wrote:<BR>> > For translations, I would also probably push Mongolian in, along with<BR>> > Spanish. I am currently making those two sets of translations go<BR>> > through all kinds of tests (I wish I could make the rest of them go<BR>> > through these as well, but time is severely limited atm).<BR>> > If this raises concern about the inclusion of the latest translations<BR>> > for other languages, I am currently working on a system for building<BR>> > "language packs" (single archives), which can simply be installed in<BR>> > any Qemu image/XO/sugar-jhbuild setup, so that anyone can try out the<BR>> > latest translations for any of our supported language whenever they<BR>> > wish to.<BR>><BR>> Interesting, how are you planning to do these language packs?<BR><BR><BR>I have the PO files for each language arranged out pretty nicely,<BR>thanks to the internal symlinking system used for Pootle.<BR>I will be generating two zip for each language - one for Update.1, and<BR>one weekly(?) that tracks HEAD - for the joyride builds. The Zip will<BR>contain pre-compiled MO files - which will be extracted and put into<BR>the correct places in the filesystem (this would either be a seperate<BR>script, or something like the Nvidia binary drivers - which seem to<BR>combine both and archive and a shell script together).<BR><BR>While this will not be an exact affair (especially for the joyrides,<BR>which are pretty fast moving for some packages, while slow for the<BR>others) the main aim of this is to make it easier for translators to<BR>test their translations in action. I have been getting a number of<BR>queries on how to easily check the translations in action - currently<BR>the method involves downloadin and compiling each PO by hand, which<BR>is too cumbersome IMO.<BR><BR>Thanks,<BR>Sayamindu<BR><BR>--<BR>Sayamindu Dasgupta<BR>[<A href="http://sayamindu.randomink.org/ramblings">http://sayamindu.randomink.org/ramblings</A>]<BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Mon, 4 Feb 2008 23:07:58 +0530<BR>From: "Sayamindu Dasgupta" <sayamindu@gmail.com><BR>Subject: Re: [sugar] What's left for Update.1<BR>To: "C. Scott Ananian" <cscott@laptop.org><BR>Cc: Kim Quirk <kim@laptop.org>, Sugar List <sugar@laptop.org>, OLPC<BR> Developer's List <devel@laptop.org><BR>Message-ID:<BR> <a1314bfe0802040937v573d556br8bc6542835465c96@mail.gmail.com><BR>Content-Type: text/plain; charset=UTF-8<BR><BR>On Feb 4, 2008 10:31 PM, C. Scott Ananian <cscott@laptop.org> wrote:<BR>> On Feb 4, 2008 11:50 AM, Sayamindu Dasgupta <sayamindu@gmail.com> wrote:<BR>> > 2008/2/4 Kim Quirk <kim@laptop.org>:<BR><BR><..snipped><BR><BR>><BR>> > For translations, I would also probably push Mongolian in, along with<BR>> > Spanish. I am currently making those two sets of translations go<BR>><BR>> I really believe that we will need an update.1.1 for Mongolia, so I<BR>> (for one) would not be sad to see the Mongolian translations not make<BR>> it for update.1. By the time we can solve the networking issues for<BR>> Mongolia, we should have translations well in hand as well.<BR>><BR>> Mongolia will likely not get updated again until there is another<BR>> opportunity to use the bulk multicast update technique again, so it<BR>> doesn't make too much sense to rush the Mongolian translations.<BR>> --scott<BR><BR>In that case - Spanish it is :-).<BR><BR>Thanks,<BR>Sayamindu<BR><BR><BR><BR>--<BR>Sayamindu Dasgupta<BR>[<A href="http://sayamindu.randomink.org/ramblings">http://sayamindu.randomink.org/ramblings</A>]<BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Mon, 4 Feb 2008 13:41:43 -0500<BR>From: "'Caperton, Idit'" <idit@worldwideworkshop.org><BR>Subject: [sugar] Update.1. When What How and Why<BR>To: <jg@laptop.org>, "'Kim Quirk'" <kim@laptop.org><BR>Cc: sugar@lists.laptop.org<BR>Message-ID: <20080204184144.0BB8BA3E@smtp.globixmail.com><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Hello There - It's already February of 2008!!!<BR>So reading these exchanges by our highly respected OLPC software leaders in<BR>Cambridge (Jim and Kim, and others) in the past two weeks, and in the past<BR>months in general, has been startling to me (and my team).<BR>The only thing that's a bit more overwhelming is the OLPC Library List :)<BR><BR>I read Jim's list of To-Do's, see below, and then the casual comment in the<BR>open from Kim to Jim: "I think this is way too much stuff for Update.1."<BR><BR>Yes, this is a transparent and ambitious open-source software development<BR>project. The first of its kind.<BR><BR>But, it doesn't mean that it cannot be well-managed with reasonable<BR>executable plans and dates attached to the plans (that could be revised by<BR>the community, if needed).<BR><BR>In my organization, we call it a strategic plan and a production schedule,<BR>and we attached to it reasonable phases and dates -- and most<BR>accountability.<BR><BR>But I am not aware -- what does OLPC do to re-evaluate process and progress<BR>on an ongoing basis? and how does the olpc org learns how to optimize and do<BR>things better, and on schedule? How does the OLPC software development<BR>system learns to be deliverables-oriented, and how do we learn to lead these<BR>global processes more productively?<BR><BR>FACT: