Development using prototype site with small group of user / testers. Fez 1.2.0 Beta will be used by a select group of Communities and Collections. The UQ Library will be the initial primary user for Collections such as meeting notes, Fryer Findaids, image collections.
Subversion will be used to track changes to project source code and database schemas
Programmers will each work using a personal test site, checking changes into subversion regularly
The prototype site will be updated from subversion to pickup changes from developers, the user / testers are asked to test any new features
The featureset is worked through according to a project plan in various development phases. At the end of each phase, the project is reviewed for changes to the features and the project plan is updated to reflect any changed goals
How will the project team be organized?
The development team will consist of Christiaan Kortekaas and Matthew Smith.
The change control board will consist of Belinda Weaver, Chris Taylor, Eric Hornsby and Andrew Bennett.
What development and collaboration tools will be use?
We plan to use the following tools
extensively through out the project:
Requests for requirements changes will be tracked in the issue
tracker
The change control board (CCB) will review requested
changes and authorize work on them as appropriate
After the feature complete
milestone, no new features will be added to this release.
After the code complete milestone,
no entirely new product source code will be added to this
release.
All source code commit log messages must refer to a specific
issue ID, after the feature complete milestone.
Project Planning Dependencies
Does this project conflict or compete for resources with any
other project?
Yes, and we have determined how many hours each
person can actually dedicate to this project. A programmer will be working on the project virtually full time, while another programmer will work at about 50% of their time (MS).
Are the same human or machine resources allocated to maintenance
of past versions and/or planning of future versions during this
release time period?
Yes, we predict that team members
will spend an average of 5% of their time maintaining
previous releases and planning future releases during this release
time frame. Some weeks may be higher if an urgent patch to a
previous release is needed.
Does this project depend on the success of any other
project?
Yes, the Fedora Project (external) is core to the success and sustainability of this project, although the Fedora source is available so if that project ended it could be continued internally or by the open source community.
Does any other project depend on this project?
Yes, the UQ Library Archives system, Australian Digital Theses system, Digilib, WebLaw, ePrints, Fryer Archives (EAD), Vetscans Archival and UQ Library Meeting Notes systems will be transferred into Fez under various levels of security.