Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-05 Thread Sayamindu Dasgupta
On Tue, Mar 4, 2008 at 12:56 PM, Edward Cherlin [EMAIL PROTECTED] wrote:
 On Mon, Mar 3, 2008 at 10:41 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote:
   On 3/4/08, Edward Cherlin [EMAIL PROTECTED] wrote:
  
.snipped
  
  
 You're talking about testing the keyboard layout and fonts. What about
 localization of software?

 According to Pootle, except possibly for XO-Bundled (89%), the Nepali
 localization is not in good shape. The rest of the modules are less
 than half translated, and Etoys less than 1%.

 Sayamindu, how many people do we have working on this?

  

   As per user account stats in Pootle, we have five people signed up for
Nepali translations.

  Is there a way for me to find out these things, or do I have to ask
  you each time?

  Is there a way for me to communicate with these five other than a
  blast to the whole localization mailing list?

  I asked two other questions:



As I mentioned earlier, I am planning on having a per language page -
taking the data from the Pootle database. But I need to take care of
other Pootle related stuff before that.

Thanks,
Sayamindu



-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Benjamin M. Schwartz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

John Gilmore wrote:
| I recommend that once you have developer keys, you leave the machines
| unlocked.  You are going to be running a lot of unsigned builds in the
| future -- you're customizing your builds.

Eventually, there must be a way for countries (and even trials) to get
signed custom builds.  Either they get their own signing keys, or OLPC
offers to sign a nepal.1 branch of tweaked releases.  I understand why
this infrastructure has not yet been built, but it will be needed in order
for Bitfrost to be used at all.

- --Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHzGK8UJT6e6HFtqQRAgrlAJ9t3RWJ0Iy41UB1HG9/QdcgTFfzYACglaxN
oyGyaZ/pTCRANRT7ARB4eVc=
=wuVO
-END PGP SIGNATURE-
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Richard A. Smith
Bryan Berry wrote:
 
 Here is the Rough Test Plan I have in mind
 
 1. Boot into firmware and run test-all

Note that the current shipping firmware can sometimes report false 
positives for sticky keys in the keyboard test.  So if you think you 
have sticky keys upgrade the firmware to Q2D13 and also duplicate the 
test under Linux to verify you really have a sticky key.

 I appreciate any other ideas on testing the XO's, particularly testing
 the batteries and the network.

All the battery failures I've seen can be detected with a full 
charge/discharge cycle.  Unplug the laptop from ext power and let it run 
down until you get a red led or it shuts off then plug up to ext power 
and recharge. Re-charge should take at least 1.5 hours.  Then unplug 
again.  Build 656 should run in idle for 3 to 3.5 hours.  If you get a 
green LED in less than 1.5h or the XO shuts off pre-maturely, or if the 
Red light flashes, then RMA that unit.  If you get an early shutoff you 
might repeat the test.  At least one report of a battery getting better 
after a few cycles.  Not sure if this was just user error or really valid.

If the battery-won't-charge problem is there then the charge time drops 
to 10's of minutes so its a quick re-test.

Right now I'm only interested in units that have _flashing_ red led.  So 
if you get a flashing LED contact me please.  I have plenty of data for 
the other problem.

But if you are curious or think you are getting confusing results you 
can run olpc-logbat and watch the numbers or send them to me and we can 
analyze any issues.

-- 
Richard Smith  [EMAIL PROTECTED]
One Laptop Per Child
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Edward Cherlin
On Sun, Mar 2, 2008 at 11:38 PM, Bryan Berry [EMAIL PROTECTED] wrote:
 Hey guys,

  Nepal should receive its shipment of 200 XO's in roughly 14 days from
  today.

  Here is the Rough Test Plan I have in mind

  1. Boot into firmware and run test-all
  2. Load customized image based on 656 build
  3. Test localization on each XO (read Nepali, type in Nepali)

You're talking about testing the keyboard layout and fonts. What about
localization of software?

According to Pootle, except possibly for XO-Bundled (89%), the Nepali
localization is not in good shape. The rest of the modules are less
than half translated, and Etoys less than 1%.

Sayamindu, how many people do we have working on this? What
organizations are involved? Why aren't there more?

  4. Test that basic activities like browse, E-Paati, EToys work
  5. Associate XO's w/ school server via active antenna, test basic school
  services, cache, moodle, file downloads, chat
...
  We will have two pilot schools. One w/ 110 students and the other w/ 50
  students.

And 40 spares? Any idea what you want to do with them?

  Notes: These XO's may have been tested thoroughly at the factory but I
  would prefer to at least run the firmware's test-all command after the
  XO's arrive in Nepal. I have been a sysadmin for about 10 years and I
  have always run some kind of diagnostics on new hardware before I put it
  into production.

Quite right.

  Thanks in advance for everyone's help.


  --
  Bryan W. Berry
  Systems Engineer
  OLE Nepal, http://www.olenepal.org

  ___
  Devel mailing list
  Devel@lists.laptop.org
  http://lists.laptop.org/listinfo/devel




-- 
Edward Cherlin
End Poverty at a Profit by teaching children business
http://www.EarthTreasury.org/
The best way to predict the future is to invent it.--Alan Kay
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Bryan Berry
We need to do a lot of work on the localization, a lot. There hopefully
will be a renewed effort on this from our team starting next week.

There aren't 40 spare XO's. A chunk of those will go to the teachers
(10-15) leaving some for spares and we may have a special class for kids
not in the lucky grades 2  6 can learn how to use the XO.

Bryan
OLE Nepal
http://www.olenepal.org

On Mon, 2008-03-03 at 18:49 -0800, Edward Cherlin wrote:
 On Sun, Mar 2, 2008 at 11:38 PM, Bryan Berry [EMAIL PROTECTED] wrote:
  Hey guys,
 
   Nepal should receive its shipment of 200 XO's in roughly 14 days from
   today.
 
   Here is the Rough Test Plan I have in mind
 
   1. Boot into firmware and run test-all
   2. Load customized image based on 656 build
   3. Test localization on each XO (read Nepali, type in Nepali)
 
 You're talking about testing the keyboard layout and fonts. What about
 localization of software?
 
 According to Pootle, except possibly for XO-Bundled (89%), the Nepali
 localization is not in good shape. The rest of the modules are less
 than half translated, and Etoys less than 1%.
 
 Sayamindu, how many people do we have working on this? What
 organizations are involved? Why aren't there more?
 
   4. Test that basic activities like browse, E-Paati, EToys work
   5. Associate XO's w/ school server via active antenna, test basic school
   services, cache, moodle, file downloads, chat
 ...
   We will have two pilot schools. One w/ 110 students and the other w/ 50
   students.
 
 And 40 spares? Any idea what you want to do with them?
 
   Notes: These XO's may have been tested thoroughly at the factory but I
   would prefer to at least run the firmware's test-all command after the
   XO's arrive in Nepal. I have been a sysadmin for about 10 years and I
   have always run some kind of diagnostics on new hardware before I put it
   into production.
 
 Quite right.
 
   Thanks in advance for everyone's help.
 
 
   --
   Bryan W. Berry
   Systems Engineer
   OLE Nepal, http://www.olenepal.org
 
   ___
   Devel mailing list
   Devel@lists.laptop.org
   http://lists.laptop.org/listinfo/devel
 
 
 
 

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Sayamindu Dasgupta
On 3/4/08, Edward Cherlin [EMAIL PROTECTED] wrote:

.snipped

 You're talking about testing the keyboard layout and fonts. What about
 localization of software?

 According to Pootle, except possibly for XO-Bundled (89%), the Nepali
 localization is not in good shape. The rest of the modules are less
 than half translated, and Etoys less than 1%.

 Sayamindu, how many people do we have working on this? What
 organizations are involved? Why aren't there more?


As per user account stats in Pootle, we have five people signed up for
Nepali translations.

Thanks,
Sayamindu

-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Edward Cherlin
On Mon, Mar 3, 2008 at 10:41 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote:
 On 3/4/08, Edward Cherlin [EMAIL PROTECTED] wrote:

  .snipped


   You're talking about testing the keyboard layout and fonts. What about
   localization of software?
  
   According to Pootle, except possibly for XO-Bundled (89%), the Nepali
   localization is not in good shape. The rest of the modules are less
   than half translated, and Etoys less than 1%.
  
   Sayamindu, how many people do we have working on this?
  

  As per user account stats in Pootle, we have five people signed up for
  Nepali translations.

Is there a way for me to find out these things, or do I have to ask
you each time?

Is there a way for me to communicate with these five other than a
blast to the whole localization mailing list?

I asked two other questions:

   What organizations are involved?

   Why aren't there more?

Please take a look at the Recruiting Localizers section of the
Localization Wiki page. I want to see the same information for Nepali.
Do I need to do it myself, as I did for Khmer, or can I get some help?

Actually, I want to see the same kind of information for the 60 or so
languages in Pootle, and quite a few more. Is anybody willing? Having
some of you for each language and country spend a little of your time
on gathering information and recruiting others to the cause will get
us through much faster than keeping all your heads down and doing the
work with the few people we have now.


  Thanks,
  Sayamindu

  --
  Sayamindu Dasgupta
  [http://sayamindu.randomink.org/ramblings]




-- 
Edward Cherlin
End Poverty at a Profit by teaching children business
http://www.EarthTreasury.org/
The best way to predict the future is to invent it.--Alan Kay
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel