Infrastructure Team/TODO

From Sugar Labs
< Infrastructure Team
Revision as of 18:26, 5 December 2008 by Dfarning (talk | contribs) (add task tables)
Jump to navigation Jump to search

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

Active Tasks

Task Owner Priority Next Milestone Notes

Requested Tasks

Task Owner Priority Next Milestone Notes

Completed Tasks

Task Owner Priority Completion Date Notes

Backups

We are considering a couple of possibilities:

  • MIT provides a backup service for a few bucks per machine per month via Tivoli
  • Harvard Computer Society filer

Shell accounts

Setup workload will be distributed between the sysadmins and a few members of the core team.

General

  • CMS to host a few, nice looking, official pages.
  • git for both core and activities. personal repos. (ssh access for devs)
  • Trac for core and activities
  • buildbot, master + a few slaves (ssh access for devs)
  • RT system
    • Is this really needed? We can just use other infrastructure for help requests... Firefoxman 19:27, 18 May 2008 (UTC)
  • Pootle
  • LDAP or OpenID authentication across various Sugarlabs tools