Re: [Sugar-devel] [PATCH sugar] Control Panel: making about my computer section hardware independent, OLPC #11232

2011-10-18 Thread Simon Schampijer

On 10/17/2011 08:38 PM, Sascha Silbe wrote:

Excerpts from Simon Schampijer's message of 2011-10-17 11:07:13 +0200:


- powerpc is not a popular Sugar platform to make an enormous effort for
supporting it


I wouldn't consider anything we discussed an enormous effort. With
that attitude PowerPC would never be a viable platform. Catch-22.


I knew people would jump on that. The original patch would not have had 
any impact on Sugar running on powerpc, just that the version displayed 
in the CP would not have a meaning. I could have lived with that. Still, 
I am waiting for reports of people running Sugar on powerpc...And I 
don't think *this* is a blocker for them.



- displaying all of the string on both cases (OLPC/powerpc) will likely
confuse people used to the old humanized string that is displayed at current

- the string does always start with CL: CL1 for XO-1, CL1B for XO-1.5,
CL2 for XO-1.75, to differentiate we can do the following:

if: string.startswith('CL') string[6:13]
else: display all of the string


Sounds good enough to me. We don't even need the length check as
foo[6:13] will simply give an empty string if foo is too short. Might be
good to add a comment to that effect, though.


I will send a new full patch.

Regards,
   Simon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH sugar] Control Panel: making about my computer section hardware independent, OLPC #11232

2011-10-18 Thread Simon Schampijer
'/ofw' is not used anymore on the XO, '/proc/device-tree' is used now
instead. Instead of just adjusting for that change we took the
chance to make the section hardware independent.

As the firmware version we display the bios version if available on non XO
hardware. On the XO we display a human readable extraction of what is
found in .../openprom/model. On other architectures (e.g. powerpc) we
display all of the content of that file.

As ethtool has become a depedency of Sugar we can now
display the wireless firmware as well on any hardware.

The serial number is often only readable by root on non-XO
hardware, that is why we do not read it. If the serial number
can not be found on an XO we display the entry as 'Not available'.

The patch has been tested on XO 1, 1.5, 1.75 and on a Thinkpad T61.

Signed-off-by: Simon Schampijer si...@laptop.org
---
 extensions/cpsection/aboutcomputer/model.py |   24 +++---
 extensions/cpsection/aboutcomputer/view.py  |   65 +--
 2 files changed, 49 insertions(+), 40 deletions(-)

diff --git a/extensions/cpsection/aboutcomputer/model.py 
b/extensions/cpsection/aboutcomputer/model.py
index a02eee6..431c9c0 100644
--- a/extensions/cpsection/aboutcomputer/model.py
+++ b/extensions/cpsection/aboutcomputer/model.py
@@ -35,6 +35,7 @@ _NM_DEVICE_TYPE_WIFI = 2
 
 _OFW_TREE = '/ofw'
 _PROC_TREE = '/proc/device-tree'
+_DMI_DIRECTORY = '/sys/class/dmi/id'
 _SN = 'serial-number'
 _MODEL = 'openprom/model'
 
@@ -96,18 +97,29 @@ def print_build_number():
 print get_build_number()
 
 
+def _parse_firmware_number(firmware_no):
+if firmware_no is None:
+firmware_no = _not_available
+else:
+# try to extract Open Firmware version from OLPC style version
+# string, e.g. CL2   Q4B11  Q4B
+if firmware_no.startswith('CL'):
+firmware_no = firmware_no[6:13]
+return firmware_no
+
+
 def get_firmware_number():
 firmware_no = None
 if os.path.exists(os.path.join(_OFW_TREE, _MODEL)):
 firmware_no = _read_file(os.path.join(_OFW_TREE, _MODEL))
+firmware_no = _parse_firmware_number(firmware_no)
 elif os.path.exists(os.path.join(_PROC_TREE, _MODEL)):
 firmware_no = _read_file(os.path.join(_PROC_TREE, _MODEL))
-if firmware_no is None:
-firmware_no = _not_available
-else:
-firmware_no = re.split(' +', firmware_no)
-if len(firmware_no) == 3:
-firmware_no = firmware_no[1]
+firmware_no = _parse_firmware_number(firmware_no)
+elif os.path.exists(os.path.join(_DMI_DIRECTORY, 'bios_version')):
+firmware_no = _read_file(os.path.join(_DMI_DIRECTORY, 'bios_version'))
+if firmware_no is None:
+firmware_no = _not_available
 return firmware_no
 
 
diff --git a/extensions/cpsection/aboutcomputer/view.py 
b/extensions/cpsection/aboutcomputer/view.py
index e5f2f32..257e165 100644
--- a/extensions/cpsection/aboutcomputer/view.py
+++ b/extensions/cpsection/aboutcomputer/view.py
@@ -16,7 +16,6 @@
 # along with this program; if not, write to the Free Software
 # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA
 
-import os
 from gettext import gettext as _
 
 import gtk
@@ -47,8 +46,7 @@ class AboutComputer(SectionView):
 scrollwindow.add_with_viewport(self._vbox)
 self._vbox.show()
 
-if os.path.exists('/ofw'):
-self._setup_identity()
+self._setup_identity()
 
 self._setup_software()
 self._setup_copyright()
@@ -127,37 +125,36 @@ class AboutComputer(SectionView):
 box_software.pack_start(box_sugar, expand=False)
 box_sugar.show()
 
-if os.path.exists('/ofw'):
-box_firmware = gtk.HBox(spacing=style.DEFAULT_SPACING)
-label_firmware = gtk.Label(_('Firmware:'))
-label_firmware.set_alignment(1, 0)
-label_firmware.modify_fg(gtk.STATE_NORMAL,
-  style.COLOR_SELECTION_GREY.get_gdk_color())
-box_firmware.pack_start(label_firmware, expand=False)
-self._group.add_widget(label_firmware)
-label_firmware.show()
-label_firmware_no = gtk.Label(self._model.get_firmware_number())
-label_firmware_no.set_alignment(0, 0)
-box_firmware.pack_start(label_firmware_no, expand=False)
-label_firmware_no.show()
-box_software.pack_start(box_firmware, expand=False)
-box_firmware.show()
-
-box_wireless_fw = gtk.HBox(spacing=style.DEFAULT_SPACING)
-label_wireless_fw = gtk.Label(_('Wireless Firmware:'))
-label_wireless_fw.set_alignment(1, 0)
-label_wireless_fw.modify_fg(gtk.STATE_NORMAL,
-  style.COLOR_SELECTION_GREY.get_gdk_color())
-box_wireless_fw.pack_start(label_wireless_fw, expand=False)
-self._group.add_widget(label_wireless_fw)
-

Re: [Sugar-devel] [PATCH sugar] Control Panel: making about my computer section hardware independent, OLPC #11232

2011-10-18 Thread James Cameron
Reviewed-by: James Cameron qu...@laptop.org

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH sugar] Bring back the Sugar cursor onto the intro screen, OLPC #10712

2011-10-18 Thread Simon Schampijer
This issue has a long history outlined in detail
in [1]. We once moved the xsetroot around to compensate
for SL #1476 but Daniel fixed this in Metacity in
OLPC #10693.

The proposed patch does work for me in Jhbuild and
the latest 0.94 based OLPC build. Both the cursor in
the intro screen and under Sugar are the correct
ones.

[1] http://dev.laptop.org/ticket/10712#comment:3

Signed-off-by: Simon Schampijer si...@laptop.org
---
 bin/sugar-session |9 +
 1 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/bin/sugar-session b/bin/sugar-session
index 8ea195f..d4ccd74 100755
--- a/bin/sugar-session
+++ b/bin/sugar-session
@@ -173,10 +173,6 @@ def setup_keyboard_cb():
 def setup_window_manager():
 logging.debug('STARTUP: window_manager')
 
-# have to reset cursor(metacity sets it on startup)
-if subprocess.call('echo $DISPLAY; xsetroot -cursor_name left_ptr', 
shell=True):
-logging.warning('Can not reset cursor')
-
 if subprocess.call('metacity-message disable-keybindings',
 shell=True):
 logging.warning('Can not disable metacity keybindings')
@@ -204,6 +200,10 @@ def set_fonts():
 settings = gtk.settings_get_default()
 settings.set_property(gtk-font-name, %s %f % (face, size))
 
+def set_cursor():
+if subprocess.call('echo $DISPLAY; xsetroot -cursor_name left_ptr', 
shell=True):
+logging.warning('Can not set cursor')
+
 def main():
 try:
 from sugar import env
@@ -240,6 +240,7 @@ def main():
 os.environ['TZ'] = timezone
 
 set_fonts()
+set_cursor()
 
 # this must be added early, so that it executes and unfreezes the screen
 # even when we initially get blocked on the intro screen
-- 
1.7.4.4

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [Announce] Design Team meeting

2011-10-18 Thread Gonzalo Odiard
Could you look at the toolbars review Manuel and me did in Junin?
http://wiki.sugarlabs.org/go/Talk:Design_Team/Toolbar_Catalog#Gonzalo_and_Manuel.27s_review_at_2011-09-26

Gonzalo

On Mon, Oct 17, 2011 at 9:22 PM, Gary Martin garycmar...@googlemail.comwrote:

 Hi all,

 Just a quick email that the Design Team meeting slipped today, the next
 meeting is now scheduled for the 31st October @ 15:00 UTC. I took the
 opportunity to tidy up the Design Meeting page (using a similar format as
 per the Activity meeting page):

http://wiki.sugarlabs.org/go/Design_Team/Meetings

 The upcoming meeting agenda items are listed, though I'm hoping to start
 some of them in ML threads and try to clear through some offline, before the
 next real-time meeting.

 Regards,
 --Gary
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH sugar] Control Panel: making about my computer section hardware independent, OLPC #11232

2011-10-18 Thread Simon Schampijer

On 10/18/2011 09:48 AM, James Cameron wrote:

Reviewed-by: James Cameronqu...@laptop.org



Acked as well by Sascha on irc, pushed to master and the 0.94 branch.

http://git.sugarlabs.org/sugar/mainline/commit/64aae3b42c259af85db4051aa54c74a1b303f21b

Regards,
   Simon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [Announce] Design Team meeting

2011-10-18 Thread Walter Bender
On Tue, Oct 18, 2011 at 6:58 AM, Gonzalo Odiard gonz...@laptop.org wrote:

 Could you look at the toolbars review Manuel and me did in Junin?

 http://wiki.sugarlabs.org/go/Talk:Design_Team/Toolbar_Catalog#Gonzalo_and_Manuel.27s_review_at_2011-09-26

 Gonzalo


 On Mon, Oct 17, 2011 at 9:22 PM, Gary Martin 
 garycmar...@googlemail.comwrote:

 Hi all,

 Just a quick email that the Design Team meeting slipped today, the next
 meeting is now scheduled for the 31st October @ 15:00 UTC. I took the
 opportunity to tidy up the Design Meeting page (using a similar format as
 per the Activity meeting page):

http://wiki.sugarlabs.org/go/Design_Team/Meetings

 The upcoming meeting agenda items are listed, though I'm hoping to start
 some of them in ML threads and try to clear through some offline, before the
 next real-time meeting.

 Regards,
 --Gary
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel



 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel


I'd also like to discuss some Journal topics, e.g., write to Journal
anytime; activities temporarily mounting directories in the volumes toolbar,
etc.

regards.

-walter


-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] jita.sugarlabs.org planned maintenance downtime, 2011-10-18 03:00 UTC

2011-10-18 Thread Walter Bender
On Mon, Oct 17, 2011 at 11:41 PM, Bernie Innocenti ber...@sugarlabs.orgwrote:

 On Mon, 2011-10-17 at 23:52 +, Aleksey Lim wrote:
  Hi all!
 
  The following services will be inaccessible for planned maintenance.
  For one hour starting from 2011-10-18 03:00 UTC.
 
  cas.sugarlabs.org
  cgit.sugarlabs.org
  git.sugarlabs.org
  chat.sugarlabs.org
  obs.sugarlabs.org
  jabber.sugarlabs.org
  meeting.sugarlabs.org
  sweets.sugarlabs.org
 
  Sorry for inconveniences.

 The maintenance work has been completed, all services should be back
 online. Cheers,


thanks guys.

-walter


 --
 Bernie Innocenti
 Sugar Labs Infrastructure Team
 http://wiki.sugarlabs.org/go/Infrastructure_Team


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH sugar] Bring back the Sugar cursor onto the intro screen, OLPC #10712

2011-10-18 Thread Simon Schampijer
This issue has a long history outlined in detail
in [1]. As stated in the ticket Metacity sets
the cursor after it's startup, so we need to make
sure Metacity is already running before we set the
cursor. This patch does try to set the cursor before
the intro screen is displayed. In my testing this
worked fine in Jhbuild and the latest 0.94 based
OLPC build.

Signed-off-by: Simon Schampijer si...@laptop.org
---
 bin/sugar-session |   12 ++--
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/bin/sugar-session b/bin/sugar-session
index 8ea195f..ec9812a 100755
--- a/bin/sugar-session
+++ b/bin/sugar-session
@@ -182,8 +182,6 @@ def setup_window_manager():
 logging.warning('Can not disable metacity keybindings')
 
 def bootstrap():
-setup_window_manager()
-
 from jarabe.view import launcher
 launcher.setup()
 
@@ -245,6 +243,10 @@ def main():
 # even when we initially get blocked on the intro screen
 gobject.idle_add(unfreeze_dcon_cb)
 
+screen = wnck.screen_get_default()
+screen.connect('window-manager-changed', __window_manager_changed_cb)
+_check_for_window_manager(screen)
+
 intro.check_profile()
 
 start_ui_service()
@@ -261,9 +263,7 @@ def main():
 home_window = homewindow.get_instance()
 home_window.show()
 
-screen = wnck.screen_get_default()
-screen.connect('window-manager-changed', __window_manager_changed_cb)
-_check_for_window_manager(screen)
+bootstrap()
 
 try:
 gtk.main()
@@ -279,7 +279,7 @@ def _check_for_window_manager(screen):
 wm_name = screen.get_window_manager_name()
 if wm_name is not None:
 screen.disconnect_by_func(__window_manager_changed_cb)
-bootstrap()
+setup_window_manager()
 
 
 main()
-- 
1.7.4.4

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH v3 sugar] Journal: don't fail to load if an activity icon is broken (fixes SL#3200)

2011-10-18 Thread Sascha Silbe
If the activity-provided icon could not be loaded, the Journal previously
died on start-up, rendering Sugar effectively unusable. Now we fall back to
the standard icon (in the What filter combo box).

SL#3203 has been filed to remind us to audit the code for similar breakages.

Signed-off-by: Sascha Silbe si...@activitycentral.com
---
v2-v3: Improve warning to mention that we fall back to a default icon.
Created TODO ticket SL#3203, mention it in the description.
v1-v2: Created ticket with test case, mention it in the summary.
No code changes.

 src/jarabe/journal/journaltoolbox.py |   30 ++
 1 files changed, 22 insertions(+), 8 deletions(-)

diff --git a/src/jarabe/journal/journaltoolbox.py 
b/src/jarabe/journal/journaltoolbox.py
index cdf6a77..f22abc5 100644
--- a/src/jarabe/journal/journaltoolbox.py
+++ b/src/jarabe/journal/journaltoolbox.py
@@ -24,6 +24,7 @@ import time

 import gobject
 import gio
+import glib
 import gtk

 from sugar.graphics.palette import Palette
@@ -319,19 +320,32 @@ class SearchToolbar(gtk.Toolbar):

 for service_name in model.get_unique_values('activity'):
 activity_info = registry.get_bundle(service_name)
-if not activity_info is None:
-if os.path.exists(activity_info.get_icon()):
+if activity_info is None:
+continue
+
+if service_name == current_value:
+combo_model = self._what_search_combo.get_model()
+current_value_index = len(combo_model)
+
+# try activity-provided icon
+if os.path.exists(activity_info.get_icon()):
+try:
 self._what_search_combo.append_item(service_name,
 activity_info.get_name(),
 file_name=activity_info.get_icon())
+except glib.GError, exception:
+logging.warning('Falling back to default icon because'
+' %r (%r) has an invalid icon: %s',
+activity_info.get_name(),
+str(service_name), exception)
 else:
-self._what_search_combo.append_item(service_name,
-activity_info.get_name(),
-icon_name='application-octet-stream')
+continue
+
+# fall back to generic icon
+self._what_search_combo.append_item(service_name,
+activity_info.get_name(),
+icon_name='application-octet-stream')

-if service_name == current_value:
-current_value_index = \
-len(self._what_search_combo.get_model()) - 1
 finally:
 self._what_search_combo.handler_unblock(
 self._what_combo_changed_sid)
--
1.7.6.3

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH v4 sugar] Journal: don't fail to load if an activity icon is broken (fixes SL#3200)

2011-10-18 Thread Sascha Silbe
If the activity-provided icon could not be loaded, the Journal previously
died on start-up, rendering Sugar effectively unusable. Now we fall back to
the standard icon (in the What filter combo box).

SL#3203 has been filed to remind us to audit the code for similar breakages.

Signed-off-by: Sascha Silbe si...@activitycentral.com
---
v3-v4: Improved warning wording some more.
v2-v3: Improve warning to mention that we fall back to a default icon.
Created TODO ticket SL#3203, mention it in the description.
v1-v2: Created ticket with test case, mention it in the summary.
No code changes.

 src/jarabe/journal/journaltoolbox.py |   31 +++
 1 files changed, 23 insertions(+), 8 deletions(-)

diff --git a/src/jarabe/journal/journaltoolbox.py 
b/src/jarabe/journal/journaltoolbox.py
index cdf6a77..2aa4153 100644
--- a/src/jarabe/journal/journaltoolbox.py
+++ b/src/jarabe/journal/journaltoolbox.py
@@ -24,6 +24,7 @@ import time

 import gobject
 import gio
+import glib
 import gtk

 from sugar.graphics.palette import Palette
@@ -319,19 +320,33 @@ class SearchToolbar(gtk.Toolbar):

 for service_name in model.get_unique_values('activity'):
 activity_info = registry.get_bundle(service_name)
-if not activity_info is None:
-if os.path.exists(activity_info.get_icon()):
+if activity_info is None:
+continue
+
+if service_name == current_value:
+combo_model = self._what_search_combo.get_model()
+current_value_index = len(combo_model)
+
+# try activity-provided icon
+if os.path.exists(activity_info.get_icon()):
+try:
 self._what_search_combo.append_item(service_name,
 activity_info.get_name(),
 file_name=activity_info.get_icon())
+except glib.GError, exception:
+logging.warning('Falling back to default icon for'
+' what filter because %r (%r) has an'
+' invalid icon: %s',
+activity_info.get_name(),
+str(service_name), exception)
 else:
-self._what_search_combo.append_item(service_name,
-activity_info.get_name(),
-icon_name='application-octet-stream')
+continue
+
+# fall back to generic icon
+self._what_search_combo.append_item(service_name,
+activity_info.get_name(),
+icon_name='application-octet-stream')

-if service_name == current_value:
-current_value_index = \
-len(self._what_search_combo.get_model()) - 1
 finally:
 self._what_search_combo.handler_unblock(
 self._what_combo_changed_sid)
--
1.7.6.3

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH sugar] Control Panel: making about my computer section hardware independent, OLPC #11232

2011-10-18 Thread Frederick Grose
On Tue, Oct 18, 2011 at 2:31 AM, Simon Schampijer si...@schampijer.dewrote:

 On 10/17/2011 08:38 PM, Sascha Silbe wrote:

 Excerpts from Simon Schampijer's message of 2011-10-17 11:07:13 +0200:

  - powerpc is not a popular Sugar platform to make an enormous effort for
 supporting it


 I wouldn't consider anything we discussed an enormous effort. With
 that attitude PowerPC would never be a viable platform. Catch-22.


 I knew people would jump on that. The original patch would not have had any
 impact on Sugar running on powerpc, just that the version displayed in the
 CP would not have a meaning. I could have lived with that. Still, I am
 waiting for reports of people running Sugar on powerpc...


Just for reference,
http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu/PPC
http://wiki.sugarlabs.org/go/Community/Distributions/Fedora#PowerPC_Fedora_16


 And I don't think *this* is a blocker for them.


  - displaying all of the string on both cases (OLPC/powerpc) will likely
 confuse people used to the old humanized string that is displayed at
 current

 - the string does always start with CL: CL1 for XO-1, CL1B for XO-1.5,
 CL2 for XO-1.75, to differentiate we can do the following:

 if: string.startswith('CL') string[6:13]
 else: display all of the string


 Sounds good enough to me. We don't even need the length check as
 foo[6:13] will simply give an empty string if foo is too short. Might be
 good to add a comment to that effect, though.


 I will send a new full patch.


 Regards,
   Simon
 __**_
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.**org Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/**listinfo/sugar-develhttp://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [ASLO] Release FractionBounce-9

2011-10-18 Thread Sugar Labs Activities
Activity Homepage:
http://activities.sugarlabs.org/addon/4488

Sugar Platform:
0.82 - 0.94

Download Now:
http://activities.sugarlabs.org/downloads/file/27663/fractionbounce-9.xo

Release notes:
9

ENHANCEMENTS:
* The ball can be customized from an image in the Journal
* Smoother transitions between levels of difficulty
* Internal refactoring of code to make it easier to read (view source)


Sugar Labs Activities
http://activities.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Sugar Digest 2011-10-18

2011-10-18 Thread Walter Bender
== Sugar Digest ==

1. Daniel Drake has announced the second release candidate of the new OLPC
software release [0], which incorporates the latest Sugar bits. You can
download 'signed' images for testing from: [1-3]. The final release is
scheduled for 1 November.

2. OLPC OZ runs a discussion website on yammer.com for teachers working with
XOs in Australia. It is a nice source of feedback about Sugar and 1-to-1
laptop deployments in general. Recently, there was a posting that referenced
an OLPC News article about a lemon-battery project [4] by Sameer Verma.
There was also a tip of the hat to Guzman Trindad, a teacher in Uruguay, who
built a pulse meter [5]. I am not sure how OLPC News missed all of the other
great work that Guzman has been doing [6] with Turtle Art and sensors [7]
and also the work of Tony Forster [8], who blogs [9] regularly about various
ways to engage children with simple sensor. His most recent posting is about
using the accelerometer on the XO 1.75 as a seismograph. Check it out.

3. While Guzman and Tony have been using the built-in sensors and simple
sensors plugged into the microphone port of the XO laptop, the Butia team in
Uruguay has been augmenting the XO with an Arduino board. The latest video
of their work is on YouTube [10]. Be sure to watch past the 'Schwarzenegger'
robot to see the XO robot programmed in Turtle Art.

4. A few weeks ago, Team Sugarlabs participated in the Boston Hub on Wheels
bicycle tour (See Team Sugarlabs [11]). Dogi road with an XO attached to his
handlebars, but he wasn't running the Turtle Art odometer program.

5. We've passed six-million downloads on ASLO [12].

=== In the community ===

6. The SF Summit [13] is this coming weekend, 21-23 October.

7. The Prague Sugar Camp (Gtk3 Hackfest 2011 [14]) is next weekend, 28-30
October.

8. Reminder: As a community member, it is important that your voice be
heard. One mechanism is for you to participate in our upcoming election: We
will be holding an election for three Sugar Labs oversight board (SLOB)
positions at the end of next month. If you are not already a ''member'' [15]
of Sugar Labs, please send your name and an explanation of your contribution
to Sugar Labs in an email to '''members at sugarlabs dot org'''. If you are
a member, please consider being a candidate [16] for one of the SLOB
positions.

=== Tech Talk ===

9. Rob Savoye has managed to build Gnash for ARM. He has made RPMs for the
XO 1.75 machine. To install his RPMs, add this .repo file to your XO:

[gnash-snapshot]
name=Gnash Snapshot for Fedora $releasever
baseurl=http://getgnash.org/yum/fedora/$releasever/updates/$basearch/
enabled=1
gpgkey=http://getgnash.org/gnashdev.key

=== Sugar Labs ===

Gary Martin has generated a SOM [17] from the past few weeks of discussion
on the IAEP mailing list.

Visit our planet [18] for more updates about Sugar and Sugar deployments.

-walter

[0] http://wiki.laptop.org/go/Release_notes/11.3.0 11.3.0
[1] http://download.laptop.org/xo-1/os/candidate/881/
[2] http://download.laptop.org/xo-1.5/os/candidate/881/
[3] http://download.laptop.org/xo-1.75/os/candidate/881/
[4]
http://www.olpcnews.com/software/sugar/measuring_a_lemon_battery_with_measure.html
[5]
http://www.olpcnews.com/hardware/peripherals/construir_un_pulsografo_con_xo.html
[6] http://anisterra.wordpress.com/2011/10/03/fisica-con-xo/
[7]
http://wiki.sugarlabs.org/go/Activities/TurtleArt/Uso_de_TortugaArte_Sensores
[8]
http://wiki.sugarlabs.org/go/Activities/TurtleArt/Using_Turtle_Art_Sensors
[9] http://tonyforster.blogspot.com/
[10] http://www.youtube.com/watch?v=IcpzVnuFP0Mfeature=channel_video_title
[11] http://wiki.sugarlabs.org/go/File:TeamSugarlabs.jpg
[12] http://activities.sugarlabs.org
[13]
http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011
[14] http://wiki.sugarlabs.org/go/Marketing_Team/Events/Gtk3_Hackfest_2011
[15] http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List
[16]
http://wiki.sugarlabs.org/go/Oversight_Board/2011-2012-candidates#Candidates
[17] http://wiki.sugarlabs.org/go/File:2011-Oct-8-14-som.jpg October
8th-14th (38 emails)
[18] http://planet.sugarlabs.org

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Sugar Digest 2011-10-18

2011-10-18 Thread Peter Robinson
On Tue, Oct 18, 2011 at 11:35 PM, Walter Bender walter.ben...@gmail.com wrote:
 == Sugar Digest ==

 1. Daniel Drake has announced the second release candidate of the new OLPC
 software release [0], which incorporates the latest Sugar bits. You can
 download 'signed' images for testing from: [1-3]. The final release is
 scheduled for 1 November.

 2. OLPC OZ runs a discussion website on yammer.com for teachers working with
 XOs in Australia. It is a nice source of feedback about Sugar and 1-to-1
 laptop deployments in general. Recently, there was a posting that referenced
 an OLPC News article about a lemon-battery project [4] by Sameer Verma.
 There was also a tip of the hat to Guzman Trindad, a teacher in Uruguay, who
 built a pulse meter [5]. I am not sure how OLPC News missed all of the other
 great work that Guzman has been doing [6] with Turtle Art and sensors [7]
 and also the work of Tony Forster [8], who blogs [9] regularly about various
 ways to engage children with simple sensor. His most recent posting is about
 using the accelerometer on the XO 1.75 as a seismograph. Check it out.

 3. While Guzman and Tony have been using the built-in sensors and simple
 sensors plugged into the microphone port of the XO laptop, the Butia team in
 Uruguay has been augmenting the XO with an Arduino board. The latest video
 of their work is on YouTube [10]. Be sure to watch past the 'Schwarzenegger'
 robot to see the XO robot programmed in Turtle Art.

 4. A few weeks ago, Team Sugarlabs participated in the Boston Hub on Wheels
 bicycle tour (See Team Sugarlabs [11]). Dogi road with an XO attached to his
 handlebars, but he wasn't running the Turtle Art odometer program.

 5. We've passed six-million downloads on ASLO [12].

 === In the community ===

 6. The SF Summit [13] is this coming weekend, 21-23 October.

 7. The Prague Sugar Camp (Gtk3 Hackfest 2011 [14]) is next weekend, 28-30
 October.

 8. Reminder: As a community member, it is important that your voice be
 heard. One mechanism is for you to participate in our upcoming election: We
 will be holding an election for three Sugar Labs oversight board (SLOB)
 positions at the end of next month. If you are not already a ''member'' [15]
 of Sugar Labs, please send your name and an explanation of your contribution
 to Sugar Labs in an email to '''members at sugarlabs dot org'''. If you are
 a member, please consider being a candidate [16] for one of the SLOB
 positions.

 === Tech Talk ===

 9. Rob Savoye has managed to build Gnash for ARM. He has made RPMs for the
 XO 1.75 machine. To install his RPMs, add this .repo file to your XO:

We do actually already have gnash on ARM, it ships with the signed
release above :-)

Peter
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [ANNOUNCE] Sugar Labs instance of Open Build System

2011-10-18 Thread Aleksey Lim
Hi all!

During the work on Sweets[1], openSUSE project, Open Build System[2]
was choosen as build farm and hosting server for software managed by
Sweets.

This is a [http://git.sugarlabs.org/0sugar/build-service patched] Sugar
Labs instance of OBS that is intended to be a:

* Hosting sources and making binaries, if there is need, for
  [[Platform_Team/Sweets|Sweets]].
* Convenient instrument to create 3rd party repositories with native
  packages for all [[#Supported_platforms|supported]] GNU/Linux
  distributions.

For detailed information, read the original Open Build System
[http://openbuildservice.org/documentation.html documentation].

For more details about Sugar Labs instance, see
http://wiki.sugarlabs.org/go/Platform_Team/Open_Build_System

It is ready to be used via Sweets[3] as well as for creating 3rd party
repositories with native packages[4].

[1] http://wiki.sugarlabs.org/go/Platform_Team/Sweets
[2] http://openbuildservice.org/
[3] http://wiki.sugarlabs.org/go/Platform_Team/Guide/Sweets_Packaging#Releasing
[4] http://wiki.sugarlabs.org/go/Platform_Team/Open_Build_System#Usage

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Single sign-on for Sugar Labs resources

2011-10-18 Thread Aleksey Lim
Hi all!

This case was already popped up from community point of view by
Pablo Flores in Tools for the community threads. So, this is a try
from Infrastructure Team side.

This is about Single sing-on feature for all Sugar Labs resources,
such as:

* http://wiki.sugarlabs.org
* http://git.sugarlabs.org
* http://bugs.sugarlabs.org
* http://activities.sugarlabs.org
* http://translate.sugarlabs.org
* https://packages.sugarlabs.org
* http://patchwork.sugarlabs.org

Basing on Infrastructure Team discussion in systems@ mailing list (it is
open, but for some time in the past it was used for discussing secure things
like passwords and its history is not public), there is a wiki page

http://wiki.sugarlabs.org/go/Infrastructure_Team/Central_Login

and a motion:

* Centralized database of all users;
* Support Single sign-on on as many as possible Sugar Labs sites;
* Having users friendly (not only for geeks) Account management
  application;
* Use OpenID, if particular site support it, as a spare authentication
  method (but OpenID does not conform to Single sign-on);
* Push this new infra to production usage;
* Look for more authentication methods, like certificate based one from
  Sugar Shell, that might be useful in addition to the existing system.

This is an invitation to broad discussion and pointing out possible
down sides of this decision (in addition to [1]).

This is also a call for doers to implement [2], we need it in any case.
Or, pointing to the existing implementation that might be reused.

[1] 
http://wiki.sugarlabs.org/go/Infrastructure_Team/Central_Login#Costs_.26_Risks
[2] 
http://wiki.sugarlabs.org/go/Infrastructure_Team/Central_Login#Account_management_application

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Single sign-on for Sugar Labs resources

2011-10-18 Thread James Cameron
On Wed, Oct 19, 2011 at 01:10:22AM +, Aleksey Lim wrote:
 This is an invitation to broad discussion and pointing out possible
 down sides of this decision (in addition to [1]).

Costs and risks not mentioned in [1] might include:

* annoying everybody with extra effort, thus creating a temporary
barrier to contributions,

* a single point of failure, when it fails, none of the resources can be
used,

* complexity of solution may lead to longer time before service is
restored,

* reduced number of engineers with sufficient understanding to be able
to fix the service when it breaks,

... and that these risks were not identified previously suggests to me
that not enough consensus has been reached, and that the decision to
proceed is hasty.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel