1,286
edits
Changes
mLine 182:
Line 182: − +
→What is next for Sugar?
We have several near-term opportunities that we should leverage:
We have several near-term opportunities that we should leverage:
* Raspian: The Raspberry Pi 3 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO-4 hardware, though not the OLPC NL3 hardware. While Raspberry Pi is not the only platform we should be targeting, it does has broad penetration into the Maker community, which shares a synergy with our emphasis on “doing”. It is low-hanging fruit. With a little polish we could have an image available for download from the Raspberry Pi website.
* Raspian: The Raspberry Pi 3 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO-4 hardware, though not the OLPC NL3 hardware. While Raspberry Pi is not the only platform we should be targeting, it does have broad penetration into the Maker community, which shares a synergy with our emphasis on “doing”. It is low-hanging fruit. With a little polish we could have an image available for download from the Raspberry Pi website.
* Trisquel: We have the potential for better leveraging the Free Software Foundation as a vehicle for promoting Sugar. Their distro of choice is Trisquel and the maintainer does a great job of keep the Sugar packages up to date.
* Trisquel: We have the potential for better leveraging the Free Software Foundation as a vehicle for promoting Sugar. Their distro of choice is Trisquel and the maintainer does a great job of keep the Sugar packages up to date.
* Sugarizer: The advantage of Sugarizer is that it has the potential of reaching orders of magnitude more users since it is web-based and runs in Android and iOS. There is some work to be done to make the experience palatable on small screens and the current development environment is—at least my opinion—not scalable or maintainable. The former is a formidable problem. The latter quite easy to address.
* Sugarizer: The advantage of Sugarizer is that it has the potential of reaching orders of magnitude more users since it is web-based and runs in Android and iOS. There is some work to be done to make the experience palatable on small screens and the current development environment is—at least my opinion—not scalable or maintainable. The former is a formidable problem. The latter quite easy to address.