You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Q1 (Jan 27-31)

Participants

  1. Danny Bernstein
  2. Peter Winckles
  3. Peter Eichman 
  4. Johannes Stigler
  5. Ben Pennell
  6. Andrew Woods
  7. Jon Roby

Prioritized Objectives   

  1. Read - Write Binaries
  2. Containment:
    1. display containment 
  3. Align migration-utils with current on-disk plan

Second priority

  1. Rebuild from OCFL
  2. Versioning

Nice to haves

  1. Simple search API
  2. Fixity
    1. Persistence Fixity: on demand - fresh calculation and comparison with stored value (/fcr:fixity)
    2. Persistence Fixity: on demand - fresh calculation (WANT-DIGEST header)
    3. Persistence Fixity: store result of calculation on demand)

Migration-utils

The primary objective for migration-utils in this sprint is to ensure that Fedora 3 content that is migrated to Fedora6-compliant OCFL is indeed persisted in a way that Fedora6 can be rebuilt from that OCFL.

Additionally, several suggestions and feedback from community stakeholders have been captured in tickets and should be resolved.

Finally, documentation should be added to the wiki  that details both the layout of OCFL produced by migration-utils as well as collects performance results of different sized migrations.

Community updates are being documented in the wiki: Fedora 3 to 6 Migration Community Updates

Tickets

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.


Resources

Standups (please post update by 10am EST)

Slack Standup Template

[Fedora 6 Standup]
Finished yesterday: 
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Working on today:
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Blockers:
  {brief textual description}

Meetings

  • No labels