Differences between revisions 15 and 16
Revision 15 as of 2009-10-09 14:20:20
Size: 3520
Editor: abr
Comment:
Revision 16 as of 2009-10-09 14:20:58
Size: 3525
Editor: abr
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 Time used:: 0.5md  Time used:: 1.5md(ABR)

Action Decide on Fedora Modules

Assigned
ABR: 2 JRG: 2

Prev assigned

Tasks adressed
["Tasks/3/3"]

Time estimated
4md

Time used
1.5md(ABR)

Priority
?

Status
In progress

Iteration
22

Notes

Problem

Decide on the layout of the final production system. Decide which supporting fedora modules should be used, and in what way.

Progress

Established a plan for the deployment of the system

Identified external modules

  • Journaling
  • Akubra
  • OAI-Provider
  • GSearch
  • Tripple store
  • REST API
  • Database

Identified internal modules

  • Domsclient
  • Bitstorage
  • ECM
  • GUI
  • Summa

Conclusion

Conclusions and recommendations to be found [:Deployment and Design of DOMS:here]

Checklist For Working On An Action

The Life Cycle of an Action:

  • Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned

  • Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.

  • Review the definition: Get another project group member to review the action definition, and update it.

  • Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Assigned and Prev assigned if new persons are assigned.

  • Implement the action: See details below

  • Review the action: Get another project group member to review what is implemented (code and documentation), and update it.

  • Finish the action: Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:

  • Update the state of the action to "In Progress" when you start working on it.
  • Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.
  • Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Hint: Continually updating the "Time used" field will make it easier for you.

  • Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.

Actions/Decide on Fedora Modules (last edited 2010-03-17 13:09:11 by localhost)