No subject
bogus at does.not.exist.com
bogus at does.not.exist.com
Sat Feb 2 07:43:15 EST 2008
and<BR>delayed again.<BR><BR>It affects everybody involved. It's pretty =
tough for OLPC management,<BR>developers, and all OLPC young users =
worldwide. And all know by now - stuff<BR>do not work well as a =
result.<BR><BR>- Where is the Update.1 master plan? And what comes after =
and when?<BR>- Who keeps track and makes sure we are constantly =
re-evaluating it and<BR>documenting changes in decisions?<BR>- Is it =
well-strategized and well-monitored against the strategy?<BR>- How does =
s--t gets done and optimized in this messy open system?<BR>- Even =
decentralized system needs organizational management - What did =
OLPC<BR>software team learned so far?<BR>- Where are the pages with =
reflections on lessons learned?<BR>- How are decisions about what's in =
or out being made?<BR>- Where are the software-release-phases with dates =
for 2008?<BR>- Is there a clear schedule and list of deliverables with =
dates for 2008?<BR><BR>I know I know -- I am taking a big risk by =
sending this kind of alarming<BR>message to the entire global Sugar =
List.<BR><BR>But please remember that I am sending it in order to shake =
the existing<BR>system, as a serious call for change, to be provocative, =
and get you all to<BR>think about it positively.<BR><BR>- and, most =
important, I do it with lots of love and care for the XO and the<BR>OLPC =
movement at large.<BR><BR>Idit Harel Caperton<BR>President & =
Founder<BR>World Wide Workshop<BR><BR>-----Original =
Message-----<BR>From: sugar-bounces at lists.laptop.org [<A =
href=3D"mailto:sugar-bounces at lists.laptop.org">mailto:sugar-bounces at lists=
.laptop.org</A>]<BR>On Behalf Of sugar-request at lists.laptop.org<BR>Sent: =
Monday, February 04, 2008 12:00 PM<BR>To: =
sugar at lists.laptop.org<BR>Subject: Sugar Digest, Vol 20, Issue =
6<BR><BR>Send Sugar mailing list submissions =
to<BR> =
sugar at lists.laptop.org<BR><BR>To subscribe or unsubscribe via the World =
Wide Web, visit<BR> <A =
href=3D"http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/l=
istinfo/sugar</A><BR>or, via email, send a message with subject or body =
'help' to<BR> =
sugar-request at lists.laptop.org<BR><BR>You can reach the person managing =
the list at<BR> =
sugar-owner at lists.laptop.org<BR><BR>When replying, please edit your =
Subject line so it is more specific than<BR>"Re: Contents of Sugar =
digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. Re: What's =
left for Update.1 (Kim Quirk)<BR> 2. Re: What's left for =
Update.1 (Sayamindu Dasgupta)<BR> 3. Re: What's left for =
Update.1 (Tomeu =
Vizoso)<BR><BR><BR>------------------------------------------------------=
----------------<BR><BR>Message: 1<BR>Date: Mon, 4 Feb 2008 10:51:41 =
-0500<BR>From: "Kim Quirk" <kim at laptop.org><BR>Subject: Re: =
[sugar] What's left for Update.1<BR>To: jg at laptop.org<BR>Cc: Sugar List =
<sugar at laptop.org>, OLPC Developer's =
List<BR> =
<devel at laptop.org><BR>Message-ID:<BR> =
=
<9073bf100802040751n2654ff44i19b418280e850b75 at mail.gmail.com><BR>Co=
ntent-Type: text/plain; charset=3D"iso-8859-1"<BR><BR>Jim,<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>People can argue otherwise (I'm open =
to a good discussion), but my<BR>recommendation is to get this build =
out, with all the known issues =
well<BR>documented.<BR><BR>Kim<BR><BR><BR>On Jan 31, 2008 10:11 PM, Jim =
Gettys <jg at laptop.org> wrote:<BR><BR>> For comment and =
discussion, here are the showstoppers I know of for<BR>> getting =
Update.1 finished. If you think there are others, please<BR>> =
speak 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>> &nbs=
p; (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=3D"http://dev.laptop.org/ticket/6136">http://dev.laptop.org/ticket/6=
136</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<BR>> that come up with updated =
activities).<BR>><BR>> 4 - we previously (without Dave Woodhouse =
being available to add to<BR>> 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 =
If everyone arrives at<BR>> school running local link and resumed =
quickly, the network might melt<BR>> from mdns mesh traffic's =
interaction with the mesh's implementation of<BR>> mutlicast. =
We've upped the multicast bitrate for multicast as a band<BR>> aid, =
until we can dynamically adjust the bitrate. But the =
fundamental<BR>> issue comes that in large, dense school =
environments, can't expect<BR>> multicast to scale far enough, and =
should be using unicast to a<BR>> presence server (jabber in our =
current case) to 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<BR>> school server, =
switch from Salut to Gabble for presence =
service<BR>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,<BR>> and the =
kids presumably will want internet access and switch over when<BR>> =
they arrive. But I'm not very confident that this will always work =
in<BR>> large 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>> Devel at lists.laptop.org<BR>> <A =
href=3D"http://lists.laptop.org/listinfo/devel">http://lists.laptop.org/l=
istinfo/devel</A><BR>><BR>-------------- next part =
--------------<BR>An HTML attachment was scrubbed...<BR>URL:<BR><A =
href=3D"http://lists.laptop.org/pipermail/sugar/attachments/20080204/0745=
1d8a/attach">http://lists.laptop.org/pipermail/sugar/attachments/20080204=
/07451d8a/attach</A><BR>ment-0001.htm<BR><BR>----------------------------=
--<BR><BR>Message: 2<BR>Date: Mon, 4 Feb 2008 22:20:40 +0530<BR>From: =
"Sayamindu Dasgupta" <sayamindu at gmail.com><BR>Subject: Re: [sugar] =
What's left for Update.1<BR>To: "Kim Quirk" =
<kim at laptop.org><BR>Cc: OLPC Developer's List =
<devel at laptop.org>, Sugar =
List<BR> =
<sugar at laptop.org><BR>Message-ID:<BR> =
=
<a1314bfe0802040850n1b82eab2tcf5f68db16376b4a at mail.gmail.com><BR>Co=
ntent-Type: text/plain; charset=3DUTF-8<BR><BR>2008/2/4 Kim Quirk =
<kim at laptop.org>:<BR>> Jim,<BR>> I think this is way too =
much stuff for Update.1. We are in code<BR>> freeze. We have items 1 =
and 2 scheduled to go into RC2; I would<BR>> suggest that we ONLY =
pick up Spanish, where we really fell short in<BR>> the current =
build; I don't agree with holding up this build for either<BR>> 4 or =
5, as this feels like new, untested code - perhaps there is no<BR>> =
'fix' even available at this time (I'd need to see the arguments =
that<BR>> this is blocking AND we have a fix); and I agree that we =
need to look<BR>> at 'Blocking' bugs that are still open to see if we =
agree they are still<BR>blocking - or move them out.<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 =
through all<BR>kinds of tests (I wish I could make the rest of them go =
through these as<BR>well, but time is severely limited atm).<BR>If this =
raises concern about the inclusion of the latest translations =
for<BR>other languages, I am currently working on a system for building =
"language<BR>packs" (single archives), which can simply be installed in =
any Qemu<BR>image/XO/sugar-jhbuild setup, so that anyone can try out the =
latest<BR>translations for any of our supported language whenever they =
wish to.<BR><BR>However, "cherry-picking" the translations for Spanish =
and Mongolian may<BR>pose a problem, which I'm not sure how to handle. =
The translations were<BR>often committed as parts of huge commits, in =
which other translations also<BR>went in. Maybe someone who's more =
familiar with Git may want to suggest some<BR>ways out =
here.<BR><BR>Thanks,<BR>Sayamindu<BR><BR><BR><BR>--<BR>Sayamindu =
Dasgupta<BR>[<A =
href=3D"http://sayamindu.randomink.org/ramblings">http://sayamindu.random=
ink.org/ramblings</A>]<BR><BR><BR>------------------------------<BR><BR>M=
essage: 3<BR>Date: Mon, 04 Feb 2008 17:59:47 +0100<BR>From: Tomeu Vizoso =
<tomeu at tomeuvizoso.net><BR>Subject: Re: [sugar] What's left for =
Update.1<BR>To: Sayamindu Dasgupta <sayamindu at gmail.com><BR>Cc: =
Sugar List <sugar at laptop.org><BR>Message-ID: =
<1202144387.6057.43.camel at tomeu-thinkpad><BR>Content-Type: =
text/plain<BR><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>Thanks,<BR><BR>Tomeu<BR><BR><BR><BR>-----------------------=
-------<BR><BR>_______________________________________________<BR>Sugar =
mailing list<BR>Sugar at lists.laptop.org<BR><A =
href=3D"http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/l=
istinfo/sugar</A><BR><BR><BR>End of Sugar Digest, Vol 20, Issue =
6<BR>************************************<BR><BR><BR><BR><BR>------------=
------------------<BR><BR>Message: 5<BR>Date: Mon, 4 Feb 2008 14:02:32 =
-0700<BR>From: "drew einhorn" <drew.einhorn at gmail.com><BR>Subject: =
Re: [sugar] Update.1. When What How and Why<BR>To: "Caperton, Idit" =
<idit at worldwideworkshop.org><BR>Cc: Kim Quirk =
<kim at laptop.org>, =
sugar at lists.laptop.org<BR>Message-ID:<BR> &n=
bsp; =
<b93ef9d00802041302p3405951dr5f58f2bbb3734ba8 at mail.gmail.com><BR>Co=
ntent-Type: text/plain; charset=3DISO-8859-1<BR><BR>For an organization =
with a relatively small number of paid employees, and<BR>a huge amount =
of volunteer labor, they are doing an outstanding job =
building<BR>extremely innovative software.<BR><BR>For as long as I have =
been paying attention to the Update.1 schedule, the<BR>due date has been =
Feb. 1. We are only 3 days past that. A lot of the =
pending<BR>items are getting pushed to Update1.1 and will not actually =
affect the Update.1<BR>release date.<BR><BR>For a comparison ask =
yourself:<BR><BR> How many days was the CentOS 5 =
release delayed<BR> with no publicly available status =
reports?<BR><BR> As I recall it was weeks. And =
they we just repackaging<BR> someone else's software =
(RHEL 5), not building brand new<BR> =
software.<BR><BR>Chill!!!!<BR><BR>On Feb 4, 2008 11:41 AM, Caperton, =
Idit <idit at worldwideworkshop.org> wrote:<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: From what we see so =
far, Update.1. has been delayed and delayed and<BR>> delayed =
again.<BR>><BR>> It affects everybody involved. It's pretty tough =
for OLPC management,<BR>> developers, and all OLPC young users =
worldwide. And all know by now - stuff<BR>> do not work well as =
a result.<BR>><BR>> - Where is the Update.1 master plan? And what =
comes after and when?<BR>> - Who keeps track and makes sure we are =
constantly re-evaluating it and<BR>> documenting changes in =
decisions?<BR>> - Is it well-strategized and well-monitored against =
the strategy?<BR>> - How does s--t gets done and optimized in this =
messy open system?<BR>> - Even decentralized system needs =
organizational management - What did OLPC<BR>> software team learned =
so far?<BR>> - Where are the pages with reflections on lessons =
learned?<BR>> - How are decisions about what's in or out being =
made?<BR>> - Where are the software-release-phases with dates for =
2008?<BR>> - Is there a clear schedule and list of deliverables with =
dates for 2008?<BR>><BR>> I know I know -- I am taking a big risk =
by sending this kind of alarming<BR>> message to the entire global =
Sugar List.<BR>><BR>> But please remember that I am sending it in =
order to shake the existing<BR>> system, as a serious call for =
change, to be provocative, and get you all to<BR>> think about it =
positively.<BR>><BR>> - and, most important, I do it with lots of =
love and care for the XO and the<BR>> OLPC movement at =
large.<BR>><BR>> Idit Harel Caperton<BR>> President & =
Founder<BR>> World Wide Workshop<BR>><BR>> -----Original =
Message-----<BR>> From: sugar-bounces at lists.laptop.org [<A =
href=3D"mailto:sugar-bounces at lists.laptop.org">mailto:sugar-bounces at lists=
.laptop.org</A>]<BR>> On Behalf Of =
sugar-request at lists.laptop.org<BR>> Sent: Monday, February 04, 2008 =
12:00 PM<BR>> To: sugar at lists.laptop.org<BR>> Subject: Sugar =
Digest, Vol 20, Issue 6<BR>><BR>> Send Sugar mailing list =
submissions to<BR>> =
sugar at lists.laptop.org<BR>><BR>> To subscribe or unsubscribe via =
the World Wide Web, =
visit<BR>> <A =
href=3D"http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/l=
istinfo/sugar</A><BR>> or, via email, send a message with subject or =
body 'help' to<BR>> =
sugar-request at lists.laptop.org<BR>><BR>> You can reach the person =
managing the list =
at<BR>> =
sugar-owner at lists.laptop.org<BR>><BR>> When replying, please edit =
your Subject line so it is more specific than<BR>> "Re: Contents of =
Sugar digest..."<BR>><BR>><BR>> Today's =
Topics:<BR>><BR>> 1. Re: What's left for =
Update.1 (Kim Quirk)<BR>> 2. Re: What's left for =
Update.1 (Sayamindu Dasgupta)<BR>> 3. Re: What's =
left for Update.1 (Tomeu Vizoso)<BR>><BR>><BR>> =
----------------------------------------------------------------------<BR=
>><BR>> Message: 1<BR>> Date: Mon, 4 Feb 2008 10:51:41 =
-0500<BR>> From: "Kim Quirk" <kim at laptop.org><BR>> Subject: =
Re: [sugar] What's left for Update.1<BR>> To: jg at laptop.org<BR>> =
Cc: Sugar List <sugar at laptop.org>, OLPC Developer's =
List<BR>> =
<devel at laptop.org><BR>> =
Message-ID:<BR>> =
<9073bf100802040751n2654ff44i19b418280e850b75 at mail.gmail.com><BR>&g=
t; Content-Type: text/plain; charset=3D"iso-8859-1"<BR>><BR>> =
Jim,<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>> People can argue otherwise (I'm open to a good =
discussion), but my<BR>> recommendation is to get this build out, =
with all the known issues well<BR>> documented.<BR>><BR>> =
Kim<BR>><BR>><BR>> On Jan 31, 2008 10:11 PM, Jim Gettys =
<jg at laptop.org> wrote:<BR>><BR>> > For comment and =
discussion, here are the showstoppers I know of for<BR>> > getting =
Update.1 finished. If you think there are others, please<BR>> =
> speak 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>> =
> &nb=
sp; (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=3D"http://dev.laptop.org/ticket/6136">http://dev.laptop.org/ticket/6=
136</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<BR>> > that come up with =
updated activities).<BR>> ><BR>> > 4 - we previously =
(without Dave Woodhouse being available to add to<BR>> > =
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 If everyone arrives at<BR>> > school running =
local link and resumed quickly, the network might melt<BR>> > from =
mdns mesh traffic's interaction with the mesh's implementation =
of<BR>> > mutlicast. We've upped the multicast bitrate for =
multicast as a band<BR>> > aid, until we can dynamically adjust =
the bitrate. But the fundamental<BR>> > issue comes that in =
large, dense school environments, can't expect<BR>> > multicast to =
scale far enough, and should be using unicast to a<BR>> > presence =
server (jabber in our current case) to 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<BR>> > school server, switch from Salut to =
Gabble for presence service<BR>> 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,<BR>> > and the kids presumably will want internet =
access and switch over when<BR>> > they arrive. But I'm not =
very confident that this will always work in<BR>> > large =
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>> > Devel at lists.laptop.org<BR>> > <A =
href=3D"http://lists.laptop.org/listinfo/devel">http://lists.laptop.org/l=
istinfo/devel</A><BR>> ><BR>> -------------- next part =
--------------<BR>> An HTML attachment was scrubbed...<BR>> =
URL:<BR>> <A =
href=3D"http://lists.laptop.org/pipermail/sugar/attachments/20080204/0745=
1d8a/attach">http://lists.laptop.org/pipermail/sugar/attachments/20080204=
/07451d8a/attach</A><BR>> ment-0001.htm<BR>><BR>> =
------------------------------<BR>><BR>> Message: 2<BR>> Date: =
Mon, 4 Feb 2008 22:20:40 +0530<BR>> From: "Sayamindu Dasgupta" =
<sayamindu at gmail.com><BR>> Subject: Re: [sugar] What's left for =
Update.1<BR>> To: "Kim Quirk" <kim at laptop.org><BR>> Cc: OLPC =
Developer's List <devel at laptop.org>, Sugar =
List<BR>> =
<sugar at laptop.org><BR>> =
Message-ID:<BR>> =
<a1314bfe0802040850n1b82eab2tcf5f68db16376b4a at mail.gmail.com><BR>&g=
t; Content-Type: text/plain; charset=3DUTF-8<BR>><BR>> 2008/2/4 =
Kim Quirk <kim at laptop.org>:<BR>> > Jim,<BR>> > I think =
this is way too much stuff for Update.1. We are in code<BR>> > =
freeze. We have items 1 and 2 scheduled to go into RC2; I would<BR>> =
> suggest that we ONLY pick up Spanish, where we really fell short =
in<BR>> > the current build; I don't agree with holding up this =
build for either<BR>> > 4 or 5, as this feels like new, untested =
code - perhaps there is no<BR>> > 'fix' even available at this =
time (I'd need to see the arguments that<BR>> > this is blocking =
AND we have a fix); and I agree that we need to look<BR>> > at =
'Blocking' bugs that are still open to see if we agree they are =
still<BR>> blocking - or move them out.<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 through all<BR>> kinds of tests (I wish I could make =
the rest of them go through these as<BR>> well, but time is severely =
limited atm).<BR>> If this raises concern about the inclusion of the =
latest translations for<BR>> other languages, I am currently working =
on a system for building "language<BR>> packs" (single archives), =
which can simply be installed in any Qemu<BR>> image/XO/sugar-jhbuild =
setup, so that anyone can try out the latest<BR>> translations for =
any of our supported language whenever they wish to.<BR>><BR>> =
However, "cherry-picking" the translations for Spanish and Mongolian =
may<BR>> pose a problem, which I'm not sure how to handle. The =
translations were<BR>> often committed as parts of huge commits, in =
which other translations also<BR>> went in. Maybe someone who's more =
familiar with Git may want to suggest some<BR>> ways out =
here.<BR>><BR>> Thanks,<BR>> =
Sayamindu<BR>><BR>><BR>><BR>> --<BR>> Sayamindu =
Dasgupta<BR>> [<A =
href=3D"http://sayamindu.randomink.org/ramblings">http://sayamindu.random=
ink.org/ramblings</A>]<BR>><BR>><BR>> =
------------------------------<BR>><BR>> Message: 3<BR>> Date: =
Mon, 04 Feb 2008 17:59:47 +0100<BR>> From: Tomeu Vizoso =
<tomeu at tomeuvizoso.net><BR>> Subject: Re: [sugar] What's left =
for Update.1<BR>> To: Sayamindu Dasgupta =
<sayamindu at gmail.com><BR>> Cc: Sugar List =
<sugar at laptop.org><BR>> Message-ID: =
<1202144387.6057.43.camel at tomeu-thinkpad><BR>> Content-Type: =
text/plain<BR>><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>> Thanks,<BR>><BR>> =
Tomeu<BR>><BR>><BR>><BR>> =
------------------------------<BR>><BR>> =
_______________________________________________<BR>> Sugar mailing =
list<BR>> Sugar at lists.laptop.org<BR>> <A =
href=3D"http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/l=
istinfo/sugar</A><BR>><BR>><BR>> End of Sugar Digest, Vol 20, =
Issue 6<BR>> =
************************************<BR>><BR>><BR>> =
_______________________________________________<BR>> Sugar mailing =
list<BR>> Sugar at lists.laptop.org<BR>> <A =
href=3D"http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/l=
istinfo/sugar</A><BR>><BR><BR><BR><BR>--<BR>Drew =
Einhorn<BR><BR><BR>------------------------------<BR><BR>________________=
_______________________________<BR>Sugar mailing =
list<BR>Sugar at lists.laptop.org<BR><A =
href=3D"http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/l=
istinfo/sugar</A><BR><BR><BR>End of Sugar Digest, Vol 20, Issue =
7<BR>************************************<BR></FONT></P></DIV></BODY></HT=
ML>
------_=_NextPart_001_01C86774.572CF310--
More information about the Sugar-devel
mailing list