Deployment Team/TODO

From Sugar Labs
< Deployment Team
Revision as of 19:15, 24 February 2010 by Cjl (talk | contribs) (moved Walter is a wanker 8/TODO to Deployment Team/TODO over redirect: revert)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

See the Community To Do list for more items that need doing.

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 or numbered list with an indented attribute list may be preferred.

  1. Facilitate communication between learners and developers. Implement ways to do so.
    priority: high champions: deployment leaders
  • 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
  • Document and complement deployment guides.

SoaS Boston Schools

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