Line 1: |
Line 1: |
| <noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude> | | <noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude> |
| {{TOCright}} | | {{TOCright}} |
− | {{Draft}} | + | {{Draft2}} |
− | =Sugar Labs Roadmap= | + | ==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 [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg05578.html 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. They following our [[Sugar Labs#Principles|principles]] and [[What is Sugar?#About the Sugar pedagogy|pedagogy]] they collaborate and 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. |
| + | |
| + | Please help us redefine our roadmap. |
| | | |
| ==Phase I== | | ==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 years. The emphasis will be 'what we share in common.' | + | 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.' |
| + | |
| + | * See this Community news post from [[Sugar Labs/Current Events/Archive/2009-03-17|10-Mar-2009, ...our '''“Big Overarching Vision Goals for 2009”''']]... |
| + | |
| + | * We will continue to refine our mission, vision, and values. They represent our public. |
| + | |
| + | * | [[What is Sugar?]] | [[Sugar Labs]] | [[Sugar Labs#Principles]] | |
| + | |
| | | |
| ==Phase II== | | ==Phase II== |
Line 25: |
Line 38: |
| 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. | | 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. |
| | | |
− | =Out of date=
| |
− |
| |
− | 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.
| |
− |
| |
− | The defining feature of the roadmap is the '''Release'''. Approximately every six months, Sugar Labs releases a updated version of the Sugar Learning Platform. Time based releases are effective methods for coordinating the efforts of loosely coupled organizations without introducing excessive amounts of managerial overhead.
| |
− |
| |
− | 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.
| |
− |
| |
− | ==Rationale==
| |
− | The Release cycle is primarily a synchronization and coordination device. It is a iterative device, as such we are not going to get it 'right' the first time.
| |
− |
| |
− | XXX clarify
| |
− | 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.
| |
− |
| |
− | The second tier of blocks are the Activities team, Translation team, Documentation team, SoaS team. These teams build on the foundation team to create an enduser user product.
| |
− |
| |
− | Support tier - Infrastructure, bug squad, deployment and education.
| |
− |
| |
− | Tie it all together - Oversight, marketing and design.
| |
− |
| |
− | ==Project Level==
| |
− |
| |
− | XXX Articulate Project level goals and targets. In general, describe how team level goal and targets affect project goals and targest
| |
− |
| |
− | == Schedule ==
| |
− |
| |
− | {| cellpadding="10" cellspacing="0" border="1"
| |
− | !Mile Stone
| |
− | !Date
| |
− | !Champion
| |
− | !Notes
| |
− | |-
| |
− | | .86 String Freeze
| |
− | | TBD
| |
− | | TBD
| |
− | | Necessary for Translators
| |
− | |-
| |
− | | .86 Design Freeze
| |
− | | TBD
| |
− | | TBD
| |
− | | Necessary for Documentors and marketer for screenshots and other visuals
| |
− | |-
| |
− | | .86 Release
| |
− | |18 Sept 2009
| |
− | |Simon
| |
− | | Necessary for downstream pickup
| |
− | |-
| |
− | |Unified SoaS release
| |
− | |TBD
| |
− | |Sebastian
| |
− | |
| |
− | |}
| |
− |
| |
− | XXX define .86 release date. In general, describe how the various team affect that schedule.
| |
− |
| |
− | XXX define SoaS release date. In general, describe how the various teams and external organizations affect that schedule.
| |
− |
| |
− | 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.
| |
− |
| |
− | XXX Link to individual team roadmaps.
| |
| | | |
| [[Category:Community]] | | [[Category:Community]] |
| [[Category:Roadmap]] | | [[Category:Roadmap]] |