...

1. Announcements:
   
   1. Tech team/committer profiles for upcoming newsletter
   2. Dan to OR next week
      1. OCFL Meet Up at OR
   3. Technology Info Session for F6 users last week
   4. Do we want a meeting next week? Dan will be at OR, Arran is out.
2. Pop-up/Other Topics:
   1. Tombstone decision from Governance
      1. Would like to see more clear definitions outlined of PURGE vs DELETE
      2. Approve Jared's recommendations via this doc so long as the definitions of purge and delete are clear
   2. Paul Trilsbeek's ACL question/consideration from Slack (#Tech channel)
      1. "So Fedora has an internal mechanism for determining the effective ACL for a given resource, walking up the hierarchy if the resource itself doesn't have one. Would there be a way to get the effective ACL via the API? (with a single call, rather than probing and walking up the hierarchy until you encounter one)"

3. Updates on:

   1. Open Tickets (but assigned in some cases): 

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3893

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3894

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3883

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3882

      5. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3881

      6. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3884

      7. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3875

   2.  In Progress and older but still relevant open tickets:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3868

   3. In Review:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3892

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3891

         - isn't this one James said he would look at or that he sent notes to Dan about?

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3834

4. New tickets:

5. Backlog Tickets to consider working: NA at present
6. Next Meeting Chair:
   1. Chair: Jared Whiklo
   2. Note Taker: Demian Katz
   3. See Rotating Schedule here 

Notes

1. Announcements:
   
   1. Tech team/committer profiles for upcoming newsletter
   2. Dan to OR next week
      1. OCFL Meet Up at OR
   3. Technology Info Session for F6 users last week
      1. Jon Gostick from Cambridge setting up F6 from scratch. David Novak also on new F6 and brought up some new tickets
   4. Do we want a meeting next week? Dan will be at OR, Arran is out.
      Next week cancelled. Demian happy to cary acrosss note taker
2. Pop-up/Other Topics:
   1. Tombstone decision from Governance
      1. Would like to see more clear definitions outlined of PURGE vs DELETE
      2. Approve Jared's recommendations via this doc so long as the definitions of purge and delete are clear
   2. Paul Trilsbeek's ACL question/consideration from Slack (#Tech channel)
      1. "So Fedora has an internal mechanism for determining the effective ACL for a given resource, walking up the hierarchy if the resource itself doesn't have one. Would there be a way to get the effective ACL via the API? (with a single call, rather than probing and walking up the hierarchy until you encounter one)"
         1. Ben agrees it might be tricky

3. Updates on:

   1. Open Tickets (but assigned in some cases): 

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3893

         in progress with Ben

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3894

         403s on assets causing CSS ddisplay issues

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3883

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3882

      5. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3881

      6. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3884

         Arran has list of institutions who attended OAI-PMH sessions. Ping her when ready to test

      7. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3875

         Ben thought this was done. will check

   2.  In Progress and older but still relevant open tickets:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3868

         Dan using 11/17 in testing. at present

   3. In Review:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3892

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3891

         - isn't this one James said he would look at or that he sent notes to Dan about? Yes it is.

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3834

4. New tickets:

5. Backlog Tickets to consider working: NA at present
6. Next Meeting Chair:
   1. Chair: Jared Whiklo
   2. Note Taker: Demian Katz
   3. See Rotating Schedule here