Action Fedora Api Evaluation
- Assigned
- ABR+KFC
- Prev assigned
- Tasks adressed
- ["TaskA.5"]
- Time estimated
- 2md
- Time used
- 0md
- Priority
- 1
- Status
- Not started
- Iteration
- 10
- Notes
- Evaluate the Fedora 3 API. Decide whether or not it will be suited as the interface to the DOMS system.
Regard the the Fedora 3 API. Decide on the following questions:
- Is it sufficiently powerful for the GUI?
- Is it of sufficient granularity for the GUI
- Is it to powerful, and should it be restricted? If so, how?
- Will additions to the API be required?
Produce a report with the answers. In particular, if the answer is no, the reasons must be detailed.
Checklist For Working On An Action
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.
- When finishing the action, change the status to "Finished" and update the "time used" field on the action page.