Difference between revisions of "Infrastructure Team/TODO"
Jump to navigation
Jump to search
m (add item to todo) |
m (reword todo to general) |
||
| Line 12: | Line 12: | ||
Setup workload will be distributed between the sysadmins and a few members of the core team. | 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. | * CMS to host a few, nice looking, official pages. | ||
| − | |||
* git for both core and activities. personal repos. (ssh access for devs) | * git for both core and activities. personal repos. (ssh access for devs) | ||
* Trac for core and activities | * Trac for core and activities | ||
Revision as of 18:35, 13 July 2008
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