Regular Attendees
- Andrew
- Bill
- Brad
- Chris
- Dan
- Jonathan
General
- Call In To: Free Conference Call HD - DuraCloud Line
Please note that we will be using the Free Conference Call HD line for this call. Information about calling into this line is available from the link above.
- - Indicates who will be taking minutes
Discussion Topics
Planning Board
Task Board
DfR Planning and Estimating - 0.1
Topic Discussion Leader Planning and Task Boards - Near Term Tasks Dan More stories and nothing but stories No one gets out of this - Brad and Dan Project Infrastructure Chris Coordination with DuraCloud Bill OR12 Submission Proposal Kickoff Dan Project and Partners Jonathan
Actions from last meeting
Last Weeks Actions:
Action Item |
Assignee |
Status |
|---|---|---|
Chris and Dan work on Object Creation Service related stories/tasks |
Chris and Dan |
|
Permit any issue to have story points for DfR |
Dan |
|
Box.net test account |
Jonathan |
|
Tie some of the DuraCloud jira items to DfR stories |
Bill + Andrew |
|
(Related Information
DfR Software Next Steps - Jan 2012
2012-01-03 - Architecture Meeting, Temple University
Status
- Jonathan
- Rensselaer trip re DfR
- Latest negotiations with Fluid - plan for them to play a reduced role
- Discussion with Thorny re collaboration
- Upcoming UK workshop on preservation in the cloud
- Will propose DfR presentation for OR12
- Andrew
- Bill
- Brad
- Chris
- Dan
- Discussed with Chris methods for setting up OCS-related stories
- Reworked Jira-Greenhopper to include story points
- Traveled to Renssalear with Jonathan to meet about DfR and DuraCloud
- Jonathan
Minutes
We need to determine what we mean by accounts and users in DfR (also with respect to DuraCloud) due to their importance in setting up policy controls in Fedora. DFR-8 needs to be reworded in light of this understanding. This issue also affects (and is affected by multi-tenancy) for both DuraCloud and DfR. Dan will take the action but this requires input from the whole development team.
Chris and Dan will look at DFR-1 during the week in light of DFR-11 for rework or removal in light of DFR-11 and make a suggestion to the group.
Bill will re-write DFR-8 to make it better fit the work.
Dan and Chris will re-examine DFR-74 in light of Bill's work in DuraCloud. DFR-74 will entirely be used for Release 0.1 to track cross-over work from DuraCloud. If there is still functions related to this card related to Fedora integration (checksums), Chris and Dan will write a new card.
Andrew will estimate the tasks used to address DFR-64 and sum them into it.
Dan will revise Jira so that Tasks can be assigned to releases, not just stories. However, stories will still be kept to levels (8 story points) that can be accomplished during a release and tasks will be "owned" by one story meaning they are also not to be split between releases for planning purposes. Stories may be related to other stories or tasks (having dependencies) anywhere especially for noting blockers.
Andrew will estimate the work for DFR-2.
DFR-23 was deemed more to address more looking at example upload/synchronization products to determine the functionality needed for DfR. Current thought is that DFR's tools will be derived from the DuraCloud upload technology. Bill will rewrite the card to reflect this. Dan, Jonathan and Brad will see if a new card needs to be written to cover work related to Box.net or other tools for upload.
Chris and the group will try out the new DfR development infrastructure during the weeks and use the chat to work out issues (if any).
Jonathan is preparing a proposal to discuss DfR-related general ideas at OR12 (this call for proposals happened last week).
Jonathan, Brad and Dan will meet as time permits this week to work on smoothing the planning and tracking approach.
Actions
Incorporated into the notes this time.
