Difference between revisions of "Sugar Labs/Roadmap"

From Sugar Labs
Jump to navigation Jump to search
m (add rational draft)
m (update template)
 
(12 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
+
<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
{{TOCright}}
+
{{Draft}}
=Sugar Labs Roadmap=
+
==Introduction==
 +
A Roadmap is a plan made up of phases.
  
The Sugar Labs Roadmap provides a system for all of the individuals and organizations who develop and deploy the Sugar Learning Platform to coordinate their schedules and work flows.
+
With the evolution of Sugar Labs comes the need to reflect and plan the future. See this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg05578.html call to task].
  
The defining feature of the roadmap is the '''Release'''Approximately every six months, Sugar Labs releases a updated version of the Sugar Learning PlatformTime based releases are effective methods for coordinating the efforts of loosely coupled organizations without introducing excessive amounts of managerial overhead.
+
Some Sugar Labs members like to quote Alan Kay, "The best way to predict the future is to invent it."  Sugar Labs has emulated some of the best practices of the most successful free and open source software projects. We should continue to refine those principles. Sugar and Sugar Labs is also more than free and open source software. Many people are enamored with the project because it envisions a new generation of learners with powerful new tools.  Sugar Labs depends on volunteers&mdash;people who want to invent the future&mdash;who love to engage in authentic activities—activities that help fulfill the potentials they individually see in Sugar's visionSuch contributors formulate personal roadmaps to build out a vision they are most passionate about. Then, following our [[Sugar Labs#Principles|principles]] and [[What is Sugar?#About the Sugar pedagogy|pedagogy]], they collaborate and [[Discovery|discover]] new [[:Category:Idea|ideas]] and methods for fulfilling a vision. [[:Category:Roadmap|Team roadmaps]] develop and get fulfilled.  They also reflect on what they've learned and take time to refine their plans.
  
Release dates up to and including .86 have been determined by the development team.  Starting with .88, the release schedule will be determined by the Sugar Labs oversight board.
+
Please help us redefine our roadmap.
  
==Rational==
+
==Phase I==
The Release cycle is primarily a synchronization and coordination deviceIt is a iterative device, as such we are not going to get it 'right' the first time.
+
Focus on Mission, Vision, and ValuesThis is a pretty high-level discussion which builds on top of similar work we did last year.  The emphasis will be 'what we share in common.'
  
XXX clarify
+
* See this Community news post from [[Archive/Current Events/2009-03-17|10-Mar-2009, ...our '''“Big Overarching Vision Goals for 2009”''']]...
Currently, the primary release cycle driver is the development team. This is not because the development team is most import. It is because it was, and continues to be, a foundation block of the project.  Now, it is time to add marketing to the foundation.
+
* And this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg05676.html post on Vision and Mission].
  
The second tier of blocks are the Activities team, Translation team, Documentation team, SoaS teamThese teams build on the foundation team to create an enduser user product.
+
* We will continue to refine our mission, vision, and valuesThey represent our public.
  
Support tier - Infrastructure, bug squad, deployment and  education.
+
* | [[What is Sugar?]] | [[Sugar Labs]] | [[Sugar Labs#Principles]] |
  
Tie it all together - Oversight, marketing and design.
 
  
==Project Level==
+
==Phase II==
 +
How we get there?
 +
* Building capacity - Building product
 +
*: See this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg05656.html discussion thread] on building engineering capacity.
 +
* Innovation - Implementation
 +
* Supply side - Demand side
 +
* Education - Technology
 +
* Internal - External
  
XXX Articulate Project level goals and targets.  In general, describe how team level goal and targets affect project goals and targest
+
The emphasis will be on what trade offs and compromises are required given our current and near term resources and how do we leverage our strengths while minimize our weaknesses.
  
== Schedule ==
+
==Phase III==
XXX define .86 release date.  In general, describe how the various team affect that schedule.
+
Iterative process between:
 +
* Personal Roadmaps
 +
* Team Roadmaps
 +
* Project Roadmaps
  
XXX define SoaS release date. In general, describe how the various teams and external organizations affect that schedule.
+
The emphasis will be on setting personal, team, and project level goals to make Phase I happen while considering the constraints identified in phase II.
  
XXX anything important enough to be listed on this scheudal is important enough to have an assigned champion to insure that it happens on time.
 
 
{| cellpadding="10" cellspacing="0" border="1"
 
!Date
 
!Topic
 
!Task
 
!Notes
 
|-
 
|31 Oct 2008
 
|Distribution
 
|Sugar 0.82 in Ubuntu 8.10
 
|
 
|-
 
|31 Oct 2008
 
|Distribution
 
|Sugar in Fedora
 
|See http://sdz.fedorapeople.org/olpc/sugar-spin.iso
 
|-
 
|31 Oct 2008
 
|Infrastucture
 
|Move email hosting to Gmail
 
|
 
|}
 
 
XXX Link to individual team roadmaps.
 
  
 
[[Category:Community]]
 
[[Category:Community]]
 
[[Category:Roadmap]]
 
[[Category:Roadmap]]

Latest revision as of 15:15, 16 July 2011

Community Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Events Calendar

Pencil.png NOTICE:  This page is a draft in active flux...
Please contribute to these contents and discuss issues on the discussion page.


Introduction

A Roadmap is a plan made up of phases.

With the evolution of Sugar Labs comes the need to reflect and plan the future. See this call to task.

Some Sugar Labs members like to quote Alan Kay, "The best way to predict the future is to invent it." Sugar Labs has emulated some of the best practices of the most successful free and open source software projects. We should continue to refine those principles. Sugar and Sugar Labs is also more than free and open source software. Many people are enamored with the project because it envisions a new generation of learners with powerful new tools. Sugar Labs depends on volunteers—people who want to invent the future—who love to engage in authentic activities—activities that help fulfill the potentials they individually see in Sugar's vision. Such contributors formulate personal roadmaps to build out a vision they are most passionate about. Then, following our principles and pedagogy, they collaborate and discover new ideas and methods for fulfilling a vision. Team roadmaps develop and get fulfilled. They also reflect on what they've learned and take time to refine their plans.

Please help us redefine our roadmap.

Phase I

Focus on Mission, Vision, and Values. This is a pretty high-level discussion which builds on top of similar work we did last year. The emphasis will be 'what we share in common.'

  • We will continue to refine our mission, vision, and values. They represent our public.


Phase II

How we get there?

  • Building capacity - Building product
    See this discussion thread on building engineering capacity.
  • Innovation - Implementation
  • Supply side - Demand side
  • Education - Technology
  • Internal - External

The emphasis will be on what trade offs and compromises are required given our current and near term resources and how do we leverage our strengths while minimize our weaknesses.

Phase III

Iterative process between:

  • Personal Roadmaps
  • Team Roadmaps
  • Project Roadmaps

The emphasis will be on setting personal, team, and project level goals to make Phase I happen while considering the constraints identified in phase II.