I had a quick chat with Michaël about moving forward with this GSoC project
where he mentioned that the impact of the project should be discussed with the
Impact of the Sugarizer School Box
An instructor walks into a classroom, equipped with a Raspberry Pi 3 or Zero W
with a pre-installed version of the proposed Sugarizer School Box distribution
that Sugar Labs will be working on.
He/she simply connects the Pi to a power supply and instantly, a local WiFi
network is set up, a Sugarizer server session starts automatically and they’re
ready to go!
Students can log in to the WiFi AP made by the Pi and visit sugarizer.org (any
other fixed url) on their local tablets/laptops/phones. So any computer
connected to this WiFi can use the Sugarizer client and any tablet/phone with
Sugarizer apps will benefit from the collaboration and backup features on the
server. All of these student devices will be served by the Pi Wifi AP.
We’ll have to see how the Pi’s can cope with the load of serving multiple
students along with the overhead of running a browser session for a client and
the connected display.
I have a Raspberry Pi B+ and a Pi Zero W at my disposal that I can use to test
this so I’ll post the results of combining sugarizer-server and a WiFi AP soon.
It should do the job as we will not be having too many students on one Pi.
It's a straightforward process to set up a local AP for the Pi with the
sugarizer-server running but if there is a need for Internet connectivity, then
we'll have to set up an Ethernet bridge to make this possible which is also not
The setup process in a classroom should ideally just be connecting the Pi to a
Minor UX features like an auto-redirect to sugarizer.org after connecting to
the WiFi AP can be implemented.
If anyone from the community has any opinions or concerns about how any part of
the School Box experience should be, then that’d be awesome.
Sugar-devel mailing list