Difference between revisions of "Infrastructure Team/TODO"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
! Notes | ! Notes | ||
|- | |- | ||
| − | | | + | | install a real ticket system such as RT |
| − | | | + | | open |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| | | | ||
| | | | ||
Revision as of 20:24, 27 August 2009
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... Firefoxman 19:27, 18 May 2008 (UTC)
- Pootle
- LDAP or OpenID authentication across various Sugarlabs tools
Completed Tasks
| Task | Owner | Priority | Completion Date | Notes |
|---|---|---|---|---|