Infrastructure Team/TODO: Difference between revisions
Appearance
m fix heading levels |
m add task tables |
||
| Line 1: | Line 1: | ||
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|InfrastructureTeam}}</noinclude> | <noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|InfrastructureTeam}}</noinclude> | ||
=== Active Tasks === | |||
{| border="1" | |||
|- | |||
! Task | |||
! Owner | |||
! Priority | |||
! Next Milestone | |||
! Notes | |||
|- | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|} | |||
=== Requested Tasks === | |||
{| border="1" | |||
|- | |||
! Task | |||
! Owner | |||
! Priority | |||
! Next Milestone | |||
! Notes | |||
|- | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|} | |||
<noinclude>=== Completed Tasks === | |||
{| border="1" | |||
|- | |||
! Task | |||
! Owner | |||
! Priority | |||
! Completion Date | |||
! Notes | |||
|- | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|} | |||
=== Backups === | === Backups === | ||
| Line 21: | Line 72: | ||
* Pootle | * Pootle | ||
* LDAP or OpenID authentication across various Sugarlabs tools | * LDAP or OpenID authentication across various Sugarlabs tools | ||
</noinclude> | |||
Revision as of 17:26, 5 December 2008
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