Versions Compared

Key

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

...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


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


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


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


Notes

  1. Announcements

    1. Zoom waiting room is now enabled – Let David know if it's a problem
  2. Sprint Post Op Reflections
    1. Sprint board
      1. Just a couple of tickets still in review
    2. Reflections on sprint? Changes for next sprint?
      1. Ben: Quiet but went well. Short week, due to holiday.
      2. Daniel: Agrees with Ben. Scope seemed appropriate. Next sprint stay conservative. Separate lanes worked well.
      3. Jared: Went well. Liked the separate lanes.
      4. Peter: Same
    3. JMS events done?
      1. ResourceTypes are not currently correct: https://jira.lyrasis.org/browse/FCREPO-3279
        1. Ben says that there was some thought that you might want to differentiate between user managed and server managed types, which is why you might want to resolve the types at render time.
        2. Jared says that some of the types are currently being added in getTriples, so perhaps the code should just be moved to getTypes and have getTriples call it.
      2. PATCH isn't implemented so those events aren't there yet
    4. Demo
      1. Features:
        1. Rebuild
        2. Messaging
        3. Transactions
      2. Rebuild will be the most interest to people.
        1. Shouldn't be too technical
      3. Andrew thinks it'd be good to demo the relationship between Fedora and OCFL versions and all of the different ways that they're created.
  3. What's up next? 
    1.  2020 Sprints - Fedora 6#2020SprintsFedora6-May4-8
    2. Feature tracking
    3. Next sprint focus?
      1. webacs
        1. Might be less important than Simple Search
        2. Maybe if someone from Maryland was on the sprint
      2. PATCH
        1. Jared: Thinks it will be easier without Modeshap
      3. DELETE
      4. Vanilla OCFL rebuild
        1. No one has vanilla currently, so the feature might that be that high of priority
        2. Migration utils produce Fedora OCFL and/or Vanilla OCFL?
        3. What does the community think? How highly valued is running on vanilla OCFL?
        4. How about a tool for converting vanilla OCFL to Fedora OCFL?
        5. Peter: It doesn't seem right to run Fedora on Vanilla OCFL but have the new objects it produces be Fedora OCFL.
      5. Simple Search
        1. Andrew: People want this feature; we haven't done it before so there's risk and unknown; might be worth doing early
        2. Ben: Agrees it'd be good to figure out early – figure out its integrations with other components
  4. Containment Index
    1. How to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
  5. Fedora 6 testing
  6. Committers/Leaders call topics

Actions

...