Page History

...

1. Announcements

   1. 5.0.1 Release
   2. Publishing CTS Test  Results
      1. https://fedora.info/spec-tests/
      2. https://github.com/fcrepo/fedora.info
2. Follow up from two meetings ago: 
   
   1. UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
3. James Silas Creel 's demo of TAMU's CAP frontend for Fedora (15 minutes
4. 5.1.0
   1. PRs
      
      1. https://github.com/fcrepo4/fcrepo4/pull/1501
      2. https://github.com/fcrepo4/fcrepo4/pull/1502
      3. https://github.com/fcrepo4/fcrepo4/pull/1465
      4. https://github.com/fcrepo4/fcrepo4/pull/1499
      5. https://github.com/fcrepo4/fcrepo4/pull/1504 (new)
   2. Issues that re ready for work:

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2937

   4. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2936

   5. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2935

5. Status of ecosystem tools:
   
   1. Java Client Release
   2. fcrepo-camel
   3. camel toolbox
   4. fcrepo-mint (question: is any one using it) 
6. 4→ 5 migration and 5 → 5 support.
   1. Next steps 
    

7. Archiving following GitHub projects (making read-only)

   1. https://github.com/fcrepo3/trippi
   2. https://github.com/fcrepo3/fcrepo-before33
   3. https://github.com/fcrepo3/fcrepo
   4. https://github.com/fcrepo3/fcrepo-historical
   5. https://github.com/fcrepo4-archive/ff-jms-solr-indexing
   6. https://github.com/fcrepo4-archive/ff-indexer-fourstore
   7. https://github.com/fcrepo4-archive/fcrepo-jruby-admin
   8. https://github.com/fcrepo4-archive/fcrepo-triplegenerators-tei
   9. https://github.com/fcrepo4-archive/fcrepo-message-consumer
8. 2019 Priorities 
   1. Modeshape replacement
   2. OCFL

9. 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

   
   

10. 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

    
    

11. 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

1. Talked about Ruben Verborgh's blog about making a front-end developers experience using linked data easier.  Might make a shift in the accessibility of linked data. 
2. Andrew mentioned this making him rethink the JS we use in the front end of fedora. 
3. Aaron Birkland talked about how they use plain old JSON in their Ember JS project at Johns Hopkins.  It worked well, but is very specific to their use case given how Ember JS works.  Aaron Coburn had been looking into designing a UI with a more general approach for linked data (maybe using React); not sure of where that went.  

...

1. Both issues done and merged into master and 5.X
   

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2969

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2970

...

1. What do we want to do for this release?  Aaron Birkland  thinks a light weight cycle for this one, given the tickets involved. Bethany Seeger and Ben Pennell  agree.
2. Simple test page should be fine for 5.0.1 - tests: building source code, running all the tests on three platforms, CTS test, and the tests in the PR for the two issues.  Maybe a few of us could go through the page and do sanity testing.  
3. Create RC for 5.0.1?  Yes, but how long would we have for public comment on it?   Danny Bernstein will create an RC for 5.0.1 today and we will test it for 1 week then release it. 
4. Andrew Woods  - would like to put CTS test results for 5.0.0 and then 5.0.1 results on the Fedora page.  Need to figure out how to highlight the differences between tests as well as how to interpret the test results.  A top level page that makes it easy to navigate through results would be nice.  More on this below. 
5. 4.7.X - need a separate conversation regarding release testing process on this branch

...

...

 

Actions

•  Danny Bernstein to write short technical summary for the  newsletter
•  Danny Bernstein  will setup test page for 5.0.1
•  Danny Bernstein to create 5.0.1 RC
•  Bethany Seeger  will start page for CTS testing results  (matrix), to include explanation of test and results
•  Andrew Woods  will start by putting up raw HTML results for CTS now, so community can have access to them. 
•  Checking with Peter Eichmanregarding: UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
•  Danny Bernstein will reach out to Yinlin Chen to see about a fcrepo4-docker release with the 5.0 architecture.

...