Page History

...

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

   
   

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

   
   

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

1. Announcements

   1. David Wilcox : Received $50K Planning Grant from IMLS to explore issues behind and how to help adopters migrate from older versions of Fedora to newer ones.  End product would be knowledge to author a grant to actually address our findings.   Individuals/organizations in the community have already reached out to us and expressed interest.  Begins in October.
   2. Danny Bernstein : Sprint 5 begins next week.
   3. James Silas Creel : Went live with our system this week.  Public now is a DSpace exhibit, but working on Fedora exhibit. Uses IIIF.  Little is custom.  Mirador for demonstration purposes, but it's really embedded in Spotlight, which is our main focus.
      
      1. http://library.tamu.edu/mirador/?manifest=https://api-pre.library.tamu.edu/fcrepo/rest/mwbManifests/AustinMap/Manifest
      2. http://library.tamu.edu/mirador/?manifest=https://api.library.tamu.edu/iiif-service/dspace/presentation/1969.1/165007
      3. http://hdl.handle.net/2249.1/156300

2. Weekly Progress Update

   1. Danny Bernstein : Are we feature complete on WebACs?  Might have a PR to be tested and merged, but work largely complete.  Props to Longshou Situ and Peter Eichman .  Let's get them reviewed and merged.  Peter Eichman can probably get to Danny Bernstein PR in the next day or so.
3. Monday morning
   1. PRs that need some love
      1. Jared Whiklo will look at one or two
      2. There was a lot of talk about stroopwafels at this point.
      3. Bethany Seeger Andrew noted a few implementation specific items that I've since modified. A few tests won't pass because of a related, unresolved ticket.  That said, the PR is ready to go, but if order is important...  I'll look one last time.
   2. 10 bugs, 6 stories

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

           - We shall contemplate.

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

         - This might have been created a while ago but not associated with the Epic until recently, which is why we are seeing it.  Peter Eichman will test and determine the status of this.

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

         - Like 2823, the status is unknown.  Bethany Seeger will review.

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

         - Danny Bernstein will look at this one.

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

         - Longshou Situ will look at this one.

4. Sprint Preparation

   1. General

      1. Danny Bernstein Should the first sprint be about closing open tickets?  Perhaps we make a determination Monday morning.

      2. Peter Eichman As a heads up, we might not be able to commit two devs to the first sprint because of internal demands.  We'll know better by Monday.
      3. Ben Pennell Also, as a heads up, I may not be able to engage in the second sprint. 
   2. Testing
   3. CTS
      1. Danny Bernstein : The challenge still stands, for those who aspire to stroopwafel glory.
   4. DocumentationTicket Summaries
      1. Danny Bernstein : Will look at this when we start the sprint.
5. Monthly email to different community groups (bseeger)
   1.  Bethany Seeger : I know that Duraspace puts out a monthly update, I was wondering if perhaps we - as the Tech group - should be doing something similar, at a lower level, to targeted groups, like Fedora-tech list and samvera.  Something to underscore that work is happening, progress is being made, provide guidance about our timeline and thinking, etc.  Let people know where we are going, such as ideas of upgrading or replacing Modeshape.
   2.  David Wilcox : There is a monthly Fedora Newsletter.  Perhaps it needs to be expanded.   It is on the Wiki so editable by all, and it might be a good idea for you all to take more ownership of it.
   3. Bethany Seeger : To me it is a lot about combating misinformation and baseless speculation.  It would certainly be targeted at other devs.
   4. David Wilcox : I think it is a good idea.  We'll have to figure out the best approach, perhaps it is a blog post.  Hearing more from Fedora devs would be helpful, especially if there is something happening that would be good to advertise.
   5. Danny Bernstein : We could provide a summary of our efforts, not a list of closed tickets but something of a sense that works is happening and progress is being made.
6. Subject URI on mementos
   1. A GET on a specific LDPRm returns a response the subject of which is the LDPRv.  This could result in a number of problems.  If indexing in a triplestore, there could be triples pertaining to 10 LDRPms all of the same LDPRv, resulting in a collision of (likely innaccurate) information.   Can API-X determine which messages are about an LDPRm and therefore choose to ignore it?  etc.
   2. Danny Bernstein : Will open a ticket to track this.

Actions

Future Agenda Topics: 

...