User:Martinlanghoff/XS 0.6 plan: Difference between revisions
Jump to navigation
Jump to search
(→Pri 3) |
(→Pri 3) |
||
Line 35: | Line 35: | ||
* Ability to switch off registration service (~2d) -- local teams are worried about bogus registrations |
* Ability to switch off registration service (~2d) -- local teams are worried about bogus registrations |
||
* Tie internet access to registration - (1w) -- some local teams are worried about locals "stealing" very limited internet bandwidth. We could block internet access from un-registered machines or just throttle them very aggressively. Naturally, needs a 'whitelist' mechanism and UI to whitelist teacher's non-XO laptops. |
* Tie internet access to registration - (1w) -- some local teams are worried about locals "stealing" very limited internet bandwidth. We could block internet access from un-registered machines or just throttle them very aggressively. Naturally, needs a 'whitelist' mechanism and UI to whitelist teacher's non-XO laptops. |
||
'''Totals - 2~3w''' |
|||
= Special offer = |
= Special offer = |
Revision as of 17:14, 9 January 2009
LHF: Low hanging fruit
Pri 1
- Scalability: ejabberd/presence partitioning via Moodle (2w)
- Lease mgmt - activation, renewal, blacklist (3~4w)
- XS: network proto layer, USB-based delivery handling, mgmt UI
- XO: firmware, initrd, userland
- Needs simple service announcement scheme
- Browse.xo transparent sign on - working with Simon (2~3d)
- DS-Backup -- Restore UI (2d)
- Management scheme (2w)
- Scripts automation
- Update callback scheme
Totals 8~9 weeks
Pri 2
- Easier transparent OS and activity upgrade - LHF -
- service announcement scheme
- small XO work (~3d work)
- XS on XO - LHF, working with Jerry
Totals - about a week of work(?)
Pri 3
- Basic reporting scheme (~4d)
- Ability to switch off registration service (~2d) -- local teams are worried about bogus registrations
- Tie internet access to registration - (1w) -- some local teams are worried about locals "stealing" very limited internet bandwidth. We could block internet access from un-registered machines or just throttle them very aggressively. Naturally, needs a 'whitelist' mechanism and UI to whitelist teacher's non-XO laptops.
Totals - 2~3w
Special offer
- 2~3 weeks of polish on Moodle for the XS to close the gaps so that we can start taking advantage of community work.
Not in the plan
- F10/F11 rebase
- Frills or cushions