SlideShare a Scribd company logo
   
Sugar : An Educational Desktop
( And absolutely not an OS, at least not right now)
Vamsi Krishna D
   
A brief history
   
OLPC: How it should have been
● VISION: To create educational
opportunities for the world's poorest
children by providing each child with a
rugged, low-cost, low-power, connected
laptop with content and software designed
for collaborative, joyful, self-empowered
learning.
● Motive: Education is part of the solution
to every problem facing the next
generation. While we can not solve
problems for them, we can give them
tools so that they can become a generation
of problem solvers.
● UNITS SOLD:
● 250,000 April 24, 2009 India (not
confirmed yet)
● 200,000 June 2008 Uruguay
● 260,000 December 1, 2007 Peru
● Support from leading companies such as
Google, Marvell and AMD.
   
The end, a beginningSugar Labs: The now makers of the Desktop.
● Mr Negroponte felt OLPC should be more
structured and took a few enterprises as an
example.
● A Split from the parent OLPC almost an year
back, due to these changing motives of OLPC.
● W. Bender Feared the GPL nature of Sugar
would be lost.
● Wanted to expand to different platforms.
● Learning should not be closed.
● SL founded by Walter Bender, the man behind
the development of the interface.
● Huge number of contributors from various
Orgs and educational institutions.
   
Why Sugar?
● As said by the founder himself:
● " (1) Sugar is designed to meet the needs of
young children learning― it puts an emphasis
on guided discovery, collaboration, and
reflection. It is not just a repackaging of an
1970s-inspired office desktop.
● (2) Sugar is built on free and open software
because learning requires more than just access
to knowledge--it also requires the ability to
appropriate knowledge and put it to use. Sugar
encourages and facilitates such appropriation
through mechanisms such as "view source."
● (3) Sugar is designed to run on small, old, slow
machines,it can breath new life into existing in
hardware."
   
The mechanisms
   
Python: the answer?
● To be easily hacked on.
● To be user/coder friendly.
A Desktop?
● Can focus more on innovation
● Distro maintainers worry about distribution.
   
The Architecture
● Is made up of components
● 1) Shell: How the user interacts with
Sugar
Two components:
Frame and Home View.
● 2) Activities: Also known as
applications in other envs.
● 3) Shell service : provides backend
services like, activity registry etc.
● 4) Journal: safe house to store
information pertaining activities and
user.
   
● 5) Datastore service: Services which
let Activities effectively maintain their
data.
● 6) Presence service: A way for
activities to be shared over a network.
● 7) Activity API : Provides means to
write new Activities
   
The Future
   
Prescient are we not?
● Community boom.
● Organization restructuring itself.
● Lack of expected user base.
● To become a distro or to remain an upstream
Desktop?

More Related Content

Similar to Introduction to Sugar

One Laptop Per Child (OLPC) KLUG Presentation
One Laptop Per Child (OLPC) KLUG PresentationOne Laptop Per Child (OLPC) KLUG Presentation
One Laptop Per Child (OLPC) KLUG Presentation
Jose de Leon
 
TTL2REPORT.pptx
TTL2REPORT.pptxTTL2REPORT.pptx
TTL2REPORT.pptx
ErickaVico1
 
BICS Tech Plan PAC Presentation
BICS Tech Plan PAC PresentationBICS Tech Plan PAC Presentation
BICS Tech Plan PAC Presentation
slater_45
 
Campkde 2010: KDE Plasma netbook
Campkde 2010: KDE Plasma netbookCampkde 2010: KDE Plasma netbook
Campkde 2010: KDE Plasma netbook
Marco Martin
 
Google it strategy
Google it strategyGoogle it strategy
Google it strategy
Tuan Nguyen
 
Gdsc IIIT Surat Orientation 2022.pdf
Gdsc IIIT Surat Orientation 2022.pdfGdsc IIIT Surat Orientation 2022.pdf
Gdsc IIIT Surat Orientation 2022.pdf
SparshJhariya2
 
From the South: building together a high-tech ecosystem
From the South: building together a high-tech ecosystemFrom the South: building together a high-tech ecosystem
From the South: building together a high-tech ecosystem
Nicolás Erdödy
 
The Future of Cloud Computing: Google Apps
The Future of Cloud Computing: Google AppsThe Future of Cloud Computing: Google Apps
The Future of Cloud Computing: Google Apps
Grove Group
 
Makerspace @uncg libraries presentation for LIS688 (june 2014)
Makerspace @uncg libraries presentation for LIS688 (june 2014)Makerspace @uncg libraries presentation for LIS688 (june 2014)
Makerspace @uncg libraries presentation for LIS688 (june 2014)
UNCG University Libraries
 
DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)
DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)
DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)
DrupalCape
 
We Need to Talk: How Communication Helps Code
We Need to Talk: How Communication Helps CodeWe Need to Talk: How Communication Helps Code
We Need to Talk: How Communication Helps Code
Docker, Inc.
 
Tools to help and engage emerging open source communities towards development...
Tools to help and engage emerging open source communities towards development...Tools to help and engage emerging open source communities towards development...
Tools to help and engage emerging open source communities towards development...
Jose Astrain
 
Learningbloks
LearningbloksLearningbloks
Learningbloks
Alex Monegro
 
Introduction to iPads in Middle School
Introduction to iPads in Middle SchoolIntroduction to iPads in Middle School
Introduction to iPads in Middle School
Gary Toews
 
The Story of Project Sputnik - Client to cloud solution
The Story of Project Sputnik - Client to cloud solutionThe Story of Project Sputnik - Client to cloud solution
The Story of Project Sputnik - Client to cloud solution
Barton George
 
ICT4D course 2013 - Sugar
ICT4D course 2013 - SugarICT4D course 2013 - Sugar
ICT4D course 2013 - Sugar
Christophe Guéret
 
Designing & delivering e learning in a multi device world
Designing & delivering e learning in a multi device worldDesigning & delivering e learning in a multi device world
Designing & delivering e learning in a multi device world
Leo Gaggl
 
GDSC_Introduction.pptx
GDSC_Introduction.pptxGDSC_Introduction.pptx
GDSC_Introduction.pptx
SachinMishra53046
 
Accessibility & Universal Design
Accessibility & Universal DesignAccessibility & Universal Design
Accessibility & Universal Design
SrutiVijaykumar
 
OLPC Great Wide Open
OLPC Great Wide OpenOLPC Great Wide Open
OLPC Great Wide Open
kymrohman
 

Similar to Introduction to Sugar (20)

One Laptop Per Child (OLPC) KLUG Presentation
One Laptop Per Child (OLPC) KLUG PresentationOne Laptop Per Child (OLPC) KLUG Presentation
One Laptop Per Child (OLPC) KLUG Presentation
 
TTL2REPORT.pptx
TTL2REPORT.pptxTTL2REPORT.pptx
TTL2REPORT.pptx
 
BICS Tech Plan PAC Presentation
BICS Tech Plan PAC PresentationBICS Tech Plan PAC Presentation
BICS Tech Plan PAC Presentation
 
Campkde 2010: KDE Plasma netbook
Campkde 2010: KDE Plasma netbookCampkde 2010: KDE Plasma netbook
Campkde 2010: KDE Plasma netbook
 
Google it strategy
Google it strategyGoogle it strategy
Google it strategy
 
Gdsc IIIT Surat Orientation 2022.pdf
Gdsc IIIT Surat Orientation 2022.pdfGdsc IIIT Surat Orientation 2022.pdf
Gdsc IIIT Surat Orientation 2022.pdf
 
From the South: building together a high-tech ecosystem
From the South: building together a high-tech ecosystemFrom the South: building together a high-tech ecosystem
From the South: building together a high-tech ecosystem
 
The Future of Cloud Computing: Google Apps
The Future of Cloud Computing: Google AppsThe Future of Cloud Computing: Google Apps
The Future of Cloud Computing: Google Apps
 
Makerspace @uncg libraries presentation for LIS688 (june 2014)
Makerspace @uncg libraries presentation for LIS688 (june 2014)Makerspace @uncg libraries presentation for LIS688 (june 2014)
Makerspace @uncg libraries presentation for LIS688 (june 2014)
 
DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)
DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)
DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)
 
We Need to Talk: How Communication Helps Code
We Need to Talk: How Communication Helps CodeWe Need to Talk: How Communication Helps Code
We Need to Talk: How Communication Helps Code
 
Tools to help and engage emerging open source communities towards development...
Tools to help and engage emerging open source communities towards development...Tools to help and engage emerging open source communities towards development...
Tools to help and engage emerging open source communities towards development...
 
Learningbloks
LearningbloksLearningbloks
Learningbloks
 
Introduction to iPads in Middle School
Introduction to iPads in Middle SchoolIntroduction to iPads in Middle School
Introduction to iPads in Middle School
 
The Story of Project Sputnik - Client to cloud solution
The Story of Project Sputnik - Client to cloud solutionThe Story of Project Sputnik - Client to cloud solution
The Story of Project Sputnik - Client to cloud solution
 
ICT4D course 2013 - Sugar
ICT4D course 2013 - SugarICT4D course 2013 - Sugar
ICT4D course 2013 - Sugar
 
Designing & delivering e learning in a multi device world
Designing & delivering e learning in a multi device worldDesigning & delivering e learning in a multi device world
Designing & delivering e learning in a multi device world
 
GDSC_Introduction.pptx
GDSC_Introduction.pptxGDSC_Introduction.pptx
GDSC_Introduction.pptx
 
Accessibility & Universal Design
Accessibility & Universal DesignAccessibility & Universal Design
Accessibility & Universal Design
 
OLPC Great Wide Open
OLPC Great Wide OpenOLPC Great Wide Open
OLPC Great Wide Open
 

Introduction to Sugar

  • 1.     Sugar : An Educational Desktop ( And absolutely not an OS, at least not right now) Vamsi Krishna D
  • 3.     OLPC: How it should have been ● VISION: To create educational opportunities for the world's poorest children by providing each child with a rugged, low-cost, low-power, connected laptop with content and software designed for collaborative, joyful, self-empowered learning. ● Motive: Education is part of the solution to every problem facing the next generation. While we can not solve problems for them, we can give them tools so that they can become a generation of problem solvers. ● UNITS SOLD: ● 250,000 April 24, 2009 India (not confirmed yet) ● 200,000 June 2008 Uruguay ● 260,000 December 1, 2007 Peru ● Support from leading companies such as Google, Marvell and AMD.
  • 4.     The end, a beginningSugar Labs: The now makers of the Desktop. ● Mr Negroponte felt OLPC should be more structured and took a few enterprises as an example. ● A Split from the parent OLPC almost an year back, due to these changing motives of OLPC. ● W. Bender Feared the GPL nature of Sugar would be lost. ● Wanted to expand to different platforms. ● Learning should not be closed. ● SL founded by Walter Bender, the man behind the development of the interface. ● Huge number of contributors from various Orgs and educational institutions.
  • 5.     Why Sugar? ● As said by the founder himself: ● " (1) Sugar is designed to meet the needs of young children learning― it puts an emphasis on guided discovery, collaboration, and reflection. It is not just a repackaging of an 1970s-inspired office desktop. ● (2) Sugar is built on free and open software because learning requires more than just access to knowledge--it also requires the ability to appropriate knowledge and put it to use. Sugar encourages and facilitates such appropriation through mechanisms such as "view source." ● (3) Sugar is designed to run on small, old, slow machines,it can breath new life into existing in hardware."
  • 7.     Python: the answer? ● To be easily hacked on. ● To be user/coder friendly. A Desktop? ● Can focus more on innovation ● Distro maintainers worry about distribution.
  • 8.     The Architecture ● Is made up of components ● 1) Shell: How the user interacts with Sugar Two components: Frame and Home View. ● 2) Activities: Also known as applications in other envs. ● 3) Shell service : provides backend services like, activity registry etc. ● 4) Journal: safe house to store information pertaining activities and user.
  • 9.     ● 5) Datastore service: Services which let Activities effectively maintain their data. ● 6) Presence service: A way for activities to be shared over a network. ● 7) Activity API : Provides means to write new Activities
  • 11.     Prescient are we not? ● Community boom. ● Organization restructuring itself. ● Lack of expected user base. ● To become a distro or to remain an upstream Desktop?