Versions Compared

Old Version 13

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version 14

changes.mady.by.user Bethany Seeger

Saved on

Key

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

...

  1. Danny Bernstein
  2. Andrew Woods
  3. Peter Eichman 
  4. Aaron Birkland Jared Whiklo 
  5. Bethany Seeger (star)
  6. David Wilcox
  7. Ben Pennell

...

  1. Announcements

    1. Some good reading: https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/
  2. Follow up from last meeting: 
    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. 5.0.1 Release
    1. Issues: 
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2969
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2970
  4. 5.1.0
    1. Borderline PRs (5.1.0 or 5.0.1?)
      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
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2937
    3. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2936
    4. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-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
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  10. Tickets resolved this week:

    Expand

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


  11. Tickets created this week:

    Expand

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


Minutes

  1. 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.  
  2. Follow up from last meeting regarding UMD fixing checks - made into an action. 
  3. 5.0.1 Release
    1. Both issues done and merged into master and 5.X
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2969
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2970
  4. Talked about point release process – for 5.0.1.   Closest thing we have is: Policy - Release Candidates which covers point releases.  Shorter period of testing.  For a point release - it's an ack. that we know something is not right and we want to get a fix out quickly. These changes should break any API.  Each time we do a point release, we should have a discussion of scope of fixes, what is necessary amount of testing required, versus a set process.   Point releases warrant a conversation, which might result in standard testing, but not necessarily.  
    1. What do we want to do for this release?  Aaron Birkland  thinks a light weight cycle for this one, given the tickets closed. 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? 
    4. 4.7.X - need a separate conversation regarding testing process on this branch
  5. 5.1.0
    1. Borderline PRs (5.1.0 or 5.0.1?)
      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
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2937
    3. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2936
    4. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2935
  6. Status of ecosystem tools:
    1. Java Client Release
    2. fcrepo-camel
    3. camel toolbox
    4. fcrepo-mint (question: is any one using it) 
  7. 4→ 5 migration and 5 → 5 support.
    1. Next steps 
     

  8. 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
  9. 2019 Priorities 
    1. Modeshape replacement
    2. OCFL

  10. Please squash a bug!

Actions

  •  Danny Bernstein to write short technical summary for the  newsletter
  •  Danny Bernstein will rename the 5x-maintenance branch to 5.x-maintenance  will setup test page for 5.0.1
  •  Danny Bernstein to create 5.0.1 RC
  •  Checking with Peter Eichmanregarding: 
    1. 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.

...