Integration with CMS back-end storage
Implementing Backend "behind the scenes" storage and system backup with Subversion (SVN) would be a great solution. All the tools are there for secure (ssh) transfer of specific files, revision control, and restoration. Just a quick creation of a 'Backup Activity' (frontend) which allows veiwing of revisions, restorations, and 'housing cleaning' of older un-needed revisions or files.
Could also be used for shared distrubted storage array. Where XO laptop users could examine parts or whole collections of files, without needing to download the actual whole collection.
Hmmmm... --IainD 21:58, 30 December 2007 (EST)
 The box sucks
The box for entering information sucks, as this is the formatting for a quote. You don't get nice line wrap-around. Everyone is copying what you input, including the blank in front of the first line. I would like to see:
==== PROJECTNAME ==== Project: Proposer: Other contributors: Audience or impact: Brief description: (link to a full description at Projects/PROJECTNAME) Relevant experience & other projects: Contact information (wiki, email, &c): [If requesting XOs] # of XOs needed, and their use:
as the template ;) --WiseWoman 09:10, 2 January 2008 (EST)