Re: [IAEP] [Sugar-devel] [Sur] Sugar oversight board meeting

2013-11-08 Thread David Farning
On Fri, Nov 8, 2013 at 8:29 AM, Sean DALY sdaly...@gmail.com wrote:
 David - what I meant was, no strategic partnership between the distros.
 Ubuntu wouldn't pose so many difficulties if M. Shuttleworth/Canonical got
 behind Sugar for example.

In my conversations with Shuttleworth and Redhat they were both pretty
upset that they were forced to bid against each other to be part of
the OLPC project. Whoever donated more got to be part of the
project the other was ignored.

That, on top of Ubuntu's screw ups in the education sector (
Canoncial, tried to assume too much control over the community lead
Edubuntu project) have left education, and sugar in particular,
struggling at Ubuntu.

 Sean



 On Thu, Nov 7, 2013 at 10:46 AM, David Farning
 dfarn...@activitycentral.com wrote:

 On Thu, Nov 7, 2013 at 3:07 AM, Sean DALY sdaly...@gmail.com wrote:
  I'm sorry Sebastian, yes I should have been more clear about which
  Sebastian
  :-)
 
  At the time, Sugar was perceived as being only available on OLPC XOs, so
  our
  effort was designed to show that it was available for other platforms.
  Indeed, our claim has always been that it was hardware-agnostic (on Mac
  using virtualization), cf. our press releases (sl.o/press). And, SoaS as
  a
  marketing concept was meant to be distro-agnostic too (SuSE...), a
  position
  fought tooth and nail by the Fedorans by the way.
 
  Pre-tablets, when small netbooks sales were exploding, Windows was
  dominant
  on PCs but ran poorly or not at all on netbooks and moreover there was
  an
  installation barrier for Windows on GNU/Linux netbooks. We were
  interested
  in reaching the 92% or so of teachers using Windows and widening Sugar
  availability on machines with pre-installed GNU/Linux (all 2% or so of
  them). Microsoft and Intel worked quickly to block GNU/Linux netbooks by
  pressuring OEMs to build faster machines, then tablets arrived and
  killed
  off netbooks.
 
  It's unfortunate that Sugar was not fully embraced by the GNU/Linux
  distros
  who missed a great opportunity in the education market where Microsoft
  had
  and has weaknesses, but that has been a symptom of free software
  projects
  struggling with strategic initiatives while concentrating on technical
  aspects.

 How does Sugar on Ubuntu (DXU) and Sugar on Tablets (DX experimental)
 affect this equation for Sugar Labs?

  Dismal marketing has contributed to dismal desktop market share
  (Microsoft's well-documented maneuvers played a role too of course).
 
  Installation: As Peter has mentioned, SoaS can be used for installation
  on a
  target PC, this is documented in the wiki.
 
  Concerning translations, language selection was available in at least
  several versions of SoaS, I remember switching French and US locale and
  keyboard demoing SoaS at an Educatec-Educatice convention in Paris. I
  have
  no doubt that solutions are possible, but do remember that Peter has
  been
  continuing SoaS work singlehandedly for some time now.
 
  Looking forward, I see a dual challenge for Sugar Labs: supporting the
  XO
  installed base (including hopefully keeping XO-4 availability alive),
  and
  transitioning to the wild new world of handheld devices.
 
  Sean
 
 
 
  On Thu, Nov 7, 2013 at 12:21 AM, Sebastian Silva
  sebast...@fuentelibre.org
  wrote:
 
 
  El 06/11/13 17:35, Sean DALY escribió:
 
  On Mon, Nov 4, 2013 at 11:05 PM, Peter Robinson pbrobin...@gmail.com
  wrote:
 
  But you have for a long time refused to actually even market SoaS!
 
 
  That's right, at the time SoaS became an official Fedora spin, Mel and
  Sebastian decided to take over marketing, which included coming up with
  unmarketable names, linking with Fedora announcements, and opening a
  Fedora
  hosted minisite (the home of SoaS), none of which was done with any
  consultation of the SL marketing team.
 
  Please try to include last names, you mean Sebastian Dzallas, original
  developer of Sugar On A Stick.
 
  Now that we're on the topic... the concept Sugar On A Stick has
  several
  problems.
 
  1.- It suggests it's the only possible Sugar OS on a USB.
  2.- It suggests it's not a serious OS to be installed on a computer.
  3.- It's impossible to translate.
  4.- It suggests it's not regular GNU/Linux, with availability of the
  Myriad other GNU/Linux educational tools.
 
  Regards,
  Sebastian Silva
  R+D SomosAzúcar
  Sugar Labs Perú
  @icarito
 
 
 
  ___
  Sugar-devel mailing list
  sugar-de...@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 



 --
 David Farning
 Activity Central: http://www.activitycentral.com





-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] [Sur] Sugar oversight board meeting

2013-11-07 Thread David Farning
On Thu, Nov 7, 2013 at 3:07 AM, Sean DALY sdaly...@gmail.com wrote:
 I'm sorry Sebastian, yes I should have been more clear about which Sebastian
 :-)

 At the time, Sugar was perceived as being only available on OLPC XOs, so our
 effort was designed to show that it was available for other platforms.
 Indeed, our claim has always been that it was hardware-agnostic (on Mac
 using virtualization), cf. our press releases (sl.o/press). And, SoaS as a
 marketing concept was meant to be distro-agnostic too (SuSE...), a position
 fought tooth and nail by the Fedorans by the way.

 Pre-tablets, when small netbooks sales were exploding, Windows was dominant
 on PCs but ran poorly or not at all on netbooks and moreover there was an
 installation barrier for Windows on GNU/Linux netbooks. We were interested
 in reaching the 92% or so of teachers using Windows and widening Sugar
 availability on machines with pre-installed GNU/Linux (all 2% or so of
 them). Microsoft and Intel worked quickly to block GNU/Linux netbooks by
 pressuring OEMs to build faster machines, then tablets arrived and killed
 off netbooks.

 It's unfortunate that Sugar was not fully embraced by the GNU/Linux distros
 who missed a great opportunity in the education market where Microsoft had
 and has weaknesses, but that has been a symptom of free software projects
 struggling with strategic initiatives while concentrating on technical
 aspects.

How does Sugar on Ubuntu (DXU) and Sugar on Tablets (DX experimental)
affect this equation for Sugar Labs?

 Dismal marketing has contributed to dismal desktop market share
 (Microsoft's well-documented maneuvers played a role too of course).

 Installation: As Peter has mentioned, SoaS can be used for installation on a
 target PC, this is documented in the wiki.

 Concerning translations, language selection was available in at least
 several versions of SoaS, I remember switching French and US locale and
 keyboard demoing SoaS at an Educatec-Educatice convention in Paris. I have
 no doubt that solutions are possible, but do remember that Peter has been
 continuing SoaS work singlehandedly for some time now.

 Looking forward, I see a dual challenge for Sugar Labs: supporting the XO
 installed base (including hopefully keeping XO-4 availability alive), and
 transitioning to the wild new world of handheld devices.

 Sean



 On Thu, Nov 7, 2013 at 12:21 AM, Sebastian Silva sebast...@fuentelibre.org
 wrote:


 El 06/11/13 17:35, Sean DALY escribió:

 On Mon, Nov 4, 2013 at 11:05 PM, Peter Robinson pbrobin...@gmail.com
 wrote:

 But you have for a long time refused to actually even market SoaS!


 That's right, at the time SoaS became an official Fedora spin, Mel and
 Sebastian decided to take over marketing, which included coming up with
 unmarketable names, linking with Fedora announcements, and opening a Fedora
 hosted minisite (the home of SoaS), none of which was done with any
 consultation of the SL marketing team.

 Please try to include last names, you mean Sebastian Dzallas, original
 developer of Sugar On A Stick.

 Now that we're on the topic... the concept Sugar On A Stick has several
 problems.

 1.- It suggests it's the only possible Sugar OS on a USB.
 2.- It suggests it's not a serious OS to be installed on a computer.
 3.- It's impossible to translate.
 4.- It suggests it's not regular GNU/Linux, with availability of the
 Myriad other GNU/Linux educational tools.

 Regards,
 Sebastian Silva
 R+D SomosAzúcar
 Sugar Labs Perú
 @icarito



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




-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Tech roadmap

2013-11-07 Thread David Farning
On Thu, Nov 7, 2013 at 12:30 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
 Re library versions, that reminds of a point I should have put in my list...

 I think now that the gobject introspection migration is over upstream can
 become more conservative about library versions. That should help both
 distributors and developers. We are already going in that direction really.
 If we add Webkit1 compatibility as discussed, I think 0.102 might have
 pretty much the same dependencies of 0.98. The only exception is libxkb if I
 remember correctly, for which introspection was really broken.

In addition to dependencies there can be issues with versions of dependencies.

Within the next couple of week we should see these fixes flow
upstream. So we can start talking about concrete issues and examples
rather than abstract notions. I think that will help clarify the
discussion.

AC's challenge was to quietly get a proof of concept in place which
adds value to deployments before suggesting making changes to
upstream. Now, AC has to clean up and abstract the proof of concept
work to prepare it for acceptance upstream.

 On Thursday, 7 November 2013, David Farning wrote:

 I agree :)

 Right now, we are sitting back and seeing what roll OLPC-Australia is
 going to play in the ecosystem. The One Education distribution out of
 Australia is a combination of Dextrose, Sugar .100 and some custom
 patches. My semi-informed guess is that Walter and Rangan (
 https://www.laptop.org.au/about ) are going to position One Education
 as the successor to OLPC-OS. I hope that we will learn more at about
 their plans at basecamp. ( http://olpcbasecamp.blogspot.com/ ) This
 would take care or the leading edge on Fedora.

 On the Ubuntu side we have a bit of a challenge balancing bleeding
 edge and stability. Sugar and Fedora tend to run a bit ahead of Debian
 and Ubuntu in library versions. It take a significant amount of effort
 to backport the necessary libraries to Ubuntu LTS. For this release we
 agreed that the proper balance of innovation and stability was Sugar
 .98 on Ubuntu 12.04. The next decision point will be which version of
 Sugar to use for the 14.04 release due in the second quarter of 2014.

 On Wed, Nov 6, 2013 at 8:05 PM, Daniel Narvaez dwnarv...@gmail.com
 wrote:
  Cool stuff.
 
  As for Fedora it would be great to have builds with the latest sugar
  (stable
  and unstable) releases. I'm not saying to ship those to deployments of
  course, but they would help upstream development, marketing and
  testing...
  And they would help AC to make the transition to the next sugar release
  smoother.
 
  On 7 November 2013 02:05, David Farning dfarn...@activitycentral.com
  wrote:
 
  Please see the link at the bottom left of http://dextrose.ac/platform/
  for the Sugar on Ubuntu images which Activity Central and Plan Ceibal
  are jointly developing.
 
  For stability it is based on Ubuntu 12.04 and Sugar .98. The testing
  is done on classmate to meet Plan Ceibal's specifications. I should
  work equally well on any machine that boots Ubuntu.
 
  It is currently is small scale testing by a couple hundred teachers.
  When the image meets Ceibal's quality standards the pilot will scale
  to approximately 10,000 units for wider testing.
 
  For more information, I have CC Anish Mangal, the project owner (agile
  speak) and Ruben Rodriguez the lead developer. Ruben has the strongest
  back ground on the technical issues involved in the port. Anish has
  the deepest understanding of timelines and objectives.
 
  On Wed, Nov 6, 2013 at 9:31 AM, Daniel Narvaez dwnarv...@gmail.com
  wrote:
   On 6 November 2013 16:20, Manuel Quiñones ma...@laptop.org wrote:
  
  
Classmates are basically just x86 netbooks, I've not tried it as I
don't have HW but I don't see any reason they shouldn't work OOTB.
  
   Yep. Sugar is running in classmates out of the box.  In Uruguay for
   example.
  
  
   You mean people are using them in Uruguay deployments? Which distro?
  
   ___
   Sugar-devel mailing list
   sugar-de...@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
  
 
 
 
  --
  David Farning
  Activity Central: http://www.activitycentral.com
 
 
 
 
  --
  Daniel Narvaez



 --
 David Farning
 Activity Central: http://www.activitycentral.com



 --
 Daniel Narvaez




-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Tech roadmap

2013-11-06 Thread David Farning
Please see the link at the bottom left of http://dextrose.ac/platform/
for the Sugar on Ubuntu images which Activity Central and Plan Ceibal
are jointly developing.

For stability it is based on Ubuntu 12.04 and Sugar .98. The testing
is done on classmate to meet Plan Ceibal's specifications. I should
work equally well on any machine that boots Ubuntu.

It is currently is small scale testing by a couple hundred teachers.
When the image meets Ceibal's quality standards the pilot will scale
to approximately 10,000 units for wider testing.

For more information, I have CC Anish Mangal, the project owner (agile
speak) and Ruben Rodriguez the lead developer. Ruben has the strongest
back ground on the technical issues involved in the port. Anish has
the deepest understanding of timelines and objectives.

On Wed, Nov 6, 2013 at 9:31 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
 On 6 November 2013 16:20, Manuel Quiñones ma...@laptop.org wrote:


  Classmates are basically just x86 netbooks, I've not tried it as I
  don't have HW but I don't see any reason they shouldn't work OOTB.

 Yep. Sugar is running in classmates out of the box.  In Uruguay for
 example.


 You mean people are using them in Uruguay deployments? Which distro?

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




-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Tech roadmap

2013-11-06 Thread David Farning
I agree :)

Right now, we are sitting back and seeing what roll OLPC-Australia is
going to play in the ecosystem. The One Education distribution out of
Australia is a combination of Dextrose, Sugar .100 and some custom
patches. My semi-informed guess is that Walter and Rangan (
https://www.laptop.org.au/about ) are going to position One Education
as the successor to OLPC-OS. I hope that we will learn more at about
their plans at basecamp. ( http://olpcbasecamp.blogspot.com/ ) This
would take care or the leading edge on Fedora.

On the Ubuntu side we have a bit of a challenge balancing bleeding
edge and stability. Sugar and Fedora tend to run a bit ahead of Debian
and Ubuntu in library versions. It take a significant amount of effort
to backport the necessary libraries to Ubuntu LTS. For this release we
agreed that the proper balance of innovation and stability was Sugar
.98 on Ubuntu 12.04. The next decision point will be which version of
Sugar to use for the 14.04 release due in the second quarter of 2014.

On Wed, Nov 6, 2013 at 8:05 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
 Cool stuff.

 As for Fedora it would be great to have builds with the latest sugar (stable
 and unstable) releases. I'm not saying to ship those to deployments of
 course, but they would help upstream development, marketing and testing...
 And they would help AC to make the transition to the next sugar release
 smoother.

 On 7 November 2013 02:05, David Farning dfarn...@activitycentral.com
 wrote:

 Please see the link at the bottom left of http://dextrose.ac/platform/
 for the Sugar on Ubuntu images which Activity Central and Plan Ceibal
 are jointly developing.

 For stability it is based on Ubuntu 12.04 and Sugar .98. The testing
 is done on classmate to meet Plan Ceibal's specifications. I should
 work equally well on any machine that boots Ubuntu.

 It is currently is small scale testing by a couple hundred teachers.
 When the image meets Ceibal's quality standards the pilot will scale
 to approximately 10,000 units for wider testing.

 For more information, I have CC Anish Mangal, the project owner (agile
 speak) and Ruben Rodriguez the lead developer. Ruben has the strongest
 back ground on the technical issues involved in the port. Anish has
 the deepest understanding of timelines and objectives.

 On Wed, Nov 6, 2013 at 9:31 AM, Daniel Narvaez dwnarv...@gmail.com
 wrote:
  On 6 November 2013 16:20, Manuel Quiñones ma...@laptop.org wrote:
 
 
   Classmates are basically just x86 netbooks, I've not tried it as I
   don't have HW but I don't see any reason they shouldn't work OOTB.
 
  Yep. Sugar is running in classmates out of the box.  In Uruguay for
  example.
 
 
  You mean people are using them in Uruguay deployments? Which distro?
 
  ___
  Sugar-devel mailing list
  sugar-de...@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 



 --
 David Farning
 Activity Central: http://www.activitycentral.com




 --
 Daniel Narvaez



-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Sugar Digest 2013-09-16

2013-09-17 Thread David Farning
 that can also
 be used for testing [11]. Meanwhile, the previous release of Sugar
 (98.8) is available on Ubuntu (12.04) [12] thanks to the efforts of
 Quidam.

 === Sugar Labs ===

 8. Please visit (and contribute to) our planet [13].

 

 [1] http://www.nytimes.com/2013/09/15/magazine/no-child-left-untableted.html
 [2] 
 http://graphics8.nytimes.com/images/2013/09/15/magazine/15klein3/15klein3-sfSpan.jpg
 [3] http://developer.sugarlabs.org/web-architecture.md.html
 [4] http://developer.sugarlabs.org/android.md.html
 [5] http://people.sugarlabs.org/walter/Guia_Ingles_10-08-2013.pdf (en)
 [6] http://people.sugarlabs.org/walter/Guia_Esp_12-08-2013.pdf (es)
 [7] http://ceibaljam.org/drupal/?q=edujam2013
 [8] http://wiki.sugarlabs.org/go/Summer_of_Code/2013
 [9] 
 http://bugs.sugarlabs.org/query?status=newstatus=assignedstatus=acceptedstatus=reopenedpriority=Immediatepriority=Urgentcomponent=Sugarstatus_field=Neworder=priority
 [10] http://build.laptop.org.au/xo/os/sugar-100
 [11] http://wiki.sugarlabs.org/go/Fedora_20#SoaS_86_64-dm_.28remix.29
 [12] 
 http://wiki.sugarlabs.org/go/Ubuntu#Ubuntu_12.04.2_LTS_-_Dextrose_Sugar_Live
 [13] http://planet.sugarlab.org


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



-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Sugar on Android via HTML5

2013-09-16 Thread David Farning
On Fri, Sep 13, 2013 at 7:51 AM, David Farning
dfarn...@activitycentral.com wrote:
 On Thu, Sep 12, 2013 at 6:54 PM, John Watlington w...@laptop.org wrote:

 On Sep 10, 2013, at 5:04 PM, Sameer Verma wrote:

 On Thu, Sep 5, 2013 at 7:51 PM, Caryl Bigenho cbige...@hotmail.com wrote:

 One of the things that makes Sugar the ideal learning platform for
 children (and youth) is the wonderful compatibility of so many of the
 Activities ... both from Activity to Activity and from student to student.
 This facilitates the sort of learning we are all hoping to see more of...
 creative problem solving, project based learning and cooperative learning.
 Without this ability to integrate parts of projects, it would just be
 another collection of apps.


 I did not want to muddy the picture by injecting my own viewpoint, but now
 that I've heard from others (on and off list) it is clear that the split is
 driven by the role they play in the ecosystem.
 Most technologists have come up with reasons why they don't think a complete
 Sugar experience would work on Android. Therefore, activities must run like
 any other app on Android. On the other hand, as Caryl said, Without this
 ability to integrate...it would just be a collection of apps.

 Somewhat knowing the limitations of what can be done with Sugar stuff on
 Android, but disregarding that for a minute, I would say that Sugar as a
 *platform* is an experience. It has a UI. It has a UX. Everything from the
 Zoom interface to the activities to the Journal is Sugar. We have taken the
 original Sugar on the OLPC XO experience and replicated that to the
 classmate PC, SoaS, and other spins and distros, but in none of these cases
 did we break the holistic Sugar experience. Now, along comes a popular OS,
 and because the tech parts don't fit, we are advocating breaking up the
 pieces and taking whatever flies. Memorize will become one of the few
 hundred thousand apps on Android.

 I disagree.

 It's like saying we'll do the cat sprite from Scratch, but nothing else.
 It's like saying we'll do the birds and pigs from Angry Birds, but not the
 slingshot. Sugar, without all its pieces isn't worth the trouble.


 Sameer,
I disagree somewhat with your thesis (and am very glad you started this
 discussion.)

 From a technological standpoint, it is actually probably easier to implement
 what you describe:
 Sugar as a monolithic Android application, which takes over the entire user
 interface when
 launched.   The reason I never considered it seriously was the larger
 ecosystem.

 The reason to move to Android from Linux is two-fold:
 - Chip vendors are dropping Linux support in favor of Android.   The cheap
 chinese ARM
  vendors only support Android.
 - Android/iOS are where application development is happening.  There is a
 much larger
 community of Android developers than Linux or Sugar developers.

 The hope was to provide the infrastructure underlying Sugar (the Journal
 datastore and
 collaboration) as Android services, encouraging their use in new Android
 applications.
 In this model, the Journal is another Android application, accessing the
 Journal datastore service.
 New Sugar activities written in HTML should be capable of running in Sugar
 on Linux
 or as Android activities (although perhaps with different execution
 wrappers).
 In this manner, perhaps we can enlarge the Sugar community with developers
 mainly
 targeting Android.

 Just to clarify:
 1. OLPC-A's intention is to create a HTML5+JS  framework for creating
 Sugar Activities.
 2. Sugar Activities created using this framework will run equally well
 on both 'Sugar for linux' and Android.
 3. This requires two separate abstraction layers wrapper one for
 Sugar on linux and one for Android.
 4. These abstraction layers make Sugar Services such as collaboration
 and the journal available within the HTML5+JS framework.

 Is there an implementation plan and roadmap available? Are there
 sufficient resources committed to these projects to see them through
 to completion?

I just wanted to follow up this thread. I find it interesting because
the answer depend a bit on the person asking the questions. Is the
person asking the questions:
1. An OLPC hater who is going to hate.
2. A muggle who is not capable of understanding OLPC.
3. A person who has proven that they support the OLPC vision while
occasionally questioning the Association's stewardship of that vision.

 If we pursue Sugar as a single Android application,
 with embedded
 Python activities, we are isolating ourselves from the Android community.

 The danger of this approach is the loss of an integrated UX.  This could be
 addressed
 by customizing the home UI, in the same manner that the XO tablet has a
 custom home UI
 implementing the Dreams interface, but that would require rooting the
 tablet in some manner.
 But the native Android UI isn't that bad...

 Cheers,
 wad


 ___
 Devel mailing list
 de

Re: [IAEP] Sugar on Android via HTML5

2013-09-13 Thread David Farning
On Thu, Sep 12, 2013 at 6:54 PM, John Watlington w...@laptop.org wrote:

 On Sep 10, 2013, at 5:04 PM, Sameer Verma wrote:

 On Thu, Sep 5, 2013 at 7:51 PM, Caryl Bigenho cbige...@hotmail.com wrote:

 One of the things that makes Sugar the ideal learning platform for
 children (and youth) is the wonderful compatibility of so many of the
 Activities ... both from Activity to Activity and from student to student.
 This facilitates the sort of learning we are all hoping to see more of...
 creative problem solving, project based learning and cooperative learning.
 Without this ability to integrate parts of projects, it would just be
 another collection of apps.


 I did not want to muddy the picture by injecting my own viewpoint, but now
 that I've heard from others (on and off list) it is clear that the split is
 driven by the role they play in the ecosystem.
 Most technologists have come up with reasons why they don't think a complete
 Sugar experience would work on Android. Therefore, activities must run like
 any other app on Android. On the other hand, as Caryl said, Without this
 ability to integrate...it would just be a collection of apps.

 Somewhat knowing the limitations of what can be done with Sugar stuff on
 Android, but disregarding that for a minute, I would say that Sugar as a
 *platform* is an experience. It has a UI. It has a UX. Everything from the
 Zoom interface to the activities to the Journal is Sugar. We have taken the
 original Sugar on the OLPC XO experience and replicated that to the
 classmate PC, SoaS, and other spins and distros, but in none of these cases
 did we break the holistic Sugar experience. Now, along comes a popular OS,
 and because the tech parts don't fit, we are advocating breaking up the
 pieces and taking whatever flies. Memorize will become one of the few
 hundred thousand apps on Android.

 I disagree.

 It's like saying we'll do the cat sprite from Scratch, but nothing else.
 It's like saying we'll do the birds and pigs from Angry Birds, but not the
 slingshot. Sugar, without all its pieces isn't worth the trouble.


 Sameer,
I disagree somewhat with your thesis (and am very glad you started this
 discussion.)

 From a technological standpoint, it is actually probably easier to implement
 what you describe:
 Sugar as a monolithic Android application, which takes over the entire user
 interface when
 launched.   The reason I never considered it seriously was the larger
 ecosystem.

 The reason to move to Android from Linux is two-fold:
 - Chip vendors are dropping Linux support in favor of Android.   The cheap
 chinese ARM
  vendors only support Android.
 - Android/iOS are where application development is happening.  There is a
 much larger
 community of Android developers than Linux or Sugar developers.

 The hope was to provide the infrastructure underlying Sugar (the Journal
 datastore and
 collaboration) as Android services, encouraging their use in new Android
 applications.
 In this model, the Journal is another Android application, accessing the
 Journal datastore service.
 New Sugar activities written in HTML should be capable of running in Sugar
 on Linux
 or as Android activities (although perhaps with different execution
 wrappers).
 In this manner, perhaps we can enlarge the Sugar community with developers
 mainly
 targeting Android.

Just to clarify:
1. OLPC-A's intention is to create a HTML5+JS  framework for creating
Sugar Activities.
2. Sugar Activities created using this framework will run equally well
on both 'Sugar for linux' and Android.
3. This requires two separate abstraction layers wrapper one for
Sugar on linux and one for Android.
4. These abstraction layers make Sugar Services such as collaboration
and the journal available within the HTML5+JS framework.

Is there an implementation plan and roadmap available? Are there
sufficient resources committed to these projects to see them through
to completion?

 If we pursue Sugar as a single Android application,
 with embedded
 Python activities, we are isolating ourselves from the Android community.

 The danger of this approach is the loss of an integrated UX.  This could be
 addressed
 by customizing the home UI, in the same manner that the XO tablet has a
 custom home UI
 implementing the Dreams interface, but that would require rooting the
 tablet in some manner.
 But the native Android UI isn't that bad...

 Cheers,
 wad


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




-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] Sugar on Android via HTML5

2013-09-13 Thread David Farning
On Fri, Sep 13, 2013 at 11:56 AM, Manuel Quiñones ma...@laptop.org wrote:
 2013/9/13 David Farning dfarn...@activitycentral.com:
 On Thu, Sep 12, 2013 at 6:54 PM, John Watlington w...@laptop.org wrote:

 On Sep 10, 2013, at 5:04 PM, Sameer Verma wrote:

 On Thu, Sep 5, 2013 at 7:51 PM, Caryl Bigenho cbige...@hotmail.com wrote:

 One of the things that makes Sugar the ideal learning platform for
 children (and youth) is the wonderful compatibility of so many of the
 Activities ... both from Activity to Activity and from student to student.
 This facilitates the sort of learning we are all hoping to see more of...
 creative problem solving, project based learning and cooperative learning.
 Without this ability to integrate parts of projects, it would just be
 another collection of apps.


 I did not want to muddy the picture by injecting my own viewpoint, but now
 that I've heard from others (on and off list) it is clear that the split is
 driven by the role they play in the ecosystem.
 Most technologists have come up with reasons why they don't think a complete
 Sugar experience would work on Android. Therefore, activities must run like
 any other app on Android. On the other hand, as Caryl said, Without this
 ability to integrate...it would just be a collection of apps.

 Somewhat knowing the limitations of what can be done with Sugar stuff on
 Android, but disregarding that for a minute, I would say that Sugar as a
 *platform* is an experience. It has a UI. It has a UX. Everything from the
 Zoom interface to the activities to the Journal is Sugar. We have taken the
 original Sugar on the OLPC XO experience and replicated that to the
 classmate PC, SoaS, and other spins and distros, but in none of these cases
 did we break the holistic Sugar experience. Now, along comes a popular OS,
 and because the tech parts don't fit, we are advocating breaking up the
 pieces and taking whatever flies. Memorize will become one of the few
 hundred thousand apps on Android.

 I disagree.

 It's like saying we'll do the cat sprite from Scratch, but nothing else.
 It's like saying we'll do the birds and pigs from Angry Birds, but not the
 slingshot. Sugar, without all its pieces isn't worth the trouble.


 Sameer,
I disagree somewhat with your thesis (and am very glad you started this
 discussion.)

 From a technological standpoint, it is actually probably easier to implement
 what you describe:
 Sugar as a monolithic Android application, which takes over the entire user
 interface when
 launched.   The reason I never considered it seriously was the larger
 ecosystem.

 The reason to move to Android from Linux is two-fold:
 - Chip vendors are dropping Linux support in favor of Android.   The cheap
 chinese ARM
  vendors only support Android.
 - Android/iOS are where application development is happening.  There is a
 much larger
 community of Android developers than Linux or Sugar developers.

 The hope was to provide the infrastructure underlying Sugar (the Journal
 datastore and
 collaboration) as Android services, encouraging their use in new Android
 applications.
 In this model, the Journal is another Android application, accessing the
 Journal datastore service.
 New Sugar activities written in HTML should be capable of running in Sugar
 on Linux
 or as Android activities (although perhaps with different execution
 wrappers).
 In this manner, perhaps we can enlarge the Sugar community with developers
 mainly
 targeting Android.

 Just to clarify:
 1. OLPC-A's intention is to create a HTML5+JS  framework for creating
 Sugar Activities.

 A small correction: activities using web technologies has been
 discussed for a while in the Sugar community, and is now being
 actively implemented as part of Sugar roadmap.

Yes, This is also figures prominently in my risk analysis. It appears
that three Sugar developers are paid by OLPC: Manq, Gonzalo, and
Walter. Please correct me if I am wrong or this has changed. Is OLPC-A
in a position to commit these resources until the project is
completed?

 2. Sugar Activities created using this framework will run equally well
 on both 'Sugar for linux' and Android.
 3. This requires two separate abstraction layers wrapper one for
 Sugar on linux and one for Android.
 4. These abstraction layers make Sugar Services such as collaboration
 and the journal available within the HTML5+JS framework.

 Is there an implementation plan and roadmap available? Are there
 sufficient resources committed to these projects to see them through
 to completion?

 If we pursue Sugar as a single Android application,
 with embedded
 Python activities, we are isolating ourselves from the Android community.

 The danger of this approach is the loss of an integrated UX.  This could be
 addressed
 by customizing the home UI, in the same manner that the XO tablet has a
 custom home UI
 implementing the Dreams interface, but that would require rooting the
 tablet in some manner.
 But the native Android UI isn't

Re: [IAEP] [support-gang] ANNOUNCEMENT XSCE 0.3 Final Release

2013-06-09 Thread David Farning
T.K.,

Can you ping me off list with your specific needs. I'll try to make sure
your needs are meet in the next couple of releases.

I have tried pinging you off list... but get get bounce notices


On Thu, Jun 6, 2013 at 9:05 PM, tkk...@nurturingasia.com wrote:

 Good news indeed and my appreciation to all the hard work the XSCE team
 have put into.

 I recently installed R2 on SD a card for XO 1.75 (512 Mib) with 3 APs. It
 seems to be working fine with 30 XO-1s connected via different AP.
 Registration went well, ejabberdctl displayed registered users, moodle
 work, backup work. So I am a happy end-user waiting to see it deployed in
 the wild soon!

 T.K. Kang



 -Original Message-
 From: George Hunt [mailto:georgejh...@gmail.com]
 Sent: Friday, June 7, 2013 08:07 AM
 To: 'Community Support Volunteers -- who help respond to help AT
 laptop.org'
 Cc: 'Support Gangsters', 'server-devel', 'Testing', 'IAEP SugarLabs',
 de...@laptop.org
 Subject: [support-gang] ANNOUNCEMENT XSCE 0.3 Final Release
 
 After three months of hard work and three weeks of working out the
 kinks in the release process, XSCE 0.3 is ready for its final release.
 
 We went conservative this release. Emphasis on stability meant less time
 for new features.
 
 
 * XSCE now runs on the XO-1.5,XO-1.75 and  XO-4.
 
 * Modular Architecture: cleanly integrate extendable services.
 
 * XSCE runs on the XOs' current OS 13.1.0 (we discovered some wrinkles
 with
 13.2.0 which push its use off to the next release)
 
 * Moodle is Back!
 
 * Content filtering via openDNS.com
 
 * Script for formatting of SD cards, and integration into system for
 content storage and memory extending swap file (does not work on XO4's)
 
 
 
 Grab an XO-1.5, XO-1.75 or a XO-4 to give XSCE 0.3 give a whirl:
 
 http://schoolserver.org/0.3
 
 If you are just getting started with XSCE we suggest using the instruction
 at
 http://wiki.laptop.org/go/User:Holt/XS_Community_Edition/0.3/Installingto
 install your first server.
 
 Once you are through the install, a good second step is to work your new
 server though it’s paces by doing the smoke test at
 http://wiki.laptop.org/go/User:Holt/XS_Community_Edition/0.3/Testing
 
 
 Monster thanks to everyone who spent months of springtime work --
 traveling
 days from quite different parts of North America to make this community
 product real.
 
 George Hunt
 
 ___
 support-gang mailing list
 support-g...@lists.laptop.org
 http://lists.laptop.org/listinfo/support-gang
 


 ___
 support-gang mailing list
 support-g...@lists.laptop.org
 http://lists.laptop.org/listinfo/support-gang




-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] XSCE 0.3 RC2 Release Announcement

2013-05-28 Thread David Farning
After three months of hard work and three weeks of working out the
kinks in the release process XSCE 0.3 RC2 is ready to go.

We went conservative this release. Emphasis on stability meant less time
for new features. A big thank you to anyone who can help increase this
stability out by testing RC2 in preparation for next weeks XSCE 0.3 release:

--Tested

* XSCE now runs on the XO-1.5,XO-1.75 and  XO-4.

* Modular Architecture: cleanly integrate extendable services.

* XSCE runs on XOs' brand new OLPC OS 13.1.0.

* Moodle is Back!

* Content filtering via openDNS.com

* Script for formatting of SD cards, and integration into
systemhttp://dansguardian.org/

-- Experimental

* ix86  x64 testing is beginning in earnest.

* Highly experimental XO-1 functionality now demonstrated, tho NOT advised!

* Auto-recognition and mounting of USB hard drives. Works but not quit well
enough to handle the hard drive being jostled enough to cause brief
disconnects.

* Full offline installs possible going forward.

  http://dansguardian.org/

Grab an XO-1.5, XO-1.75 or a XO-4 to give XSCE 0.3 RC2 give a whirl:

http://schoolserver.org/0.3

If you are just getting started with XSCE we suggest using the instruction
at http://wiki.laptop.org/go/User:Holt/XS_Community_Edition/0.3/Installingto
install your first server.

Once you are through the install, a good second step is to work your new
server though it’s paces by doing the smoke test at
http://wiki.laptop.org/go/User:Holt/XS_Community_Edition/0.3/Testing

For the truly ambitious, try putting your server hardware of choice through
the tests at and update the results table at

http://wiki.laptop.org/go/User:Holt/XS_Community_Edition/0.3/Testing/Results.

Til then, these little guys rock (TM, iLoveMyXO.com !)  Monster thanks to
the folks whose

months of springtime work went into this imminent accomplishment--
traveling days from quite different parts of North America to make this
community product real.


-- 
David Farning
Activity Central: http://www.activitycentral.com
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Promoting Pablo Flores to CEO of Activity Central

2011-12-06 Thread David Farning
I am proud to announce that we are promoting Pablo Flores as the new
CEO of Activity Central.

Pablo has a strong background in all things OLPC and Sugar from his
time at Plan Ceibal, leadership in Ceibal Jam, and most recently
as community architect for Activity Central.

Pablo and the rest of the Activity Central team will continue the core
AC mission of providing service and support for deployments.

I will continue my work in the Sugar/OLPC ecosystem by focusing on the
junction point between deployment technical teams and education teams.
My research so far has lead me to the notion of learning objects.
While poorly defined in the education literature, the vocabulary around
learning objects seems to lends itself to the intersection of technical
personal and education personal in early childhood education.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Communication from teacher - livescribe.

2011-11-17 Thread David Farning
As I mentioned earlier I am working on technology which I can
personally use to keep my nieces and nephews though early elementary
school.

Attached is a link to a live scribe video which one of their teachers
created to help parents understand the techniques the school to teach
two digit addition.

I thought it matched nicely with the idea that the XO can be used to
enhance communication between teachers and parents.

http://www.livescribe.com/cgi-bin/WebObjects/LDApp.woa/wa/MLSOverviewPage?sid=VSV4n7ZzgKgp

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Board Intentions

2011-11-10 Thread David Farning
The other day Sascha asked the question, What do Oversight Board
candidates intend to _do_ during their terms?

Here in the United states, a new school years is getting underway.
This means afternoons and evenings filled with helping nieces and
nephews with their reading, school work, and piano lessons. While they
learn, I learn about learning. It troubles me that I don't use Sugar
of XO as part of my tutoring. The question I ask my self is, How can
I recommend Sugar if I don't use it myself?

The challenges I face are:
1. Aligning with an existing class curriculum.
2. Limited time with each child.
3. Limited preparation time.
4. Limited formal training in curriculum development.
and those who know me will probably add
5. Limited patience :(

Instead of using Sugar, I look though my collection of text books and
a list of websites for resources which augment the days learning
objectives. This is not a criticism of Sugar itself. Just an
observation that while I now fall into a target category of Sugar
users, yet I don't use Sugar. Now that Activity Central is taking
shape, I am going to shift my focus to scratching my own itch as a
uncle and tutor.

My intention for the next couple of years is to create a set of
activities and lessons which fill my needs while addressing my
limitations. As I mature in my understanding of teaching, I will hire
teachers, designers, and developers to replace me in creating these
activities and lessons:) Hopefully deployments and parents will find
the activities and lessons useful enough to use and support.

With regard to the Sugar ecosystem, my goal will be to raise the voice
of content creators and inexperienced teachers.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Sugar Labs Oversight Board - Candidacy

2011-10-09 Thread David Farning
I, David Farning, would like to announce my candidacy for a position
on the Sugar Labs Oversight Board.

As a member on the original Sugar Labs Oversight Board, I came to feel
that as much as I believed in the vision of OLPC and Sugar Labs there
were a number of needs in the ecosystem which could be met by a third
organization.
1. The voice and needs of deployments were being over shadowed by the
global voice of Sugar Labs and OLPC.
2. There was no organization provide service and support for
deployments. As a result, deployments required a significant amount of
technical sophistication before they could get started.
3. Because of the volunteer nature of Sugar Labs, developers tended to
work on the interesting and innovative problems rather than the daily
grind necessary to deliver a fully polished educational platform.

For the past two years I, and a number of other developers, have been
establishing Activity Central [1] to help fill the above needs. Our
model is to provide technical service and support to deployments. This
effort has resulted in the Dextrose [2] operation system which we
custom develop and support for several large and small deployment.
Because we depend on customer revenue for our sustainability we have a
strong incentive to meet the software needs of deployments.

Because Dextrose is based on Upstream Sugar and OLPC OS releases
Activity Central has a strong incentive to assist in the continued
success of Sugar Labs and OLPC. To this end we have made a number of
commitments:
1. All code written by Activity Central developers will be released
with an open source license.
2. Activity Central developers spend 60% of their time on revenue
generating work. They are free to spend the remaining 40% of their
time on projects which are of general value to the ecosystem.
3. Activity Central supports a Community Architect whose job is
identify and support local and global communities that are valuable
parts of the Sugar Labs and OLPC ecosystem.

From time to time I am asked why I chose to form a third organization
rather than work within Sugar Labs or OLPC. A third global
organization brings several advantages to the ecosystem:
1. It promotes cooperative decision making.  When the ecosystem
consisted of two primary participants, Sugar Labs and OLP, there was a
tendency for competitive decision making. When a third player was
added to the mix, the value of cooperative decision making become more
apparent.
2. Organizations with a business focus often provide value to a Free
Software ecosystem. Interestingly OLPC-A has seen this and has been
shifting toward a 'social entrepreneurship' model.
3. Activity Central approaches the ecosystem from a different
viewpoint than either sugar Labs or OLPC. As global innovators both
Sugar Labs' and OLPC's strengths are top down. Ideas and
Implementations flow down from the central organization to deployments
and users. As a service provider, most of Activity Central's ideas and
implementation flow up from deployments and user. Our work flow is to
solve issues faced by individual deployments which we generalize and
push upstream.

thank you,
David Farning

1. http://activitycentral.com/
2. http://wiki.sugarlabs.org/go/Dextrose
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Dextrose] [Sugar-devel] About Activity Central and Dextrose (was: [ANNOUNCE] New Dextrose-3 development build: Alpha-1 (dx3ng36))

2011-09-02 Thread David Farning
On Fri, Sep 2, 2011 at 6:47 AM, Gonzalo Odiard gonz...@laptop.org wrote:
 Thanks

 Gonzalo

 On Fri, Sep 2, 2011 at 8:35 AM, Sascha Silbe si...@activitycentral.com
 wrote:

 Excerpts from Gonzalo Odiard's message of Thu Sep 01 21:24:31 +0200 2011:

  There are a public list of patches?

 Not just a list, the patches themselves are public [1].

 Sascha

 [1] https://people.sugarlabs.org/~silbe/dextrose/patchsets/
 --
 http://sascha.silbe.org/
 http://www.infra-silbe.de/

One of our goals for DX4 will be to streamline the patch maintenance
process. That is something to look at for Q1 2012.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] team updates

2011-09-02 Thread David Farning
On Fri, Aug 26, 2011 at 8:20 AM, Walter Bender walter.ben...@gmail.com wrote:
 At the last Sugar Labs oversight board meeting [1], we discussed the
 need to update the status of the various teams and local labs. You are
 receiving this email because you are currently listed as a team
 coordinator on the wiki [2]. We would like each of you to make a short
 report on your team by email to the iaep list by 9 September  and plan
 to attend the next scheduled SLOBs meeting, 16 September. Below [3] is
 an outline prepared by John Tierney that may serve to guide you in
 preparing your report.

 I am aware that some of you are no longer active in your roles. In
 those cases, could you please send me some names of possible
 replacements as team coordinators. Also, in some cases, the teams
 themselves are perhaps obsolete. This will be one of the discussion
 topics on the 16th.

 Documentation
     David Farning


 What does the team see as its constraints from being more successful
 in its Mission? What are you doing to try to resolve the constraint?
 What can Sugar Labs 'central' or the community do to help?

Documentation is a hard problem for community projects.

One solution is to focus on the documentation individual deployments
create and help make those documents more widely available.

I don't have any suggestions for continuing the team or identifying a
new coordinator.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] EduJAM day 2.

2011-05-07 Thread David Farning
Another day of EduJAM is over. The Event coordinators from Ceibal Jam set an
impressively high bar for future conferences.

The morning centered around Status and Plans reports from deployments. Plan
Ceibal started the day with a session on the technical status and efficacy of
the project. Representatives of Nepal, Rwanda, Paraguay, Uruguay, Chile, and
Argentina participated in a panel discussion about the status and plans for
their deployments.

The reports were mainly from people implementing technical aspects of the
project rather than official spokes people. As such, they were remarkably open
and constructive.

The third session was about Sugar on non-XO hardware. It is an open question
which several deployments are studying.

The afternoon was an unconference. There were three tracks in which speakers
gave a series of 30 minute talks.

The format worked well. Other Sugar and OLPC events have gotten a bit unruly as
people's passions overflowed.  This event had a lot of listening and learning
followed by conversations over dinner.  The unconference session gave a chance
for many people to give uninterrupted 30 minute talks of personal interest.
Participants were able to 'vote with their feet' about what they personally
found valuable.

Tomorrow kicks off the first day of the code sprint. Wish us luck.

Thanks to everyone that participated. I made a (significant to me) investment in
this event.  The Return on Investment for the community and Activity Central was
quite a bit above what I expected!

david

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] EduJAM day 2 Tour of Uruguay

2011-05-03 Thread David Farning
 -Original Message-
 From: qu...@us.netrek.org [mailto:qu...@us.netrek.org] On Behalf Of
 James Cameron
 Sent: Tuesday, May 03, 2011 4:47 AM
 To: David Farning
 Cc: 'IAEP'; 'Sugar Devel'
 Subject: Re: [Sugar-devel] EduJAM day 2 Tour of Uruguay
 
 On Mon, May 02, 2011 at 04:24:53PM -0300, David Farning wrote:
  From a tech point of view, the big question have been:
  4. questions about why touch pad behavior has changed in the latest
  release with out giving teachers a heads up.
 
 I don't know what release they are using, or were using.
 
 I don't know if they mean XO-1.5 or XO-1.
 
 XO-1.5 touchpad behaviour was changed; tap to click was disabled or
 enabled.  Default varied by release, and the default should be
configurable.
 
 XO-1 touchpad behaviour was changed.  Latest OLPC release on XO-1 is
 10.1.3, which has no touchpad change compared to 10.1.2, so I presume
 they were on 8.2.1 or a derivative previously?
 
 Two XO-1 changes may be relevant:
 
 1.  the enabling of automatic power management from 8.2.1 to 10.1.3, which
 causes touchpad to be momentarily unresponsive when the laptop is
 suspended; this is in the release notes [1], so OLPC did include a heads
up,
 
 2.  the revised kernel driver for XO-1 touchpad [2], which changes the
 behaviour somewhat; this is not in the release notes.  It went in with
10.1.1.
 
 Please encourage them to be involved in testing of development builds, so
 that they can provide feedback early.

+1. And we should also consider this is a custom spin for UY.  So effective
QA will involve:
1. Sugar.
2. OLPC.
3. AC -- if they chose.
4. In country development staff.
5. Users.

From what I can see, the idea that the benefits of working together is
starting to outweigh the costs for many of the participants and
organizations :)

david

 [1]  http://wiki.laptop.org/go/Release_notes/10.1.3#XO-
 1_Automatic_power_management_issues
 
 [2]  http://wiki.laptop.org/go/Touchpad_driver_changes
 
 --
 James Cameron
 http://quozl.linux.org.au/

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] EduJAM day 3 Tour of Uruguay

2011-05-03 Thread David Farning
The theme for day was using the XO to help kids learn. Because this is not
my area of expertise I will defer summarizing the day and take a moment to
explain the rational for a technical focused summit for an education
project.

There are two aspect to the OLPC ecosystem, technological and educational.
Technologically we face three general classes of problems: hardware,
software, and connectivity. When these three aspects of the project work,
teachers and students have an outstanding tool. When one or more of these
aspects is not working teachers and students have a suboptimal tool.

Once the tool is created and understood, educators can train teachers to
take advantage of the tool, create content which builds on the affordances
of the tool, and create curriculum which enable teachers to build on their
understanding and available content to create lessons which align with the
needs of their class, school, and country.

The vision for EduJAM Montevideo 2011 is to bring people working on the
technical aspects together to learn from each other and understand the needs
of educators though a series of presentations and conversations.  The goal
of this process is:
1. Better understand educators needs.
2. Learn how we as developers and engineers can make a product which is more
effective for educators. 3. Learn and communicate with our fellow developers
and engineers to learn to work more effectively.

Ideally, another organization will sponsor a complementary event which
focuses on how educators can leverage the tool to enhance learning. These
complementary events can form the nucleus for a dialog which drive the
project forward.
 
david

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] EduJAM day 1.5 Tour of Uruguay

2011-05-02 Thread David Farning
In the afternoon, our visit to the school was rained out. Instead we went to
a local festival, after which two teachers joined us on the bus. There is a
reoccurring theme of, There is no benefit in complaining about the hurdles,
they are part of life. Let's, get the job doing.

As this series of post is dedicated to helping the technical side of the
project support the education side. The fascinating takeaway was how the
availability of the Aurora project is enabling other education projects.

The region we are visiting has been suffering from migration issues as
people move from agricultural regions to the urban centers because of the
availability of opportunities. One issues is the low attendance and
completion of residents to secondary education.  Historically, secondary
education required that student take a bus which was paid for by the parents
to attend high school.

Now, with the connectivity made available via the Aurora projects and
widespread  exposure of computers via the OLPC projects, adults are saying,
Hmmm, is it possible for me to finish my high school education using these
tools?  The local teachers are saying sure we can do this via a virtual
platform using existing tools such as Moodle.

The most interesting takeaway for me was the statement that content was not
an issue.  One teacher responded, We are high school teacher. We understand
the required content and curriculum. We work with it every day. These
teacher just want the tools to distribute that content they already have.

Another couple of superstar teachers:)

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] Olidata computers in Uruguay

2011-05-02 Thread David Farning
 -Original Message-
 From: sugar-devel-boun...@lists.sugarlabs.org [mailto:sugar-devel-
 boun...@lists.sugarlabs.org] On Behalf Of Gary Martin
 Sent: Monday, May 02, 2011 2:13 PM
 To: Yamandu Ploskonka
 Cc: IAEP SugarLabs; Sugar-dev Devel
 Subject: Re: [Sugar-devel] [IAEP] Olidata computers in Uruguay
 
 On 2 May 2011, at 16:47, Yamandu Ploskonka wrote:
 
  the Sur list is following this thread in detail, I just wanted to share
a FYI for
 developers.
 
  30,000 Olidata laptops have been purchased by Ceibal at $130 apiece and
 teachers are being upgraded to those, trading in their XOs.
 
 Thanks for raising this issue! I've cc:ed the sugar-devel list as it's the
first I've
 read of this.

+1 We had the opportunity to work with one of these machines this morning.
It looks like we should start looking into supporting this piece of
hardware.

After looking at this for the past couple of weeks, I looks like installing
the Fedora based SoaS appears to be the path of least resistance.

The unit we saw this morning seems to be the most recent stock SoaS + 80% of
the dextrose patches + a patch set developed by Uruguay. 

David

  One of the most noticeable source for incompatibilities seems to be
  screen definition, 800x600 in the Olidata, and thus several Activities
  are cropped,
 
 Ouch, quite a few Activity toolbars will likely overflow at 800x600
(overflow
 widgets land in a drop down menu in the far right of the toolbar that
shows
 the text from the tool button hint only). The XO is a 1200x900 screen,
about a
 year or two back there was general consensus that we should try and make
 sure Activities worked well down too 1024x768 as that was common in
 emulated environments and regular laptops/desktops.
 
 These 800x600 display machines will want to make sure they are running
 Sugar using an environmental variable of  SUGAR_SCALING=72, this will
 shrink the UI scale down to fit the lower screen resolution. SUGAR_SCALING
 currently only has an effect at either 72 (works well for 800x600 and
 1024x768) or 100 (for 1200x900 or larger).
 
 There will likely still be activities drawing their canvas with hard coded
 expectations of screen size, but hopefully these will be reasonably few in
 number by now. Please file a ticket if you find any (bugs.sugarlabs.org),
or
 feel free to email me and I'll try and chase them up.
 
 One last additional issue you may find is with the dpi of text. Some
activities
 may seem to display overly large or small text fonts. This issue is quite
a black
 art to solve well, but still worth keeping an eye out for and reporting
back to
 the Activity developer.
 
 Regards,
 --Gary
 
  maybe something to be aware of. Etoys appears to have been fixed
 already.
 
  On 05/02/2011 02:15 AM, nanon...@mediagala.com wrote:
  El pLan Ceibal en Uruguay está entregando a las Aaestras de Primaria
  las Olidata Jump PC, con disco flash de 8 GB
 
  http://www.olidata.cl/index.php/netbook_web/show/id/10
 
  Las olidata se las dan a las MAestras a cambio de sus XO. Me parece
una
 decisión errada, ya que la intención del PLan ceibal es darles a las
Maestras
 una maquina más potente y al día (con respecto a las XO 1 de los niños, de
 hace dos o tres años), pero eso me parece un gran disparate, no puede ser
 que la MAestra no pueda hacer pruebas sobre las XO de los Niños.
 
  La MAestra tiene que entregar su XO 1.0 al Plan Ceibal (que le fue
 entregada hace un par de años) y el Plan ceibal se la cambia por una
Olidata.
 El Año pasado fueron compradas 30.000 olidata , según la pagina web
 institucional del Plan Ceibal.
 
  ---
 
  Una cosa que no me parece correcta es que  la laptop de maestra sea
 diferente ala XO: tiene más capacidad ara el Diario, eso es bueno(8 Gb
contra
 1 Gb), pero la pantalla es diferente, el hardware es distinto, y el sugar
no
 funciona en forma identica, por lo tanto cualquier cosa que la Maestra use
 en su Laptop no podrá ser repetido por los alumnos de la misma forma.
 
 
  NO tiene sentido querer darle una maquina más potente a las MAestras,
 ya que si por ejemplo la Maestra hace una actividad Etoys en su casa ,
 usando sonidos, animación , etc etc, luego va a la clase y le dice a los
niños
 que lo repitan, pero resulta que lo mismo en las Xo tal vez va mas lento,
o no
 funciona igual, o se ve solo en partes
 
  Si se le quiere dar una maquina más potente a las Maestras, deberían
 dejar que tengan las dos: la potente y la XO normal de los Niños. En
este
 momento se les cambia la XO por la Olidata.
 
  NOTA: cuando digo potente (hablando de la Olidata ), es en tono
 jocoso, espero que se entienda.
 
 
  La Olidata Tiene la pantalla un poco más chica que la XO , de 7 y
  800x400, en cambio la XO es de 7.5 y de 1200x900
 
 
  Debe ser por esa razón que ciertas actividades se ven cortadas, al
igual
 que sucede con los emuladores.
 
  Estaría bueno que los programadores hicieran como ya hicieron con
 ETOYS, que lo modificaron especialmente por 

[IAEP] EduJAM day 2 Tour of Uruguay

2011-05-02 Thread David Farning
This morning we are in a classroom observing (and after a few minutes
participating) in a class room session involving turtle art.

The first task was to draw a rectangle with two side being 3 cm long and the
other two side being less then 3 cm. This involved using as ruler to
determine how many turtle steps in a centimeter. 

Step 2 was doing this with the repeat block.

Step 3 was  attaching a right triangle which shared a side with the
rectangle.

At this school, I am not sure how wide spread the practice is, the teachers
work from a daily curriculum. It is up to them to build us of the XO into
the lesson plan.

Once per week a plan Ceibal teacher trainer come to the school to help the
teacher create learning task which align with the upcoming curriculum. Using
this system of training the trainer appears to be a cost effective method of
scaling expertise.

From a tech point of view, the big question have been:
1. Running sugar on non-xo hardware.
2. The journal is a bit confusing.
3. Print is a must.
4. questions about why touch pad behavior has changed in the latest release
with out giving teachers a heads up.

david

 

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] EduJAM day 2.5 Tour of Uruguay

2011-05-02 Thread David Farning
The afternoon and evening sessions of the tour were a great complement to
the morning session.  Yes, you heard correctly, afternoon _and_ evening
sessions:) Pablo has us hopping. Tomorrow morning starts a 600am.

The afternoon session was again at public school 286. Rather than observe
and interact with the kids in the class room, the teachers asked us to take
a step back and look at the larger picture of how the laptop project affect
the school and how the school affects the project. One interesting note was
the emphasis they had that the laptops were educational tools. They were
part of a larger tool box consisting of textbooks and other activities.

While kids usually receive their laptop at 6, when they start school, it is
common for kids to begin using and becoming familiar with the laptop and
sugar when they are 4 years old. By the time kids enter high school they
have had several years of experience. This presents a challenge for teachers
as they try to catch up and keep up with the kids :)

The primary technical requests were that social-calc works and that there is
timeline activity.

In terms of education theory, it was interesting to listen to a discussion
the evolved from the timeline request.  Several teachers commented that the
timeline was a very valuable tool because it would give the students a place
to consolidate the information they had learned over several week.  Maybe it
was my poor Spanish. But the conversation seemed to reflect concepts very
similar to portfolios and the act of refection the journal affords.

The evening session was with Flordeceibo. (http://www.flordeceibo.edu.uy/ )
We started the evening off with a video providing an overview of project. It
is just over 2.5G so I hope that someone with some bandwidth uploads it and
links to it in a blog post.

Sadly, the university and Flordeceibo are not directly involved in teacher
training.  Teacher education happens in a parallel system similar to normal
schools.

The real meat of the session (for software developers) happened after the
break during a feedback session. Several of the Flordeceibo members had
lists of bugs they have encountered during the last few years. At that point
the passion became palpable.

Because of the sheer amount of feedback we invited everyone to share
'headlines' of their concerns at this session. Then, follow up Sunday
morning at the first day of the hack feast.

Over the last couple of months one on the most important lessons we have
learn while working with ParaguayEduca is the importance of one on one and
face to face sessions between developers and educators. The normal tools
that open source developers use for feedback are too 'unfamiliar' to most
teachers.

Instead the feedback, at least initially, requires a personal relationship
which builds trust and helps the developer and educator learn how to
effectively communicate. As a result, we invited everyone to join the sugar
camp on Sunday morning.  I would like to encourage all developers to spend
time talking one on one with the Flordeceibo members to turn their feedback
into a format which is can be submitted as bug reports.

david

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Awesome day 0 for eduJAM.

2011-05-01 Thread David Farning
Yesterday was have picture perfect start to eduJAM!

The day was planned by the Ceibal-volunteer associations as part of their
annual (sometime biannual) meeting. For lack of a better word, my Spanish is
still rather fuzzy, I will use the term Ceibal-volunteer associations to
describe Ceibal-Jam, Rap-Ceibal, and Flordeceibo.

Many of us in Sugar Labs are familiar with Ceibal-Jam, the software-arm of
the project, from the public work at http://ceibaljam.org/ . Particularly
interesting is their work on Sugar activities at
http://ceibaljam.org/drupal/?q=lista_proyectos .

Rap-Ceibal is the volunteer support organization. There public work is at
http://rapceibal.blogspot.com/ . They are doing really interesting work
creating regional centers. Basic service and support happens in the schools,
while more complicated or specialized service and support happen in the
regional centers.  It is a great model.

Thirdly, Flordeceibo, is the education arm that builds on the technical work
of Ceibal-Jam, Rap-Ceibal, and other organization to enable a efficient and
effective education for student in Uruguay. http://www.flordeceibo.edu.uy/

The morning started with the groups giving status reports of current
projects and roadmaps for next year. It was a great example of people
saying, 'we see a problem and we are trying to fix it.'

The afternoon was a series of videoconferences with distant schools. Groups
from various school shared their experiences and concern. This was followed
by an open discussion on how to meet their needs.

Midafternoon we broke up and shared a meal, ( The proper translation for the
dish was 'delicious heart attack on a plate' ) with others planning on
attending the Tour of Uruguay.

Overall two thumbs up to everyone involved. As special shout out to Antel, a
Uruguayan telecommunications firm, for providing the facilities -- which
included an video conferencing system that would make any hacker want to get
in there and take in apart to figure out how it works :) The moderator,
Latise (sp?) did an outstanding job of keeping the program running smoothly
and on schedule. Which can be harder than it appeared when you have a room
full of smart, curious, and passionate people.

david

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] EduJAM day 1 Tour of Uruguay

2011-05-01 Thread David Farning
EduJam started with a bang this morning with visit to the Aurora project in
Tala, Uruguay.  The project, run by a local farmers cooperative, brings WIFI
to farmers outside of Tala.  The local telcos decided that it is not
profitable enough to bring service to the area. In true hacker  fashion they
built their own system.

The core of the system is a number of transmission towers which are
connected via directional antennas.  These towers can be comfortably located
about 10km apart. Each tower has a number of WIFI transmitters which serve
local families. If the family is close they can use standard WIFI. As they
move farther from the tower they use a systems of extenders to connect to
the nearest tower.

These towers are daisy chained to enable coverage for a wide area at a very
low price. Back in Tala, a nearby community with internet connectivity, the
projects connects via a standard DSL connection.

The most amazing part is that they can set up a complete tower, antennas,
and base station for less than $1,000 each. They fabricate the towers
themselves. The families which will be using the tower erect it themselves.
Some of the towers are taller than 20 meters. Pretty impressive. Once the
tower is up, project members come and install the transmitters.

It is a great example of hardware hacking. The local families, left behind
by the local telco, are scratching their own itch to provide connectivity
for their kids who use XOs and for themselves. The project members are
freely sharing their knowledge and experience with other co-operatives so
they can set up system for themselves and their children.

Absolutely brilliant idea which is being well executed :)  Formal session
was follow by an asado which gave us a great chance to talk with the people
with that set up the project.

david

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] ANNOUNCE: Moving Sugar to GPLv3+

2011-04-25 Thread David Farning
technical discussion snipped

 Since this is the core point of disagreement within the community, the act
of
 accepting or rejecting the GPLv3 assumes for us the deeper meaning of
 refusing or endorsing TiVo-ization and DRM in conjunction with Sugar.

'Premature optimization is the root of all evil' -- Donald Knuth

The question is: Of the tasks Sugar Labs can do to improve the educational
valued of Sugar and collaboration within the ecosystem is tweaking the
license among the critical tasks?

david

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] eduJAM! 2011: A Vibrant Summit With A Diverse Range Of Offerings

2011-03-21 Thread David Farning
 -Original Message-
 From: sugar-devel-boun...@lists.sugarlabs.org [mailto:sugar-devel-
 boun...@lists.sugarlabs.org] On Behalf Of Organización eduJAM! 2011
 Sent: Monday, March 21, 2011 2:05 PM
 To: iaep@lists.sugarlabs.org; sugar-de...@lists.sugarlabs.org
 Subject: [Sugar-devel] eduJAM! 2011: A Vibrant Summit With A Diverse Range Of
 Offerings
 
 We are very excited to update you with the latest information about
 the�eduJAM! 2011 http://ceibaljam.org/?q=edujam2011_en �summit. It is
 great to see that the different pieces of the puzzle are coming together for 
 what
 will undoubtedly be a landmark for the international community of educational
 free-software developers. Many of the main developers behind the Sugar
 platform will be present (Walter Bender, Aleksey Lim (alsroot), and Bernie
 Innocenti among�others http://ceibaljam.org/node/1108 ). Additionally,
 people working on different OLPC deployments will be there which guarantees
 an excellent environment for moving the area of 1-to-1 computing in education
 projects and related discussions forward.
 
 More than anything we aim to make the summit an event to create and amplify
 relationships in this community.
 
 Place
 
 The summit will take place at the Universidad del Trabajo del Uruguay (UTU) 
 and
 more specifically in its brand-new�PAOF building
 http://ceibaljam.org/node/1171 �which is located in Ciudad Viaja, the 
 historic
 and commercial heart of Montevideo. Apart from this allowing us to work within
 a comfortable and versatile space, it also provides opportunities to enjoy 
 this
 beautiful part of the city during free hours.
 
 Program
 
 The summit will begin in the afternoon of�Thursday, May 5 with an informal
 reception aimed at allowing us to get to know each other as well as catch up.
 
 On�Friday, May 6 the intensive work begins. This day will be organized in two
 tracks. In the morning we will focus on a broad vision of the core challenges
 encountered when designing a software platform aimed at learning in school
 environments in general and in 1-to-1 scenarios in particular. We can revise 
 and
 revisit these experiences in light of the experiences made within this 
 context in
 the past few years. What has and hasn�t worked when it comes to the
 software? How can we support the creation of effective learning communities?
 How can we make the development processes in such a diverse and distributed
 community more efficient? Which applications are we still missing? These are
 some of the questions which will be on the table.
 
 In the afternoon the summit will turn sweet as we fully dedicate it to Sugar. 
 On
 the one hand we will hold a �Sugar Camp� where will discuss the current state
 of developments, local labs, the roadmap and how to optimize the work in the
 community.
 
 Simultaneously on Friday afternoon there will be workshops aimed at people
 such as students and newcomers who want to learn how to develop for Sugar.
 
 On�Saturday, May 7 the morning will be focused on the various experiences
 made in 1-to-1 projects. There will be talks by people working on different
 deployments, explaining what they have done and discussing the necessities and
 requirements when it comes to software platform. We consider this to be an
 important input for planning future work.

I would like to make a personal invitation to deployment developers and 
technical support staff to participate in the events Saturday, Sunday and (if 
possible) into the next week. On Saturday, Activity Central will create a 
'Critical Tasks' list. As we identify critical tasks which are shared across 
multiply deployments, we will add them to the Dextrose TODO list for our 
upcoming release and inclusion in the next OLPC OS release.

 This afternoon will be run in an �unconference� mode. This means that there
 will be different talks, workshops, and discussion rounds which will be 
 planned
 and decided upon by the participants on the spot. We thereby hope to learn
 more about the various ongoing projects, discuss roadmaps as well as form
 small development and investigation groups.

Starting Saturday afternoon Activity Central developers will run a 'Critical 
Tasks' workshop to help deployments identify and work on their important bugs 
and feature requests. Through the follow week AC developers will be available 
to:
1. Help you solve those critical tasks.
2. Help you push those solutions upstream to OLPC and Sugar Labs.
3. Help you identify and coordinate with other deployments and organizations 
that are facing similar issues.

Look forward to see you at eduJAM.
david

 
 Conozco Uruguay Tour
 
 Independent of the summit, a variety of activities will take place in the days
 leading up to it. These activities are aimed at people who want to explore the
 experiences Uruguay is making with Plan Ceibal in more depth. They will take
 place between Saturday, April 30 and Thursday, May 5. Together with RAP Ceibal
 and OLPC we have developed the 

Re: [IAEP] Sugar Labs 2010-2011 Election Information

2010-10-30 Thread David Farning
On Sat, Oct 30, 2010 at 12:10 PM, Luke Faraone l...@sugarlabs.org wrote:
 Hi all,

 Sorry for the confusion regarding the 2010-2011 elections. We all could
 have done a better job promoting it. For that reason, I'm adjusting the
 election schedule[1] as follows:

  * 2010-11-01 23:59 EDT: Candidate list closed. (per SLOB motion)
  * 2010-11-10 23:59 EST: Deadline for applications for membership.
 Applications after this date will not be processed before the election.
  * 2010-11-13: All valid 2010-2011 applications processed.
  * 2010-11-14 17:00 EST: Ballots sent by email, start of voting period.
  * 2010-11-28 17:00 EST: Voting period ends.

I wonder if Luke wrote this email on his industry leading mobile
device while attending the 'Rally to Restore Sanity.' [1]

david

1. http://www.rallytorestoresanity.com/

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Moving forward.

2010-10-25 Thread David Farning
Yesterday I sent a rather blunt email on my concerns about the
project.  It seems the observations resonated with many people while
striking several nerves.  The volume of private mail or CCed mail (to
a subset of the Sugar Labs participants) responses was unexpectedly
high.

The five main themes of the responses are:
1. Could you possibility be any more abstract?
2. Several of the points are valid.  Here are my
responses/suggestions. This should be on a public thread, but someone
else will have to start it.
3. The core problem is trust.
4. This conversation is like an iceberg, the 'community' only sees
10% and not the other 90%.
5. Dave you are just a jerk, now shut up.

For better of worse, all five points are valid.  I am a bumbling jerk
who is struggling to rebuild community trust without airing anyone's
dirty laundry, including my own.

To put all of my cards on the table:
1. The ideas driving OLPC and Sugar are sound.
2. Sugar Labs will continue to fragment until the issue of trust is resolved.
3. Because of this, I left Sugar Labs to start a business which
provides service and support for Sugar.
4. I need Sugar to succeed. I need OLPC to succeed.
5. I have been trying to operate 'under the radar' because some in
Sugar Labs and OLPC have contacted individuals I am working with and
'suggested' that they not work with me.

Talk about the pot calling the kettle black.  I get pissed off about
the lack of trust and community building in Sugar Labs, so I go off
and form a fork which operates largely in secret.

Two years ago, I suggested that the over sight board appoint Walter
Bender as Executive Director of Sugar Labs so he would be able to
speak on behalf of Sugar Labs.  He had three skills which Sugar Labs
needed. 1) He was able to clearly and effectively communicate the
goals of Sugar and the mission of Sugar Labs. 2) He was able to create
an identity for Sugar Labs outside of OLPC. 3) He was a tireless
advocate for Sugar.  In the past two years Sugar Labs has progressed,
largely because of Walter.  The goal of sugar and Sugar labs is well
understood. Sugar Labs has a clear identity.

Now, Sugar Labs has different needs; pragmatic bridge building between
individuals and organization.  It is time to look for someone with
those particular skill to lead/herd Sugar Labs forward.  As such I
would like to recommend that SLOB ask and appoint Adam Holt as the
next Executive Director of Sugar Labs.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] stepping down as maintainer

2010-10-24 Thread David Farning
On Sun, Oct 24, 2010 at 7:55 AM, Bastien bastien.gue...@wikimedia.fr wrote:
 Hi David,

 I think everyone agrees that Tomeu stepping down as a maintainer is a
 big loss.  I join my voice to those who already expressed this and my
 thanks to Tomeu for all the crazy work he's been achieving here - and
 it's not only lines of code, it's also a general welcoming and helping
 attitude, which is priceless.

 I did a small experiment: I clicked on the Getting involved button.

 I'm not falling into those categories: developer, designer, educator,
 content writer.  I can help as a translator (I did so in the past) and
 as a people person.

 So I clicked on the People person button.

 I understand the projects listed here and how I can help them: marketing
 team, documentation team, deployment team, local labs, soas.

 Here is my list (preference order) :

 - *Local labs*: I will try to have more people involved in Sugar from
  France.  Since early october, we have at least two new members of OLPC
  who will work more on Sugar.

 - *Sugar on a stick*: together with other members, I will try to develop
  a french Soas.

 - *Marketing team*: [sadly enough, we don't seem to have news from Sean.
  Hopefully nothing bad happened to him - he's usually very responsive.]
  My role here could be a general outreach role: trying to translate
  marketing documents, speak more about Sugar in events, etc.

Bastien,
Thank you for all you have done and being the first person to
_step_up_ and identify yourself as willing (and from your past
performance -- able) to commit to working on a much needed set of
tasks.

 I'm addressing this message to you since your the contact for this role.

 :)

 There is something I miss in the list of teams/projects for people
 persons: community management.  This is very different from marketing
 and outreach.  Maybe this project/role could be advertized somewhere
 on the wiki.

 I'll keep this list updated about progress I make in this role.

 PS: I don't dwell on Sugar criticism because I fail to grok how this
 could help us go ahead and keep moving forward.

+1.  The focus is not criticism or even discussion.  The criticism
is a call to action -- Sugar Labs needs help.

The focus is the generous response of people like you going though the
process of:
1.  Determining what can be done to make Sugar and Sugar Labs better.
2. Identifying how you can apply your time and specific talents to those needs.
3. Making the public commitment to work on a few specific needs.

david

  Criticism is useful
 when resources are growing, not when they are shrinking.

 --
  Bastien

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] stepping down as maintainer

2010-10-23 Thread David Farning
On Tue, Oct 19, 2010 at 11:50 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 Hi,

 for personal reasons have to drastically reduce my involvement in the project.

 Will be leaving maintenance of my modules and unsubscribing from the
 mailing lists. My place on the board is vacant from now on and I'll be
 adding to the wiki the new vacancies:
 http://wiki.sugarlabs.org/go/Vacancies

 Cheers and good luck,

 Tomeu

Sugar Labs lost its lead developer.  It is unfortunate that no-one has
done a public review of the reasons and implications of Tomeu quiting.
 Tomeu's leaving is significant enough that Sugar Labs should take a
hard look at what is working, what is not working, and how to fix the
pieces that are not working.

At the risk of angering pretty much everybody Sugar Labs has three
fundamental problems.  Sugar Labs is optimistic to the point of
untruthfulness.  Sugar Labs is lead by veto rather than vision.  There
is a lack of accountability to stakeholders.

Sugar Labs is optimistic to the point of untruthfulness.  The main
_symptom_ of this is the current state of Sugar Labs.  Sugar is not
perfect. Sugar Labs is not perfect.

The _disease_ is an adherence to faulty premises rather then the use
of the Scientific Method of: Ask a question. Do background research.
Construct a hypothesis. Test your hypothesis by doing an experiment.
Analyze your data and draw a conclusion. Communicate your results.

Premise 1. Sugar is open source, written in python, and the source is
easily available.  Therefore kids will develop and improve Sugar.
What fraction of useful and usable improvements have been committed
into sugar by the target users.  The key metric is commit ratio.
Everyone has an antidote about some budding hacker.  As with the patch
acceptance process, developing Sugar requires more than solving logic
problems.

In theory this premise is sound, and desirable, the overall technical
capabilities of a nation will improve as more people are exposed to
Sugar at an early age.  The question become what is the time lag
between exposure to Sugar and useful contribution to Sugar?

Premise 2. Sugar is open source, written in python, and the source is
easily available.  Therefore deployments will develop Sugar.  What
fraction of useful and usable improvements have been committed into
sugar by deployments.

In theory this premise is sound, and desirable, Sugar deployments and
their associated support infrastructure provide a catalyst for
building local technical capability. The question becomes, considering
the limited resources of deployments, is the benefit of contributing
upstream worth the cost?

Premise 3.  Any problems with Sugar are because the user, teacher, or
deployment is not smart or motivated enough.  What are the usability
concerns of users, teachers, and deployments? How are those concerns
being addressed?

In theory this is true yet undesirable.  A significantly motived
person _can_ figure out just about anything.  The primary decision
making factor for users, teachers, and deployments is marginal
benefit.  Does using and learning to use the laptop/Sugar prove a
marginal benefit over other learning opertunities.

Sugar Labs is lead by veto rather than vision. A _symptom_ is the
development process. It it easy to have fix commited to Fedora or
OLPC.  It is hard to have a fix commited to Sugar Labs.  When someone
sends a useful fix to either OLPC or Fedora, a senior developer takes
the patch, review it, fixes it up (if necessary) and thanks the
contributor.  This provides an incentive and on-ramp for less
experienced developers to participate and contribute.

Sugar Labs rejects most patches.  Once a patch is technically correct,
which can take several iterations for a new developer, it is forward
to another developer for their vote of approval.  The end result is
that very few people bother to submitted patches upstream.

The _disease_ is a marginalization of anyone who dissents.  As a
result no one is willing to take a risk.  There is an unwritten
checklist for participation.  1) Are you a knowledgeable, experienced,
and patient open source developer? 2) Is your goal open source
advocacy? 3) Are you a strict constructionist? 4)  This results in
very low participation in Sugar Labs.

There is the lack of accountability to stakeholders.  The Board of
Directors of an non-profit organization the board reports to
stakeholders, particularly the local communities which the nonprofit
serves.  The Executive Director is responible for carrying out the
strategic plans and policies as established by the board of directors.

As a starting point for bringing Sugar Labs out its current crisis, I
suggest the following plan:

1. Each Oversight board member, or candidate, identify a stakeholder
and spend the next 12 months advocating for that stakeholder.
Advocating includes: Identify the specif needs and goals of the
stakeholder.  Identify the resources that stakeholder can contribute
to Sugar Labs.  Identify how 

Re: [IAEP] [Sugar-devel] Proposal release management

2010-06-24 Thread David Farning
On Thu, Jun 24, 2010 at 4:49 AM, Bert Freudenberg b...@freudenbergs.de wrote:
 On 24.06.2010, at 09:32, Simon Schampijer wrote:

 Hi,

 in May I tried to find someone to replace me as release manager [1] for
 0.90, but as nobody has stepped up to do the job as we defined it I
 decided that it will be best to keep this role for some more time. I
 think it will be important for Sugar that we keep some continuation of
 the processes that we have been setting up during the last years. It
 would also be very good if someone would like to lend a hand with this
 or shadow me for future tasks so more people in Sugar Labs have direct
 hands-on knowledge.

 We defined the role of the release manager in the past 3 releases like
 the following:

 * setting the schedule
 * make sure that the Feature process is followed by the submitters [2]
 * keeping the wiki updated about the released modules and making sure to
 have final release notes available
 * sending email reminders about approaching Freezes, tarball due dates etc

 The schedule would be based on the GNOME releases, a 6 month release
 cycle. As there is not much time left for 0.90 [3] I think we should
 mainly focus on stabilizing and landing the features that were left over
 from the last release. I would start to announce a time frame for future
 releases so that future development can go on. New Features would be
 handled by the Feature process, as it has been the case in the past.

 What do others think about this?

Thanks Simon.  That is a good plan.  You have been doing an
outstanding job implementing it for the last several cycles.

 I think thanks are in order. It's a solid, low-risk plan for the last mile 
 in our development cycle. Now we just need to get our acts together in 
 covering the middle ground, so you actually have something to release :)

 To that extent I proposed to the Etoys developers to follow the Sugar 
 development cycle more closely. And that's what we're going to do.

Thanks Bert.  That will help those of us working downstream a great
deal.  As a side note, what is the situation with Etoys vs scratch?
Many teachers are very familiar with (and love) scratch and wonder why
sugar ships Etoys:-(

david

 Thank you for stepping up again!

 - Bert -


 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] What Sugar ships (was Re: Proposal release management)

2010-06-24 Thread David Farning
On Thu, Jun 24, 2010 at 9:52 AM, Bert Freudenberg b...@freudenbergs.de wrote:
 On 24.06.2010, at 15:29, David Farning wrote:

 On Thu, Jun 24, 2010 at 4:49 AM, Bert Freudenberg b...@freudenbergs.de 
 wrote:

 To that extent I proposed to the Etoys developers to follow the Sugar 
 development cycle more closely. And that's what we're going to do.

 Thanks Bert.  That will help those of us working downstream a great
 deal.  As a side note, what is the situation with Etoys vs scratch?

 Why do you think there's a vs? Both have their place.

I apologize, it would have been better if I had phrased the question
as, Can you explain the differences and similarities between scratch
and etoys and their different use cases?  My original question was
rather off the cuff and off topic:(

The teachers I talk to seem to have a similar misunderstanding to my
knowledge gap.  (Note these are neither squeak, etoys, or sugar
experts) That etoys is a rebranded squeak for sugar.

Many developers (again non-squeak, etoys, or sugar experts) are under
the impression that etoys is squeak without the licensesing issues.

 Many teachers are very familiar with (and love) scratch and wonder why
 sugar ships Etoys:-(

 david

 While Scratch is less powerful than Etoys, it certainly is more polished and 
 easier to get into. That was one of its design goals - to let teenagers have 
 immediate fun in an hour after school, without needing too much guidance. 
 Etoys OTOH was designed to be used by a skilled teacher as part of a larger 
 curriculum - and it is a prototype that escaped into the wild without 
 seeing much polishing.

 So I can see why teachers love Scratch. I love Scratch, too. It requires much 
 less effort to get started. Certainly enough, Scratch comes pre-installed on 
 many OLPC builds (and OLPC recently sponsored me to add basic Journal 
 support). Besides, the xo bundle can easily be downloaded.

 But for inclusion in Sugar itself there are more criteria than just ease of 
 use. Like the willingness of developers to work in the Sugar community. Which 
 is almost synonymous to the development process itself being open. Or making 
 serious efforts to fit into Sugar - be that UI design, or supporting 
 collaboration etc.

 Etoys is working in that direction, and also welcoming contributions. The 
 Scratch developers have other priorities. In a way, Scratch is so beautifully 
 simple *because* its development is so tightly controlled. It's like an Apple 
 product compared to a Linux one. The Linux program might be more powerful, 
 but many people would still prefer the simpler, polished, less confusing 
 Apple product. Others see beyond the flaws of the Linux program, and some 
 dive in and help improving it. Given time, money, and effort it might even 
 attract users in the general public ;)

 Btw, a good way for teachers to learn about Etoys is attending Squeakfest:

        http://squeakfest.org/

 Coming back to your question, why Sugar ships Etoys, it's because Etoys 
 developers care about it, and the others find it to be useful. Which is the 
 case for anything that Sugar ships.

Thanks.  Would you mind turning your answer into a blog post to which
I can refer people when they ask about etoys and squeak... and how
they fit together.  It comes up alot:)

One of the downstream projects I am working on is USR which stands for
Ubuntu [Sugar,Squeak, Scratch] Remix.  Once we have the Sugar part
stabilized we will start working on the Squeak part.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [SLOBS] RFC: F11-0.88 as a Sugar Labs Project

2010-06-18 Thread David Farning
On Thu, Jun 17, 2010 at 10:20 PM, Mel Chua m...@melchua.com wrote:
 On 06/17/2010 10:28 PM, Bernie Innocenti wrote:
 At the next meeting, I would like to propose the Fedora 11 with Sugar
 0.88 builds for the XO-1 and XO-1.5 as a new official project.

 It is sponsored jointly by Paraguay Educa and Activity Central,
 coordinated by me and hosted by the Sugar Labs infrastructure:

    http://wiki.sugarlabs.org/go/Deployment_Team/Sugar-0.88
    http://people.sugarlabs.org/bernie/olpc/f11-xo1-0.88/

 If the board approves, I will add a link to the sidebar, near Sugar on a
 Stick, and create a top-level homepage with content directed at users.

 I need help picking a pronounceable name, F11-0.88 is revolting.

 Posted to
 http://wiki.sugarlabs.org/go/Oversight_Board/Minutes#Agenda_items as a
 motion, since all the links are public anyhow and the discussion will be
 as well.


I would encourage that  F11-S0.88 _not_ become an official Sugar Labs
at this time.  My biggest concern is maintenance responsible.  If the
project becomes an official project, Sugar Labs has an implied
maintenance responsibility.   If F11-S0.88 sucks, it will cast a long
shadow on the upstream project Sugar Labs not the downstream project
where that shadow belongs.

On the other hand, if Sugar Labs would like to assume maintenance
responsibility they are welcome to roll the project into SL.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Health nuts

2010-06-15 Thread David Farning
On Tue, Jun 15, 2010 at 11:06 AM, Beth Santos b...@waveplace.org wrote:

 Hey all,

 Looking for someone who can get me in touch with people who might be
 interested in developing health-focused Etoys education software- nutrition,
 sanitation, HIV/AIDS awareness, malaria prevention, anatomy, etc. This is an
 initiative I want to grow in countries in Africa and could use some content
 help. Whether it's international health professionals or computer
 programmers who want to make the actual games, let me know.


A rather minor point

As we talk about content to augment teaching specific concepts or tasks ,it
might be better to use the educator terminology of learning object[1] rather
than game.  I see rather a lot of push back when talking to teachers about
'games', but the parse 'learning object' seems to resonate well:)

david

1. http://en.wikipedia.org/wiki/Learning_object

 Beth


 ---
 *Beth Santos*
 Outreach Coordinator
 Waveplace Foundation

 Tel: +1 610 797 3100 x 44
 Fax: +1 610 797 3199
 Cell: +1 603 661 1273
 http://www.waveplace.org

 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] maintaining activities (was Re: Too many open fronts?)

2010-06-10 Thread David Farning
On Thu, Jun 10, 2010 at 1:41 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Thu, Jun 10, 2010 at 06:17, Martin Langhoff
 martin.langh...@gmail.com wrote:
 On Wed, Jun 9, 2010 at 11:10 PM, Bernie Innocenti ber...@codewiz.org wrote:
 El Wed, 09-06-2010 a las 02:59 -0700, Yioryos Asprobounitis escribió:
 However, the 20month+ old F9/0.82, os802 build remains the official XO-1 
 build.

 It's just a formality, nobody has been doing any work on it for years.

 To clarify: I am working on it. and it mainly helps deployments that
 are implementing security. It is taking ages because, well, I am doing
 the work of 5 people.

 I share Yiorios' concerns. Both OLPC and SL are overreaching wildly.

 We have to focus on polish, on getting something useful in the hands
 of children. On making a difference there. We cannot leave XO-1.5
 unfinished. We have to hear the SoaS crowd when they point out that
 very few activities are shippable.

 I agree in that focusing is very important. But paradoxically, you can
 be in a situation in which individuals are focused on their work but
 the organization as a whole isn't focused at all.

One possible approach is for Sugar Labs to focus on being an
innovative upstream while downstreams like Activity Central, SoaS, and
deployments focus on the polish. Activity Central is pulling
deplolyment level polish into Sugar.

dav

 To have focus at the team level we need someone who takes a step back
 from the task at hand and takes a look at where we are and where we
 are supposed to go.

 I think teams provide a space for that and allows for different people
 to take that reflective role at periodic times.

 We used to have an Activity Team and it actually saw the importance of
 maintaining existing activities so had processes for adoption and for
 finding the resources. Unfortunately, as often happens in efforts like
 ours, the person driving that effort had to attend to other matters
 and the team languished.

 But we still have people reading our mailing lists with the skills and
 interest to maintain activities and update them to work on other
 platforms than the XO-1 with 8.2.x, but we lack focus.

 Can we find someone who wants to coordinate the team?

 It's not such a big role in terms of work, the responsibilities are
 the following:

 - keep the mission statement updated in the wiki page
 http://wiki.sugarlabs.org/go/Activity_Team ,

 - keep the members list updated,

 - call for biweekly meetings and moderate them,

 - publish meeting minutes and logs.

 But this relatively small effort can bring the focus we need.

 Regards,

 Tomeu

 cheers,


 m
 --
  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
 ___
 olpc mailing list
 o...@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/olpc

 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] maintaining activities (was Re: Too many open fronts?)

2010-06-10 Thread David Farning
 We have to focus on polish, on getting something useful in the hands
 of children. On making a difference there. We cannot leave XO-1.5
 unfinished. We have to hear the SoaS crowd when they point out that
 very few activities are shippable.

 I agree in that focusing is very important. But paradoxically, you can
 be in a situation in which individuals are focused on their work but
 the organization as a whole isn't focused at all.

 One possible approach is for Sugar Labs to focus on being an
 innovative upstream while downstreams like Activity Central, SoaS, and
 deployments focus on the polish. Activity Central is pulling
 deplolyment level polish into Sugar.

 Will all those downstreams work on polish separately or will they
 cooperate and pool resources in a common place?

The best answer I can give is It depends.  Typically, upstreams and
downstreams tend to branch and merge.

A good example is the kernel. Over the last 5-10 years many projects
and companies have tired to branch... and maintain that branch.  They
realized that maintaining a branch is _really_ expensive.  The
remaining (successful) projects and companies work very hard to stay
in sync with the upstream kernel.

FWIW, at Activity Central we have no infrastructure of our own.  (This
is not completely true, bernie does send around his hot bugs list
for members of the Deployment Support Network. Once the bugs have been
assigned, all review happens on the lists or irc.)Everything thing
happens in either Sugar Labs, OLPC, Debian, Ubuntu, or Fedora.  This
is intentional.  Rather than ship anything custom, we must push it
upstream.

The key is that we, and others, search for common goals and push them
forward.  A successful open source ecosystem depends on finding
intersections rather than forcing unions.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] Quote, docs (was Re: Sugar Digest 2010-05-20)

2010-05-24 Thread David Farning
On Sun, May 23, 2010 at 5:52 PM, Edward Cherlin echer...@gmail.com wrote:
 On Thu, May 20, 2010 at 11:42, Walter Bender walter.ben...@gmail.com wrote:
 ==Sugar Digest==

 One of the nice things as you walk through the museum is that on
 almost every wall is a quote about play. They have a nice collection
 of quotes on line as well (See
 http://www.museumofplay.org/about_play/quotes.html). I read them a
 favorite quote from Marvin Minsky, which seemed to resonate with them:

    The playfulness of childhood is the most demanding teacher we have.

 Thanks. I added that one to http://wiki.sugarlabs.org/go/User:Mokurai/Quotes

 We talked about how we might engage them in some informal learning
 activities using Sugar.

 I have had such talks with The Tech Museum of San Jose and the
 Exploratorium, and intend to talk with others. The Tech invites
 interactive exhibit designs.

 I had written an NSF grant a while back: Adding depth to and building
 community within informal education, which was rejected, but is worth
 pursing nonetheless.

 Would you be intereted i joii i a a appi
 I'd proposed to explore how children's activities at informal learning
 venues can be extended by providing learners with inexpensive,
 ubiquitous access to learning software (Sugar on a Stick). By
 designing, developing, and testing a proof of concept that combines
 informal learning activities with in-depth follow up at home or in the
 classroom we still hope to demonstrate a learning ecology that
 increases public interest in, understanding of, and engagement with
 science, technology, engineering, and mathematics.

 Specifically, I proposed to leverage Sugar on a Stick to promote the
 use of Sugar in informal learning settings: prototyping Sugar-based
 exhibit kiosks in museums and libraries that will facilitate visitor
 interactions. Visitors will be given a Sugar-on-a-Stick USB storage
 device with which they can make bookmarks of exhibits that they
 visited, found interesting, or saved data from. Exhibit designers can
 use kiosks to collect visitor information and offer additional
 activities and data that visitors can work with when back at school or
 home. Activities can be downloaded to the Sugar-on-a-Stick device from
 the kiosk. The work done by visitors can be incorporated into the
 exhibit itself and featured on line, with the potential to reach a
 broader audience.

 I still hope to learn how the data- and instrumentation-rich
 facilities found in informal learning settings and Sugar might be
 combined to further engage the interest of learners in scientific and
 technological literacy. I hypothesized that by giving visitors the
 ability to take programs and data home with them, we will be able to
 challenge them with more in-depth and engaging problem solving. Giving
 them activities to take home, connecting these activities to other
 learning experiences and interests, and connecting these activities to
 a community of learners are significant enhancements to the status quo
 of informal learning.

 We need to evaluate the technical, logistical, and pedagogical impacts
 on the museum exhibit experience, library digital and human resources,
 and education programs s that we can develop an implementation guide
 for informal-learning professionals.

 === Help wanted ===

 2. We have a number of vacancies (See
 http://wiki.sugarlabs.org/go/Vacancies). Many of these positions
 require organization as opposed to technical skills and only a
 commitment of a few hours per week.

 Clearly I should offer to take this one on:

 Document team coordinator: carries administrative tasks such as
 organizing regular meetings, keep the TODO list updated, keep the
 membership list, and makes sure that the team has clear goals and is
 kept focused. I'll look over the latest at
 http://wiki.sugarlabs.org/go/Documentation_Team and see if I have any
 questions.

That would be excellent.  There is a small team working on API
documentation.  For the next 6 months, they will be working on
'restructured text' API documentation for core sugar documentation.  I
believe that they have settled on sphinx as the preferred tool.

I hope you find this a useful addition to the documentation team and
useful addition to the Sugar Labs.

david

 regards.

 -walter

 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep




 --
 Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin
 Silent Thunder is my name, and Children are my nation.
 The Cosmos is my dwelling place, the Truth my destination.
 http://www.earthtreasury.org/
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep
___
IAEP -- It's An Education 

Re: [IAEP] [Sugar-devel] Supporting Sugar .88 on the XO1

2010-05-21 Thread David Farning
On Fri, May 21, 2010 at 4:46 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
 On Fri, May 21, 2010 at 02:04, David Farning dfarn...@gmail.com wrote:
 On Thu, May 20, 2010 at 6:55 PM, Paul Fox p...@laptop.org wrote:
 david wrote:
   As Bernie announced, we working on supporting Sugar .88 on the XO-1.

 hi david --

 for those of us joining this thread late, can you expand on what/who
 you mean by we?  (or tell me to read the archives, if that's
 more appropriate.)

 Sorry, By we, I mean Activity Central and compnay that Bernie,
 Caroline, and I have started to support OLPC and Sugar deployments.

 It is going to take me awhile to figure out how to communicate with
 the community.  I would like to keep the larger Sugar and OLPC
 projects aware of what our company is doing.  But, I don't what it to
 sound like a press release of pitch for the company:)

 Any blog we could syndicate in the planet(s)?

Excellent point,

I'll start a blog and request that it be syndicated on the Sugar Labs
and OLPC planets.

 Regards,

 Tomeu

 david
 paul


   This projects is customer driven by the deployment in Paraguay.  They,
   along with bernie, made a decision that it would be more useful,
   usable, and cost effective to settle on .88 rather than .82.  This
   strictly a decision made by a single deployment, which I support.
  
   As an ecosystem we can make lists of Pros on Cons why this is a good
   or bad decision and why I am an idiot.  At the end of the day this was
   a decision made by a deployment.  The primary reason for this decision
   is that the deployment does not yet has an established base of .82
   machines.  Something we need to be aware of as developers is that
   deployments think on a much longer scale.  As developers, if we have a
   bug we can commit a fix and rebuild within a few days.  Deployments
   can take weeks if not months to push a minor update.
  
   Major version upgrades are something developers can do every six
   months.  From my experience a couple couple of weeks of 'hmmm,  better
   file a bug on that' and I have well running machines after an upgrade.
    For a enterprise, such as a deployment, the decision to update
   becomes much harder and takes much longer to implement. As Martin
   pointed out, a significant amount of Quality Assurance goes into a
   deployment upgrade.  Not only do the hardware, OS, and learning
   platform need to work together, all infrastructure, activities and
   third party applications must also work after the update.  The problem
   just got significantly harder:)  If I hit a bug while while sitting in
   my office that is one thing.  If a teacher hits a bug where the
   computers no longer connect to the server that is another thing
   entirely.
  
   On the other hand, there have been several significant improvements in
   both Sugar and Fedora over the last couple of releases.  It would be
   valuable to make those improvement available to end users.
  
   My research has indicated that education institutions find that 3
   years is the right balance between stability and improved
   functionality of new software.  Because to the newness of the Sugar 2
   years is a reasonable first round of updates due to the higher than
   normal increases in usefulness and usability.
  
   Blame and credit are important motivators in this game:( As such, if
   we fail, it is the fault of Bernie, paraguayeduca, and I for: 1)
   starting with a bad premise, 2) making bad technical decision, or 3)
   making bad operational decisions.  If we fail it will be due to the
   cooperative efforts of deployments, Sugar Labs, OLPC, and other
   interested third parties.
  
   david
   ___
   Sugar-devel mailing list
   sugar-de...@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel

 =-
  paul fox, p...@laptop.org

 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Supporting Sugar .88 on the XO1

2010-05-20 Thread David Farning
On Thu, May 20, 2010 at 6:55 PM, Paul Fox p...@laptop.org wrote:
 david wrote:
   As Bernie announced, we working on supporting Sugar .88 on the XO-1.

 hi david --

 for those of us joining this thread late, can you expand on what/who
 you mean by we?  (or tell me to read the archives, if that's
 more appropriate.)

Sorry, By we, I mean Activity Central and compnay that Bernie,
Caroline, and I have started to support OLPC and Sugar deployments.

It is going to take me awhile to figure out how to communicate with
the community.  I would like to keep the larger Sugar and OLPC
projects aware of what our company is doing.  But, I don't what it to
sound like a press release of pitch for the company:)

david
 paul


   This projects is customer driven by the deployment in Paraguay.  They,
   along with bernie, made a decision that it would be more useful,
   usable, and cost effective to settle on .88 rather than .82.  This
   strictly a decision made by a single deployment, which I support.
  
   As an ecosystem we can make lists of Pros on Cons why this is a good
   or bad decision and why I am an idiot.  At the end of the day this was
   a decision made by a deployment.  The primary reason for this decision
   is that the deployment does not yet has an established base of .82
   machines.  Something we need to be aware of as developers is that
   deployments think on a much longer scale.  As developers, if we have a
   bug we can commit a fix and rebuild within a few days.  Deployments
   can take weeks if not months to push a minor update.
  
   Major version upgrades are something developers can do every six
   months.  From my experience a couple couple of weeks of 'hmmm,  better
   file a bug on that' and I have well running machines after an upgrade.
    For a enterprise, such as a deployment, the decision to update
   becomes much harder and takes much longer to implement. As Martin
   pointed out, a significant amount of Quality Assurance goes into a
   deployment upgrade.  Not only do the hardware, OS, and learning
   platform need to work together, all infrastructure, activities and
   third party applications must also work after the update.  The problem
   just got significantly harder:)  If I hit a bug while while sitting in
   my office that is one thing.  If a teacher hits a bug where the
   computers no longer connect to the server that is another thing
   entirely.
  
   On the other hand, there have been several significant improvements in
   both Sugar and Fedora over the last couple of releases.  It would be
   valuable to make those improvement available to end users.
  
   My research has indicated that education institutions find that 3
   years is the right balance between stability and improved
   functionality of new software.  Because to the newness of the Sugar 2
   years is a reasonable first round of updates due to the higher than
   normal increases in usefulness and usability.
  
   Blame and credit are important motivators in this game:( As such, if
   we fail, it is the fault of Bernie, paraguayeduca, and I for: 1)
   starting with a bad premise, 2) making bad technical decision, or 3)
   making bad operational decisions.  If we fail it will be due to the
   cooperative efforts of deployments, Sugar Labs, OLPC, and other
   interested third parties.
  
   david
   ___
   Sugar-devel mailing list
   sugar-de...@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel

 =-
  paul fox, p...@laptop.org

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Working with a commercial entity.

2010-05-17 Thread David Farning
There has been discussion on development processes and a development
team lead over the past couple of days.  As this discussion moves
forward, I would like the community to consider the effects of working
with commercial entity.

Over the past couple of months I have been exploring business
opportunities to promote the adoption and development of Sugar.  One
of these opportunities is a service and support business for
deployments.  As such, we are building network of developers to work
on deployment specific issues.

One consideration is that these deployment specific issues are often
boring -- stuff like bug fixes.  As such we are paying the developers
the going rate rate for developers in their country or region.  This
brings three advantages:
1. The deployment issues are fixed.
2. These fixes are pushed upstream for inclusion into Sugar.
3.  There is a growing pool of skilled developers, with knowledge of
how to work with the Sugar community, co-located with deployment

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] Working with a commercial entity.

2010-05-17 Thread David Farning
On Mon, May 17, 2010 at 6:20 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
 On Mon, May 17, 2010 at 6:52 PM, Jonas Smedegaard d...@jones.dk wrote:
 Making deals with
 commercial partners have a tendency to spawn discrete communication and work
 shared openly but as a result, not a peer process (a famous example is that
 of Google Android release process of linux kernel patches).

 Actually, most of the kernel development these days is funded. The
 planning, design, development, review and rework are done openly. All
 teh technical work is open and transparent, that's all.

 Android, of a thousand of funded projects, has been mismanaged from
 the PoV of the kernel upstream. Sure. But the correlation you are
 trying to make is not there. The evidence is overwhelmingly on the
 other side.

 cheers,


All of the participants on this thread have identified potential
strengths and potential weakness of commercial projects working
together with community projects.

I expect that transparency will be my biggest problem.  Not because I
am doing anything super secret, but because I am reaching outside of
the open source community and working mostly with educators and
deployers.  Many of them have little of no experience working with
open source development methodologies.  Thus it will take ramp up time
to acclimate new developers to the community.

WRT to crowding out.  This tends to happen when 'paid developers'
operate as a block and give each other more authority then developers
outside the block.  As such _all_ of the Sugar developers_ I am
working with are doing bug fixes -- which must be pushed upstream.  It
is pretty hard to argue that fixing bugs, many of which have been open
for years, is crowding out others.  This issue may come up again as
the particular group of developers I am working with become more
experience and earn commit and maintainer authority.

The bottom line is that some communities and companies find ways to
work effectively together and others don't.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] deployment focused event

2010-05-11 Thread David Farning
Following up on the 'realness' event happening later this month, we
will be holding a deployment focused event in July to prepare Sugar
for deployment in Maine.

Last summer Sugar Labs spent a significant amount of resources, both
real and emotional, on a pilot at the GPA.  Now, a year later and
hopefully a year smarter we are going to take another run at a US
based deployment.  This time the deployment will be part of the Maine
1-to-1 program.

Lessons learned:
1) Hardware is hard -- At the GPA project we spent too much time
dealing with hardware issues.  This time we will partner with the
Maine 1-to-1 program.  They have successfully deployed 3000 laptops in
middle and high schools in Maine.  We will leverage their hardware and
deployment expertise by adding Sugar to their existing program and add
adding elementary schools to their target audience.

2) Don't expect a community to deal with deployment specific bugs --
on the deployment's timeline.  The open source development model
brings many advantages when creating an open learning platform.
Customer service is not one of those advantages.  As many of you may
have notice, there has been an uptick in the number of deployment
specific patches flowing upstream to Sugar Labs over the last couple
of weeks.  With Bernie's help, I have been sponsoring several local
developers to fix usability issues for the Paraguay deployment.  The
effort has had the twin benefits of fixing issues in Paraguay and
gradually acclimating the upstream developers at Sugar Labs to deal
with patches from deployments.  I will continue this effort by
sponsoring developers to do customer service for the Maine deployment
so Sugar Labs can focus on being upstream.

If anyone is interesting is learning more about this particular
approach to supporting a deployment I invite you to join us at
http://www.fossed.com/ .

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] stepping down as development team coordinator

2010-05-11 Thread David Farning
Thanks for all of your hard work over the years.  You have left your
excellent mark on Sugar and Sugar Labs.

You have carried a heavy load for a long time!  I hope that we
continue to see your participation in the Sugar / OLPC ecosystem.  (I
am already seeing your name pop up around gnome:)

david

On Tue, May 11, 2010 at 10:28 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
 Hi,

 I don't have much time these days, so I'm dropping the development
 team coordinator role in order to have a bit more of time to focus on
 the other stuff.

 I have added the following description to the Vacancies page:

 * Development team coordinator: carries administrative tasks such as
 organizing regular meetings, keep the TODO list updated, keep the
 membership list, and makes sure that the team has clear goals and is
 kept focused.

 We are seeing an increased interest on the development of Sugar, so I
 hope somebody will find time to take this.

 Note that we are still missing people who want to coordinate the
 community and deployment teams, and also miss a release manager. These
 are much more important IMO than the developer team coordinator.

 Regards,

 Tomeu
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Fedora Summer Coding

2010-04-09 Thread David Farning
It might me worth submitting a few of the SoaS relate GSOC projects to
Fedora Summer Coding. [1]

If any projects are accepted by FSC, it would leave more GCOS slots
open for non-SoaS projects.  FSC looks close enough to GSoC that the
additional overhead of working with both programs would be minimal.

david

1. https://fedoraproject.org/wiki/Summer_Coding_2010
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] SoaS change of direction: heads-up on convos in other lists

2010-03-20 Thread David Farning

On Sat, Mar 20, 2010 at 11:54 AM, Martin Langhoff martin.langh...@gmail.com 
wrote:

On Sat, Mar 20, 2010 at 12:46 PM, Peter Robinson pbrobin...@gmail.com wrote:

On Sat, Mar 20, 2010 at 10:26 AM, Sean DALY sdaly...@gmail.com wrote:

The problem with this approach is that it renders SoaS ineffective for
new tryers of Sugar (i.e. the overwhelming majority of teachers and
parents we are trying to reach).


I don't think it will be any less ineffective than having 20
activities of which half have issues, crash or just don't run.


Are people saying _only 6 activities work reliably?_

My question of which is it? was assuming there are more than 6 that
run well, demo well, maintained, etc. So it meant which plan is it, 6
activities that allow downloading and installing of more, or the good
ones?

If there are only 6 good ones...  would focus on making that list longer.

Did APIs break with Sugar churn, Fedora churn? Developers upload
without testing? (Rethorical! Flamefest warning! Those questions are
bound to be a flamefest blaming people who don't deserve to be
blamed... :-( )


A big issue that we are have on the .deb side is the the distros are pushing 
ahead with new, faster, stronger While sugar has stabilized on a base.  The 
biggest issue for us is with xulrunner and browse.  Since mozilla has dropped 
support for xulrunner and xpcom in favor of web kit.  Ubuntu is not willing to 
carry it forward in the upcoming LTS release.

I don't know if one can properly assign blame.  It is more the nature of 
evolutionary software development.  Upstreams move forward while downstreams 
are more hesitant because they have significant investments and support cost to 
consider.

david


cheers,



m
--
 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
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep





signature.asc
Description: OpenPGP digital signature
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [SLOBS] non-free activities on ASLO

2010-03-19 Thread David Farning

On Thu, Mar 18, 2010 at 6:01 PM, Martin Langhoff martin.langh...@gmail.com 
wrote:

On Thu, Mar 18, 2010 at 2:41 PM, Chris Ball c...@laptop.org wrote:

Yes.  We ratified at a SLOBS meeting that non-free activities (or
content) should *not* be hosted on ASLO, and attempted to specify
what we mean by non-free:


I personally think it is very good that free are clearly separated
from non-free, and I think it's good strategically for all involved.

There is one aspect that will be tricky on the content side -- it is
very easy to create / release content that is in itself free, but
dependent on non-free software. Picture the well-meaning content
creator that releases a Flash interactive under a CC license (and it
uses fancy Flash10 things that are not in Gnash).

Educational content creators aren't as educated as FOSS programmers in
the vagaries and politics of patents, software licensing and all (they
are educated in other legalities, usually). We can't flame them for
being dumb, they are smart about a different set of things.

Much of their work will be what Debian would call contrib -- Free in
itself but depending on non-free bits.

While 'contrib' in Debian is usually not very big, if Sugar succeeds
attracting content creators, it might be a big category... at least
until the free tools mature, and the authors learn why it matters,
switch tools, etc.

It is a social process that will take a while -- I am sure there'll be
'contrib' stuff for quite a while, maybe forever.

/rambling background

So... what about contrib?



Martin articulated my views rather well.

I believe that Sugar Labs is an education project which uses open source 
development methodologies and licences because they are socially just and 
extremely cost effective at building the common platform.

The ecosystem to support and develop deployments is _as_ important as the 
platform itself.

As such, as part of my ongoing sugar ecosystem building efforts I have 
registered ACTIVIDADES.COM and will establish a marketplace for non-free 
activities.

I will continue all of my current technical ASLO support and development and 
will abstain from further policy discussion about what should be hosted on the 
Sugar Labs site.

david  


signature.asc
Description: OpenPGP digital signature
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Systems] [Sugar-devel] Turtle Art on Activities.sugarlabs.org

2010-02-28 Thread David Farning

+1. Solutions Grovey has several moodle experts in house

On Sat, Feb 27, 2010 at 3:09 PM, Bernie Innocenti lt;ber...@codewiz.orggt; 
wrote:
On Sat, 2010-02-27 at 15:34 +, Aleksey Lim wrote:
gt; we can move in several directions at the same time,
gt;
gt; * web hosting,
gt; nbsp; I'm more thinking about Moodle because hacking AMO will increase 
ASLO
gt; nbsp; patch which could be wrong way to go since we don't have PHP coders
gt; nbsp; involeved to ASLO coding

We already have a Moodle instance running here:

nbsp;http://schools.sugarlabs.org/

I don't know if anyone is using it, and it may very well be an updated
version at this time. Caroline could tell you more about it.

If you need a development Moodle installation, just let me know.


gt; * sugar UI,
gt; nbsp; we already have FileShare activity
gt; nbsp; I'm working on Library-2 activity which should support not only 
server
gt; nbsp; model but also per-to-peer sharing model (activity will have thumb
gt; nbsp; view to make object browsing more useful)

Very interesting...

--
nbsp; // Bernie Innocenti - http://codewiz.org/
nbsp;\X/ nbsp;Sugar Labs nbsp; nbsp; nbsp; - http://sugarlabs.org/




signature.asc
Description: OpenPGP digital signature
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Turtle Art on Activities.sugarlabs.org

2010-02-25 Thread David Farning
The other day during an infrastructure meeting, Walter brought up some
thought on how to enable kids to exchange Turtle Art projects

Alsroot has been thinking about how to do this through a.sl.o since he
became the activities.sugarlabs.org code maintainer.

The high level view is that someone can easily upload Turtle Art creations
to somewhere and then they, or others, can go to a portal to download other
Turtle Art creations.

Client side, this would require:
1. Adding a widget to either the journal or the TA activity to upload the TA
Bundle.
2. Adding a TA bundle installer to handler TA Bundle downloads.

Server side, this would require:
1. A place to accept TA bundle uploads.
2. A search-able place from which to download TA bundles

We have some similar systems we can look to as examples.
1. Scratch -- Scratch has an upload button and users can download scratch
projects from --  http://scratch.mit.edu/galleries/browse/newest
2. ASLO --  Users upload XO bundles via a web interface and download via a
web interface.

My initial instinct is to see if ASLO can be adopted to fit this need.
Primarily because we have it, it works, and it is scalable.  On the other
hand, if the only tool in one's toolbox is a hammer, everything looks like a
nail. (How is that for over using clichés and buzzword?)

Considerations:
ASLO rocks:)
ASLO can be adapted to handle various file types.  For example:
https://addons.mozilla.org/en-US/firefox/browse/type:3
https://addons.mozilla.org/en-US/firefox/browse/type:2

Each file type can have a separate look and feel.

Is the activity creation and upload process too complicated for young users?

Moving forward:
Would it be possible to journal or TA widget which:
1.  Walks the student though a upload wizard.
2.  Combines the TA project into a into a bundle with the metadata generated
in the wizard.
3.  Sends the bundle to activites.sl.o/uploads

Would it be possible to setup/adapt ASLO to:
1. Handle TA files types.
2. Accepts TA bundles+metadata uploads and inserts them into the review
queue.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] ASLO bootcamp at RIT weekend of March 7 or 14

2010-02-17 Thread David Farning
I just wanted to poll the interest on these lists about an ASLO bootcamp
which we are planning for either the weekend of March 7 or 14 on the RIT
campus.

The format will be a series of 5 sessions on:

   - 1.1 Session 0
Systemshttp://wiki.sugarlabs.org/go/Machine/Discovery_One/BootCamp#Session_0_Systems
   - 1.2 Stage 1 Basic Web Site
Technologieshttp://wiki.sugarlabs.org/go/Machine/Discovery_One/BootCamp#Stage_1_Basic_Web_Site_Technologies
   - 1.3 Stage 2
Cachinghttp://wiki.sugarlabs.org/go/Machine/Discovery_One/BootCamp#Stage_2_Caching
   - 1.4 Stage 3 Load
balancinghttp://wiki.sugarlabs.org/go/Machine/Discovery_One/BootCamp#Stage_3_Load_balancing
   - 1.5 Stage 4
Reliabilityhttp://wiki.sugarlabs.org/go/Machine/Discovery_One/BootCamp#Stage_4_Reliability

Each session will be a three hour block consisting of:
1h Theory - Lecture.
1h Tutorial - structured exploration.
1h Free exploration.

To encourage wider participation, I hope to:
1. Live stream and record the lectures.
2. Encourage remote participation via IRC
2. Make all tutorials and resources available on the Sugar Labs wiki.

Please let me know if you are interested in participating in person,
remotely, or possible use the resources in the future.  The long term goal
is to create a bootcamp format where senior community members can
effectively engage and share their knowledge and experience with new
community members.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Systems] ASLO bootcamp at RIT weekend of March 7 or 14

2010-02-17 Thread David Farning
On Wed, Feb 17, 2010 at 8:13 PM, Bernie Innocenti ber...@codewiz.orgwrote:

 On Wed, 2010-02-17 at 15:18 -0600, David Farning wrote:
  I just wanted to poll the interest on these lists about an ASLO
  bootcamp which we are planning for either the weekend of March 7 or 14
  on the RIT campus.
 
  The format will be a series of 5 sessions on:
* 1.1 Session 0 Systems
* 1.2 Stage 1 Basic Web Site Technologies
* 1.3 Stage 2 Caching
* 1.4 Stage 3 Load balancing
* 1.5 Stage 4 Reliability
  Each session will be a three hour block consisting of:
  1h Theory - Lecture.
  1h Tutorial - structured exploration.
  1h Free exploration.
 
  To encourage wider participation, I hope to:
  1. Live stream and record the lectures.
  2. Encourage remote participation via IRC
  2. Make all tutorials and resources available on the Sugar Labs wiki.
 
  Please let me know if you are interested in participating in person,
  remotely, or possible use the resources in the future.  The long term
  goal is to create a bootcamp format where senior community members canng
  effectively engage and share their knowledge and experience with new
  community members.

 I wish I were there in person, but I'll try to participate from remote
 if we can get people to join IRC and redirect important communication
 through it.

 Very nice!

This brings us up to 6 in person and 6 remote!

I am working on the logistics of 5 three hour blocks each followed by a hour
meal break.  It will be a lot of work but it should be worth it.  The
lecture, tutorial, explore, break sequence should give us a nice rhythm that
will suit both in person and remote learning.  I am planning on giving the
lectures.  Dogi can run the tutorial sections.

I am particularly interested about how the free exploration hours will go.
The participants seem to have a wide variety of backgrounds and interest.
So, the exploration will take us in interest directions.  We have many more
details to work out.

It could be a total flop or it could be a home run.  But it seems worth the
risk.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Weekly Infrastructure Meeting Reminder

2010-02-09 Thread David Farning
Can we bump the wikimedia machine and aslo discussion to the top of
the meeting, so our friend from RIT don't need to wait for us to cover
the other issues.

The topic should be pretty short this week.  We are in a holding
pattern until the spring term at RIT starts.

In the meantime we will be adding a temporary web node at Gnaps to
handle the load until the cluster comes online.  That should be pretty
minor.

david

On Tue, Feb 2, 2010 at 1:38 PM, Stefan Unterhauser
ste...@unterhauser.name wrote:
 Infrastructure meeting:
 Volunteer Infrastructure Gang, Sugarlabs Infrastructure Team
 and TreeHousers :)

 # Date: 2010-02-02
 # Time: 21:00 UTC (16:00 EST, 22:00 CET)
 # Agenda: http://etherpad.com/9LHNuaKPY2
 # Location: #treehouse on irc.oftc.net
 # or Link: http://embed.mibbit.com/?server=irc.oftc.netchannel=%23treehouse

 cu
 dogi
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] Local Labs for Mexico

2010-01-02 Thread David Farning
Gabriel,

Would you please create a local lab proposal like the ones on
http://wiki.sugarlabs.org/go/Local_Labs .  From there we can start
figuring out how to proceed most effectively.

david

2009/11/17 Gabriel Molina skip...@gmail.com:
 Hello!

 I'm very interested in Sugar Project and I'd like to know if there are
 people working to introduce this project in Mexico. If not, I'd like to
 start a Local Lab based on the experiencies of other latin american
 counties. For now I'm gathering information to know the situation of this
 project in my country.

 Cheers

 --
 ちりも積もれば山となる

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Looking for local labs.

2009-12-09 Thread David Farning
For the past year, I have been deliberately keeping Sugar Labs out of
the way of local labs to help insure that early local labs were not
over whelmed by the visions or personalities of Sugar Labs.  Browsing
the list lately, it looks like it might be time to take a shot at
collecting ideas from existing local labs so we can share them with
the world.

In particular, http://wiki.sugarlabs.org/go/Local_Labs is really out
of date.  I would appreciate it if anyone knows of a local lab they
could add it to that page or send a quick reply to this this so I can
add it.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] The sugar stack

2009-11-27 Thread David Farning
It seems time to think about the next _big_ technical issue for
growing Sugar Labs.  Clearly articulating the Sugar Stack.  For the
last year or so, we have been circling the issue with talk of stable
APIs, Glucose, Fructose, and expected dependencies.

Last year, we created the release cycle.  At first, _everyone_
disagreed with the idea; Release cycles are perfect for _no_one_.
Defining the Sugar Stack is going to be nearly as painful, because the
'stack definition' is not going to be perfect for anyone.

Some reasons for defining a stack:
1. Statement of quality.  One of the most frequently cited reasons for
the glucose, fructose, honey classification is quality.
- Glucose is the core stuff.
- Fructose is the supported stuff.
- Honey is the rest.
This is a very valid method of defining layers of the project; Fedora
had core and extras, Ubuntu has main and universe, Eclipse has various
levels of official-ness, (none of which I can remember) The kernel
simply has 'in-tree' and 'out-of-tree'.

2. Statement of synchronisation.  In some instances it is desirable
for various parts of a project to be tested and release together.
- Sugar core is developed according to a release cycle.
- Fructose tends to align with the release cycle.
- Honey happens 'when it happens.'
This is also very valid; Distro all have synchronised releases.  The
desktop managers all ship a core at distinct release points.  Ecplise
has its release train.

3. Statement of what is provided.  Down streams _need_ to know what
applications they can depend on.
- Core APIs
- Optional things to meet dependencies.
Most languages provide for core functionality which can be extended
with modules.  Apache also is organized as http server and installable
modules.

Many of the discussion about this have stalled because of confusion
over what aspect the stack we are trying to define.

 As a starting point, I would suggest:
1. That we get rid of the glucose - fructose categorisation.  It is
overloaded and confusing
2. That Quality and synchronisation of activities becomes an
Activities Team issue.

This shifts the discussion back to the hard problem of how to think
terms of 'Sugar-Space' and 'Activities-Space'.

Long term projects success depends on external organisation knowing
what they can depend on to be part of Sugar.

Before starting a holy war  The process of articulating the Sugar
stack, much the the release cycle, is an evolutionary process.  There
is no way the anyone could sit down and declare, 'This is what Sugar
consists of... and will consist of in the future.'

Instead, the stack is a snapshot of agreed upon APIs, libraries, and
applications on which downstream activities developers can depend.  I
suggest that:
1. The development team and activities team work together to start
defining the boundary between core and activities.
2. All changes to the core and activities boundary should go through
the new features (or similar) process.

After a few iterations, this process will become as second nature as
the release process.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] OOo4Kids available for Sugar!

2009-11-16 Thread David Farning
The basics of uploading to activities.sl.o sounds like something the
marketing guy should know:)

I am on IRC so I can walk you through the process.  (you can
upload it and then I will assign eric as author/developer so he owns
and maintains the project)

david

On Mon, Nov 16, 2009 at 4:06 AM, Sean DALY sdaly...@gmail.com wrote:
 http://eric.bachard.free.fr/news/2009/11/ooo4kidsactivityxo-is-available.html

 Eric has announced availability of the Sugar port of OOo4Kids.

 I haven't had the chance to test it yet.

 What's the procedure to add an Activity to activities.sugarlabs.org?
 So we can ask Eric to do that.

 thanks

 Sean
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] OOo4Kids available for Sugar!

2009-11-16 Thread David Farning
The relevant information is on the wiki is at
http://wiki.sugarlabs.org/go/Activity_Library .

Uploading specific information is at
http://wiki.sugarlabs.org/go/Activity_Library/Authors

Please note, I wrote those processes before anyone besides me had
actually uploaded an activity:(  I am not sure how close they match
the reality of current activities policy and procedures.

david

On Mon, Nov 16, 2009 at 5:18 AM, Sean DALY sdaly...@gmail.com wrote:
 believe me, there is no shortage of things I should know ;-)

 IRC not possible for me right now, but the marketing guy thinks he
 could work on a link on the homepage of a.sl.o explaining to any
 potential Activity developer (myself included) how to do it

 Sean


 On Mon, Nov 16, 2009 at 11:16 AM, David Farning dfarn...@sugarlabs.org 
 wrote:
 The basics of uploading to activities.sl.o sounds like something the
 marketing guy should know:)

 I am on IRC so I can walk you through the process.  (you can
 upload it and then I will assign eric as author/developer so he owns
 and maintains the project)

 david

 On Mon, Nov 16, 2009 at 4:06 AM, Sean DALY sdaly...@gmail.com wrote:
 http://eric.bachard.free.fr/news/2009/11/ooo4kidsactivityxo-is-available.html

 Eric has announced availability of the Sugar port of OOo4Kids.

 I haven't had the chance to test it yet.

 What's the procedure to add an Activity to activities.sugarlabs.org?
 So we can ask Eric to do that.

 thanks

 Sean
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep



___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Sugar Digest 2009-11-16

2009-11-16 Thread David Farning
On Mon, Nov 16, 2009 at 1:47 PM, Walter Bender walter.ben...@gmail.com wrote:
 === Sugar Digest ===

 1. I am writing this update today while waiting to see if I will
 called to jury duty. I was originally supposed to report last week,
 but a deferment was granted since I was in Bolzano. I am not sure why
 I had never been called before—both my wife and children have served
 several times. But unlike the airport in Rome, there is at least a
 place to sit and plug in my laptop and get on-line while I wait, so
 here it goes.

I had noticed that there was very little traffic on the lists and IRC
about SugarCamp Bolzano.  As Walter points out, we got a tremendous
amount done,  but very little of it worthy of headlines.  My kind of
Meeting!

A very interesting dynamic was that almost _no_ time was spent talking
about what Sugar Labs _should_ do.  Rather it was a chance to work on
all of the nagging issues that are hard to get started on when your
primary resources are IRC, mailing lists, and google.

Kudos to Simon for a very well organised week.  My only gripe was the
lack of sound absorption material on the walls.  Dogi has a very low
pitch to his voice.  It was sometime hard for me to hear him when
there were other discussions happening in different parts of the room.
 As far as gripes go it is not a very serious one:)

As for me, I am enjoying one last morning watching the sun rise over
the mountains before it is time to head home.

Thanks for a good week.

david

 I was in Rome overnight in transit from Bolzano, where we held a
 week-long Sugar Camp
 [http://wiki.sugarlabs.org/go/Marketing_Team/Events/Sugarcamp_Bolzano_2009].
 Bolzano is in South Tyrol, in the Italian Alps. The autonomous
 regional government is a user of free software and is exploring ways
 in which they can engage the FOSS community more deeply. They have a
 regional development organization, TIS [http://www.tis.bz.it/], that
 fosters FOSS projects in the region, provides infrastructure and
 support, and an annual Free Software Week. It was in the context of
 [http://www.freesoftwareweek.org/ Free Software Week] that we came to
 Bolzano.

 Rather than meet at TIS, we (Simon Schampijer, Tomeu Vizoso, Dave
 Farning, Sean Daly, Stefan Unterhauser (Dogi), Carlo Falciola, Adam
 Holt, Christian Vanizette, and I) spent the week at
 [http://www.cts-einaudi.it/ CTS Luigi Einaudi], a technical school a
 short walk from the city center. We were given a comfortable room with
 Internet access, just upstairs from the school's coffee bar and next
 door to where the [http://live.gnome.org/ZeitgeistHackFest2009 Gnome
 Zeitgeist team] was meeting. Over the course of the week, we
 interacted with teachers, students, developers, and a variety of
 people in the region who have an interest in Sugar.

 We had a busy week. My typical day was to get up at 6:00, go down
 stairs for an early breakfast with David, who would have already been
 up for at least an hour, take a 20-minute walk to the school, arriving
 at 8:00, in time for the first espresso of the day. We'd write code,
 discuss ideas, brainstorm, and write more code until 20:00, at which
 point we'd make a plan for dinner—usually a pizza or some knudel and
 the local weizenbier or a glass of lagrein. Somehow or other, we would
 never manage to get back to the hostel until after midnight. Pizza,
 Python, and friends, surrounded by the Dolomites—not a bad way to
 spend the week.

 We made progress on the roadmap for 0.88, having brainstormed on a
 number of topics
 [http://wiki.sugarlabs.org/go/File:Ideas_0.88_0.90.pdf]. The themes
 that rose to the top were: a simplified collaboration model;
 resolution of some outstanding issues regarding the Home View, e.g.,
 how to best launch new verses resume activities; and some changes to
 the Journal—possibly the incorporation of versions and a better
 integration of the Journal into the activity workflow, e.g., making it
 possible to modify the description field while the activity is open.
 Other themes include accessibility and testing.

 Simon organized the discussions through the week. He kept us focused
 and productive. He also got some hacking in, spending time working
 through many of the issues associated with providing global support
 for spell-check. In doing this, he'll have laid out the framework for
 providing other global services.

 Tomeu spend most of his week being interrupted by people asking him
 questions. (Five minutes of Tomeu time usually was enough to keep me
 busy for a few hours.) But he did manage to make progress on his work
 on Python introspection. This work will lead to a much more efficient
 use of Python modules in Sugar.

 David and Dogi (working with Bernie and Aleksey from afar) did an
 overhaul of some of our back-end systems, which had been becoming
 stressed as more and more people are using Sugar. (For example, we've
 already surpassed 1.5-million downloads from activities.sugarlabs.org.
 It was just a few weeks ago that 

[IAEP] Mirrors in Argentina and Paraguay

2009-11-14 Thread David Farning
A quick thanks to the local labs in Argentina and Paraguary.  They
have set up mirrors to help distribute Sugar Labs content.

Their status will be updated on mirrors.sugarlabs.org next time page is updated.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Systems] Sharing Google Apps calendars

2009-11-05 Thread David Farning
On Thu, Nov 5, 2009 at 12:02 AM, Bernie Innocenti ber...@codewiz.org wrote:
 Personal and team calendars hosted at our Google Apps instance can now
 be shared with anyone outside the @sugarlabs.org domain also in
 read-only and read-write mode.

Cool, I don't think this was possible when we first set up the calendars.

 The default policy for Google Apps was to restrict sharing with the
 outside world to free/busy mode.

 If there's user demand for it, we could install a DAViCal server on
 Sunjammer.

 --
   // Bernie Innocenti - http://codewiz.org/
  \X/  Sugar Labs       - http://sugarlabs.org/

 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Fwd: Sugar Digest 2009-11-02

2009-11-03 Thread David Farning
On Tue, Nov 3, 2009 at 2:31 PM, Sameer Verma sve...@sfsu.edu wrote:
 On Tue, Nov 3, 2009 at 11:41 AM, David Farning dfarn...@sugarlabs.org wrote:
 On Tue, Nov 3, 2009 at 9:28 AM, Walter Bender walter.ben...@gmail.com 
 wrote:
 I think there are more recommended activities than fit at any one
 time. They are chosen randomly from the list. As to how the list is
 compiled, I do not know, but I believe that Etoys is already a
 recommended activity. I'll double-check.

 Currently there is not a formal recommended policy.  Basically,
 whenever I see a cool new activity I add it to the recommend list and
 remove an activity that has been around for awhile.  I think Aleksey
 does the same.

 If anyone would like to create and maintain more formal recommended
 list it is very easy to create an activities.sl.o editor's account for
 them.

 david


 I had written about this a long time ago. My approach was to rank
 activities based on a list of attributes (weighted scoring). The
 activities with the highest attributes would be the ones installed.
 The same approach could be used for Recommended activities. The
 thread is at 
 http://lists.laptop.org/pipermail/grassroots/2008-September/000707.html
 . The GoogleDocs spreadsheet is at
 http://spreadsheets.google.com/ccc?key=p_Xhb6KcXLyEViA50CnCaDghl=en

If you are interested, the job of recommend list[1] maintainer is
open.  ASLO is getting 100,000 visits a month, doubling every three
months, so the effect of your work would be rather widespread.

david

1. http://activities.sugarlabs.org/en-US/sugar/recommended

 Sameer

 -walter

 On Tue, Nov 3, 2009 at 10:25 AM, Rita Freudenberg r...@squeakland.org 
 wrote:
 Walter Bender wrote:

 5. Thanks to the efforts of Josh Williams, Aleksey Lim, and David
 Farning, the new http://activities.sugarlabs.org site went on-line
 over the weekend. The new look is clean and also in compliance with
 Mozilla copy




 I would like to know how the activities on the starting page are chosen.
 What does it require from an activity to be recommended?
 My question is not just out of curiosity, I would like to see Etoys there.
 So I would like to know if we could do anything to be considered a
 recommended activity?

 Thanks,
 Rita



 --

 Rita Freudenberg
 Squeakland Foundation
 http://www.squeakland.org





 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep


___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Fwd: Sugar Digest 2009-11-02

2009-11-03 Thread David Farning
On Tue, Nov 3, 2009 at 9:28 AM, Walter Bender walter.ben...@gmail.com wrote:
 I think there are more recommended activities than fit at any one
 time. They are chosen randomly from the list. As to how the list is
 compiled, I do not know, but I believe that Etoys is already a
 recommended activity. I'll double-check.

Currently there is not a formal recommended policy.  Basically,
whenever I see a cool new activity I add it to the recommend list and
remove an activity that has been around for awhile.  I think Aleksey
does the same.

If anyone would like to create and maintain more formal recommended
list it is very easy to create an activities.sl.o editor's account for
them.

david

 -walter

 On Tue, Nov 3, 2009 at 10:25 AM, Rita Freudenberg r...@squeakland.org wrote:
 Walter Bender wrote:

 5. Thanks to the efforts of Josh Williams, Aleksey Lim, and David
 Farning, the new http://activities.sugarlabs.org site went on-line
 over the weekend. The new look is clean and also in compliance with
 Mozilla copy




 I would like to know how the activities on the starting page are chosen.
 What does it require from an activity to be recommended?
 My question is not just out of curiosity, I would like to see Etoys there.
 So I would like to know if we could do anything to be considered a
 recommended activity?

 Thanks,
 Rita



 --

 Rita Freudenberg
 Squeakland Foundation
 http://www.squeakland.org





 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Infrastructure Status Report

2009-11-03 Thread David Farning
While SoaS and Trademarks have gotten most of the attention lately,
other parts of Sugar Labs are growing and moving forward.   A lot is
happening on the infrastructure side of the project.  Some of it
behind the scenes and some of it more public.

--Capacity growth--
The biggest challenge faced by the team is handling capacity growth.

-Machines-
The first and most visible need is additional servers. Initially we
outsourced several of our services.  While cost effective, that policy
created problems because each place we outsourced to had different
support policies and system requirements.

Now we are going through a consolidating phase.  It is much easier to
maintain a consistent infrastructure.  Several of our services now
need to be clustered across groups of co-located machines for load
balancing and increasing reliability.

We are also seeing growth rate which are doubling every quarter for
Activities.sl.o.

-Administrators-
The second and less visible need is for administrators to help keep
the systems alive.  Sorry Bernie, we are going to have to pull you
(kicking and screaming) from sysadmin to Infrastructure team leader.
We are going to need to work on training and identify others so that
they can take authority and responsibility of parts of the
infrastructure.

--Specific Tasks--
There are a number of specific tasks in progress which need help.

-Launch Pad-
Luke is working on migrating pieces of the Infrastructure to Launch
Pad.  There are a number of Pros and Cons to this.

The big win will be using the LB bug tracker.  Upstream trac (our
current bug tracker) development has stalled make it very difficult to
maintain dev.sl.o.  Other improvements will be LP answers and LP
blueprints.  The user facing portion of LP is very good.

Overall the LP team has been very good to work with. But I still have
a number of reservations that I hope Luke and the LP team can take
care of:
1.  Integration with the rest of Sugar Labs services.  Specificly
git.sl.org and translate.sl.org.
2.  Ability not to get lost in Ubuntu.  There are several place where
it is very easy to unwittingly exit the Sugar project and end up
wandering around Ubuntu.
3.  Ability to get easily get back to the rest of the *sl.org

I encourage others to get involved in this project to insure that:
1. It is the right thing to do.
2. Work with the Sugar and LP communities to insure that this process
is beneficial to both parties.
3. Work with the Sugar user and developer communities to insure that
the migration goes smoothly.

-Activities.sl.org-
I am working on separating activities.sl.o from the rest of the Sugar
Labs services.

 There are several reasons for separating out a.sl.o:
1.  It will be easier to grant admin authority to a.sl.o with granting
admin authority to all of the SL infrastructure.
2.  A.sl.o is a resource hog.  By splitting it out, we can think about
scaling a.sl.o without worrying about how it will affect the rest of
the infrastructure.
3.  Security. The separation with provide a fence between a.sl.o and
the rest of the infrastructure.  If one part is compromised it will
not affect the other parts.

If any one want to help out,  there are several interesting tasks...
1. Setting up a fresh instance of a.sl.o.
2. Load balancing and HA for the php front end.
3. Load balancing and HA for the my SQL database.

-Beamrider-
Bernie is in the process of splitting up the services on sunjammer
between two machines, it and Beamrider.  This is primarily lead by the
needs to:
1.  Scale sunjammer.  In addition to SL stuff, Sunjammer is also
hosting services for local labs and OLE.
2.  Increase security and reliability.  Sunjammer will remain the
'developer' machine, hosting developer accounts and testing/devel
services, while beamrider will host higher priorith services.

-Machines and Rack space-
Finally, we need to start thinking about future machine and rack space
needs.  Of particular concern is finding a hosting provider that is
willing and able to our growing number of machines in a single
facility.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] 'apt-get install sugar-platform' available for Ubuntu9.10.

2009-11-03 Thread David Farning
On Mon, Nov 2, 2009 at 6:38 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Mon, Oct 26, 2009 at 01:02, David Farning dfarn...@sugarlabs.org wrote:
 After a couple of weeks of reading tutorials, help from Aleksey, and
 some Ubuntu developers there are Sugar packages available for Ubuntu
 9.10.

 Just gave them a try and worked great, congrats all! Which are the next steps?

Cool

The next steps are a proper bug tracker and start patching.  It has
been a little frustrating because all of the bugs on this thread have
been part of the lower packages.  As part of my learning I have been
starting with the easiest packages first, the activities.  From there
I hope to move to the more complicated core sugar packages and finally
start on xulrunner an csound.

The basic strategy is to move towards Debian's upstream packages.  The
goal is to allow Ubuntu and Debian to share patches and feedback
without step on each others toes with regard to packaging methods.
Debian has added several interesting features to automate the
packaging process.  But, these features make it harder for new
packagers to get started.

 Btw, why did we needed to build our own xulrunner?

The xpcom provided by the Ubuntu xulrunner does not seem to work correctly.

david

 Regards,

 Tomeu

 For now, these packages are available on the Ubuntu-Sugarteam PPA
 (personal package archive) at
 https://launchpad.net/~sugarteam/+archive/0.86 .

 To use these packages, just add
 'http://ppa.launchpad.net/sugarteam/0.86/ubuntu karmic main' to the
 end of /etc/apt/sources.list

 Ubuntu-Sugarteam

 --
 Ubuntu-sugarteam mailing list
 ubuntu-sugart...@lists.ubuntu.com
 Modify settings or unsubscribe at: 
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-sugarteam




 --
 «Sugar Labs is anyone who participates in improving and using Sugar.
 What Sugar Labs does is determined by the participants.» - David
 Farning

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] 'apt-get install sugar-platform' available for Ubuntu9.10.

2009-10-29 Thread David Farning
On Thu, Oct 29, 2009 at 6:29 AM,  s.bouta...@free.fr wrote:
 Hi,

 After a couple of weeks of reading tutorials, help from Aleksey, and
 some Ubuntu developers there are Sugar packages available for Ubuntu
 9.10.

 Thank you for your work. After some testing, I wrote a small blog-entry with
 some screenshots on OLPC France's blog, here:

 http://olpc-france.org/blog/2009/10/un-cartable-numerique-pur-sucre/

 The Ubuntu variant used ist UNR 9.10.

Thanks Samy,
We have been struggling on the Ubuntu side of the project for awhile.

A couple of people have already expressed interest in helping out!  I
am hoping that the Ubuntu-SugarTeam can holding some informal
packaging Sugar for Ubuntu classes next week.  As a project Ubuntu has
a lot (too much) packaging information available.  If we can sort out
the important stuff, it shouldn't take too long to get some more
packagers on board.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] 'apt-get install sugar-platform' available for Ubuntu9.10.

2009-10-29 Thread David Farning
Thanks for the bug report.

I pushed a new copy xulrunner.  It has been accepted but it is
going to wait in the build queue for about 18 hours before in makes it
to https://launchpad.net/~sugarteam/+archive/0.86 .

Sorry about that.  I didn't expect anyone to blog about the repo yet.
I'll make a new ~sugarteam/+archive/0.86-testing for testing our
packages and leave ~sugarteam/+archive/0.86 for stabler public stuff.

david

On Thu, Oct 29, 2009 at 6:11 PM, Sameer Verma sve...@sfsu.edu wrote:
 On Thu, Oct 29, 2009 at 2:50 PM, David Farning dfarn...@sugarlabs.org wrote:
 On Thu, Oct 29, 2009 at 6:29 AM,  s.bouta...@free.fr wrote:
 Hi,

 After a couple of weeks of reading tutorials, help from Aleksey, and
 some Ubuntu developers there are Sugar packages available for Ubuntu
 9.10.

 Thank you for your work. After some testing, I wrote a small blog-entry with
 some screenshots on OLPC France's blog, here:

 http://olpc-france.org/blog/2009/10/un-cartable-numerique-pur-sucre/

 The Ubuntu variant used ist UNR 9.10.

 Thanks Samy,
 We have been struggling on the Ubuntu side of the project for awhile.

 A couple of people have already expressed interest in helping out!  I
 am hoping that the Ubuntu-SugarTeam can holding some informal
 packaging Sugar for Ubuntu classes next week.  As a project Ubuntu has
 a lot (too much) packaging information available.  If we can sort out
 the important stuff, it shouldn't take too long to get some more
 packagers on board.

 david
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep


 Trying to install sugar-platform in Ubuntu 9.10 leads to  a dependency 
 problem.

 sudo apt-get install sugar-platform
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  sugar-platform: Depends: sugar-fructose (= 0.86.2) but it is not
 going to be installed
 E: Broken packages


 Sameer

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] 'apt-get install sugar-platform' available for Ubuntu9.10.

2009-10-25 Thread David Farning
After a couple of weeks of reading tutorials, help from Aleksey, and
some Ubuntu developers there are Sugar packages available for Ubuntu
9.10.

For now, these packages are available on the Ubuntu-Sugarteam PPA
(personal package archive) at
https://launchpad.net/~sugarteam/+archive/0.86 .

To use these packages, just add
'http://ppa.launchpad.net/sugarteam/0.86/ubuntu karmic main' to the
end of /etc/apt/sources.list

Ubuntu-Sugarteam
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] thin clients

2009-10-24 Thread David Farning
On Sat, Oct 24, 2009 at 12:04 PM, Deborah Boatwright
boatwrig...@newmarket.k12.nh.us wrote:
 Hello,

 I am intrigued by many aspects of Sugar on a Stick.  My school uses Novell 
 with Windows XP on the desk top.

 Then I have a thin client network using LTSP-KIWI Opensuse that does not work 
 well. It is two servers and 72 thin clients.

  I have a mobile laptop lab of 24 PC that are R30 thinkpads.

 My question is I found this site and wondered if I can use Sugar as an 
 application on my thin clients.

 http://en.opensuse.org/Sugar

Short answer is yes you can.

Longer answer it might take some work.  From what I have seen,
OpenSuse is the current leader in education solutions base on thin
clients.

I am ccing David Van Assche, the opensuse package maintainer.  He will
be most knowledgeable about (or can refer you to knowledgeable people)
deploying Sugar on OpenSuse in a thin client environment.

david

 The district has said it is switching to linux 100% and will use a windows 
 application server to deliver apps that are necessary otherwise.

 Sincere Regards,
 Deb
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] We want to create our local Sugar Labs Argentina.-

2009-10-22 Thread David Farning
On Thu, Oct 22, 2009 at 7:34 AM, Gustavo Ibarra ibarr...@gmail.com wrote:

 On Thu, Oct 22, 2009 at 2:18 AM, Rafael Enrique Ortiz Guerrero
 dir...@gmail.com wrote:

 Hello Gustavo.
 Glad to have you here.

 On Wed, Oct 21, 2009 at 11:57 PM, Edward Cherlin echer...@gmail.com
 wrote:
  Please copy to argent...@lists.laptop.org. I am not subscribed to it
  because, unfortunately, I do not speak or write Spanish.



  Welcome/Bienvenido.

 Hola amigos!

 First of all, thank you for the welcome.

Hey Gustavo,

A Local Lab in Argentina is great!

We have found that Local Labs are incredibly helpful to the community
at large.  Usually, I try to help labs get set up. But now, I would
like to stay out of the picture.  There are some really great Local
Labs that are doing amazing this.

The true value of a Local Lab is building on top of Sugar to solve
your _local_ needs.  So, would you mind working with Rafael and other
existing local labs to set up SLA.  The big thing is that you do what
is best for Argentina.

Most of the stuff we have in the wiki about local lab is based on
conversations I have had with Jono Bacon.  This means that the
policies and procedures are based on _my_ interruption of how to apply
best practices from Ubuntu Locos to Sugar Labs.  While that was enough
to get started,  now that there are a couple of healthy labs around
the world it is best that the local labs to work together and share
internal best practices with each other.  After about 5 more local
labs are in place, I would like to help start compiling a list of best
practices on wiki.sl.o.

david

   Edward Cherlin echer...@gmail.com wrote:

  I have just started organizing online meetings on the collaboration
  features of Sugar and the XO. Any interested teachers are welcome to
  join us for testing and tutorial sessions. We also need questions from
  teachers and students on anything that has puzzled them, and
  volunteers to translate the materials we create to Spanish and other
  languages.
  Our joint sessions will use Sugar on a Stick, which is set up to use a
  particular Jabber server. At some point we will provide instructions
  for connecting to that server from other forms of Sugar. They may very
  well be in the Wiki, but I haven't looked.


 Edward,  i am sending this email with copy to argent...@lists.laptop.org

  Gustavo Ibarra ibarr...@gmail.com wrote:

  We ask permission to create our local Sugar Lab for Argentina, as
  members of
  the Sugar Labs community, accepting and respecting MEMORANDUM OF
  UNDERSTANDING
  http://wiki.sugarlabs.org/go/Deployment_Team/Local_Lab_MOU and
  the appropiate use of the LOGO
  http://wiki.sugarlabs.org/go/Marketing_Team/Logo#Logo_usage


 Rafael Enrique Ortiz Guerrero dir...@gmail.com wrote:

 Local labs efforts must ask permission primary form it's own local
 communities, for the overall community we ask to follow the rules of
 distribution and participation already concerted with the overall
 community, like the MOU f.e... i also recommend you to see SL
 governance and SL .co governance to have ideas about to organize
 participation.

 I'd like to make one clarification
 We are thinking to start with SLA in an informal way. We believe it is not
 necessary to be formal in order to the kind of work we are doing. And we
 would create a non profit foundation when it be necessary.
 --
 Saludos,
 Gustavo.-

 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Systems] ASLO updates

2009-10-15 Thread David Farning
I'll try to document how mirror brain is setup and how it affects
other systems in the wiki this afternoon.

Changes to devel, testing, or product activities.sl.o should not
affect one another.  They are three separate instances consisting of:
1. Separate code trees.
2. Separate database instances.
3. Separate file storage.

Two variations of the file tree are stored.  These trees are (I am
using mozilla terminology for the trees):
1. Application tree.
2. Repo tree.

Each instance has an individual application tree stored at
www-sugarlabs/activitie-*/files.  Each instance interact directly with
its application tree.  From a user pov this tree is call the sand box.

Each instance can have an _optional_ repo tree.  An instance interacts
with its repo tree via the 'download server.'   From a a user pov this
tree is the set of downloadable files.

Our confusion was because we were pointing the download server at the
application tree via a symlink.  When the download server was the same
machine as the application server it worked correctly.  Adding
mirrorbrain forced us to clearly draw the line between the download
server and the application server. Long term, it is good system
design.  Short term, a bug in mirrorbrain cause it to incorrectly
handle symlinks in the vhost directory part.

Moving forward--
1. Work Flow -- What ever you decide for a work flow is fine.
2. A.sl.o modularization -- a.slo is design to split up into several
pieces as it grows:
2.1 Application server. This is the primary php application.  It can
be split across multiple machines using mod_perbal.
2.2 Database server. This is the primary database.  It can be split
across multiple machines as necessary.  There are limited to
scalability due to db replication issues.
2.3 Download server.  This is the primary download server.  It can be
scaled using various CDN techniques.
2.4 Memcache server.  Memcach sits between the application server and
the database.  Memcache reduces database server load and is easier to
scale than multiple database server.

Currently, all of these pieces are sitting on sumjammer. As a result
we were a bit hand wavy about the abstraction barriers between the
pieces.

Due to the improvements bernie and danny have done to sunjammer we are
maxing out at 45% cpu usage.

Due to mirror brain we have reduced our the bandwith usage on
Sunjammer from between 100 and 150 GB per day to less than five GB.
The big gain is that offloading the downloads reduces the cache churn
and eth0 interupts on Sunjammer.

Recommended growth roadmap--
Based on discussions with the AMO infrastructure team the recommend
plans for grow are:
1. Split off download server.  We have effectively done that via
mirrorbrain.  But at some point we will need to see about putting
mirrorbrain on a separate machine.
2. Split off download server.  At some point, we will need to put the
database on a separate machine which will grow into cluster of
machines.
3. Split off memcache server.  At some point we will need to split off
memcache machines.  Memcache machines can just be a bunch of old
machines with lots of memory.
4. Build multiple application servers.  This is just a matter of using
mod_perlbal to distribute across multiple servers.

I have no idea when we are going to have to make the above changes.
Current growth trajectory for a.sl.o is about 25% per months.  But,
this could change when:
1. SoaS buleberry comes out.
2. Sugar .86 starts to hit the street and the updater starts
automatically pinging a.sl.o for updates.

I do want to make sure that ever though a.slo. _looks_ like a black
box, scaling a.sl.o is a solved problem.

Hope this helps.
david

On Thu, Oct 15, 2009 at 3:04 AM, Aleksey Lim alsr...@member.fsf.org wrote:
 On Thu, Oct 15, 2009 at 07:34:50AM +, Aleksey Lim wrote:
 On Thu, Oct 15, 2009 at 02:42:15AM -0400, Bernie Innocenti wrote:
  [cc += dfarning, alsroot, syst...@]
 
  El Wed, 14-10-2009 a las 17:47 -0700, Josh Williams escribió:
   I've made some bug fixes to the new ASLO design, I've tested it lightly
   and it seems to work in all major browsers (even ie6). If you have a few
   moments, please test it out (download/upload activities, browse around)
   and let me know if you see any display bugs or major usability issues.
  
   http://activities-devel.sugarlabs.org/en-US/sugar/
 
  All links to activity bundles appear to be broken :-(
  For example:
 
   http://activities-devel.sugarlabs.org/en-US/sugar/downloads/file/26072/xpi/labyrinth-7.xo?src=addondetail
 
  I'm not sure how to fix it, but I can imagine that it may be related
  with moving the activity bundles from their old location
  (/srv/www-sugarlabs/activities/files) to the upload directory
  (/srv/upload/activities/) done by Dfarning in order to enable
  Mirrorbrain.
 
  Earlier today, alsroot asked me to fix some permission issues that would
  prevent aslo from writing new activities in the new location.

 Thats intended to be so, activities-devel is just mysql copy 

[IAEP] Slobs election results 2009

2009-10-14 Thread David Farning
The results are in for this years election.  The winners are in for
this years election.

Walter Bender
Tomeu Vizoso
Mel Chua
Bernie Innocenti
Chris Ball
Sean Daly
Adam Holt

David Farning
Slobs Election Referee 2009
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Systems] Content Delivery Network is in production

2009-10-12 Thread David Farning
 Seems to be working pretty well from here in Portugal, download.sl.o
 gets redirected to download2.sl.o (solarsail @ MIT?) and utwente.nl.
 Both max out my connection (1.2 MB/s).

Nice, we will be adding mirrors as the system stabilizes.  The goal is
for the download infrastructure to  be ready to handle 10X the
bandwidth usage as on the last soas release.

As soon as then SoaS and Marketing teams decide dates for the release
and associated press releases can someone send notices of those dates
to the systems mailing.

Last year I had to restart the web server on sunjammer every couple of
hours when it froze:(  It would be nice to have Bernie and the other
infrastructure gurus around on days we expect larger than normal loads


david
 Congrats,

 Tomeu
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Systems] Content Delivery Network is in production

2009-10-12 Thread David Farning
On Mon, Oct 12, 2009 at 10:56 AM, Yama Ploskonka yamap...@gmail.com wrote:
 wow wow wow, this is a way cool concept.  Local updates that would be truly
 local automagically.  I really would want to know how this ends up working
 for the large deploys , esp. Uruguay.  I have been told that some servers
 are quite overstressed already as it seems (correct me here please) that as
 the machines there are booted they automatically try to connect somewhere
 OLPCish.  If it were true, I guess that should be fixed.

Some where between 80 and 90% of activity bundle download traffic
comes from Uruguary:)  I am hoping to find a couple of mirrors in
Uruguay in the next couple of days.  If you have any leads  We
need room for about 30GB of content.

Yes, .82 deployments are set to communicate directly with olpc
servers.  This has been updated in .86.  Another option is for Sugar
Labs to work with the VIG to make our mirror system available to OLPC.

david

 On Mon, Oct 12, 2009 at 9:34 AM, David Farning dfarn...@sugarlabs.org
 wrote:

  Seems to be working pretty well from here in Portugal, download.sl.o
  gets redirected to download2.sl.o (solarsail @ MIT?) and utwente.nl.
  Both max out my connection (1.2 MB/s).

 Nice, we will be adding mirrors as the system stabilizes.  The goal is
 for the download infrastructure to  be ready to handle 10X the
 bandwidth usage as on the last soas release.

 As soon as then SoaS and Marketing teams decide dates for the release
 and associated press releases can someone send notices of those dates
 to the systems mailing.

 Last year I had to restart the web server on sunjammer every couple of
 hours when it froze:(  It would be nice to have Bernie and the other
 infrastructure gurus around on days we expect larger than normal loads


 david
  Congrats,
 
  Tomeu
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep


___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Montessori madness...

2009-10-12 Thread David Farning
Stephen Jacobs (cced) the Professor of the OLPC/Sugar course at the
Rochester institute of Technology is a product of Montessori schools.
His mother was a Montessori teacher.

I have found it helpful to include him in Montessori related
discussion.  He has a good sense of what happens 'in the classroom' in
addition to a theoretical understanding of Montessori.

david

On Mon, Oct 12, 2009 at 11:44 AM, Yama Ploskonka yamap...@gmail.com wrote:
 Montessori, and all of Experiential Education, rely so very much on the
 personality of the teacher that they have very limited scalability.  This
 single matter is a whole sub-science in itself, with scant actual work
 beyond the empirical.

 Because some Schools of Montessori (there are factions and cults as anywhere
 else) are even more rigid than others (I was blessed to have my 1 1/2 year
 as Montessori teacher assistant happen in a more open one),  the tendency to
 fall into rigid Walls you mention is way too common. I was warned of that as
 I was considering specialized formal training. Even CUT had a Montessori...
 I don't know if it was you who mentioned some Montessori did not want to
 even consider XOs.

 As to the spark in their eyes, yes, certainly.  One problem we have is that
 right now the learning curve for getting the XO/Sugar to be useful for them
 is so steep that it's unlikely they will get there.

 BTW, the reports from Arahuay indicate that there they let the canes be
 handled by trusty older kids, ingenious way to avoid setting themselves to
 charges of abuse.

 a last BTW, and I should be getting to work, my nephews 3 and 1 1-2 years
 old at the time got the time of their lives with Lion King Activities, a
 most excellent set of learning and exploring software from back then,
 apparently able to navigate around by themselves on a PC.  Of course,
 uncle was by, so as was mentioned earlier, that made the
 self-learning-computer somewhat redundant and unworthy as a datapoint,
 something I do earnestly agree.

 That is why, again, I ask for ways we could find to communicate with real
 teachers right there on the ground.

 And a final BTW, Rishi Valley Institute for Educational Resources deserves a
 look
  http://river-rv.blogspot.com/
 They seem to be managing to do education under very difficult circumstances,
 somewhat similar to what Sameer describes as happening in Bhagmalpur, and a
 good point is to enhance peer-supported learning

 I quote For millions of children in the under-privileged sections of rural
 communities, RIVER has created, tested, successfully implemented and
 replicated, in India and abroad, a path-breaking Multi-Grade, Multi-Level
 (MGML) Methodology in Primary Education. Around 75,000 teachers and
 67,50,000 children are being benefited by this unique system based on
 activity based learning. Unlike the glaring drawbacks existing in the
 prevalent, mono-grade, teacher directed, text book based teaching system,
 the MGML methodology has started a silent revolution that makes learning
 joyful, reduces student dropouts, enhances community school linkage and
 makes the teacher more accountable. 


 On Mon, Oct 12, 2009 at 10:51 AM, Sameer Verma sve...@sfsu.edu wrote:

 On Mon, Oct 12, 2009 at 1:55 AM, Martin Langhoff
 martin.langh...@gmail.com wrote:
  On Mon, Oct 12, 2009 at 10:18 AM, Sameer Verma sve...@sfsu.edu wrote:
  I've been reading Montessori Madness for a few hours now, and I find

  Of course, I like most of Montessori's approach. But remove the human
  elements and... poof! it's effects will be gone. Montessori strategies
  in a crowded group with an unenthusiastic teacher have very slim
  chances.
 

 Indeed. My kid goes to a Montessori (which is why I was reading this
 book) but we've seen several M schools around here, where an
 indifferent teacher destroys the environment. It reverts to a Pink
 Floyd'ish assembly-line of faceless students processed into pink
 filler meat (Cue 4:21 http://www.youtube.com/watch?v=2VUhoD3vM9Q).
 Interestingly, my current discussions with them are about the
 introduction of Sugar in that environment (after-school sessions,
 maybe) but they think the kids are too young. They would like for the
 kids to be 5 at least...

  Bryan, you need to postulate your theory more formally :-)
 

 Or, become a Maria incarnate...I'm sure a born-again Montessori will
 get you tremendous following ;-)

 cheers,
 Sameer
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep


 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Content Delivery Network is in production

2009-10-11 Thread David Farning
For the last couple of week, we have been working with Peter Pöml to
set up mirrorbrain as the content deliver network for Sugar Labs.
There are a number advantages for using a content delivery network.

1. Usability -  We can  remove the mirror information from
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Download_locations
.  All a _user_ has to worry about is the single
http://download.sugarlabs.org location , redirection to individual
mirrors is invisible to the user.

2. Scalability - Rather that increasing the bandwidth or throughput on
a primary sl.org machine we can distribute the load across a system of
mirrors.  Mirrors are a very well understood concept in free software
delivery.  Mirrorbrain is used by both opensuse and open office with
loads 2 orders of magnitutide above Sugar Labs' loads.

3. Locality - Mirrorbrain uses geoip for to determine the physical
location of downloader and mirrors.  Mirrorbrain can determine the
most appropriate mirror for a given download.

Any traffic going through htp://download.sugarlabs.org (including
activity bundles) will be served through the content delivery network.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] FW: Live webinar: VirtualBox Web Console

2009-10-03 Thread David Farning
I was talking with Sun about shipping a preconfigured Virtual Box+Sugar
package just before the entered talks with oracle

Mayne it is time to revisit that potential partnership.

david

On Fri, Oct 2, 2009 at 8:56 PM, Caryl Bigenho cbige...@hotmail.com wrote:

  Hi Folks,

 If you would like to learn more about Virtual Box from the engineers
 working on it, you might want to check out this webinar.

 Caryl

 --
 Date: Fri, 2 Oct 2009 17:49:40 -0700
 From: s...@communications2.sun.com
 Subject: Live webinar: VirtualBox Web Console
 To: cbige...@hotmail.com

   Live webinar: VirtualBox Web 
 Consolehttps://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu
   [image:
 .]https://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu
*» **Register 
 Now!*https://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu

 *October VirtualBox Live Show*
 *The VirtualBox Web Console*

 Dear Caryl Bigenho,

 The VirtualBox Web Console (VBoxWeb) is an open source project implementing
 an AJAX version of the popular VirtualBox user interface. As a modern web
 interface, it allows you to access and control remote VirtualBox instances. 
 Join
 us for the next edition of VirtualBox 
 Livehttps://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu,
 where you'll learn how to use VBoxWeb to:

- Browse your virtual machines and inspect their settings
- Start virtual machines in headless mode
- Pause/resume VMs
- Save the state of running VMs
- Terminate VMs (hard power off or ACPI)
- Remote control your VMs using the integrated RDP Web Control

  *WHO: *
 Andy Hall and Achim Hasenmueller, VirtualBox Engineering Director
  *WHAT:*
 *VirtualBox Live 
 Showhttps://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu
 *
  *WHEN:*
 October 7, 2009, 8:00 am PDT / 11:00 am EDT / 15:00 UTC/GMT
 (The presentation will be approximately 45 minutes long, followed by QA.)
 *WHERE:*
 Simply access the web seminar from the comfort of your own home or office.
  *WHY:*
 If you want to save time, money and frustration, you'll want to join this
 webinar on the world's most popular open source virtualization software.


  *  Tune in, or miss out. Register now. 
 *https://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu

 If you have questions or feedback, please send them to
 virtualboxinquir...@sun.com.

 Thank you,
 Sun Microsystems, Inc.

 PS: If you can't join us live, make sure you catch the archive, which will
 be posted here within 24 hours of the 
 showhttps://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVRVupKVSSYCCYYWCCVLuHptXHKKjLkkVJIpnLgohxohluHptQJhu.
   Sun Microsystems, Inc. respects your privacy.
 You are receiving this email at cbige...@hotmail.com because of your
 registration activity related to VirtualBox.

 Privacy Policy http://www.sun.com/privacy  |   
 Trademarkshttp://www.sun.com/suntrademarks/  |
 Update My 
 Profilehttps://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVSVLuHptXHKKjLkkVJIpnLgohxohluHptQJhuVupKVSSYCCYYWCC
   |
 Unsubscribehttps://communications2.sun.com/servlet/cc6?kmgQWAYQSVJIpnLgohxohluHptQJhuVaVTV8wv2682Xb9VSCAUASUC

 Please do not reply to this email. Instead, contact the 
 editorjavaseforbusiness-inquir...@sun.com
 .

 Sun Microsystems, Inc., 18 Network Circle, M/S: UMPK18-124, Attn. Global
 eMarketing, Menlo Park, CA 94025 USA

 © 2009 Sun Microsystems, Inc. All rights reserved


 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] 2009-2010 Sugar Labs Oversight Board Election Starting Soon

2009-10-01 Thread David Farning
The elections committee has sorted out all of the know voter issues
which were raised after the trial election earlier this week.

Eligible members should receive a voter token within the next few minutes.

If you have any problems please contact me via this mailing list,
memb...@sugarlabs.org, or dfarn...@sugarlabs.org

David Farning
SLOBs election 2009-2010 referee
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] 2009-2010 Sugar Labs Oversight Board Election Starting Soon

2009-10-01 Thread David Farning
We have just received a notice that when voting one person only got a
partial list of candidates.

They solved the issue by discarding the ballot and trying again.

David Farning
SLOBs election 2009-2010 referee

On Thu, Oct 1, 2009 at 7:32 PM, David Farning dfarn...@sugarlabs.org wrote:
 The elections committee has sorted out all of the know voter issues
 which were raised after the trial election earlier this week.

 Eligible members should receive a voter token within the next few minutes.

 If you have any problems please contact me via this mailing list,
 memb...@sugarlabs.org, or dfarn...@sugarlabs.org

 David Farning
 SLOBs election 2009-2010 referee

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Test ballot complete. Feedback

2009-09-29 Thread David Farning
I would like to announce the completion of the Sugar Labs Test Election.

Know issues:
The election server is very overloaded.  It was not uncommon for the
server to take a minute or more to process a a submission.  As far as
I can tell everyones vote was processed.  Please keep track of your
'token' so you can verify that you vote has been processed correctly.

The test election was mis-configured to run until October 28 instead
of September 28.  I will verify that the SLOBs election is configured
correctly.

Incorrect email on membership roster.  I received one notice that
someone did not receive a voter token.  I will verify their name
against the membership log and update the email roster list as
necessary.

Does anyone else have feedback on the test election?  Please submit
that feedback to this list or to me personally.

David Farning
SLOBs election 2009-2010 referee
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] Test ballot complete. Feedback

2009-09-29 Thread David Farning
It turns out that the first five people to request member ship via
mem...@sugarlabs.org were missing from the email roster.

They follow:

* Sebastian Dziallas sebast...@?.? | sdz | APPROVED

* Tom Gilliard satel...@?.? | satellit | APPROVED

* Brian Jordan bcjor...@?.? | Bcjordan | brian | APPROVED

* Caroline Meeks solutiongr...@?.? | APPROVED

* Dave Bauer d...@?.? | daveb | APPROVED

The membership committee has added them to the roster.

David Farning
SLOBs election 2009-2010 referee
On Tue, Sep 29, 2009 at 6:02 PM, David Farning dfarn...@sugarlabs.org wrote:
 I would like to announce the completion of the Sugar Labs Test Election.

 Know issues:
 The election server is very overloaded.  It was not uncommon for the
 server to take a minute or more to process a a submission.  As far as
 I can tell everyones vote was processed.  Please keep track of your
 'token' so you can verify that you vote has been processed correctly.

 The test election was mis-configured to run until October 28 instead
 of September 28.  I will verify that the SLOBs election is configured
 correctly.

 Incorrect email on membership roster.  I received one notice that
 someone did not receive a voter token.  I will verify their name
 against the membership log and update the email roster list as
 necessary.

 Does anyone else have feedback on the test election?  Please submit
 that feedback to this list or to me personally.

 David Farning
 SLOBs election 2009-2010 referee

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Sugarcamp_Bolzano_2009

2009-09-29 Thread David Farning
I would like to re-extend the invitation for Sugarcamp_Bolzano_2009[1].

As it stands, we have four people currently registered:
   1. Simon Schampijer
   2. Tomeu Vizoso
   3. Walter Bender
   4. David Farning

If anyone else is interested please add your name to the wiki page[1].



1. http://wiki.sugarlabs.org/go/Marketing_Team/Events/Sugarcamp_Bolzano_2009
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Xoos Special Interest Group

2009-09-28 Thread David Farning
As promised, we have started work on the XO operating system SIG at
Sugar Labs.  The SIG pages are at http://wiki.sugarlabs.org/go/Xoos .

Based on feedback from the current developers working in this space,
the most valuable starting point will be to start making daily Xoos
builds.  The next step will be to work with others in this space to
create a release cycle which includes alphas, betas, and final
releases.  These releases will enable more users and testers to
participate in the development cycle.

Initially, communication will happen on the de...@lists.laptop.org,
sugar-...@lists.sugarlabs.org, and fedora-olpc-l...@redhat.com mailing
lists.

We have received initial support from the OLPC contributor program in
the form of developer machines.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] XO Special interest group at Sugar Labs

2009-09-21 Thread David Farning
On Sun, Sep 20, 2009 at 10:30 PM, Daniel Drake d...@laptop.org wrote:
 2009/9/21 David Farning dfarn...@sugarlabs.org:
 My idea is to start by getting a working version of the current
 versions of Sugar and Fedora running on an XO.  The SIG might lose
 some of the specific hardware benefits and mass deployment features on
 the first couple of iterations.  But, it can work towards the larger
 deployments needs as the development, testing, and triaging processes
 improve.

 Thanks for the initiative.
 How do you plan to work with the existing efforts? e.g. SoaS ported
 and modified for XO, and F11-for-XO1


The project is starting with work flow focused goals.
1. Create a team.
2. Create a release cycle.
3. Start cranking out releases each one better than the last.

The missing gap in the current Sugar- distro- XO workflow is that
CJB is working from the deployment and hardware back to the distro and
Sugar.  This is both necessary and exactly what OLPC _needs_ Chris to
focus on. (Think of the relationship between redhat and fedora)

But, he and the entire ecosystem would benefit from a time based
release focus upstream.  That way they can pick an upstream and spend
six or eight months making it deployment ready rather than starting
from scratch every year or eighteen months.

It would be great if you would bring your work into the project.  As
far as I can tell, you and Chris are the two most knowledgeable people
working on this problem.  Not sure what your time available is:)
Hopefully, we can build a tight team to make your work more widely
available.

The goal is to provide a place where the various people working on
'upstream' XO, disto, and Sugar issues can come together, tighten
focus, and make their work available to the widest possible audience.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] 2 idea's to train people dyslexia

2009-09-21 Thread David Farning
Marten,

I would like to introduce you to Marilyn Hagle (CCed).  She is active
at the intersection of dyslexia and technology based education tools.

She has recently written a grant to set up a pilot for researching and
using sugar as a platform for helping kids overcome or adapt to their
dyslexia.

david

On Mon, Sep 21, 2009 at 5:37 AM, Marten Vijn i...@martenvijn.nl wrote:
 On Mon, 2009-09-21 at 12:17 +0200, Tomeu Vizoso wrote:
 On Wed, Sep 16, 2009 at 09:56, Marten Vijn i...@martenvijn.nl wrote:
  On Wed, 2009-09-16 at 09:34 +0200, Marten Vijn wrote:
  Hi,
 
  I am not a dyslexia expert, maybe a bit more that average.
 
  idea 1
  Today I read in a newspaper that it helps people
  to let them hear what they (words not the characters).
  __^ type*
 
  *Actually I do knwo a lot about dyslexia, like that is really annoying
  not being capable to write normal emails without make errors.
  No patches seem to be availible.
 
  Training young kids _in time_ prevents a lot frustration, dropouts from
  school and waste of very creative talented kids.
 
  My son would have a  50% change of being born with it too. So having
  having a good educational toolset seems important.

 Wonder if we could involve on this an existing dyslexia organization?

 good idea.

 http://books.google.nl/books?id=pLvC1kKUWTkCpg=PA47lpg=PA47dq=audio
 +feedback
 +dyslexiasource=blots=iMn_I_8efusig=CQhPMzM15_twYh43WTSbKP6qbmMhl=nlei=DlO3Sru8KI_E-QavmsXcCQsa=Xoi=book_resultct=resultresnum=5#v=onepageq=f=false

 http://www.springerlink.com/content/r33873h07n78j722/



 mmm,
 I 'll keep it on my list for dutch researchers. Not If I will to
 sucseed.

 I never know who am talking to tomorrow :)

 cheers,
 Marten


 Regards,

 Tomeu

  cheers
  Marten
 
 
 
 
 
  --
  Marten Vijn
  linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6
  http://martenvijn.nl
  http://opencommunitycamp.org
  http://wifisoft.org
 
 
  ___
  IAEP -- It's An Education Project (not a laptop project!)
  IAEP@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/iaep
 



 --
 Marten Vijn
 linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6
 http://martenvijn.nl
 http://opencommunitycamp.org
 http://wifisoft.org


 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] [SoaS] The Future of Sugar on a Stick

2009-09-21 Thread David Farning
On Mon, Sep 21, 2009 at 3:37 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Mon, Sep 21, 2009 at 08:30, Mel Chua meta...@gmail.com wrote:
 There's a lot going on in this thread, so here is my attempt to
 summarize discussions so far. If I've missed or misstated anything, my
 apologies - and it's a wiki, so go fix it. ;-)

 http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick

 By my count, there are 4 things we need to decide on and then execute
 in order to wrap up this conversation. Some are already in progress.

    * 4.1 Make a SoaS mailing list
    * 4.2 Formalize a SoaS development team
    * 4.3 Determine what Sugar on a Stick refers to
    * 4.4 Determine what the code Sebastian is working on is called

 Only the third one has a clear owner (SLOBs) and can be decided at
 this time (the 4th seems to depend on the answer to the 3rd). How can
 we move these forward - and are there any other blocker decisions that
 aren't listed here?

 Great summary, this is my understanding of how things stand today:

 4.1 can be left entirely to the SoaS team for decide

 4.2 also depends only on the SoaS team, haven't heard nobody against
 SoaS qualifying for a project inside SLs. SoaS is already listed as a
 project in the wiki, btw:

 http://wiki.sugarlabs.org/go/Category:Project
 http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines

 4.3 a decision panel has been proposed to help with this

 4.4 only depends on the SoaS team, but may depend on 4.3 to avoid name clashes

 Regards,


After reading this thread again, Mel's and Tomeu's summaries are spot on.

1,2, and 4 are SoaS Project level decisions.

We could go even one step further and say 4.3 is a marketing team/soas
project level decision.  This give the marketing team the freedom to
identify a marketing strategy base on either the platform of a
specific project with the overall project without committing the Sugar
Labs to a 'official' position

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] 2 idea's to train people dyslexia

2009-09-21 Thread David Farning
CCing iaep.

Your questions are good.  As participants, we have hashed this over to
death:)  But, our external message is still not spread widely enough:(

I will leave the questio open so we, as a community, can both help
answer your specific questions and figure out how to simplify and
amplify those answers.

david

On Mon, Sep 21, 2009 at 10:22 AM, Marilyn Hagle
mari...@fineartsforall.org wrote:
 David,

 I have been meaning to write to you.  Thank you sincerely for making this
 connection.  I really appreciate it.

 I am attaching at the bottom of this email the letter I sent to the grant
 writing participants last week.  At this point it we have not succeeded in
 receiving funding from the Dept. of Ed.  However the work is moving on.  I am
 particularly interested in testing Sugar.  I have a couple of questions . . .
 first . . . is Sugar a complete operating system, or is it an addon to an
 operating system, or both?  I would really like to download and installation
 .iso, but have not found such a thing.  Maybe I am not looking hard enough?

 I joined the IAEP list.  :)

 Hope you are well.

 Marilyn


 Quoting David Farning dfarn...@sugarlabs.org:

 Marten,

 I would like to introduce you to Marilyn Hagle (CCed).  She is active
 at the intersection of dyslexia and technology based education tools.

 She has recently written a grant to set up a pilot for researching and
 using sugar as a platform for helping kids overcome or adapt to their
 dyslexia.


 :)

 *

 Hi there everyone!  Thought I ought to send you a note to let you know what is
 happening.

 I know now that we did not make the first cut.  I received a letter in the 
 mail
 with the reasons and most were related to the structure of the main narrative.
 One thing they mentioned was that I did not give detail about which
 evidence-based technology practices we were using.  Heck, I just thought that
 was something that we incorporated into the process.  Another issue they had
 was that the resource kits would not be developed until the fourth year.  My
 reasoning was that I thought it prudent to be sure about our methods and
 conclusions before we start sharing them with others.

 In the grant documentation it states that they reserve the right to issue a
 second award if there are funds available, so there is tiny remote hope.  I
 have written to the competition manager for this grant, David Malouf, (who was
 very helpful to answer questions earlier) and asked him about other options.

 There is another similar grant that has been posted which is due in October.
 An interesting note is that they took at least three points from our narrative
 and incorporated them into this new grant.  It really looks like they took our
 proposal and used it as a basis for the new offer.  The difference is that the
 new grant asks specifically for graphics and charts for disabled children, not
 audiobooks or netbooks.

 I had not remembered that I had a contact person at Mozilla when I was working
 on the grant in July.  When I received the aforementioned letter, it jolted my
 brain and I thought to go the Mozilla website.  Come to find out, the Mozilla
 Foundation is eager to consider educational projects offering greater
 accessibility to dyslexic students.  So I sent them our narrative and the
 staff summary for consideration.  I doubt they have vast funding like
 the Dept. of Ed, but we will see what happens.

 The educators among us are back to work at our day jobs, but the work to 
 modify
 existing technology for dyslexic children must continue anyway. This past week
 my husband and I were able to find a technology solution for Hannah's book
 reading situation at school.  She is required to read one 200 page book per
 week or she misses recess.  She cannot keep up.

 Did you know that you can go to http://booksshouldbefree.com and
 http://gutenberg.org and easily download the html versions and mp3 files for
 many wonderful books?  (I knew about them before, but did not realize they 
 were
 so easy to access.)

 We added OMusic, an online music player, and FoxVox, a text-to-speech reader 
 to
 Firefox.  The html book files and mp3 audio book files are in a books
 directory on the hard drive of Hannah's EeePC.  We bookmarked the html book
 files.  When Hannah opens a book, she clicks on the music note (OMusic) at the
 bottom of the Firefox window, and chooses the audio file for the chapter she 
 is
 reading.  She arrows down the text with the reader, always keeping the current
 text at the top of the window so she does not get lost.

 Hannah is currently reading/listening to Alice in Wonderland.  Already 
 resident
 on her EeePc are these books:

  *  Secret Garden
  *  Anne of Green Gables
  *  Heidi
  *  Grimms Fairy Tales
  *  Moby Dick
  *  Aesop's Fables
  *  Beatrix Potter Complete
  *  The Day Boy and The Night Girl
  *  The Enchanted Castle
  *  Dracula
  *  Gulliver's Travels
  *  Peter Pan

 Hannah has

Re: [IAEP] XO Special interest group at Sugar Labs

2009-09-21 Thread David Farning
On Mon, Sep 21, 2009 at 3:41 PM, Peter Robinson pbrobin...@gmail.com wrote:
 Hi David,

 On Mon, Sep 21, 2009 at 7:48 PM, David Farning dfarn...@sugarlabs.org wrote:
 For the past several months the OLPC/Sugar Labs ecosystem has been
 getting requests to provide releases of more recent versions of Sugar
 on the XO.

 The leading effort in this direction seems to be the F11-XO1 project.
 I would like to like to invite F11-XO1 to become part of the XO SIG.
 I have been trying to articulate the project goals and gather momentum
 across several groups.
 1.  OLPC as a downstream.
 2. Sugar Labs as a focus point.
 3. Various ecosystem leaders to do pilots with current versions of Sugar on 
 XOs.
 4. Various testers to provide user level testing.

 The goal of this groups is not to _fragment_ the existing efforts.
 The goal is bring the various efforts together to form a critical mass
 to help pull this propel forward.

 As far as I'm aware there is no F11-XO1 project, I'm aware of a couple
 of different projects to get the latest Sugar releases on the XO.
 - The SoaS on XO which is being run my Martin Dengler in conjunction
 with SoaS and SL (that's where its all hosted).
 - The OLPC project to get Fedora 11 on both the XO-1.5 and XO-1 which
 is being handled by Steven M. Parrish (and Daniel Drake / Chris Ball)

This confusion is part of what I am hoping to clear up by create a
single clearly defined project.

I have heard back from many of the people working on the various
projects. the work flow seems to be:
1. Sugar development team creates platform.
2. Fedora packagers package Sugar... and everything else required to
make a disto.
3a. SoaS takes packages and turns them into a Soas image.
3b. Soas is getting pretty well test via test days and deployments
such as the GPA.
4a. Steven take the Fedora packages adds the XO specific bit and turns
them into xo builds.
4b. limited testing for xo builds.

Because of time restrictions, the F11 on XO effort seems to be
reactive.  They take the output from cjb and the fedora packages and
create builds.  I believe that the XO SIG could help generate interest
and attract more developers and testers to the project.

 Both projects are cross pollinated and use components of work done by
 both as well as myself and other Fedora upstream people. I don't
 believe there's much difference between them as where possible I
 believe most stuff is pushed upsteam. There is no current Fedora based
 project working on this directly due to the down stream projects.

 I have my own build that I use but that isn't generally published and
 is mostly to test core fedora for dependency bloat and breakages.

Would it be useful if we started by combining your work and Stevens
into an automatic build system.  This could help identify breakages.
Then we could create a release cycle of alpha and beta and final
releases.

By creating the daily builds and widely broadcasting the various
releases, we can engage a larger community of testers.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] XO Special interest group at Sugar Labs

2009-09-20 Thread David Farning
In some of the other threads we have been seeing an interest in the
Sugar Labs Community improving the Sugar experience on the XO.  As
such, I would like to create a XO SIG within Sugar Labs.  I have filed
an initial draft application with the OLPC Contributors program for 5
loaner machines for developers.

My idea is to start by getting a working version of the current
versions of Sugar and Fedora running on an XO.  The SIG might lose
some of the specific hardware benefits and mass deployment features on
the first couple of iterations.  But, it can work towards the larger
deployments needs as the development, testing, and triaging processes
improve.

One piece that I would like to be very clear that the goal of the SIG
is to be an community led upstream for OLPC.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


[IAEP] Mailing list consensus techniques.

2009-09-19 Thread David Farning
There are several passionate threads happening on various SL mailing
lists.  As we push through these discussion I would like remind
participants about a couple of tactics I have learned for successfully
building a consensus on a mailing list.

1. Never take (or make) it personal.  Passion is good.  But always
focus on the issues.

2.  Focus on educating others.  There will be vocal minorities who
don't understand what you are saying.  But for the most part people
are listening and learning.

3. Rather than finding faults in specific posts, create a series of
impersonal 'summary' threads.

4.  No single issue or decision is a show stopper.   As long as Sugar
Labs sticks to a cycle of exploration through implementation,
collaboration, and reflection, the project and any products based on
the platform will improve.

5.  Try not to post more than once a day to a thread. Quality of
thought is more effective then quantity or volume of words.

david
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Debian-olpc-devel] Glucose 0.84 and 0.85 packaged for Debian!

2009-09-19 Thread David Farning
I tried them out briefly in a VM this morning, worked great.

A couple of questions.

I don't understand the debian work flow.  I see that you are carrying
.82, .84, and .85.  Will you continue to carry all of them going
forward?

Do you have a recommended work flow for basing downstream packages on
work.  I got my mind wrapped around git-buildpackage last night. I
cloned your work and tried build some of them on GnewSense.

It there a prefered method for setting the upstream for third and
lower generation packages?  The best I could come up with is:

1. git.sl.org - upstream
2. manually sync /debian from git.debian.org to git.gnewsense.org
3. do final work in git.gnewsense.org

david

On Sat, Sep 19, 2009 at 5:43 PM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Sun, Sep 20, 2009 at 00:32, Jonas Smedegaard d...@jones.dk wrote:
 Hi all,

 As subject says, Glucose (and some of Fructose) 0.84.0 and 0.85.7 is now
 packaged for Debian!

 More info at http://wiki.debian.org/Sugar and
 http://wiki.sugarlabs.org/go/Community/Distributions/Debian .

 Wow, tomorrow will give it a go.

 Thanks,

 Tomeu

 --
 «Sugar Labs is anyone who participates in improving and using Sugar.
 What Sugar Labs does is determined by the participants.» - David
 Farning

 ___
 Debian-olpc-devel mailing list
 debian-olpc-de...@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/debian-olpc-devel

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [SLOBS] SLOBs Position on SoaS

2009-09-16 Thread David Farning
As Sean and Martin point out the consequences of this decision extend
past SoaS.  The effects seem to centre on four levels:

1. Procedural.
2. Mission, Vision, and Values.
3. Operations.
4. SoaS the project.

As we work through the levels, a pretty good decision _should_ emerge.

Procedural--
As a general rule, decisions are made on public mailing lists.  Once a
consensus is reached on the lists, the consensus is presented to SLOBs
for ratification.  Occasionally, a SLOB will point out that we missed
an important point Then we refine the decision and iterate through
the process again.

I apologize for any confusion about that.  I did not realize that my
dual roles as a member of the board and the guy who often works on
building consensus would cause confusion.  Hopefully, by not sitting
on the board next term some of that confusion will clear up.

Values--
While thinking about how to present this issue to the board for
ratification, I keep coming back to the value.

The success and trust in Sugar Labs is premised on empowering and
enabling rather than excluding.

The questions becomes, How do we make an official relationships
between Sugar Labs and a project empowering and enabling to both
parties? and How do we prevent an official relationship between a
project and Sugar Labs from excluding other interesting projects?

Any thoughts?

david


On Tue, Sep 15, 2009 at 4:03 PM, Sebastian Dziallas sebast...@when.com wrote:
 Let me rephrase again, to make things clear. I'd love to hear an
 official answer on this. Soon.

 Is the current SoaS going to be the primary way Sugar Labs distributes a
 Sugar-centric GNU/Linux distribution?

 --Sebastian
 ___
 SLOBs mailing list
 sl...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/slobs

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


Re: [IAEP] [Sugar-devel] Project Guidelines posted

2009-09-14 Thread David Farning
On Sun, Sep 13, 2009 at 8:00 PM, Bryan Berry br...@olenepal.org wrote:
 On Fri, 2009-09-04 at 12:25 -0500, David Farning wrote:
 Project/SIGs are product focused.  The exist to help guide a project
 through it's life cycle.  For example, there has recently been some
 rather heated discussions about working more closely with Qt.  This is
 an example of a idea the could start as a SIG and grow into a project
 and be included in the Learning Platform if it proves useful.

 Sorry to have not been involved in this conversation.

 So it sounds to me like Karma should be an SL SIG and later an SL
 Project. I really don't have an idea of how it will be governed but I
 will leave that to later as i see how the community around it develops.
 So I guess Karma can't progress from SIG to project until the leadership
 process is defined.

The work going on in Nepal is one of the primary reasons for
establishing SIGs and projects.  Nepal is doing an amazing job of
creating solutions for local problems.

Sigs/projects are a place where deployments can share ideas and work
together on solutions for local issues.

A good example of how to progress would be to work through the
questions on the SIG guidelines at
http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines .  The
questions are not just bureaucratic hurdles.  They represent some of
the best practices that Eclipse, Apache and Fedora have found helping
ideas grow into successful projects.  You have already worked through
most of the issues for karma.

The project wiki format is basically the same a a team wiki page.  It
is pretty flexible yet makes it easy for someone to discover what your
project is all about and how to get involved.

david

 I feel bad because I have been putting the SL logo on the
 karmaeducation.org site. Sorry if I was using the SL branding
 prematurely. I also put the SL logo in the Karma presentations.



 --
 Bryan W. Berry
 Technology Director
 OLE Nepal, http://www.olenepal.org


___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Project Guidelines posted

2009-09-14 Thread David Farning
On Mon, Sep 14, 2009 at 9:29 AM, Bryan Berry br...@olenepal.org wrote:
 On Mon, 2009-09-14 at 09:21 -0500, David Farning wrote:
 The work going on in Nepal is one of the primary reasons for
 establishing SIGs and projects.  Nepal is doing an amazing job of
 creating solutions for local problems.

 Sigs/projects are a place where deployments can share ideas and work
 together on solutions for local issues.

 A good example of how to progress would be to work through the
 questions on the SIG guidelines at
 http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines .  The
 questions are not just bureaucratic hurdles.  They represent some of
 the best practices that Eclipse, Apache and Fedora have found helping
 ideas grow into successful projects.  You have already worked through
 most of the issues for karma.

 The project wiki format is basically the same a a team wiki page.  It
 is pretty flexible yet makes it easy for someone to discover what your
 project is all about and how to get involved.

 david

 tks for the thoughtful response Dave

 good, then i don't feel bad about using the SL logo :)

 What should the next step for Karma be on the SIG/Project route?

I think that I would start converting the karma wiki page into
sig/project to raise its visibility.

Then over the next six months of so try to align you release cycle
with the larger Sugar release cycle.

 I think it will take 6+ months for a governance strategy for Karma to be
 worked out. Essentially right now we are just trying to reimplement the
 work done in Flash to html5+javascript. Later when different individuals
 have differing ideas, we may need some governance. Right now, the main
 focus is How do we convert the talking water buffalo from flash to
 html5?

I wouldn't worry to much about governance.  The guidelines are set up
so that as a sig works through the process, leaders and governance
models will emerge.

Once the mission, vision, and implement roadmap are in place we can
tag karma as a sig.

david

 Bryan W. Berry
 Technology Director
 OLE Nepal, http://www.olenepal.org


___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [SLOBS] The Future of Sugar on a Stick

2009-09-14 Thread David Farning
On Mon, Sep 14, 2009 at 4:05 PM, Sebastian Dziallas sebast...@when.com wrote:
 Martin Dengler wrote:
 On Mon, Sep 14, 2009 at 06:33:47PM +0200, Sebastian Dziallas wrote:
 Martin Dengler wrote:
 On Mon, Sep 14, 2009 at 05:32:55PM +0200, Sebastian Dziallas wrote:
 == What is SoaS? ==

 [...] SoaS aims to make it easy for local deployers to provide each
 student with a thumbdrive (stick) [...]

 Notably, this does not say SoaS is Sugar Labs' way of providing
 [anyone] with a [image to put on a] thumbdrive.

 Should we understand SoaS goal as a source-only distribution-making
 kit?  If SoaS is to be Sugar Labs' way of distributing Sugar, we
 should clearly say so.  If not, then we should clearly say so as well.

 That's actually a pretty important point and affects strongly the
 future of SoaS. Since it clearly depends on SL's point of view, it's
 something on which other opinions (like SLOBs') are needed.

 It'd be interesting to have your point of view.

 Heh, yeah. I probably should explain...

 So my vision is that this SoaS is actually *the* way of distributing
 Sugar, as a SL product. If Sugar Labs doesn't think so, I'd have
 preferred to be informed much earlier. But wait, who's SL here?

 Is it me? Is it SLOBs? Who's going to provide certainty here?

 I personally would like to see open discussions about SoaS being made
 publicly on the mailing list (whether its a SoaS list or sugar-devel) to
 encourage as many people to get involved as possible as well as to
 minimise duplication of effort. I'd also like to gain this certainty
 about what are the plans for the SoaS brand in general are, etc.

 --Sebastian

I am working on a reply, which I hope articulates Sugar Lab's needs so
SoaS can figure out where it fits in.

david

 Thanks,
 Sebastian Dziallas

 Martin

 --Sebastian

 Martin
 ___
 SLOBs mailing list
 sl...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/slobs

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

[IAEP] Unifying the Sugar Labs experience Was: [Sugar-devel] Project Guidelines posted

2009-09-12 Thread David Farning
 Isn't this related to Brainstorm and Blueprints in Launchpad?

Yes, I agree they are closely related.

I would like to take a step back and look at the problems we are
trying to solve.

Backstory.
Over the past couple of months I have spent most of my time working
with 'external' people and organizations.  I have been looking for
ways we can work together.  Originally, I though of the problem as how
do we Identify, Engage, and Empower potential contributors.  That is
pretty standard volunteer recruitment strategy.  This approach has
been creating a dissonance that I did not understand until Mel chewed
me out last night.

The dissonance is that identifying, engaging, and empowering potential
contributors flies in the face of nearly everything Sugar Labs stands
for.  The correct approach is to focus on creating a community culture
where potential contributors can discover what they want to do,
discover how to engage with the community, and discover how they can
implement their ideas. Identify, Engage, and Empower still holds true.
 Sugar Labs must be discoverable so new contributors can figure out
how they fit in.

Consistency and clarity of community.
In marketing we often talk about the importance of a clear and
consistent message.  The release cycle is premised around clear and
consistent dates for developers to converge and diverge.  The way to
make Sugar Labs discoverable is to create a clear and consistent
community.

Creating this consistency does not depend on long weighty legal tomes.
In fact, the opposite is true.  This consistency comes from clearly
sticking to a few guiding principles.  Following are three examples of
reoccurring situations that happen across the project.

#1
A few months ago we were discussing the the pros and cons of updating
Sugar via activities.sugarlabs.org.  Initially the discussion were
heated and rather handwavey.  Then the devteam implemented the 'new
feature' process.  Engaging in the new feature process shifted _all_
of my energy from _proving_ that update is a good idea to creating a
viable implementation.

The new feature process provided be a very good template for how to
proceed if I wanted my feature to be considered for the next release.
I filled out the form and hacked together reasonable proof of concept
code.  One day a core developer, aslroot, pickup the code and rewrote
it.  A few days later I got a email from Simon asking me to clean up
the release notes because it was going to included in .86.

The new process guidelines provided me, the inexperienced developer, a
way to align my work flow and expectations with the development team.

#2
Last Summer we work we several groups of students.  Jameson worked
with Mel and Leslie Hawthorn on the GSOC project.  Fred worked with
Prof. Steve Jacobs and I with the RIT co-op students.

Our experiences were very different.  At RIT we were flying blind. It
was the first time:
Anyone taught a course combining community service and technology
using open source and Sugar.
RIT made an exception to allow unpaid co-ops.
RIT allow remote co-op.

None of us had clear expectations.  Communications suffered.

GSOC is now in its 5th iteration.  They have very good guidelines for
how projects can effectually 'identify, engage, and empower' students.
Identify - via the project proposal.
Engage - via the mentor.
Empower - the student is free to explore, collaborate, and reflect
within the limits and expectation of the project.

#3
Recently the GSOC team brought in $4500. $2000 in travel money and
$2500 in general money.  The challenge was determining how to spend
it.  Rather than push this decision up to the oversight board we
appointed the GSOC mentors an ad hoc committee who had authority to
spend their money as they see fit.  The oversight board is in the
process of approving this via lazy consensus.

By creating a very light weight decision making body of GSOC mentors
we pushed the spending authority out to the people with who were
highly engaged in the GSOC project.

Themes
Life cycle guidelines --  The value of life cycle guidelines show up
across the project.  The new feature process does a very good job of
explaining how to take an idea for a new feature through to becoming
part of a release.  The process makes no judgment on the value of an
idea. Instead it aligns expectations of  the new developer and the
release team.

The GSOC guidelines are another variation on life cycle guidelines.
It focuses on best practices to help insure that students, mentors,
and projects all have matching expectations.

Delegating authority -- The oversight board and the ad hoc GSOC
spending committee are are both example of delegating authority
through lightweight decision making bodies.  It took less than ten
minutes to set up the committee and get board approval.  The decision
are being made by those most knowledgeable about the subject.

Future action items.
Project guidelines -- Project guidelines are just life cycle
guidelines for how top 

Re: [IAEP] Where should we put Lesson Plans? Currwiki?

2009-09-10 Thread David Farning
it might be worth forgetting about where and how to best publish the
curriculum for this term.

Creating curriculum for a new class seems like enough of a challenge
for one intern for one semester.  Next term as you are figuring out
how to scale out the curriculum to the rest of the school, you can
figure out how to make it widely available.

david

On Thu, Sep 10, 2009 at 6:34 AM, Luke Faraone l...@faraone.cc wrote:
 On Thu, Sep 10, 2009 at 06:27, David Van Assche dvanass...@gmail.com
 wrote:

 curriki != moodle courses, format is quite different. So unless you create
 seperate instances of the courses one will have to choose either curriki
 format or moodle format.

 Hm, that doesn't sound right: wouldn't Curriki benefit by making their
 content easily convertible to a variety of formats?
 CC'ing an acquaintance of mine at Curriki to get the full story.

 On Thu, Sep 10, 2009 at 9:50 AM, Tomeu Vizoso to...@sugarlabs.org wrote:

 On Thu, Sep 10, 2009 at 09:32, David Van Asschedvanass...@gmail.com
 wrote:
  Well, this is really what moodle was created for. Especially
  considering its
  the main tool used in all XS server implmentations and is in use in at
  least
  40% of British schools. I'm not sure about the American numbers, but
  pretty
  sure it must be highly used there too. Creating courses in moodle is
  not
  only easy, but extremely powerful, and can be easily shared with other
  teachers. There are existing general moodle implementations, though
  none
  have enough content, including the sugarlabs one
  (schools.sugarlabs.org) I'm
  focusing my own efforts on linux-for-education.org, where little by
  little
  we're growing the site. The latter has 5 sugar based courses I created
  and
  several ubuntu and opensuse courses. Apart from the courses, the
  glossaries
  and database modules link straight into the course content, allowing
  students to easily look up terms used in courses that might be
  confusing.

 But I guess you can deploy Curriki content in Moodle instances? I
 think the main point of Curriki is working together with an existing
 community, not so much about what is used to deploy the content.

 Regards,

 Tomeu

  kind regards,
  David Van Assche
 
  On Thu, Sep 10, 2009 at 3:27 AM, Bryan Berry br...@olenepal.org
  wrote:
 
   From: Caroline Meeks carol...@solutiongrove.com
   Subject: [IAEP] Where should we put Lesson Plans? Currwiki?
   To: iaep iaep@lists.sugarlabs.org, Kellie Doty
         kmd...@mail.harvard.edu
   Message-ID:
         b74fba2b0909091618s103ddaa0oe4e2767f2aa02...@mail.gmail.com
   Content-Type: text/plain; charset=iso-8859-1
  
   I'd like to introduce Kellie Doty, she is a fellow student in the
   Technology, Education and Innovation program at Harvard Grad School
   for
   Education and she is in Intern at Sugar Labs this fall working on
   the
   GPA
   project.  Kellyie's role will be to help us develop curriculum, test
   it
   at
   GPA and publish it in a format that will be easy to adopt by other
   teachers.
   One of her first tasks will be to take the lessons we did
   over the summer and try to write them up.
  
   One question is where should we put lesson plans?
  
   My first thought was wiki.sugarlabs.org
    our wonderful maze of twisty pages all different.  But Kellie
   pointed
   out that teachers need to be able to find things through various
   paths
   such as subject, grade level and activities used.
  
   My second thought was Moodle as it probably has a module for that.
 
  +1 for curriki. It has an existing community of teachers to work w/
  and
  it is a good tool, geared to their needs
 
 
  --
  Bryan W. Berry
  Technology Director
  OLE Nepal, http://www.olenepal.org
 
  ___
  IAEP -- It's An Education Project (not a laptop project!)
  IAEP@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/iaep
 
 
 
  --
 
  Ted Turner  - Sports is like a war without the killing.
  ___
  IAEP -- It's An Education Project (not a laptop project!)
  IAEP@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/iaep
 



 --
 «Sugar Labs is anyone who participates in improving and using Sugar.
 What Sugar Labs does is determined by the participants.» - David
 Farning



 --

 Marie von Ebner-Eschenbach  - Even a stopped clock is right twice a day.
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep



 --
 Luke Faraone
 http://luke.faraone.cc

 ___
 IAEP -- It's An Education Project (not a laptop project!)
 IAEP@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/iaep

___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] student guidelines _very_ rough draft

2009-09-08 Thread David Farning
Thanks Martin,

I'll ping Helen later today.

david

On Tue, Sep 8, 2009 at 5:49 AM, Martin
Langhoffmartin.langh...@gmail.com wrote:
 FWIW, Helen Foster @ Moodle handles that -- according to Google's SoC
 ppl -- is one of the best-run GSoCs. What I hear from students is that
 the explicit 'expectations' document is very good guidance. All the
 docs are -- I think -- interesting:

   http://docs.moodle.org/en/Category:GSOC

 as a mentor, Helen is always there, and sends me brief kind emails in
 advance of deadlines, calls on meta-mentors to help when I am bogged
 down and not answering to my mentees in timely fashion, etc.

 Her approach is really outstanding.

 As a mentor for 3 runs now, I have so say that the best indicators of
 success have been...

  - The time I spend on it -- not just direct irc time -- quality code
 review takes a lot of time!

  - How hard the students work, and how skilled they are, *before* the
 project starts. A student that can't get a checkout and a build going
 and patch a bug or two without help is of no interest to me (in the
 context of GSoC). Pretty damn high bar, but there are a lot of people
 applying for GSoC -- get the best ones :-) -- and it will be valuable
 dev time diverted from other work.

 hth,


 m

 On Tue, Sep 8, 2009 at 12:45 AM, David Farningdfarn...@sugarlabs.org wrote:
 This summer, Sugar Labs had 12 students working under various gsoc,
 intern, workstudy, and co-op programs.  Overall, the results have been
 promising.  There are a few things which we can do to improve the
 experience for everyone.

 Based on conversations with other opensource project the three keys to
 success for working with students are:
 1. Clearly defined expectations for student, sponsor, and project.
 2. Clearly project plan with implementation strategy.
 3. Experienced mentor.

 Below is a very rough draft of a student guidelines document.  I would
 appreciate suggestions.

 david

 
 Thank you for your interest in working, and learning, with Sugar Labs.

 Sugar Labs has a large number of smart and passionate student
 participants.  These student often go on to become Sugar Lab's most
 important contributors and project leaders.  One of the advantage of
 being a student is that  you can combine your learning experience at
 Sugar Labs with your official school activites through intern-ships,
 co-ops, work study programs, and privately sponsored contracts.

 The following guidelines are intended to insure that your Sugar Lab's
 experience is beneficial for you, your school, and Sugar Labs.
 Working with Sugar Lab's as an intern, co-op,  or work study student
 means that there is a contractual obligation between you, your school,
 and Sugar Lab's.  This document represents the thoughts and
 deliberations which have gone into making your experience at Sugar
 Labs beneficial for you, your school, and Sugar Labs.[REPEATED TEXT]

 == project description==

 Experience has shown than the most important factor in having a
 successful experience at Sugar Labs is your project plan.  The plan
 represents the vision of what you want to accomplish and provides
 roadmap for how to make that vision a reality.

 Exploration, collaboration, and reflection.  Plan provides boundaries
 so you can freely explore.

 First big project for many students.

 Done before starting program

 good plan implies investment by student-investment by student results
 in good mentor.

 Fail to plan - Plan to fail.

 The plan should include:
 [CHECK LIST]
 *deliverable
 *learning objective

 ==mentor==
 The second most important piece to success is your mentor.
 link to community
 master - apprentice

 ==General information==
 Below is general information for filling out your school's forms.

 ===Overview===
 Sugar Labs is organized as a member project of the Software Freedom
 Conservancy[1].  The SFC is an umbrella organization which handles the
 accounting work, financial management, and makes sure the activities
 of Sugar Labs fit within the scope of the non-profit status.

 ===Mission statement===
 The mission of Sugar Labs® is to produce, distribute, and support the
 use of the Sugar learning platform; it is a support base and gathering
 place for the community of educators and developers to create, extend,
 and teach with the Sugar learning platform.

 ===Funding===
 Sugar Labs is funded through donations from its contributing members.

 ===Agency Name===
 Sugar Labs (A member project of the Software Freedom Conservancy)

 ===Agency Contact===
 Bradley M. Kuhn

 ===Postal Address===
 Software Freedom Conservancy
 1995 Broadway FL 17
 New York, NY 10023-5882

 ===Telephone===
 +1-212-461-3245 tel
 +1-212-580-0898 fax

 ===Email===
 conserva...@softwarefreedom.org

 ===Addition information===
 For additional information or forms please contact dfarn...@sugarlabs.org.
 ___
 IAEP -- It's An Education Project (not a laptop project!)
 

[IAEP] student guidelines _very_ rough draft

2009-09-07 Thread David Farning
This summer, Sugar Labs had 12 students working under various gsoc,
intern, workstudy, and co-op programs.  Overall, the results have been
promising.  There are a few things which we can do to improve the
experience for everyone.

Based on conversations with other opensource project the three keys to
success for working with students are:
1. Clearly defined expectations for student, sponsor, and project.
2. Clearly project plan with implementation strategy.
3. Experienced mentor.

Below is a very rough draft of a student guidelines document.  I would
appreciate suggestions.

david


Thank you for your interest in working, and learning, with Sugar Labs.

Sugar Labs has a large number of smart and passionate student
participants.  These student often go on to become Sugar Lab's most
important contributors and project leaders.  One of the advantage of
being a student is that  you can combine your learning experience at
Sugar Labs with your official school activites through intern-ships,
co-ops, work study programs, and privately sponsored contracts.

The following guidelines are intended to insure that your Sugar Lab's
experience is beneficial for you, your school, and Sugar Labs.
Working with Sugar Lab's as an intern, co-op,  or work study student
means that there is a contractual obligation between you, your school,
and Sugar Lab's.  This document represents the thoughts and
deliberations which have gone into making your experience at Sugar
Labs beneficial for you, your school, and Sugar Labs.[REPEATED TEXT]

== project description==

Experience has shown than the most important factor in having a
successful experience at Sugar Labs is your project plan.  The plan
represents the vision of what you want to accomplish and provides
roadmap for how to make that vision a reality.

Exploration, collaboration, and reflection.  Plan provides boundaries
so you can freely explore.

First big project for many students.

Done before starting program

good plan implies investment by student-investment by student results
in good mentor.

Fail to plan - Plan to fail.

The plan should include:
[CHECK LIST]
*deliverable
*learning objective

==mentor==
The second most important piece to success is your mentor.
link to community
master - apprentice

==General information==
Below is general information for filling out your school's forms.

===Overview===
Sugar Labs is organized as a member project of the Software Freedom
Conservancy[1].  The SFC is an umbrella organization which handles the
accounting work, financial management, and makes sure the activities
of Sugar Labs fit within the scope of the non-profit status.

===Mission statement===
The mission of Sugar Labs® is to produce, distribute, and support the
use of the Sugar learning platform; it is a support base and gathering
place for the community of educators and developers to create, extend,
and teach with the Sugar learning platform.

===Funding===
Sugar Labs is funded through donations from its contributing members.

===Agency Name===
Sugar Labs (A member project of the Software Freedom Conservancy)

===Agency Contact===
Bradley M. Kuhn

===Postal Address===
Software Freedom Conservancy
1995 Broadway FL 17
New York, NY 10023-5882

===Telephone===
+1-212-461-3245 tel
+1-212-580-0898 fax

===Email===
conserva...@softwarefreedom.org

===Addition information===
For additional information or forms please contact dfarn...@sugarlabs.org.
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New Activities on a.sl.o was Sugar Digest 2009-08-11

2009-09-04 Thread David Farning
Thanks,

They look great.

david

On Thu, Sep 3, 2009 at 9:27 PM, Gonzalo Odiardgodi...@gmail.com wrote:
 Caroline, i have uploaded rthe activities:

 http://activities.sugarlabs.org/es-ES/sugar/addon/4212
 http://activities.sugarlabs.org/es-ES/sugar/addon/4213
 http://activities.sugarlabs.org/es-ES/sugar/addon/4214

 Gonzalo


 On Tue, Aug 11, 2009 at 2:13 PM, Caroline Meeks solutiongr...@gmail.com
 wrote:

 ===In the community===

 3. Gonzalo Odiard reported on a successful
 [http://lists.laptop.org/pipermail/olpc-sur/2009-August/004099.html
 Sugar Day Argentina on the Sur list.] Gonzalo also describes three new
 activities: [http://190.0.162.1/godiard/sugar/Domino/6/Domino.xo], a
 game where the pieces may have different mathematical operations or
 concepts which need to match;
 [http://190.0.162.1/godiard/sugar/Ecomundo.xo], an ecosystem in which
 there is grass, rabbits and foxes that are born, eat, reproduce and
 die; and [http://190.0.162.1/godiard/sugar/Elements/2/Elements.xo], a
 proof-pof-concept of a Javascript activity.

 Will these be going onto activities.sugarlabs.org?


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


___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep


  1   2   3   4   5   6   >