Iteration 3 end-of-iteration meeting 2007-11-22
1. Iteration 5 status
The iteration still has an outstanding release test. Apart from that it is deemed done.
Design ingest module
The action is done, although check of review followup has not been done.
Adding licenses and source code to libraries has been postponed. For some libraries even the version number is still missing.
Approximately 9/10 of all jars have version numbers.
Approximately 2/3 of all jars have licenses
Approximately 1/4 of all jars have source code attached.
Kowari was a special case, since it seemd to have packaged class files of other projects in its own jar file. However, we will not attempt to analyse the licenses of whatever is included there, we will assume the Kowari license holds.
Spent time
- TE
- 7md
- ABR
- 1 md
- TSH
- ?? md
Salvage data model from pre-analysis project
The action has some outstanding issues, which are documented on the action page. Estimated time to follow up on these is 1½ md.
We have decided to postpone this followup to an upcoming iteration.
The action has had some amount of "feature creeping", as it turned out that we often starting solving the outstanding issues, rather than document them.
Spent time
- KFC
- ½ md
- BAM
- 4 md
- MKE
- 3 md
- ABR
- 1 md
- JRG
- ½ md
Identify Gentofte Objects
The ask is done - outstanding issues in data model are of course also outstanding in Gentofte objects.
However, example objects exist, and the moel is documented.
Spent time
- KFC
- ½ md
- BAM
- 1 md
- ABR+JRG
- ½ md
- MKE
- 2½ md
Study Group
Task is done. Not all of the identified book is read, but it is not considered essential.
Spent time
- KFC
- 1 md
- ABR
- 3½ md
- JRG
- 2 md
- TSH
- ½ md (??)
Present results of risk/stakeholder analysis
The task is done, as far as possible with TSH off ill.
Results will be presented on this meeting.
Spent time
- KFC
- 1½ md
- TSH
- ?? md
Release test
Release test guidelines are written but not reviewed.
The release test is written and reviewed, but needs followup, and the procedure around codefreeze, building package etc. is still outstanding.
The release test hsa not yet been done.
The time for doing the release test hass not been estimated.
Time spent
- KFC
- 1md
- ABR
- ½ md
3. Release test
KFC presented how to ru nrelease test.
We decided on the following:
- Code freeze is done on release candidate
- We will tag the code on release with the version number.
- We will build a package with the version number on release.
We briefly discussed version numbers, but didn't conclude anything precise.
The release test will be done Monday by JRG and KFC. ABR will be responsible for fixing eventual bugs.
We did not decide on a QA master for this release. That will be done Monday.
4. Risks and Stakeholders
KFC presented the work done. Highlights:
- We will introduce steering group meetings at the end of iterations
- We will send out news letters to the library at the end of iterations
- Communication is registered in the communication plan
- We should start following the Fedora mailing lists.
- Communication is the number one need for meeting our top risk. We will make a presentation meeting for the library ASAP.
- We need a plan for what should be done each itearation (update stakeholder/risk/communication tables, write news letter, ...)
5. End of iteration tasks
ABR was elected reponsible for the news letter this iteration.
KFC will call a meeting with the steering group. Topics:
- MKE + TE + BAM time in project
- Digitization workflow/metadata system money - module for DOMS?
Everyone should remember to write task status in the tasks they have worked on in this iteration.
6. Next iteration
Points relevant for next iteration:
- Finish data model
- Make pre-ingest module
- DOMS presentation meeting
- Write iteration schedule documentation (see action in iteration plan)
- Possibly IT service coordination
7. Next full iteration
We will try to start the iteration 2007-12-13 to make everyone particiapte before christmas holidays start.
The iteration will probably last slightly into January. Hopefully TE and MKE can still participate.
Issues will be Summa integration and bit storage.
8. AOB
We need a documentation section on the wiki, which refers to generally interesting documents like our data model document. BAM takes action.
KFC has (again) visited media department. They wanted to show digitisation workflow system. Turns out that DOMS + workflow solves almost all problems. Could the money for getting a new system possibly be converted into money spent for developing a module for DOMS? E.g. the UI?