...
- Jared Whiklo
- Danny Bernstein
- Jim Coble
- Andy Wagner
- Doron Shalvi
- Yinlin Chen
- Esmé Cowles
- Kevin Ford
- Michael Durbin
- Simeon Warner
- Benjamin Armintor (late)
Agenda
Outstanding issues on Fedora API Specification
The following ticket should be squash/merged by another committer if approved:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2402 - The following ticket should be squash/merged by another committer if approved... once Danny Bernstein merges code-review PR:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2105 - ...
Status of "in-flight" tickets
...
- #82 about ordering issues, which was largely not an API issue
- #81, a little bit of langage in the spec should clear up confusion here
- change a "may" to a "must" if a preference is applied, the fedora implementation should say so
- #80, there's some disagreement about whether fedora should redirect or proxy to external content, and once a clear consensus is achieved, the spec should reflect it
- Benjamin Armintor is the only one who has articulated a need for proxying, while presumably other stakeholders are content with redirects
- Feedback at LDCX suggested that other stakeholders minimally preferred proxied content, and in some cases required it.
- A new issue was opened for this Proxy vs. Redirect requirement in the spec.
- Benjamin Armintor is the only one who has articulated a need for proxying, while presumably other stakeholders are content with redirects