Goals/2018 Submissions: Difference between revisions

Newer edit →

Revision as of 20:41, 6 July 2018

Operational
- Maintain in working order the Sugar desktop and a core set of Sugar activities against the two popular and always changing Linux distributions; Fedora and Debian.
- Maintainable mechanism for handling activities (port to new ASLO and migration of relevant wiki pages to activity README.md files in activity git repo)
- Maintain infrastructure services for contributors; such as Wiki, web site, GitHub organisation, IRC channel, and shell server.
- Ensure all Python code is migrated to Python3
- Improve Migration of Wiki to git project
- A Possible Stable version for Sugar Desktop Outside Linux (Mac OSX / Windows)

Outreach
- Introduce a Music Blocks programme in India (Outreach)
- Establish connection with Sugar Labs deployments (Outreach)
- Turtle/Music Blocks workshops in Nigeria, India, and Japan (Outreach)
- Outreach to Maker community

Community Building
- Maintain an active community of learners creating pedagogic contents for Sugar/Sugarizer
- Maintain an active community of developers for Sugar/Sugarizer
- Alignment of Sugar Labs with educational institutions. Identify the gaps and build approaches to fill those gaps.

Internal Organizational Improvements
- Fully staff all boards, offices, and committees
- Improve trust within Oversight Board by meeting face to face, by teleconference, and by enabling and guaranteeing the right to private deliberation by the board
- Improve communication within and across SLOB and Community.
- Devise a means to compensate, and thus incentivize, developers

Future-Looking
- Develop a better Activity for creating Activities, with features from Bret Victor's essays, such as https://atom.io/packages/hydrogen
- Set up a matrix of VirtualBox prebuilt Sugar VMs, perhaps in partnership with Oracle
- Teachers Guide for Sugar/Sugarizer (make Sugar easier to use)
- Pre-preared (language and keyboard layout) Virtual Machines with Sugar
- Changing UI/UX layout of Sugar and working on colors
- Develop guides describing how Sugar can support Common Criteria and other semi-mandated teaching curriculums
- Competitive & SWOT (Strengths/Weaknesses/Opportunities/Threats) analyses of Sugar
- Integrating a means for students or children to work together in accomplishing a goals
- A rubric for in-person events for collaboration and advocacy. This would act like a "formula" for organizing effective "sugarcamps"
- A portfolio approach to what a potential consumer of Sugar may look for
- Work on describing a vision for Sugar Labs

@@ Line 1: / Line 1: @@
 * Operational
 ** Maintain in working order the Sugar desktop and a core set of Sugar activities against the two popular and always changing Linux distributions; Fedora and Debian.
 ** Maintainable mechanism for handling activities (port to new ASLO and migration of relevant wiki pages to activity README.md files in activity git repo)
@@ Line 8: / Line 7: @@
 ** Improve Migration of Wiki to git project
 ** A Possible Stable version for Sugar Desktop Outside Linux (Mac OSX / Windows)
 *Outreach
@@ Line 16: / Line 13: @@
 ** Turtle/Music Blocks workshops in Nigeria, India, and Japan (Outreach)
 ** Outreach to Maker community
 * Community Building
 ** Maintain an active community of learners creating pedagogic contents for Sugar/Sugarizer
 ** Maintain an active community of developers for Sugar/Sugarizer
+** Alignment of Sugar Labs with educational institutions. Identify the gaps and build approaches to fill those gaps.
 * Internal Organizational Improvements
 ** Fully staff all boards, offices, and committees
-** Improve trust within Oversight Board by meeting face to face, by teleconference, and by enabling and guaranteeing the right to private deliberation by the board.
+** Improve trust within Oversight Board by meeting face to face, by teleconference, and by enabling and guaranteeing the right to private deliberation by the board
+** Improve communication within and across SLOB and Community.
 ** Devise a means to compensate, and thus incentivize, developers
+* Future-Looking
+** Develop a better Activity for creating Activities, with features from Bret Victor's essays, such as https://atom.io/packages/hydrogen
+** Set up a matrix of VirtualBox prebuilt Sugar VMs, perhaps in partnership with Oracle
+** Teachers Guide for Sugar/Sugarizer (make Sugar easier to use)
+** Pre-preared (language and keyboard layout) Virtual Machines with Sugar
+** Changing UI/UX layout of Sugar and working on colors
+** Develop guides describing how Sugar can support Common Criteria and other semi-mandated teaching curriculums
+** Competitive & SWOT (Strengths/Weaknesses/Opportunities/Threats) analyses of Sugar
+** Integrating a means for students or children to work together in accomplishing a goals
+** A rubric for in-person events for collaboration and advocacy. This would act like a "formula" for organizing effective "sugarcamps"
+** A portfolio approach to what a potential consumer of Sugar may look for
+** Work on describing a vision for Sugar Labs