https://wiki.sugarlabs.org/api.php?action=feedcontributions&feedformat=atom&user=MariahnoelleSugar Labs - User contributions [en]2026-05-13T21:32:46ZUser contributionsMediaWiki 1.43.0https://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001542017 Goals2017-04-12T20:08:03Z<p>Mariahnoelle: /* Maintain and promote various related stand-alone projects that supports free/libre learning and Constructionist Learning */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: Enhance user experience for Sugarizer Apps<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Enhance App offering||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Actively recruit and maintain developers for Sugarizer<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Make the platform easier for developers to contribute||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Maintain and promote various related stand-alone projects that supports free/libre and Constructionist Learning====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Maintain development and documentation of Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Quarterly updates/pruning on the documentation for Music Blocks and Turtle Art ||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: Support individuals at the high school and college level with financial incentives, more importantly mentorship.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Participate as an organization in Google Summer of Code||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|Participate as an organization in Google Code-in||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Provide funding to individuals to create and/or maintain ongoing projects in their given communities.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001532017 Goals2017-04-12T20:07:46Z<p>Mariahnoelle: /* Maintain and promote various related stand-alone projects */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: Enhance user experience for Sugarizer Apps<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Enhance App offering||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Actively recruit and maintain developers for Sugarizer<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Make the platform easier for developers to contribute||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Maintain and promote various related stand-alone projects that supports free/libre learning and Constructionist Learning====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Maintain development and documentation of Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Quarterly updates/pruning on the documentation for Music Blocks and Turtle Art ||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: Support individuals at the high school and college level with financial incentives, more importantly mentorship.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Participate as an organization in Google Summer of Code||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|Participate as an organization in Google Code-in||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Provide funding to individuals to create and/or maintain ongoing projects in their given communities.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001522017 Goals2017-04-12T20:06:08Z<p>Mariahnoelle: /* Maintain and promote various related stand-alone projects */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: Enhance user experience for Sugarizer Apps<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Enhance App offering||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Actively recruit and maintain developers for Sugarizer<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Make the platform easier for developers to contribute||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Maintain development and documentation of Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Quarterly updates/pruning on the documentation for Music Blocks and Turtle Art ||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: Support individuals at the high school and college level with financial incentives, more importantly mentorship.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Participate as an organization in Google Summer of Code||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|Participate as an organization in Google Code-in||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Provide funding to individuals to create and/or maintain ongoing projects in their given communities.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001512017 Goals2017-04-12T20:04:48Z<p>Mariahnoelle: /* Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible. */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: Enhance user experience for Sugarizer Apps<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Enhance App offering||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Actively recruit and maintain developers for Sugarizer<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Make the platform easier for developers to contribute||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Maintain development and documentation of Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: Support individuals at the high school and college level with financial incentives, more importantly mentorship.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Participate as an organization in Google Summer of Code||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|Participate as an organization in Google Code-in||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Provide funding to individuals to create and/or maintain ongoing projects in their given communities.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001502017 Goals2017-04-12T20:02:20Z<p>Mariahnoelle: /* To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission. */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Maintain development and documentation of Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: Support individuals at the high school and college level with financial incentives, more importantly mentorship.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Participate as an organization in Google Summer of Code||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|Participate as an organization in Google Code-in||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Provide funding to individuals to create and/or maintain ongoing projects in their given communities.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001492017 Goals2017-04-12T19:58:56Z<p>Mariahnoelle: /* Maintain and promote various related stand-alone projects */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Maintain development and documentation of Music Blocks and Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001482017 Goals2017-04-12T19:57:46Z<p>Mariahnoelle: /* Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education. */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education<br />
||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??<br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Increase awareness of learners and learning communities for Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001472017 Goals2017-04-12T19:57:01Z<p>Mariahnoelle: /* Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education. */</p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||??||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education|| Needs a volunteer|| ??|| ??||?<br />
|-<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??||? <br />
|-<br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??||? <br />
|-<br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??||?<br />
|-<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??||? <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Increase awareness of learners and learning communities for Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001462017 Goals2017-04-12T19:55:48Z<p>Mariahnoelle: </p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work the the distributors of those platforms to promote F/L tools for education.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Work with Trisquel||??||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education|| Needs a volunteer|| ??|| ??||?<br />
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??||? <br />
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??||? <br />
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??||?<br />
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??||? <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Increase awareness of learners and learning communities for Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Increase awareness of learners and learning communities for Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001452017 Goals2017-04-12T19:37:19Z<p>Mariahnoelle: </p>
<hr />
<div>__NOTOC__<br />
[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]<br />
<br />
See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Current Sugar Labs Mission Statement===<br />
Sugar Labs<sup>®</sup> is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.<br />
<br />
===Vision===<br />
<br />
Text to be defined.<br />
<br />
__TOC__<br />
<br />
<br />
{{toclimit|limit=1}}<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n = inability to share.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001382017 Goals2017-04-11T23:22:45Z<p>Mariahnoelle: /* Example templates for guidance */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started on April 9th.]<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001372017 Goals2017-04-11T23:19:11Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started on April 9th.]<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.===<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001362017 Goals2017-04-11T23:18:29Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.===<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001352017 Goals2017-04-11T23:16:21Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Example templates for guidance===<br />
* Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.===<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001342017 Goals2017-04-11T23:15:19Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
===Goal:A broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.====<br />
* Objective: Expected achievements that are well-defined, specific, measurable, and derived from the goal(s).<br />
* Action: Efforts conducted to achieve the objectives.<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001332017 Goals2017-04-11T23:11:47Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001322017 Goals2017-04-11T23:11:17Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where it is not possible to have reliable internet service.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001312017 Goals2017-04-11T23:10:03Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects====<br />
* Objective: Music Blocks<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective: Turtle Art<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use where it is not possible to have reliable internet service.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are secure and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001302017 Goals2017-04-11T23:07:42Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are safe and our systems are distributed.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
* Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001292017 Goals2017-04-11T23:06:22Z<p>Mariahnoelle: /* Sugar Labs Stated Goals: */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
====Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include====<br />
# Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
====Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.====<br />
# Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.====<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.====<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.====<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To make sure our servers are safe and our systems are distributed.====<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
====To maintain domains and trademarks.====<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001282017 Goals2017-04-11T23:04:02Z<p>Mariahnoelle: /* Sugar Labs Stated Goals: */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
* Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
* Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* To make sure our servers are safe and our systems are distributed.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
* To maintain domains and trademarks.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001272017 Goals2017-04-11T23:03:09Z<p>Mariahnoelle: /* Sugar Labs Stated Goals: */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# To make sure our servers are safe and our systems are distributed.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# To maintain domains and trademarks.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Objective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001262017 Goals2017-04-11T23:02:08Z<p>Mariahnoelle: /* Sugar Labs Stated Goals: */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# To make sure our servers are safe and our systems are distributed.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
# To maintain domains and trademarks.<br />
## Objective: <br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
## Obective:<br />
::::{| class="wikitable"<br />
|-<br />
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<u>Can someone take what is listed on [http://wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001252017 Goals2017-04-11T22:56:38Z<p>Mariahnoelle: /* Sugar Labs Stated Goals: */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: not be limited to Raspbian and Trisquel.<br />
{| class="wikitable"<br />
|-<br />
! Action Name !! Action Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|}<br />
<br />
<br />
## Objective:<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective:<br />
##Objective:<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective:<br />
##Objective:<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective:<br />
##Objective:<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective:<br />
##Objective:<br />
# To make sure our servers are safe and our systems are distributed.<br />
## Objective:<br />
##Objective:<br />
# To maintain domains and trademarks.<br />
## Objective:<br />
##Objective:<br />
<br />
<u>Can someone take what is listed on [wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001242017 Goals2017-04-11T22:55:53Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: not be limited to Raspbian and Trisquel.<br />
{| class="wikitable"<br />
|-! Action Name !! Action Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed <br />
|-<br />
|Examples||Example|| Examples|| Example|| Example||Example <br />
|-<br />
|| | | | | | <br />
|-<br />
|| | | | | | <br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
! Header C1 !! Header C2 !! Header C3<br />
|-<br />
| R1C1 || R1C2 || R1C3<br />
|-<br />
| R2C1 || R2C2 || R2C3<br />
|}<br />
<br />
## Objective:<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective:<br />
##Objective:<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective:<br />
##Objective:<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective:<br />
##Objective:<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective:<br />
##Objective:<br />
# To make sure our servers are safe and our systems are distributed.<br />
## Objective:<br />
##Objective:<br />
# To maintain domains and trademarks.<br />
## Objective:<br />
##Objective:<br />
<br />
<u>Can someone take what is listed on [wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001232017 Goals2017-04-11T22:52:13Z<p>Mariahnoelle: /* Sugar Labs Stated Goals: */</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: not be limited to Raspbian and Trisquel.<br />
{| class="wikitable" ! Action Name ! Action Description ! Resources ! Committee/Volunteer ! Date Started ! Date Completed |<br />
|Examples|Example| Examples| Example| Example|Example |<br />
|- | | | | | | <br />
|- | | | | | | <br />
|}<br />
<br />
## Objective:<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective:<br />
##Objective:<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective:<br />
##Objective:<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective:<br />
##Objective:<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective:<br />
##Objective:<br />
# To make sure our servers are safe and our systems are distributed.<br />
## Objective:<br />
##Objective:<br />
# To maintain domains and trademarks.<br />
## Objective:<br />
##Objective:<br />
<br />
<u>Can someone take what is listed on [wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001222017 Goals2017-04-11T22:46:44Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
# Sugar Labs Mission and Vision<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
## Objective: not be limited to Raspbian and Trisquel.<br />
### {| class="wikitable" !Action Name !Action Description !Resources !Committee/Volunteer !Date Started !Date Completed |- | | | | | | |- | | | | | | |- | | | | | | |}<br />
## Objective:<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
## Objective:<br />
##Objective:<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
## Objective:<br />
##Objective:<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
## Objective:<br />
##Objective:<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
## Objective:<br />
##Objective:<br />
# To make sure our servers are safe and our systems are distributed.<br />
## Objective:<br />
##Objective:<br />
# To maintain domains and trademarks.<br />
## Objective:<br />
##Objective:<br />
<br />
<u>Can someone take what is listed on [wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
<br />
<br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001212017 Goals2017-04-11T22:40:04Z<p>Mariahnoelle: </p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
# Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include<br />
*Objective 1: not be limited to Raspbian and Trisquel.<br />
<br />
# Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
*Objective 1:<br />
*Objective 2:<br />
<br />
<br />
# Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
*Objective 1:<br />
*Objective 2:<br />
<br />
# Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
*Objective 1:<br />
*Objective 2:<br />
<br />
# To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
*Objective 1:<br />
*Objective 2:<br />
<br />
# To make sure our servers are safe and our systems are distributed.<br />
*Objective 1:<br />
*Objective 2:<br />
<br />
# To maintain domains and trademarks.<br />
*Objective 1:<br />
*Objective 2:<br />
<br />
<br />
<u>Can someone take what is listed on [wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
<br />
<br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=2017_Goals&diff=1001202017 Goals2017-04-11T22:35:08Z<p>Mariahnoelle: Created page with "[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th. ==Sugar Labs Mission and Vision== ===Sugar Labs Mission Statement:==..."</p>
<hr />
<div>[This is a draft based on proposals made on the IAEP email thread started by Walter Bender on April 9th.<br />
<br />
==Sugar Labs Mission and Vision==<br />
<br />
===Sugar Labs Mission Statement:===<br />
The mission of Sugar Labs is to reach global learners (and educators) with powerful free and open source educational tools to help them to engage in Constructionist learning.<br />
<br />
===Vision===<br />
<br />
==2017 Sugar Labs Goals, Objectives & Actions==<br />
<br />
===Sugar Labs Stated Goals:===<br />
#Develop, distribute, and maintain Sugar as free and open source software for a variety of platforms to include, but not be limited to Raspbian and Trisquel.<br />
<br />
#Develop, distribute, and maintain a variety of Sugarizer Apps and installations as a free and open source educational tool available for as many devices as possible.<br />
<br />
#Maintain and promote various related stand-alone projects such as Music Blocks and Turtle Art Days where appropriate.<br />
<br />
#Develop, distribute and maintain a series of school server versions for use in areas where, for one reason or another, it is not possible to have reliable internet service.<br />
<br />
#To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.<br />
<br />
#To make sure our servers are safe and our systems are distributed.<br />
<br />
#To maintain domains and trademarks.<br />
<br />
<br />
<u>Can someone take what is listed on [wiki.sugarlabs.org/go/2016_Goals 2016 Goals] and plug them into the goals, objectives and actions on this page for the year?</u><br />
<br />
<br />
<br />
<br />
==Current and historical context to guide the goals, objectives and actions listed above==<br />
<br />
===What is Sugar Labs?===<br />
<br />
Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.<br />
<br />
At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.<br />
<br />
Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC XO hardware.<br />
<br />
===Who develops Sugar?===<br />
<br />
Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)<br />
<br />
===Who uses Sugar?===<br />
<br />
Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC XO hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.<br />
<br />
===Who supports Sugar?===<br />
<br />
When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?<br />
<br />
===What is next for Sugar?===<br />
<br />
We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.<br />
<br />
We have several near-term opportunities that we should leverage:<br />
* Raspian: The Raspberry PI 3.0 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO 4.0 hardware. While RPi 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 RPi website.<br />
* 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.<br />
* 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.<br />
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.<br />
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.<br />
<br />
===Specific actions===<br />
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=Google_Code_In_2015&diff=96313Google Code In 20152015-12-02T19:55:52Z<p>Mariahnoelle: /* Collaboration */</p>
<hr />
<div><noinclude>[[Category:Trac Reference]][[Category:Idea]]<br />
[[Category: GCI2015]]</noinclude><br />
<br />
[[File:Gci-sugarlabs-2015.png]]<br />
<br />
This is the project page for the Sugar Labs application to [http://www.google-melange.com/gci/homepage/google/gci2015 Google Code In 2015]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the first week of November 2015.<br />
<br />
== Message to potential participants ==<br />
<br />
It is important that you obtain permission of your parents.<br />
<br />
Es importante que obtengas el permiso de tus padres para participar.<br />
<br />
https://developers.google.com/open-source/gci/resources/contest-rules<br />
<br />
Please see the Contest Rules for Eligibility and Registration process.<br />
<br />
https://developers.google.com/open-source/gci/resources/contest-rules<br />
<br />
'''Details regarding the required forms and paperwork are here: [[Google Code In 2015/Participate#Students]].'''<br />
<br />
Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/<br />
<br />
Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org<br />
<br />
== Why we are participating ==<br />
<br />
Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.<br />
<br />
== Some background from GCI ==<br />
<br />
[See https://developers.google.com/open-source/gci/resources/getting-started]<br />
<br />
===Open Source Fundamentals ===<br />
<br />
You can contribute without being a coder!<br />
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:<br />
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.<br />
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.<br />
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.<br />
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.<br />
;User Interface: User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.<br />
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.<br />
=== Collaboration===<br />
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.<br />
<br />
=== Quality over Quantity === <br />
<br />
It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.<br />
<br />
== Some basics about Sugar Labs ==<br />
<br />
For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].<br />
<br />
=== Getting started with coding ===<br />
<br />
Sugar development is in either Python or Javascript.<br />
<br />
* You will need knowledge of Python and GTK (See http://python-gtk-3-tutorial.readthedocs.org/en/latest/);<br />
* or Javascript/HTML5;<br />
* and then the basic of Sugar development (See http://www.flossmanuals.net/make-your-own-sugar-activities/);<br />
* and to have a Sugar development environment running (See http://developer.sugarlabs.org).<br />
<br />
Please note that you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.<br />
<br />
=== Getting started with GIT ===<br />
<br />
Some knowledge of git is important as your work will be submitted to our git repository (https://github.com/sugarlabs). The basic mechanism is a pull request (PR), which is detailed in [http://developer.sugarlabs.org/contributing.md.html].<br />
<br />
GitHub provides a tutorial (See https://try.github.io/levels/1/challenges/1), although there are many others as well.<br />
<br />
Note that our bug tracker is http:bugs.sugarlabs.org.<br />
<br />
=== Getting started with Sugarizer === <br />
<br />
Sugar Web Framework is the JavaScript Framework for Sugar [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md]. Sugarizer [http://sugarizer.org] is a subset of Sugar that allow runing activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.<br />
<br />
<!-- Begin comment out this section<br />
<br />
== Tasks ==<br />
'''Note:''' This is our preliminary list of tasks. We can add more as the contest progresses.<br />
<br />
Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task.<br />
<br />
Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]].<br />
<br />
===Beginner Tasks===<br />
We have several tasks that are targeting people new to Sugar and Sugar development. You are only allowed to complete two beginner tasks.<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Title !! Description !! Hours !! Mentor !! Tag<br />
|-<br />
|Install the Sugar development environment||Following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner<br />
|-<br />
|Install Sugar in a virtual machine||If your intention is to focus on documentation and training or outreach, then you may want to install Sugar in a virtual machine. Following the instructions at [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Tutorials][http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Virtual_machines][http://wiki.sugarlabs.org/go/Downloads#Virtual_Machines_on_all_platforms], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner<br />
|-<br />
|Create an example program in Turtle Blocks||We distribute examples with the Turtle Blocks programming environment. Create your example -- some art, some geometry, some multimedia, a simple game -- to be included with the package. Deliverable is a Turtle Blocks project file to be reviewed by Sugar Labs designers and educators. (Use either the Python version bundled with Sugar or the Javascript version at [http://turtle.sugarlabs.org Turtle Blocks JS]) One source of inspiration might be [https://www.pinterest.com/walterbender/turtle-art/]. || 48 || all || beginner<br />
|-<br />
|Create an example program in Music Blocks||We distribute examples with the [http://walterbender.github.io/musicblocks Music Blocks] programming environment. Create your example -- some music (and art) -- to be included with the package. Deliverable is a Music Blocks project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner<br />
|-<br />
|Create a simple machine in Physics||We distribute examples with the [http://activities.sugarlabs.org/en-US/sugar/addon/4193 Physics Activity]. Create a simple machine we can include in the examples collection -- some interesting mechanical device. Deliverable is a Physics activity project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner<br />
|}<br />
<br />
===Documentation/Training===<br />
Tasks related to creating/editing documents and helping others learn more<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Title !! Description !! Hours !! Mentor !! Tag<br />
|-<br />
|Update the Sugar Labs entry in Wikipedia|| The Sugar Labs entry in Wikipedia could use some TLC. Please bring it up to date. || 48 || Walter || Documentation<br />
|-<br />
|Update the Sugar Labs wiki page on git||The [[Activity Team/Git Tutorial]] is out of date: we have migrated to GitHub. Please update the page to reflect the GitHub workflow. See http://developer.sugarlabs.org/contributing.md.html for more details || 48 || Walter || Documentation<br />
|-<br />
|Turtle Blocks Programming Guide 1|| Add live examples missing from the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks]. || 48 || Walter || Documentation<br />
|-<br />
|Turtle Blocks Programming Guide 2|| Extend the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks] to include more examples. || 48 || Walter || Documentation<br />
|-<br />
|Music Blocks Programming Guide|| Extend the [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide to Programming with Music Blocks] to include more examples. || 48 || Walter || Documentation<br />
|-<br />
|Turtle Blocks Classroom Guide||Write a guide on how to use Turtle Blocks in the classroom -- a manual for teachers who might want to engage in programming. Please consult with a classroom teacher when creating the guide.|| 96 || Walter || Documentation<br />
|-<br />
|Music Blocks Classroom Guide||Write a guide on how to use Music Blocks in the classroom -- a manual for teachers who might want to engage in programming with Music. Please consult with a music teacher when creating the guide.|| 96 || Walter || Documentation<br />
|-<br />
|Sugarizer Server API Documentation||Write a documentation for the REST API for Sugarizer Server. Include some GET/POST/DELETE sample inside || 48|| Lionel || Documentation<br />
|-<br />
|Sugarizer Server Collaboration Tutorial||Write a tutorial on how to connect a Sugarizer Client to a Sugarizer Server and how to use it to do Journal sharing and collaboration || 24 || Lionel || Documentation<br />
|-<br />
|Sugarizer wiki page||Write a Sugarizer page in the SugarLabs wiki || 24 || Lionel || Documentation<br />
|}<br />
<br />
For information about how to create help pages for activities <br />
<br />
http://wiki.sugarlabs.org/go/Activities/Help/Contribute<br />
<br />
https://github.com/godiard/help-activity/blob/master/source/restructuredtext.rst<br />
<br />
https://github.com/godiard/help-activity/blob/master/source/collaborating.rst<br />
<br />
===Outreach/Research===<br />
Tasks related to community management, outreach/marketing, or studying problems and recommending solutions<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Title !! Description !! Hours !! Mentor !! Tag<br />
|-<br />
|Turtle Art Day||Organize a Turtle Art Day in your community. Details at [http://people.sugarlabs.org/walter/Guia_Ingles_10-08-2013.pdf]||96||Walter||Outreach<br />
|-<br />
|Promo Video||Create a 60 second promotional video on Sugar and its community.||96||Mariah||Outreach<br />
|-<br />
|Hangout Q&A||Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. Invite friends, family, peers, as well as academic and community leaders.||96||Mariah||Outreach<br />
|-<br />
|Local Lab Wiki||Create/update a "Local Lab" page for your area/country. Fill in the page with information on the Sugar community in your area. This could include contact information, mailing lists, events and any other information that may be relevant. ||96||Mariah||Research<br />
|-<br />
|How-To Guide||Create a guide for how to host your own DIY Sugar on a Stick party. The guide should include at least two promotional item designs (like a sticker, brochure, flyer). Feel free to change the name to something else. ||96||Mariah||Outreach<br />
|-<br />
|DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. Then, hold a workshop on the basics of using Sugar. Take pictures to document the experience. Post a blog about it.||96||Mariah||Outreach<br />
|-<br />
|Potential Users||Gather information on who could benefit from using or knowing about Sugar. Look at non-profit organizations, academic institutions, the home-school community. Build a database including contact information, website URLS, social media profiles, and any other relevant information.||96||Mariah||Research<br />
|-<br />
|Sugar Tools & Resources||Find the resources that people are using throughout the world to learn about or teach Sugar Activities. This can include manuals, teacher guides, YouTube videos, blogs, etc. Document what type of resource it is, the URL for the resource, the target audience of the resource and whether it is up-to-date.||96||Mariah||Research<br />
|-<br />
|Introduce Yourself||Write a blog post about why you are participating in Google Code-In, what you hope to learn from the GCI and how Sugar Labs can help you. Include a picture. Share blog post through social media.||48||Mariah||Outreach<br />
|-<br />
|Interview a GCI Peer||Interview another Sugar Labs GCI participant. Ask them questions about how they are selecting/completing tasks, any successes/struggles they are having, etc. Post on participant blog. Share blog post through social media.||48||Mariah||Outreach<br />
|--<br />
|Interview an Educator||Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. Post about it on the blog, include a picture. Share the blog post through social media and with the educator.||48||Mariah||Outreach|<br />
|-<br />
|Review an Activity||Write a review about an Activity in Sugar. Explain how you use it, what kind of project you could do with it, any bugs it might have, etc. Post your review. The review can be a video review or a written review with screenshots. Share the blog post through social media.||48||Mariah||Outreach<br />
|-<br />
|Women in the Sugar Community||Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. Write a blog post about what you learned when making this presentation and include a link to the presentation.||48||Mariah||Outreach<br />
|-<br />
|Wrap-Up||Write a blog post about your experience as a GCI participant for Sugar Labs. Share your thoughts on what was successful and what can be improved for next year's participants. Feel free to include pictures, videos, links to work that you are most proud of. Share the post through social media.||48||Mariah||Outreach<br />
|-<br />
|Analyze and optimize the Sugar Labs wiki performance.|| The main documentation for the Sugar Labs organization is placed in the Sugar Labs wiki. Speeding up the wiki access is important for the community. Analyze and optimize our wiki using Google PageSpeed Tools. Get a score of 85 or above for the Sugar Labs wiki. [https://developers.google.com/speed/ Google PageSpeed] || 144 || Bernie || Research, QA<br />
|-<br />
|New mailing list for Sugar Labs|| In Sugar Labs, as most open source organizations, we use mailing lists to communicate with one another. Currently, we are using mailman 2. Make some research, for example among other open source organizations, to propose at least one new open source package to deploy a new mailing list for Sugar Labs. Implement the chosen software using Docker containers. || 144 || Bernie || Research<br />
|-<br />
|High availability in our Docker infrastructure || In Sugar Labs, mainly we use Virtual Machines and Docker containers to host our main services. We want you to test the Docker Swarm functionality in order to create a Docker cluster. For this task, you will have two clean Ubuntu VMs in order to install and configure the Docker Swarm. We will provide you also two Docker images. In order to complete the task, the docker cluster and the failover functionality must be working. || 144 || Bernie || Research<br />
|}<br />
<br />
===User Interface===<br />
Tasks related to user experience research or user interface design and interaction<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Title !! Description !! Hours !! Mentor !! Tag<br />
|-<br />
|Icon design for Music Blocks||The icons used for the main toolbar in Music Block don't "sing" to me. This task is to design better icons both in terms of expressing the intention of the button and visual engagement of the user. || 72 || Walter, Devin || UI, design<br />
|-<br />
|Save file design for Music Blocks||Since Music Blocks programs don't always create artwork, when you save the project, there may be no corresponding image to associate with it. This task is to design a default graphic to use in such cases. || 72 || Walter, Devin || UI, design<br />
|-<br />
|Classroom collaboration|| Sugar provides tools for sharing and collaborating among students, e.g., peer editing of texts, chat, group programming, etc. Survey the list of collaboration-enabled activities and categorize them by whether they are learning utilities, classroom management utilities, communication, games, etc. || 72 || Walter || UI, pedagogy<br />
|-<br />
|Classroom management 1|| Sugar provides only a few tools for classroom management, e.g., the Share With Teacher webservice. Survey classroom services that run either as web services or native in desktop environments.|| 72 || Walter || UI, pedagogy<br />
|-<br />
|Classroom management 2|| Sugar provides only a few tools for classroom management, e.g., the Share With Teacher webservice. Which of the results from the Classroom management 1 task would be useful to incorporate into the Sugar ecosystem? Evaluation should include s description of the service and a sketch of how the user interaction would work. || 72 || Walter || UI, pedagogy<br />
|-<br />
|Sugar on a small screen|| Sugar was originally designed as a desktop environment for small computers. But these days, many children have access to smart phones rather than computers. This task is to make some sketches as to how Sugar might be redesigned for a smart phone form-factor. A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI<br />
|-<br />
|Programming on a small screen|| We put an emphasis on programming in Sugar. One popular programming environment is Turtle Blocks. Recently we made a Javascript version that can run in a browser (and hence on a smart phone). How should the UI change to accommodate that form-factor? A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI<br />
|-<br />
|End-user customization||We try to encourage our users to re-imagine Sugar as they'd like it. Users can change the icon layout, the background screen, and the XO avatar. What else should be made easier to customize with minimal programming? || 72 || Walter || UI<br />
|-<br />
|Sugarizer marketing web page||Create a marketing web page to explain what is Sugarizer and replace the [http://sugarizer.org current one] || 40 || Lionel || UI<br />
|}<br />
<br />
===Quality Assurance===<br />
Tasks related to testing and ensuring code is of high quality.<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Title !! Description !! Hours !! Mentor !! Tag<br />
|-<br />
|Behavior diff for Turtle Blocks JS|| [https://turtle.sugarlabs.org Turtle Blocks JS] is a Javascript port from the Python version of the activity. The goal of this task is to document any differences in behavior between the two versions.||72||Walter||QA<br />
|-<br />
|Unit tests for JS activities||We have no unit tests for our Javascript activities. This task is to investigate approaches to unit testing in Javascript||72||Walter||QA<br />
|-<br />
|Test Sugar on a Stick || Help test the latest Sugar on a Stick on Fedora (F21). See [http://dl.fedoraproject.org/pub/alt/stage/21_Beta_RC4/], [https://fedoraproject.org/wiki/Test_Results:Fedora_21_Beta_RC4_Desktop#Sugar_.28non-blocking.2C_all_arches.29] #fedora-qa (freenode IRC). Deliverable is a report of the major Sugar features, e.g., desktop, journal, collaboration, and the core activities, e.g., Write, Browse, Turtle, Chat, Speak, etc. || 48 || Satellit || QA, SoaS<br />
|-<br />
|Interview a teacher|| Ultimately the quality of our work is determined by our end users. Interview a classroom teacher who is using Sugar and solicit feedback about what works, what doesn't. || 72 || Walter || QA<br />
|-<br />
|Interview a student|| Ultimately the quality of our work is determined by our end users. Interview a student who is using Sugar in school and solicit feedback about what works, what doesn't. || 72 || Walter || QA<br />
|}<br />
<br />
===Code===<br />
Tasks related to writing or refactoring code<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Title !! Description !! Hours !! Mentor !! Tag<br />
|-<br />
| Sugar Bug 3921 Journal palette is not updated|| [https://bugs.sugarlabs.org/ticket/3921 Ticket 3921] Journal palette is not updated when I stay in the same column || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 4172 Set color of insensitive buttons || [https://bugs.sugarlabs.org/ticket/4172 Ticket 4172] The greyed-out "Next" button on the intro screen comes up with the text in the same colour as the background, i.e. you cant see it. || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 4461 "Volume busy" dialog appear in Sugar || [https://bugs.sugarlabs.org/ticket/4461 Ticket 4461] Trying to unmount a pendrive, a "Volume is busy" dialog appear. || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 4613 Neighborhood view should respect max_participants limit || [https://bugs.sugarlabs.org/ticket/4613 Ticket 4613] max_participants should limit the number of joiners. If the maximum has been reached, joining should be disabled and some feedback given to the user. It would also be nice if the icon indicated (with a badge, perhaps) the maximum. || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 4894 Frame settings edge delay || [https://bugs.sugarlabs.org/ticket/4894 Ticket 4894] Frame settings doesn't allow option other that edge delay = 0 || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 381 Neighborhood view improvements || [https://bugs.sugarlabs.org/ticket/381 Ticket 381] Right now the neighborhood view is disappointingly random. Neighborhood view icons should be placed in a spatially repeatable way. || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 2478 Buttons unresponsive when launching Sugar || [https://bugs.sugarlabs.org/ticket/2478 Ticket 2478] Buttons unresponsive when launching Sugar until Journal appears on Home View || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 3006 Ad-hoc network icon mixup || [https://bugs.sugarlabs.org/ticket/3006 Ticket 3006] Ad-hoc network icons are not properly displayed at times|| 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 3119 Check if the connection has been established || [https://bugs.sugarlabs.org/ticket/3119 Ticket 3119] Check if the connection has been established || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 3143 Remove icon-slicer dependency || [https://bugs.sugarlabs.org/ticket/3143 Ticket 3143] icon-slicer is not needed. || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 3708 Sugar doesn't DHCP connecting to ad-hoc wifi point || [https://bugs.sugarlabs.org/ticket/3708 Ticket 3708] Add DHCP support for ad hoc networks || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 3831 Frame animation has regressed || [https://bugs.sugarlabs.org/ticket/3831 Ticket 3831] It is not smooth. || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 4449 Language names are not translated || [https://bugs.sugarlabs.org/ticket/4449 Ticket 4449] "Spanish" and other language names are not translated in My Settings language section || 72 || Martin Abente || Code, Python<br />
|-<br />
| Sugar Bug 4693 Send to friend not working || [https://bugs.sugarlabs.org/ticket/4693 Ticket 4693] This feature only works intermittently || 72 || Martin Abente || Code, Python<br />
|-<br />
| Collaboration refactoring in Story || The [https://github.com/walterbender/story Story] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Story. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Turtle Blocks || The [https://github.com/walterbender/turtleart Turtle Blocks] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Turtle Blocks. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Portfolio || The [https://github.com/walterbender/portfolio Portfolio] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Portfolio. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Reflect || The [https://github.com/walterbender/reflect Reflect] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Reflect. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Physics || The [https://github.com/walterbender/physics Physics] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Physics. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Sugar Chess || The [https://github.com/walterbender/sugarchess Sugar Chess] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Sugar Chess. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Paths || The [https://github.com/walterbender/paths Paths] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Paths. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Erikos || The [https://github.com/walterbender/erikos Erikos] (AKA Simon) activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Erikos. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Fraction Bounce || The [https://github.com/walterbender/fractionbounce Fraction Bounce] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to Fraction Bounce. || 72 || Walter || Code, Python<br />
|-<br />
| Collaboration refactoring in Teacher Share || The [https://github.com/walterbender/teachershare Teacher Share] activity supports collaboration through a Telepathy Tube Channel, which is deprecated. We have ported the [https://github.com/walterbender/dimensions Dimensions activity] (which also used Tubes) to use a [https://github.com/walterbender/dimensions/commits/text-channel Text Channel], which is still supported. This task is apply a similar patch to TeacherShare. || 72 || Walter || Code, Python<br />
|-<br />
| Turtle Confusion in Javascript || [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] presents 40 shape challenges to the learner that must be completed using basic Logo-blocks. The challenges as based on Barry Newell's 1988 book, Turtle Confusion: Logo Puzzles and Riddles. This task is to implement Turtle Confusion within the framework of the [http://turtle.sugarlabs.org JavaScript version of Turtle Blocks].|| 72 || Walter || Code, JavaScript<br />
|-<br />
| Turtle Blocks JS: Loudness block doesn't work on Windows || [[https://github.com/walterbender/turtleblocksjs/issues/238] Issue 238 || 72 || Walter, Amit || Code, JavaScript<br />
|-<br />
| Turtle Blocks JS: Cannot import images on Android || [[https://github.com/walterbender/turtleblocksjs/issues/237] Issue 237 || 72 || Walter, Amit || Code, JavaScript<br />
|-<br />
| Turtle Blocks JS: Camera doesn't work on Android || [[https://github.com/walterbender/turtleblocksjs/issues/236] Issue 236 || 72 || Walter, Amit || Code, JavaScript<br />
|-<br />
| Turtle Blocks JS: Sometimes long press puts menu in wrong place. || [[https://github.com/walterbender/turtleblocksjs/issues/235] Issue 235 || 72 || Walter, Amit || Code, JavaScript<br />
|-<br />
| Turtle Blocks JS: Polar coordinate grid not centered under some circumstances. || [[https://github.com/walterbender/turtleblocksjs/issues/234] Issue 234 || 72 || Walter, Amit || Code, JavaScript<br />
|-<br />
| Turtle Blocks JS: Text rotation not saved properly in SVG output || [[https://github.com/walterbender/turtleblocksjs/issues/233] Issue 233 || 72 || Walter, Amit || Code, JavaScript<br />
|-<br />
| Music Blocks: Accent (Articulation) || [https://github.com/walterbender/musicblocks/issues/72 Issue 72] Articulation is a clamp block and affects all notes contained within. || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: matrix blocks don't load in collapsed state || [https://github.com/walterbender/musicblocks/issues/76 Issue 76] The matrix blocks can collapse (like start and action blocks) but the collapse state does not preserve when saving/loading project files. || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Staccato || [https://github.com/walterbender/musicblocks/issues/71 Issue 71] Staccato is a clamp block and affects all notes contained within || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Lilypond CHORDS bug || [https://github.com/walterbender/musicblocks/issues/70 Issue 70] Currently no Rhythmic Value generated for Chords || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Firefox clicking || When running Music Blocks in Firefox, there is a clicking sound with the notes. Some bug in how we are using Tone.js? This task is to track down the problem and fix it. || 72 || Walter, Devin || Code, Javascript<br />
|-<br />
| Music Blocks: Rhythmic Dot bug || [https://github.com/walterbender/musicblocks/issues/69 Issue 69] Dot is Calculating Rhythmic Values Incorrectly || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Matrix style 2 || [https://github.com/walterbender/musicblocks/issues/68 Issue 68] We need a "Sticky" First Column for the Matrix || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Matrix style 1 || [https://github.com/walterbender/musicblocks/issues/67 Issue 67] Columns are not Spacing Correctly in Matrix || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Repeat Block bug || [https://github.com/walterbender/musicblocks/issues/66 Issue 66] Repeat is creating parsing problem for TUPLETS in Matrix Generation || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: missing chunks || [https://github.com/walterbender/musicblocks/issues/65 Issue 65] Chunks sometimes do not show up in Palette || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks: Lilypond TUPLET bug 2 || [https://github.com/walterbender/musicblocks/issues/64 Issue 64] Scaling issue || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Lilypond TUPLET bug 1 || [https://github.com/walterbender/musicblocks/issues/63 Issue 63] Calculating sixteenth note triplets (and greater?) as "3/4" || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Play Backwards Feature || [https://github.com/walterbender/musicblocks/issues/58 Issue 58] describes a new feature: play the notes backward. || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Export Matrix as HTML file Feature || [https://github.com/walterbender/musicblocks/issues/57 Issue 57] describes a new feature: export the note selection matrix as HTML. || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Matrix highlight Bug || [https://github.com/walterbender/musicblocks/issues/56 Issue 56] describes a bug regarding highlighting the matrix || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Lilypond output || [https://github.com/walterbender/musicblocks/issues/55 Issue 55] More Robust Aggregation for LilyPond output design || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Parsing voices || [https://github.com/walterbender/musicblocks/issues/53 Issue 53] Enhancement to Lilypond output: parsing voices when note values are simultaneous || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Default Tempo enhancement || [https://github.com/walterbender/musicblocks/issues/52 Issue 52] Reset tempo on clear || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Android || [https://github.com/walterbender/musicblocks/issues/51 Issue 51] does Tonejs work on Android? is there an alternative? || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Lilypond Save Button || [https://github.com/walterbender/musicblocks/issues/50 Issue 50] Save to Lilypond button design enhancement || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks timing drifts || [https://github.com/walterbender/musicblocks/issues/49 Issue 49] We need a realtime clock || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Planet graphics || [https://github.com/walterbender/musicblocks/issues/44 Issue 44] Add some graphic for the planet upload/download || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Safari download || [https://github.com/walterbender/musicblocks/issues/37 Issue 37] Safari does not "download" the .tb files, it just opens a new window with the code in it. || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks block highlighting is inconsistent || [https://github.com/walterbender/musicblocks/issues/32 Issue 32] Notes stay lit up during debug mode. || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Invert Pitches Feature || [https://github.com/walterbender/musicblocks/issues/30 Issue 30] Invert pitches clamp based on pitch interval|| 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Skip Feature || [https://github.com/walterbender/musicblocks/issues/29 Issue 29] Play every nth note enhancement || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Transposition by Ratio || [https://github.com/walterbender/musicblocks/issues/28 Issue 28] Transposition by Ratio || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Block Matrix enhancements || [https://github.com/walterbender/musicblocks/issues/27 Issue 27] User Interaction for Matrix Improvement design enhancement || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks playback notes slowly || [https://github.com/walterbender/musicblocks/issues/22 Issue 22] Add slow playback step-by-step mode|| 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Synth selection || [https://github.com/walterbender/musicblocks/issues/19 Issue 19] Add support for voices/instruments/synths || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Build Newton's color scheme demo || [https://github.com/walterbender/musicblocks/issues/17 Issue 17] Program a demo of Newton's Color/Music dualilty|| 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Volume enhancement || [https://github.com/walterbender/musicblocks/issues/15 Issue 15] Make volume logarithmic || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Music Blocks Restore matrix || [https://github.com/walterbender/musicblocks/issues/13 Issue 13] Restore selected blocks in Matrix || 72 || Walter, Devin || Code, JavaScript<br />
|-<br />
| Add collaboration to LOL Game || [http://activities.sugarlabs.org/en/sugar/addon/4717 LOL Game] is a small sample of JavaScript activities in Sugar-Web, add Sugarizer presence API to play the game with two player || 40 || Lionel || Code, JavaScript<br />
|-<br />
| Write a Munin plugin to monitor network resource usage on Docker containers.||In Sugar Labs, we use Docker container to host important services. Monitoring the resource usage is critical for the infrastructure health. We have written a Munin plugin to monitor CPU and memory usage on Docker containers. The next step is to monitor the network usage on our Docker containers. This tasks requires writing a Munin plugin, preferably in Perl, for monitoring network resource usage on Docker containers. [https://docs.docker.com/articles/runmetrics/ Docker runtime metrics] [https://github.com/scanterog/munin-plugin-docker Git Repo] || 144 || Bernie || Coding<br />
|}<br />
<br />
End of commented out section --><br />
<br />
<!--<br />
== Unsorted tasks ==<br />
=== Sugar enhancements from bugs.sugarlabs.org ===<br />
Each of these open tickets is potential task-worthy.<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Ticket !! Description !! Type !! Component<br />
|-<br />
| [http://bugs.sugarlabs.org/ticket/1646 1646] || No way to force-close (kill) an activity || enhancement || Sugar<br />
|}<br />
<br />
=== Sugar bugs from bugs.sugarlabs.org ===<br />
Each of these open tickets is potential task-worthy.<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Ticket !! Description !! Type !! Component<br />
|-<br />
| [http://bugs.sugarlabs.org/ticket/4307 4307] || clipboard.set_with_data/set_with_owner is not introspectable || defect || Sugar<br />
|}<br />
<br />
=== Activity enhancements from bugs.sugarlabs.org ===<br />
Each of these open tickets is potential task-worthy.<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
!Ticket !! Description !! Component<br />
|-<br />
| [http://bugs.sugarlabs.org/ticket/758 758] || Port to new tube API || Read<br />
|}<br />
--><br />
<br />
== Mentors ==<br />
;NOTES TO MENTORS:<br />
:Please refer to [[Google Code In 2015/Participate#Mentors]] for details regarding enrolling as a mentor.<br />
:Please add yourself to the list below.<br />
:Feel free to add new tasks to the table above.<br />
<br />
Depending on the project, we will assign multiple mentors from our various development and support teams.<br />
<br />
* Walter Bender - also org admin for GCI<br />
* Sam Parkinson (student volunteer)<br />
* Ignacio Rodriguez (student volunteer)<br />
* German Ruiz<br />
* Amit Kumar Jha<br />
* Martin Abente<br />
* Mariah Noelle Villarreal<br />
* Gary Servin Cardozo<br />
* Rajul Srivastava<br />
* Julio Daniel Reyes<br />
* Arturo Volpe<br />
* Lionel Laské<br />
* Bernie Innocenti<br />
* Devin Ulibarri</div>Mariahnoellehttps://wiki.sugarlabs.org/index.php?title=User:Mariahnoelle&diff=96312User:Mariahnoelle2015-12-02T19:31:38Z<p>Mariahnoelle: Created page with "I am passionate about education liberties and freedoms. I want to expose more people to free and open educational resources. One way I do this is by advocating for free softwa..."</p>
<hr />
<div>I am passionate about education liberties and freedoms. I want to expose more people to free and open educational resources. One way I do this is by advocating for free software use in the classroom and after-school programs in the U.S. I have done this in San Antonio, TX, Davenport, IA and now Boston, MA. Sugar is a prime example of free education software. My involvement with Sugar Labs and free software in education began when I conducted a small qualitative research project in Montevideo, Uruguay on the communication between educators, developers, and stakeholders on the Plan Ceibal OLPC implementation. Since then, I have organized a Turtle Day in San Antonio in conjunction with Open Ed Jam (www.openedjam.org), facilitated after-school and summer programs using almost exclusively free software including Sugar and Turtle, as well as helped out here and there with outreach efforts.<br />
<br />
== Google Code-in ==<br />
[[File:Gci-sugarlabs-2015.png|thumb|left|100px| GCI 2015 Flyer]] I'm mentoring again for Google Code-in because it was such a blast last year! I plan to be more involved this year with new task ideas and by giving better, timely feedback to the students. I hope to learn more about the students and their backgrounds as they share their progress through the outreach/research tasks. Hopefully, having the posts and documentation will add to the community and This year I designed a little flyer that can be shared on social media to help spread the word about our involvement with the contest. Check it out and please share it with appropriate organizations or schools with which you may be affiliated! <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Sugar Board 2015 Proposal ==<br />
Coming soon!</div>Mariahnoelle