Difference between revisions of "Deployment Team/TODO"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | <noinclude>{{ GoogleTrans-en | + | <noinclude>{{ GoogleTrans-en}}{{TeamHeader|Deployment Team}}</noinclude>{{TOCright}} |
| + | ==General== | ||
| + | Deployments are encouraged to report or link here their needs for features, services, assistance from the Sugar Labs community. | ||
| + | A wiki table may be used, or for ease of editing, a bulleted list with an indented attribute list may be preferred. | ||
| + | |||
| + | * <strike>Schedule byweekly meetings and announce then on IAEP/Sugar.</strike> | ||
| + | :: biweekly meetings are in the shared calendar | ||
| + | * Determine Regional Sugar labs governance. | ||
| + | ** Create a set of principles | ||
| + | ** Create a strawman business model | ||
| + | * Facilitate communication between learners and developers. Implement ways to do so. | ||
| + | *: '''priority:''' high '''champions:''' deployment leaders | ||
| + | *: '''Edit a wiki section.''' | ||
| + | * Document and complement deployment guides. | ||
| + | |||
| + | ==SoaS Boston Schools== | ||
| + | * See also [[Sugar on a Stick/TODO]] | ||
=== Active Tasks === | === Active Tasks === | ||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
| Line 54: | Line 70: | ||
|} | |} | ||
| − | === | + | == Deployment X == |
| − | + | ||
| − | + | == Deployment Y == | |
| − | + | ||
| − | + | == Deployment Z == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''See''' the [[Sugar Labs/TODO|Community To Do list]] for more items that need doing. | '''See''' the [[Sugar Labs/TODO|Community To Do list]] for more items that need doing. | ||
Revision as of 23:37, 28 July 2009
General
Deployments are encouraged to report or link here their needs for features, services, assistance from the Sugar Labs community.
A wiki table may be used, or for ease of editing, a bulleted list with an indented attribute list may be preferred.
Schedule byweekly meetings and announce then on IAEP/Sugar.
- biweekly meetings are in the shared calendar
- Determine Regional Sugar labs governance.
- Create a set of principles
- Create a strawman business model
- Facilitate communication between learners and developers. Implement ways to do so.
- priority: high champions: deployment leaders
- Edit a wiki section.
- Document and complement deployment guides.
SoaS Boston Schools
- See also Sugar on a Stick/TODO
Active Tasks
| Task | Owner | Priority | Next Milestone | Notes |
|---|---|---|---|---|
| One pager for internal use at Gardner | Caroline | High | Draft is started | |
Requested Tasks
| Task | Owner | Priority | Next Milestone | Notes |
|---|---|---|---|---|
| Easy Install for Mac emulation of Sugar | Help Wanted! | High | Ticket #114 All Gardner teachers have Macbooks. We need to make it easy for them to install and try out Sugar. | |
| Collaborate to improve professional development resources | Caroline&Sebastian | Medium | Work out hiring and tasking an HGSE Intern and find out what other stakeholders should be involved | |
Deployment X
Deployment Y
Deployment Z
See the Community To Do list for more items that need doing.