Difference between revisions of "Infrastructure Team/TODO"

From Sugar Labs
Jump to: navigation, search
m (update link)
Line 54: Line 54:
 
* buildbot, master + a few slaves (ssh access for devs)
 
* buildbot, master + a few slaves (ssh access for devs)
 
* RT system
 
* RT system
** Is this really needed? We can just use other infrastructure for help requests... [[User:Firefoxman|Firefoxman]] 19:27, 18 May 2008 (UTC)
+
** Is this really needed? We can just use other infrastructure for help requests... [[User:LFaraone|LFaraone]] 19:27, 18 May 2008 (UTC)
 
* Pootle
 
* Pootle
 
* LDAP or OpenID authentication across various Sugarlabs tools
 
* LDAP or OpenID authentication across various Sugarlabs tools

Revision as of 07:33, 1 September 2009

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

Active Tasks

Task Owner Priority Next Milestone Notes
install a real ticket system such as RT open

Requested Tasks

Task Owner Priority Next Milestone 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... LFaraone 19:27, 18 May 2008 (UTC)
  • Pootle
  • LDAP or OpenID authentication across various Sugarlabs tools

Completed Tasks

Task Owner Priority Completion Date Notes