Versions Compared

Old Version 13

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version Current

changes.mady.by.user Karen Estlund

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Fedora 4.7.1 release is out
    1. Release Planning
  2. Fedora/API-Spec delta-document: Aaron Birkland available to spearhead?
    1. Initial planning about scope and purpose: google doc
  3. Fedora/API-Spec - is it ready for initial community input (proposed deadline for input May 1)
  4. Focus on intra-repository-resource-relationship performance
    1. Storing these relationships as URIs (Prefer:InboundReferences and referential integrity go away)
    2. Optimizing the backend database index
  5. Fedora DevOps interest group in collaboration with Islandora and Hydra
  6. Trajectory of development
    1. Common API and import/export facilitates transfer between impls
      1. Transfer impact mitigated by "external-content"?
  7. Interest in Fedora Docker? ...looking for another maintainer for fcrepo4-docker
  8. WebApp configuration possibilities - fcrepo-webapp-plus limitations
    1. AuthZ
    2. Audit
    3. Minter
    4. Backup/Restore
    5. API-X?
  9. ...

  10. Status of "in-flight" tickets

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13202
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

...

  • Aaron Birkland working on this
    • Has a document defining scope and audience of effort
    • Who is this for and what do we want?
    • Line by line analysis vs. high level overview
    • Google doc, anyone can contribute
    • Next step: move to wiki page and solicit input from the community in terms of what we’re looking for
    • Assemble team to divide and conquer
  • Near-term benefit: helping with development, clarify tasks to be performed on Fedora implementation to align it with the spec
  • Line by line comparison will help generate actionable tickets
  • Aaron Birkland will move the doc to the wiki and send a message out to the community for feedback, ideally by the end of the week
  • Andrew Woods looking for stakeholders to participate in this effort

...