Difference between revisions of "Deployment Team/Roadmap"

From Sugar Labs
Jump to navigation Jump to search
Line 3: Line 3:
 
Modified from an email from [[User:Dfarning]]:
 
Modified from an email from [[User:Dfarning]]:
  
 +
==Overview==
 
Our goal is to make Sugar and Sugar Activities “freely and readily available to learners everywhere.”
 
Our goal is to make Sugar and Sugar Activities “freely and readily available to learners everywhere.”
  
−
==Phase 1. Planning==
+
===Planning===
  
 
The first phase is planning and communicating. Sugar Labs needed to increase it's development transparency, making it easier for our partners to develop with us and build on top of the Sugar platform. Marco has been doing good work on a [[ReleaseTeam/Roadmap|release roadmap]] and establishing a release cycle.
 
The first phase is planning and communicating. Sugar Labs needed to increase it's development transparency, making it easier for our partners to develop with us and build on top of the Sugar platform. Marco has been doing good work on a [[ReleaseTeam/Roadmap|release roadmap]] and establishing a release cycle.
Line 11: Line 12:
 
This is not something that we necessarily get right on the first try but by working together, Sugar Labs, OLPC and our other partners will improve the process.
 
This is not something that we necessarily get right on the first try but by working together, Sugar Labs, OLPC and our other partners will improve the process.
  
−
==Phase 2. Packaging==
+
===Packaging===
  
 
The second phase is packaging. Sugar Labs needed to reduce the barrier to entry to test and use Sugar. Greg and his team have been getting Sugar prepared on [[Community/Distributions/Fedora]]. Jonas has been shouldering the load at [[Community/Distributions/Debian]]. Morgan, Luke and James have been getting Sugar ready to ship on [[Community/Distributions/Ubuntu]]. Aleksey has been working on [[Community/Distributions/Gentoo]].
 
The second phase is packaging. Sugar Labs needed to reduce the barrier to entry to test and use Sugar. Greg and his team have been getting Sugar prepared on [[Community/Distributions/Fedora]]. Jonas has been shouldering the load at [[Community/Distributions/Debian]]. Morgan, Luke and James have been getting Sugar ready to ship on [[Community/Distributions/Ubuntu]]. Aleksey has been working on [[Community/Distributions/Gentoo]].
Line 19: Line 20:
 
We have still have a way to go before Sugar is available on all desktops. Our next step in the packaging phase is to work on the server side
 
We have still have a way to go before Sugar is available on all desktops. Our next step in the packaging phase is to work on the server side
  
−
==Phase 3. Partnering==
+
===Partnering===
  
 
The third phase is partnering. Sugar Labs needs to partner with existing open source in education projects. Some of the most successful projects are [www.skolelinux.org SkoleLinux], a Debian based project that has had good penetration in Northern Europe. In the next few months they will be join [www.linex.org LinEx], a distribution which originated in the Extremadura region of Spain. [k12linux.org K12Linux], formally know as k12LTSP, is base on the Linux Terminal Server Project. [edubuntu.org Edubuntu] is Ubuntu's education projects.
 
The third phase is partnering. Sugar Labs needs to partner with existing open source in education projects. Some of the most successful projects are [www.skolelinux.org SkoleLinux], a Debian based project that has had good penetration in Northern Europe. In the next few months they will be join [www.linex.org LinEx], a distribution which originated in the Extremadura region of Spain. [k12linux.org K12Linux], formally know as k12LTSP, is base on the Linux Terminal Server Project. [edubuntu.org Edubuntu] is Ubuntu's education projects.
Line 27: Line 28:
 
The biggest advantage of partnering is our ability to leverage their existing marketing, customer support, and feedback processes.
 
The biggest advantage of partnering is our ability to leverage their existing marketing, customer support, and feedback processes.
  
−
==Phase 4. Placing==
+
===Placing===
  
 
The end goal is placing Sugar in front of students. Realistically, we are six-months away (as of October 2008) from non-OLPC turn-key deployments. In the meantime, we need to start developing a network of early adopters and technically proficient teachers to pull us forward.
 
The end goal is placing Sugar in front of students. Realistically, we are six-months away (as of October 2008) from non-OLPC turn-key deployments. In the meantime, we need to start developing a network of early adopters and technically proficient teachers to pull us forward.
 +
 +
==Schedule==
 +
 +
{| cellpadding="10" cellspacing="0" border="1"
 +
!Date
 +
!Task
 +
!Notes
 +
|-
 +
|2008-11-03
 +
|
 +
|
 +
|-
 +
|11-10
 +
|
 +
|
 +
|-
 +
|11-17
 +
|
 +
|
 +
|-
 +
|11-24
 +
|
 +
|
 +
|-
 +
|12-1
 +
|
 +
|
 +
|-
 +
|12-8
 +
|
 +
|
 +
|-
 +
|12-15
 +
|
 +
|
 +
|-
 +
|12-22
 +
|
 +
|Sucrose 0.83 Beta 1 (0.83.4)—Feature, API, String freeze
 +
|-
 +
|12-29
 +
|
 +
|
 +
|-
 +
|2009-01-05
 +
|
 +
|
 +
|-
 +
|01-12
 +
|
 +
|
 +
|-
 +
|01-19
 +
|
 +
|
 +
|-
 +
|01-26
 +
|
 +
|
 +
|-
 +
|02-02
 +
|
 +
|
 +
|-
 +
|02-09
 +
|
 +
|
 +
|-
 +
|02-16
 +
|
 +
|
 +
|-
 +
|02-23
 +
|
 +
|
 +
|-
 +
|03-02
 +
|
 +
| Sucrose 0.84 Tarballs Due—Hard code freeze
 +
|}

Revision as of 04:27, 28 October 2008

This article is a stub. You can help Sugar Labs by expanding it.

Modified from an email from User:Dfarning:

Overview

Our goal is to make Sugar and Sugar Activities “freely and readily available to learners everywhere.”

Planning

The first phase is planning and communicating. Sugar Labs needed to increase it's development transparency, making it easier for our partners to develop with us and build on top of the Sugar platform. Marco has been doing good work on a release roadmap and establishing a release cycle.

This is not something that we necessarily get right on the first try but by working together, Sugar Labs, OLPC and our other partners will improve the process.

Packaging

The second phase is packaging. Sugar Labs needed to reduce the barrier to entry to test and use Sugar. Greg and his team have been getting Sugar prepared on Community/Distributions/Fedora. Jonas has been shouldering the load at Community/Distributions/Debian. Morgan, Luke and James have been getting Sugar ready to ship on Community/Distributions/Ubuntu. Aleksey has been working on Community/Distributions/Gentoo.

We are a few weeks away from Fedora based liveCDs and liveUSBs. Ubuntu will follow when some Abiword version issues are resolved.

We have still have a way to go before Sugar is available on all desktops. Our next step in the packaging phase is to work on the server side

Partnering

The third phase is partnering. Sugar Labs needs to partner with existing open source in education projects. Some of the most successful projects are [www.skolelinux.org SkoleLinux], a Debian based project that has had good penetration in Northern Europe. In the next few months they will be join [www.linex.org LinEx], a distribution which originated in the Extremadura region of Spain. [k12linux.org K12Linux], formally know as k12LTSP, is base on the Linux Terminal Server Project. [edubuntu.org Edubuntu] is Ubuntu's education projects.

There are many other project that are either regionally based, distribution based, or hardware based.

The biggest advantage of partnering is our ability to leverage their existing marketing, customer support, and feedback processes.

Placing

The end goal is placing Sugar in front of students. Realistically, we are six-months away (as of October 2008) from non-OLPC turn-key deployments. In the meantime, we need to start developing a network of early adopters and technically proficient teachers to pull us forward.

Schedule

Date Task Notes
2008-11-03
11-10
11-17
11-24
12-1
12-8
12-15
12-22 Sucrose 0.83 Beta 1 (0.83.4)—Feature, API, String freeze
12-29
2009-01-05
01-12
01-19
01-26
02-02
02-09
02-16
02-23
03-02 Sucrose 0.84 Tarballs Due—Hard code freeze
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Deployment_Team/Roadmap&oldid=9843"