Infrastructure Team/TODO: Difference between revisions
No edit summary |
No edit summary |
||
| Line 47: | Line 47: | ||
|} | |} | ||
=== Backups === | === Backups === | ||
| Line 84: | Line 68: | ||
* Pootle | * Pootle | ||
* LDAP or OpenID authentication across various Sugarlabs tools | * LDAP or OpenID authentication across various Sugarlabs tools | ||
<noinclude>=== Completed Tasks === | |||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | |||
|-style="background:#787878; color: white;" | |||
! Task | |||
! Owner | |||
! Priority | |||
! Completion Date | |||
! Notes | |||
|- | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|} | |||
</noinclude> | |||
[[Category:TODO]] | [[Category:TODO]] | ||
Revision as of 16:17, 17 March 2009
Active Tasks
| Task | Owner | Priority | Next Milestone | Notes |
|---|---|---|---|---|
| Move api.sugarlabs.org to sunjammer | dfarning | |||
| Move buildbot.sugarlabs.org to sunjammer | dfarning | |||
| Move pydocweb.sugarlabs.org to sunjammer | dfarning |
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... Firefoxman 19:27, 18 May 2008 (UTC)
- Pootle
- LDAP or OpenID authentication across various Sugarlabs tools
Completed Tasks
| Task | Owner | Priority | Completion Date | Notes |
|---|---|---|---|---|