ICE cycle 2008-04-24
Summary
In the previous cycle we started twittering about what we have been doing when we were doing it (just for fun at the moment). For those who didn't noticed our twittering, we released a Beta version of ICE 2.0 during the cycle, and also setup a server version for some of our ICE-RS pilot users. Daniel's presentation to visitors from the University of South Africa at USQ went well. Peter was in the UK at at Open Repositories 2008 this cycle where he presented a poster title “Swimming upstream. From the repository to the source, in search of better content ”.
This next cycle we are working towards establishing a larger group of pilot users for ICE version 2.0 at USQ for courseware. However, before we can proceed there are a few things we'd like to fix first including Subversion folder conflict handling, and other requirements for the server version such as automatic syncing, so we'll start with some testing rather than piloting first.
This cycle meeting was held 2008-04-14 as 2008-04-10 was a holiday.
Predicted work units: 70
Overview of completed tasks
Administration
ICE 2.0 Beta installers for Windows and OS X
2.0 release notes
Demonstration for visitors from University of South Africa.
Application
Continue with stabilization tasks for ICE 2.0
Setup ICE server version for testing with:
ICE research group
ICE-RS pilot users
Faults and features as required by USQ users
Overview of new tasks
Administration
How to guides, for example:
How to setup an ICE service
How to setup ICE as a server
How to create/customize slides
USQ ICT infrastructure requirements and follow up
Setup USQ MPR for server version piloting (dependent on ICT)
ICE Beta 2 release
Application
Continue with stabilization tasks for ICE 2.0 from feedback
Subversion folder conflict handling
Multi-threading issues i.e. Subversion
Server version testing/development requirements
Setup Windows server for OOo
Investigate options for automatic syncing
Email functionality
About the cycle notes
The cycle notes are used to summarize the outcomes of the completed cycle and provide stake-holders with an overview of the tasks for the next cycle. They are also used to raise any issues for discussion and provide other information for those who are unable to attend the meetings. Specific information on tasks to be completed are available in the ticketing system, see below.
More information
http://ice.usq.edu.au/trac/roadmap
Modified: Apr 14, 2008