...
- Danny Bernstein
- Peter Eichman
- Bethany Seeger (out)
- Jared Whiklo (out)
- Andrew Woods (out)
- Ben Pennell
- Aaron Birkland (out)
- Mohamed Mohideen Abdul Rasheed (out)
- David Wilcox
- James Silas Creel
Agenda
Announcements
- Sprint 2
- Open questions
- ?Authn and Authz in CTS update.
Remaining work
- Release Candidate
- Open questions
<your agenda item here>
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
Announcements
- Peter is out tomorrow
- Bethany will be at DLF
- Presenting on Tuesday
Sprint status
Default messaging
- Suggestion: Add documentation for changing messaging for production
- Either disable or change to queues
- Add broadcaster to documentation: https://gitlab.amherst.edu/acdc/repository-extension-services/tree/master/acrepo-connector-broadcast
- Add in-line documentation to spring.xml config file
- https://wiki.duraspace.org/display/FEDORA5x/How+to+Disable+Messaging
Fork of jetty-plugin
- Upstream project is willing to merge/release
- However, Fedora needs a slightly different version of Jetty
- Before 5.0.0-RC, need to decide on which jetty-plugin to use
AuthN / AuthZ in CTS
- Need a pluggable mechanism for different AuthN approaches
- Need to update CTS to use user URIs instead of literals
- URIs in Basic-Auth is not allowed
- Can we offer a configurable approach:
- Expect jar in classpath
- Expect given implementation classname
- Danny to move this forward
Remaining work
Tickets
...
- Camel component may be able to be removed
...
- David was at Samvera connect last week, did workshop with 5.0 version from a few weeks ago
- went through new memento API
- increasing interest in OCFL
- Fedora camp in Berlin in the next few months
- 8 new Fedora memberships, primarily around Europe.
- David will be giving Semantic web workshop soon, including info about CLAW
- There is interest in decentralized web in academic contexts, although it is focused more specifically on libraries
- Well attended by VEVO people
- jcreel mentions Texas A&M Walking Fedora 4 into spotlight using IIIF
- They are using api-x extensions from amherst, so they may be able to test with fcrepo5 in the not too distant future
- Generate PCDM from their graph
- Wondering about the best approach doing releases/versioning of API-X extensions
- May make sense to put some into fcrepo-extensions repo
- Having a registry of API-X solutions would be helpful too.
- They are using api-x extensions from amherst, so they may be able to test with fcrepo5 in the not too distant future
Road to Release
- Authn/Authz work for CTS to allow for pluggable authentication, with default authentication
- https://github.com/fcrepo/Fedora-API-Test-Suite/pull/260
- Aaron Coburn suggested that requiring users to write an authenticator in java was a high bar
- Will add option for specifying header for admin and permissionless users.
- Added "root-controller-user-webid" and "permissionless-user-webid", plus passwords
- if provided without a provided authenticator, get basic auth
- have to add user agent base URI in front of the usernames
- Documentation of server managed triples: What are the Server Managed Triples
- Older ticket related to using direct/indirect containers to add triples regardless of ACLS
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1889
- A number of CTS tickets/issues remaining
- https://github.com/fcrepo/Fedora-API-Test-Suite/issues
- Some of these don't need to be addressed prior to release candidate
- Documentation is fairly close to complete, may be sufficient for the release candidate
- Should we do a full set of testing prior to release or after?
- we don't have the vagrant project updated yet, so we wouldn't be able to run some components of the release testing yet
- So testing would involve downloading and testing, and possibly with the one click
- Early November, Peter will be looking at their camel infrastructure and how they will run camel toolbox with 5.0
- Will involve putting 5.0 into their local web application
- May not be until post release (January) before some of the environment tools start getting updated, such as camel toolbox, import-export, etc.
- Attempt to make decision about release candidate next week.
- Jetty 9.4 would help us be able to use the official maven-jetty-console release rather than our fork in fcrepo4-labs
- maven-jetty-console released an update from our PR, so they are on a sufficiently up to date to deal with Java 9 files
- check in to see if anyone has time to work on it.
- if not, then may move the project into fcrepo4 instead of labs
...