Differences between revisions 4 and 5
Revision 4 as of 2008-08-14 08:19:28
Size: 3019
Editor: bam
Comment:
Revision 5 as of 2010-03-17 13:12:48
Size: 3023
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
[:Agendas/2008-08-12:Agenda] [[Agendas/2008-08-12|Agenda]]
Line 9: Line 9:
KFC created a new [:Manning:Manning wiki page] to make planning easier. KFC created a new [[Manning|Manning wiki page]] to make planning easier.
Line 17: Line 17:
 * [:Iteration09:Iteration 9]  * [[Iteration09|Iteration 9]]
Line 30: Line 30:
 * [:Iteration10:Iteration 10]  * [[Iteration10|Iteration 10]]

2008-08-12 End of Summer Iterations Meeting

Attendants: KFC, ABR, TSH, EK, BAM

Agenda

0. Praticalities

KFC created a new Manning wiki page to make planning easier.

1. Forcefully ending iteration 9 and 10

Note: Actions cannot be pushed. Instead finish the action, when the iteration finishes, and create a new action in the new iteration.

  • We discovered that the wiki transfer was not complete. The pages that were transferred early on (templates and structure), were not updated when the full wiki was transferred. TSH will make a list of the affected pages. New action.

  • We also need a new action to update tasks affected in iterations 9+10

  • Iteration 9

    • Action Action Checklist
      • Forced finish. Still missing something -> new action

    • Action Finish Mini DOMS
      • Not started. Move action to later iteration.

    • Action Milestone Plan
      • Forced finish. Continue as part of status meetings.
    • Action Mjoelner Timeframe
      • Finished
    • Action Update Task List
      • Forced finish. New action to update WBS.

    • Action Wiki Magic
      • Forced finish. Still missing some links between actions/iterations and tasks. ABR?
  • Iteration 10

    • Action Datamodel For Example Collections
      • Forced finish. Missing description.
    • Action Datamodel Language Class Decision
      • Forced finish. New action in next iteration.

    • Action Decide On Example Collections
      • Forced finish.
    • Action Fedora Api Evaluation
      • Forced finish. This action expanded into also writing APIs and web-services.
    • Action Fedora Journaling Evaluation
      • Forced finish. Missing documentation. ABR will write what Journaling does for us - and what it doesn't.
    • Action Fedora XACML Evaluation
      • Forced finish. Missing documentation. BAM will update the documentation (licence: look at the data model documentation).

2. Iteration 11

Title/Goal: Testbed based on Fedora 3 + final Data Model

TODO

  • We need to update our risk management pages. A major risk now is that changing the data model will affect Mjølners chances of building a functional GUI. We should commit to a data model and then agree that we only make changes if we have extremely good reasons.

  • We started discussing the data model, and we agreed that we need a new action to go through the data model including TDR (Trusted Digital Repository) requirements, and we will prepare and hold a meeting in which we agree on the data model.

  • To finish the test bed, we need:
    • Set up of Fedora 3 including user identification
    • Bit storage
    • Pid generator
    • Search: we are not sure if gSearch works with Fedora 3 yet, so we want to wrap simple search in a Summa-like interface
    • Testbed documentation
  • KFC? will create an iteration 11 and call for a meeting next week

Minutes/2008-08-12 End Of Summer Iterations Meeting (last edited 2010-03-17 13:12:48 by localhost)