Re: automatic reminder of 'software update' when installing a new build

2009-01-07 Thread Ixo X oxI
I second... on the idea of checking for network, before putting up the
'software update' dialog box.  It certainly annoys me to no end, when my
network needs a manual key and the dialog box covers over the network view
so I can't connect to my access point.

Or even another idea, is not showing the dialog box on the
network/neighborhood view.  So I can select it, then switch back to home
view and continue with the update?

-iXo

On Tue, Jan 6, 2009 at 11:49, Eben Eliason e...@laptop.org wrote:

 On Thu, Dec 25, 2008 at 1:42 AM, Mikus Grinbergs mi...@bga.com wrote:
  Visited a friend, and helped him install a new build in his XO.  The
  first time the new build completed booting, he was presented with an
  action bar (to request software update) near the top of Home View.
 
  It so happened that the XO had not automatically connected to my
  friend's wireless AP - but he did not realize this.  Being
  well-meaning, he clicked the rightmost button ('Check now') in the
  action bar -- there was some software processing and then a Could
  not access the network message -- he needed to exit through Control
  Panel to get back to Home View (and never saw the action bar again).
 
 
  The software update facility assumes that a connection to the
  network is already available when it gets to run.  If conditions are
  such that the network connection has *not* been set up when booting
  completes, should the action bar to request software update still
  be automatically presented as the first thing the user sees ?

 Good question.

 Perhaps the cleanest option is to have the chunk of code which
 displays the dialog check for a network connection first, and short
 circuit when one isn't found.  In this manner, the update alert will
 only appear when a connection is available in the first place.
 Chances are good that most people using the laptops will get online
 sooner than later anyway.

 - Eben


  mikus
 
  ___
  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

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


Re: Stop Button not working for my application

2009-01-07 Thread Tomeu Vizoso
2009/1/6 shivaprasad javali jbs...@gmail.com:
 Hi,

  I have ported my application running on Linux to the XO. The
 application runs alright but when I click on the stop button( The one
 provided by sugar and not the one present in my application) the application
 doesn't shutdown like other applications and I don't know why. What really
 happens when we press the stop button corresponding to an activity. What
 signals are sent to the activity?

With so little information about what you are trying to do, I cannot
give an appropriate answer to your questions.

But perhaps will be useful for you to look at the log of your activity
in ~/.sugar/default/logs and ask here for help if you cannot interpret
it (pasting the contents of that file).

HTH,

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


Re: [Testing] Please help test our pre-release build of 8.2.1

2009-01-07 Thread Ixo X oxI
Note:
   I olpc-update to  staging-9 .

So far works great. able to find my favorite marked access point, after two
reboots.

Seem to work better/faster that staging-7  (or speed could be my
imagination? :)

However, found a 'bug/typo'  in  Browse / Library file
 /home/olpc/.library_pages/index.html

 Linkage:  Software Repository goes to TRAC  (i.e. dev.laptop.org)  by
mistake .

Is this a bug or a feature ?  :)

Icons on home view still re-arranged from build 767 view...

Continuing my testing... will report if I find anything else.

-iXo

On Sun, Jan 4, 2009 at 23:17, Ixo X oxI i...@myna.ws wrote:

 FYI,
   Downloading 8.2.1 (staging-7) now on an XO currently running with 8.2
 (build 767) .

 Will report on anything out of the ordinary when I play with it tomorrow.
 :)
 -iXo

 On Fri, Jan 2, 2009 at 08:09, Brian Pepple bpep...@fedoraproject.orgwrote:

 Hi All,

 A pre-release build of 8.2.1 is now available for testing. It has passed
 an initial smoke test and now needs broader testing.

 The build download and problem reporting instructions are here:
 http://wiki.laptop.org/go/Friends_in_testing#Current_status

 The very early draft release notes are here:
 http://wiki.laptop.org/go/Release_Notes/8.2.1

 Please send a note to the list if you try this build even if you don't
 find anything interesting. We want to measure our test capacity.

 Thanks,
 /B
 --
 Brian Pepple bpep...@fedoraproject.org

 https://fedoraproject.org/wiki/User:Bpepple
 gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
 BD5E 6F9E 8688 E668 8F5B  CBDE 326A E936 810C C15E

 ___
 Testing mailing list
 test...@lists.laptop.org
 http://lists.laptop.org/listinfo/testing



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


File bugs, don't fix 'em.

2009-01-07 Thread John Gilmore
genesee wrote:
  before the mesh search cycle is done, the 'looking for a mesh' keeps
  blinking forever while my wifi is solid. If I let the mesh search run it's
  course, (while I'm doing something else ...it takes a few minutes), then
  there's just my solid wifi circle in my frame.
 
 That sounds like a bug (the perpetual blinking).  Manual intervention
 must be preventing some signal from getting through; we should
 definitely fix that so the states of both devices are consistent.
 File a ticket? :)  Thanks.
 
 - Eben

Why would anyone bother to file a ticket about this?  One was filed
*15 months* ago, reported fixed when it wasn't actually, reopened
three months ago, and is still not fixed.  See
http://dev.laptop.org/ticket/4074 .  You yourself didn't look for an
existing ticket before suggesting that this user, who was nice enough
to help you debug your product, file yet another one.

The same bug has likely been reported in #5459 (13 months ago), #6872
(6 months ago), #6944 (8 months ago), and almost certainly more often
(I got tired of wasting my time looking).  None of these bugs has been
altered in any way in the last *THREE MONTHS*.  It's common knowledge
among users that there's a bogus mesh icon that blinks sometimes.
Everyone has learned to ignore it, including those responsible for
fixing it.

It seems to take special chivvying to get almost any bug report looked
at by a developer.  (I've filed a lot of bugs and chivvied a lot of
developers.)  It seems to me that in programmer culture, when there's
nobody measuring progress by bugs actually fixed over the last week or
month, generally bugs don't get fixed.  This was as true at Cygnus as
at OLPC (the difference is that significant Cygnus revenue came from
top-notch bug support, so mgmt paid a lot more attention to it; we
wrote the first free software bug tracker, PRMS, for example).  Here's
*everything* that happened in TRAC since before the New Year:

  
http://dev.laptop.org/timeline?from=01%2F07%2F09daysback=8ticket=onmilestone=onwiki=onupdate=Update

The latest XO release 8.2.0 has major bugs that make the whole machine
lock up; that make it impossible or painful to use with some encrypted
WiFi AP's; etc.  The memory lockup is a *regression* that didn't exist
in the prior release.  Since fixes for these are not going into the
current priority release (8.2.1), nobody is bothering with them.  Only
when it's the last week of the release will anybody bother looking at
bug lists(*) -- and then it'll be obvious that the release can't possibly
go out so broken, so the schedule must be slipped.  Well, no, the
time to fix the big bugs was over the last month and over the next
month.  At least we have half that time left.

Eben, going to fix, not just file, any bugs this week?   :-)

John

(*): Exceptions: cjb, dsd and dsaxena have pushed along some fixes for
big longstanding power-related bugs in the last month.  Tho we have
not improved either battery life or our ability to measure it -- at
all -- over 8.2.0 yet, with only a month to go.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: March date realistic ?

2009-01-07 Thread Daniel Drake
On Wed, Jan 7, 2009 at 2:07 AM, Mikus Grinbergs mi...@bga.com wrote:
 There's about 35 normal workdays between the end of XOCamp
 and the proposed date for factory-release.  As a mere sampling
 of the distance that ought to be covered, I'm listing a dozen
 regressions (things that worked in 767 but do not in 2615):

  -  No mesh
  -  No GUI for moving files USB -- Journal
  -  No video
  -  sugar-install-bundle fails
  -  page-up in Terminal gets overdone
  -  Journal key (Magnifying glass) takes too long to act
  -  Help Activity fails
  -  Can't launch Terminal if /etc/olpc-security not present
  -  Record Activity gets X system error
  -  Incomplete GUI for controlling resources
  -  Initial state of Power controls shown wrong
  -  Various Activities do not launch on f10

Please ensure there are tickets filed for all of these. All except the
first 2 are news to me, although I have been a bit behind lately and
can't claim to have given joyride extensive use.

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


Re: automatic reminder of 'software update' when installing a new build

2009-01-07 Thread Daniel Drake
On Thu, Dec 25, 2008 at 6:42 AM, Mikus Grinbergs mi...@bga.com wrote:
 The software update facility assumes that a connection to the
 network is already available when it gets to run.  If conditions are
 such that the network connection has *not* been set up when booting
 completes, should the action bar to request software update still
 be automatically presented as the first thing the user sees ?

This is http://dev.laptop.org/ticket/7947

It has been known for a while, but is non-trivial to implement and
nobody has stepped up so far. It is also not quite as simple as
delaying the update message: after an OS upgrade, it is important to
inform the user straight away that their activities might not work
until they run the activity updater.

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


Re: [Sugar-devel] p2p stream tubes

2009-01-07 Thread Bert Freudenberg
(cc'ing olpc)

On 07.01.2009, at 12:42, Guillaume Desmottes wrote:

 Le mercredi 07 janvier 2009 à 12:22 +0100, Bert Freudenberg a écrit :
 On 07.01.2009, at 12:13, Guillaume Desmottes wrote:

 Hi guys,

 I released telepathy-gabble 0.7.18 yesterday which implements a
 long-awaited feature: peer to peer connections in stream tubes!

 Great!

 Please feel free to test this new version and report any problem you
 could have.


 Are you going to put this in OLPC's Joyride? Didn't see 7.17 there,
 it's still at 7.16.

 I'm not really following Joyride's dev cycle but yes, it would be nice
 to have it if possible. So it would be great if someone can upgrade  
 the
 package.


Looks like 0.7.17 and 0.7.18 are only tagged for Fedora 11 but not for  
olpc4:

http://kojipkgs.fedoraproject.org/packages/telepathy-gabble/

Could someone fix this?

- Bert -


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


Why olpc user is locked?

2009-01-07 Thread Emiliano Pastorino
Hi everyone,

I was wondering, why olpc user account is locked when creating it?

The thing is I would like to give access to a console in Uruguay's
customized build, as root is password protected. We need that so
the kids/teachers could do some basic maintenance if anything fails
when booting sugar.

What would happen if I delete the line in olpc-development.stream:
chroot $INSTALL_ROOT /usr/bin/passwd -l olpc
and add this one:
chroot $INSTALL_ROOT /usr/bin/passwd -d olpc
?



-- 
Emiliano Pastorino
LATU - Plan Ceibal
Av. Italia 6201 CP: 11500, Montevideo, Uruguay
Tel: (598 2) 601 3724 int.: 469
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] Presence Server

2009-01-07 Thread Martin Langhoff
Hola Carlos!

2009/1/5 Carlos Dario Isaza Zamudio cdisa...@gmail.com:
 What changes need to be made on the XO side and on the XS side in order for
 this to work.

 So far i installed the idmgr on the XS and changed the line

It should work out-of-the-box, no special configuration needed.

 - what version of the XS have you installed?
 - did you follow the installation instructions? There are important
steps to follow there...

I recommend you try with
http://xs-dev.laptop.org/xs/other/OLPCXS-0.5.1-dev03-i386.iso - (that
is the release candidate for 0.5.1, a bugfix revision to 0.5 ) and
follow the instructions at
http://wiki.laptop.org/go/XS_Installing_Software

cheers,



martin
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: Customized images

2009-01-07 Thread Carlos Dario Isaza Zamudio
Send to china

Carlos Dario Isaza Zamudio::ConTi
Ingeniero Electronico
Proyecto Todos @l Computador
Celular (57) 300 814 9308
Universidad Nacional de Colombia - Sede Manizales
GNU/Linux Registered User #465475
eSSuX - Usuarios y Desarrolladores GNU/Linux UNAL Manizales


On Tue, Jan 6, 2009 at 5:59 PM, Erik Garrison e...@laptop.org wrote:

 On Tue, Jan 06, 2009 at 04:12:39PM -0500, Carlos Dario Isaza Zamudio wrote:
  I'm sorry there was a misunderstanding on my part.
 
  The idea with the images is for manufacturing the computers. In my state
 we
  want to make a kind of customized image with some configuration and send
 for
  manufacturing the computers.
 
  Any ideas?

 Do you mean you want to send an image to the factory in China?

 Or do you mean you want to install a customized image on laptops
 locally?

 Erik

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


Boston address to take delivery on a Dell?

2009-01-07 Thread Jameson Quinn
Sorry to bother the list, but I have to buy a new laptop during XOCamp (old
one finally went totally belly-up). I was thinking of getting a $600 Dell
with Ubuntu. Can anybody give me a mailing address where they could take
delivery on such a machine? Please include the reason why I can trust that
you are really coming to xocamp. (And if you have a free-as-in-toilet couch
http://wiki.laptop.org/go/XO_couchsurfingtoo, that would be even more
excellent).

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


Re: File bugs, don't fix 'em.

2009-01-07 Thread Tomeu Vizoso
I don't know why I'm discussing this here, but anyway.

If someone is giving as much as it's in his hands and even then it's
not enough but that guy chooses to keep going instead of jumping ship,
is it fair to throw shit at him for not being able to give more? Even
more when you probably have no idea about which other responsibilities
that person has apart from fixing and filing bugs.

OLPC has very high and noble goals and their employees and contractors
are working as much as they can despite the ridiculous amount of
resources available. Even if some of them are working in a project
that you don't like, is it really fair to picture them as slackers in
front of all the people?

Is this just obvious to me? Or are there other people that think that
OLPC troubles are due to their workers being incompetent and/or lazy?

Regards,

Tomeu

On Wed, Jan 7, 2009 at 18:01, Wade Brainerd wad...@gmail.com wrote:
 Frustration aside, the purpose and responsibility of management is to
 stay on top of bugs, push people to comment on and fix them, etc.

 It certainly should not be the users' responsibility.  Programmers
 typically don't have the high level appreciation for the project
 status and goals to be able to triage and prioritize, and it also
 takes a lot of their time.

 So in the case where we are frustrated that a bug isn't getting dealt
 with, we should be bugging Greg, and he should be bugging Eben :)

 -Wade
 ___
 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: Fedora Desktop on XO

2009-01-07 Thread Erik Garrison
On Wed, Jan 07, 2009 at 07:47:36AM +0530, Rahul Sundaram wrote:
 Peter Robinson wrote:


 I don't believe that is true at all. I believe XFCE is an install
 option during a full install and there's a fully Fedora blessed XFCE
 spin available from Fedora here http://spins.fedoraproject.org/ . It
 is certainly not the main desktop they support but it is no less
 supported than any other desktop. I think the XFCE SIG (Special
 Interest Group would somewhat disagree
 https://fedoraproject.org/wiki/SIGs/Xfce

 As the maintainer of the the Xfce Live CD as well as a member of the  
 SIG, I can vouch for that. Xfce is a pretty well supported desktop in  
 Fedora in as much as any desktop is. The maintainers take care of bugs  
 quickly, new releases gets pulled in fast etc. We don't have as many  
 people working on it but it is a smaller community upstream as well.

Ok.  This is good to know.  I had heard differently and not pursued more
details.

 One thing, we try not to do, is deviate from upstream and apply many  
 patches like some of the other Xfce based spin-off's do which is a  
 general Fedora policy as well and not something specific to the Xfce 
 team.

My apologies.  I was not well informed.

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


Re: March date realistic ?

2009-01-07 Thread Daniel Drake
Please use reply-to-all

On Wed, Jan 7, 2009 at 5:05 PM, Mikus Grinbergs mi...@bga.com wrote:
 Please ensure there are tickets filed for all of these.
 All except the first 2 are news to me

 Yes, all but one have tickets.  The one that doesn't is GUI for accessing
 removable storage content -- I included it because of publicized complaints
 from teachers in Mongolia and Tuvalu about saving their files to USB.  A
 ticket of mine relating to this topic was closed a while ago with the
 notation A new design is being worked on -- but I'm not sure where this
 new design is documented -- so how might one file a new ticket against a
 non-described capability ?

 

 Besides, what good does a ticket do ?

As I've said before, this is the way that developers prefer to work. I
speak as someone who has worked on a lot of issues similar to the ones
you have described, and someone who intends to continue bug fixing as
time allows. We appreciate your contributions, but it really helps if
you can collaborate with the developers on their preferred platform.

But this is a non-issue, because as you say, tickets are already
filed. Thanks! Now to find some time and resources to fix them  :)

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


Re: Fedora Desktop on XO

2009-01-07 Thread Erik Garrison
On Wed, Jan 07, 2009 at 07:47:36AM +0530, Rahul Sundaram wrote:

 One thing, we try not to do, is deviate from upstream and apply many  
 patches like some of the other Xfce based spin-off's do which is a  
 general Fedora policy as well and not something specific to the Xfce 
 team.

The patches I described (e.g. desktop icon creation) appear to have
been backported from the development version of XFCE.  Is backporting
patches from the mainline XFCE development against policy?

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


Re: automatic reminder of 'software update' when installing a new build

2009-01-07 Thread Mikus Grinbergs
 The software update facility assumes that a connection to the
 network is already available when it gets to run.  If conditions are
 such that the network connection has *not* been set up when booting
 completes, should the action bar to request software update still
 be automatically presented as the first thing the user sees ?
 
 This is http://dev.laptop.org/ticket/7947
 
 It has been known for a while, but is non-trivial to implement and
 nobody has stepped up so far. It is also not quite as simple as
 delaying the update message: after an OS upgrade, it is important to
 inform the user straight away that their activities might not work
 until they run the activity updater.

I agree that the user who installs a new build ought to be 
cautioned.  But the success of the implementation depends entirely 
upon the correct reference list being provided back at the ranch.

I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list 
Activity versions that were *older* than those listed for plain 
G1G1.  And what about customized country deployments -- who will 
make sure that the activity updater accesses the set of Activities 
appropriate to the build someone in the hinterlands is installing ?

mikus

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


Re: March date realistic ?

2009-01-07 Thread Tomeu Vizoso
On Wed, Jan 7, 2009 at 18:16, Daniel Drake d...@laptop.org wrote:
 Please use reply-to-all

 On Wed, Jan 7, 2009 at 5:05 PM, Mikus Grinbergs mi...@bga.com wrote:
 Please ensure there are tickets filed for all of these.
 All except the first 2 are news to me

 Yes, all but one have tickets.  The one that doesn't is GUI for accessing
 removable storage content -- I included it because of publicized complaints
 from teachers in Mongolia and Tuvalu about saving their files to USB.  A
 ticket of mine relating to this topic was closed a while ago with the
 notation A new design is being worked on -- but I'm not sure where this
 new design is documented -- so how might one file a new ticket against a
 non-described capability ?

 

 Besides, what good does a ticket do ?

 As I've said before, this is the way that developers prefer to work. I
 speak as someone who has worked on a lot of issues similar to the ones
 you have described, and someone who intends to continue bug fixing as
 time allows. We appreciate your contributions, but it really helps if
 you can collaborate with the developers on their preferred platform.

 But this is a non-issue, because as you say, tickets are already
 filed. Thanks! Now to find some time and resources to fix them  :)

As an aside, this functionality will be restored when the latest sugar
code gets into joyride.

Regards,

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


Re: File bugs, don't fix 'em.

2009-01-07 Thread Noah Kantrowitz

On Jan 7, 2009, at 2:48 AM, John Gilmore wrote:

 genesee wrote:
 before the mesh search cycle is done, the 'looking for a mesh' keeps
 blinking forever while my wifi is solid. If I let the mesh search  
 run it's
 course, (while I'm doing something else ...it takes a few  
 minutes), then
 there's just my solid wifi circle in my frame.

 That sounds like a bug (the perpetual blinking).  Manual intervention
 must be preventing some signal from getting through; we should
 definitely fix that so the states of both devices are consistent.
 File a ticket? :)  Thanks.

 - Eben

 Why would anyone bother to file a ticket about this?  One was filed
 *15 months* ago, reported fixed when it wasn't actually, reopened
 three months ago, and is still not fixed.  See
 http://dev.laptop.org/ticket/4074 .  You yourself didn't look for an
 existing ticket before suggesting that this user, who was nice enough
 to help you debug your product, file yet another one.

 The same bug has likely been reported in #5459 (13 months ago), #6872
 (6 months ago), #6944 (8 months ago), and almost certainly more often
 (I got tired of wasting my time looking).  None of these bugs has been
 altered in any way in the last *THREE MONTHS*.  It's common knowledge
 among users that there's a bogus mesh icon that blinks sometimes.
 Everyone has learned to ignore it, including those responsible for
 fixing it.

 It seems to take special chivvying to get almost any bug report looked
 at by a developer.  (I've filed a lot of bugs and chivvied a lot of
 developers.)  It seems to me that in programmer culture, when there's
 nobody measuring progress by bugs actually fixed over the last week or
 month, generally bugs don't get fixed.  This was as true at Cygnus as
 at OLPC (the difference is that significant Cygnus revenue came from
 top-notch bug support, so mgmt paid a lot more attention to it; we
 wrote the first free software bug tracker, PRMS, for example).  Here's
 *everything* that happened in TRAC since before the New Year:

  
 http://dev.laptop.org/timeline?from=01%2F07%2F09daysback=8ticket=onmilestone=onwiki=onupdate=Update

Funny, I don't see your name on there either.

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


New joyride build 2616

2009-01-07 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2616

Changes in build 2616 from build: 2615

Size delta: 0.00M

-db4 4.7.25-6.fc10
+db4 4.7.25-7.fc10

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New joyride build 2616

2009-01-07 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2616

Changes in build 2616 from build: 2615

Size delta: 0.00M

-db4 4.7.25-6.fc10
+db4 4.7.25-7.fc10

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: automatic reminder of 'software update' when installing a new build

2009-01-07 Thread Bert Freudenberg

On 07.01.2009, at 18:31, Mikus Grinbergs wrote:

 I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list
 Activity versions that were *older* than those listed for plain
 G1G1.

That's exactly as it is supposed to work. G1G1 lists dev versions,  
G1G1/8.2 the stable versions tested with 8.2.


- Bert -


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


New joyride build 2617

2009-01-07 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2617

Changes in build 2617 from build: 2616

Size delta: 0.00M

-glibc 2.9-3
+glibc 2.9-4
-glibc-common 2.9-3
+glibc-common 2.9-4

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Fedora Desktop on XO

2009-01-07 Thread Rahul Sundaram
Erik Garrison wrote:
 On Wed, Jan 07, 2009 at 07:47:36AM +0530, Rahul Sundaram wrote:
 One thing, we try not to do, is deviate from upstream and apply many  
 patches like some of the other Xfce based spin-off's do which is a  
 general Fedora policy as well and not something specific to the Xfce 
 team.
 
 The patches I described (e.g. desktop icon creation) appear to have
 been backported from the development version of XFCE.  Is backporting
 patches from the mainline XFCE development against policy?

There isn't a strict policy against anything, there is a set of 
recommendations outlined at

http://fedoraproject.org/wiki/PackageMaintainers/WhyUpstream
https://fedoraproject.org/wiki/Packaging/Guidelines#All_patches_should_have_an_upstream_bug_link_or_comment

Backporting is usually more accepted since the upstream path is clear 
and we don't have carry them forever. If you have specific suggestions 
(and pointers to those patches if any), then please report them in 
bugzilla and the maintainers involved can consider them on a case by 
case basis.

If you wish to discuss ideas, post to fedora-devel list or ping nirik 
(Kevin Fenzi) in #fedora-devel. I am mether on irc and available on all 
the usual channels as well.

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


Re: automatic reminder of 'software update' when installing a new build

2009-01-07 Thread Mikus Grinbergs
 I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list
 Activity versions that were *older* than those listed for plain
 G1G1.
 
 That's exactly as it is supposed to work. G1G1 lists dev versions,
 G1G1/8.2 the stable versions tested with 8.2.

o.k.

My intuitive thinking (from the viewpoint of a customer) had been 
that G1G1 would denominate the software versions packaged for the 
systems delivered to participants in the fall 2007 offering, whereas 
G1G1/8.2 would denominate the software versions packaged for the 
systems delivered to participants in the fall 2008 offering.

mikus

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


Will OLPC survive 2009 ? Half of OLPC laid off, others get salary cuts. Sugar development stops at OLPC

2009-01-07 Thread Ton van Overbeek
Have you seen the blog entry
http://blog.laptop.org/2009/01/07/refocusing-on-our-mission/ ?
See also 
http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html
and all
the other blogs (engadget, gizmodo, pc world, ...).

It does not look very good.
Sugar seems to be now completely left to Sugar Labs,
support for the large deployments is outsourced/spun off, etc.
I have no idea what this means for the ongoing work for 8.2.1 and 9.1
and how this will affect XO-camp.

For everybody at OLPC affected I wish you all the best for the future and
I hope the original OLPC ideas will survive in one form or an other.

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


Re: File bugs, don't fix 'em.

2009-01-07 Thread genesee

Whoa, now! I didn't mean to open a can of worms...

I searched Trac quite a while ago about this and was only reminded by Mikus'
post and foolishly decided to add my 2 cents worth. See what happens when I
reply? The 'official' Forum would be a better venue for my input if there
was more activity there, (the 'News Forum is brutal, slow, ugly and useless
on my xo). The politics and dynamics of olpc v. sugarlabs v. foss v.
University of Oregon Fighting Ducks v. G1G1 has never been clear to me. I
have learned which authors to pay attention to on the lists. Walter, of
course, is my hero. Funny, can't recall a single post by NN? Some I pursue
and trust are Mikus, cscott, Tomeu, Michael Stone, skierpage, AuntiMame,
whatshisface at S.F. State and a few others. Hate to see y'all bickering.
You guys rock!

Sure there is something wrong...but it is always thus. Is the Media Lab
Vallhalla? Was PARC heaven on earth? Is Xanadu, well, Xanadu? (btw, where
the hell is Ted Nelson and why isn't he here?)



Tomeu Vizoso-2 wrote:
 
 I don't know why I'm discussing this here, but anyway.
 
 If someone is giving as much as it's in his hands and even then it's
 not enough but that guy chooses to keep going instead of jumping ship,
 is it fair to throw shit at him for not being able to give more? Even
 more when you probably have no idea about which other responsibilities
 that person has apart from fixing and filing bugs.
 
 OLPC has very high and noble goals and their employees and contractors
 are working as much as they can despite the ridiculous amount of
 resources available. Even if some of them are working in a project
 that you don't like, is it really fair to picture them as slackers in
 front of all the people?
 
 Is this just obvious to me? Or are there other people that think that
 OLPC troubles are due to their workers being incompetent and/or lazy?
 
 Regards,
 
 Tomeu
 
 On Wed, Jan 7, 2009 at 18:01, Wade Brainerd wad...@gmail.com wrote:
 Frustration aside, the purpose and responsibility of management is to
 stay on top of bugs, push people to comment on and fix them, etc.

 It certainly should not be the users' responsibility.  Programmers
 typically don't have the high level appreciation for the project
 status and goals to be able to triage and prioritize, and it also
 takes a lot of their time.

 So in the case where we are frustrated that a bug isn't getting dealt
 with, we should be bugging Greg, and he should be bugging Eben :)

 -Wade
 ___
 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
 
 

-- 
View this message in context: 
http://n2.nabble.com/automatic-reminder-of-%27software-update%27-when-installing-a-new-build-tp1802177p2126188.html
Sent from the Software development mailing list archive at Nabble.com.

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


Re: Journal integration for Scratch

2009-01-07 Thread Philipp Kocher
Bert Freudenberg wrote:
 On 18.12.2008, at 08:08, Philipp Kocher wrote:

 One more thing, the scratch icon is not shown in the journal for files
 with the scratch mimetype. I think the file
 /usr/share/sugar/data/mime.defaults has to be adapted to include the
 scratch-mimetype.
 
 
 It just has to be listed in the activity bundle's info file:
 
 http://wiki.laptop.org/go/Activity_bundles#.info_File_Format
 
 - Bert -
 
 
I added the mime_types attribute to the activities.info file and the 
icon attribute is set as well. But still the Scratch icon is not shown 
in the Journal (the default octet-stream icon is shown) even so the 
Scratch mime-type is set in the metadata file in the datastore.

I think the problem is connected to the gtk theme (gtk-update-icon-cache 
and update-mime-database). e.g. etoys has file etoys.xml in 
/usr/share/mime/packages and probably the icon in the icon cache.

How can I put the icon in the icon-cache?

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


Re: Will OLPC survive 2009 ? Half of OLPC laid off, others get salary cuts. Sugar development stops at OLPC

2009-01-07 Thread genesee

Judging by my Google Alert for 'olpc', the whole thing failed in early 2008!
Whoever is the OLPC Steve Jobs might could use a John Sculley.
Seriously, I feel for the OLPC folks and wish them the best. This past
October I had to take a demotion/pay cut at my crappy retail job or join the
unemployment lines. Glad I did G1G1 in 2007, ain't no way I could afford it
this time around.
 

Ton van Overbeek wrote:
 
 Have you seen the blog entry
 http://blog.laptop.org/2009/01/07/refocusing-on-our-mission/ ?
 See also
 http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html
 and all
 the other blogs (engadget, gizmodo, pc world, ...).
 
 It does not look very good.
 Sugar seems to be now completely left to Sugar Labs,
 support for the large deployments is outsourced/spun off, etc.
 I have no idea what this means for the ongoing work for 8.2.1 and 9.1
 and how this will affect XO-camp.
 
 For everybody at OLPC affected I wish you all the best for the future and
 I hope the original OLPC ideas will survive in one form or an other.
 
 Ton van Overbeek
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel
 
 

-- 
View this message in context: 
http://n2.nabble.com/Will-OLPC-survive-2009---Half-of-OLPC-laid-off%2C-others-get-salary-cuts.-Sugar-development-stops-at-OLPC-tp2126060p2126369.html
Sent from the Software development mailing list archive at Nabble.com.

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


Re: Will OLPC survive 2009 ? Half of OLPC laid off, others get salary cuts. Sugar development stops at OLPC

2009-01-07 Thread david
On Wed, 7 Jan 2009, Ton van Overbeek wrote:

 Have you seen the blog entry
 http://blog.laptop.org/2009/01/07/refocusing-on-our-mission/ ?
 See also 
 http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html
 and all
 the other blogs (engadget, gizmodo, pc world, ...).

 It does not look very good.
 Sugar seems to be now completely left to Sugar Labs,

I don't think that this is any surprise. wasn't this already in the plans?

it's also nothing like what the headlines are stating  (OLPC abandons 
Sugar)

 support for the large deployments is outsourced/spun off, etc.

a team of people working on the specific area can be better than trying to 
get the attention of a team that's being pulled in many directions trying 
to support many deployments


that being said, cutting half the people and having to cut pay for the 
remainder is not good

but as I understand it the remaining orginization is still going to be 
about twice the size that OLPC was in Q2/Q3 of 2007 when the XO hit mass 
production

 I have no idea what this means for the ongoing work for 8.2.1 and 9.1
 and how this will affect XO-camp.

 For everybody at OLPC affected I wish you all the best for the future and
 I hope the original OLPC ideas will survive in one form or an other.

I agree with both of these points.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


for those recently laid off...

2009-01-07 Thread Albert Cahalan
In case any low-level hackers are included in the layoffs, note
that my employer can hire a good number of them. (if US citizen)
In case you know somebody appropriate who no longer reads devel,
please let him know. People might unsubscribe when laid off, or
might have been subscribed via a now-dead laptop.org address.

Overtime is rare, and paid, so there could be plenty of time for
hacking on personal projects. The work is interesting and varied.
Some will find it to be feel-good work as well.

Since we need multiple people, you don't need to be an expert in
everything. We need versatile hackers with a wide range of skills.
Roughly, desired skills/experience goes something like this:

comfortable with a hex dump
debugger internals
emulator internals, including JIT
compiler internals
assembly for multiple platforms
reverse engineering
internals for multiple OSes
malware internals
network protocols (any and all)
embedded development in general
vulnerability discovery

It wouldn't hurt to be handy with numerous other things: soldering,
AI, WxWidgets, i18n issues, logic analyser, spectrum analyser, etc.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel