...

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees 

• Jared Whiklo 
• Nick Ruest
• Bethany Seeger
• Longshou Situ
• Unknown User (acoburn)David Wilcox
• A. Soroka
• Allen Flynn
• Yinlin Chen
• Esmé CowlesNamita Bahulekar
• Michael Durbin
• Yinlin Chen 
• Kevin Ford (ArtIC)

Agenda

1. Vagrant versions - how should it be used and how is it being used

2. Status of "in-flight" tickets

   Expand
   Image Added

Ticket Summaries

1. Please squash a bug!

   Expand
   Image AddedImage Added

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 40 jqlQuery filter=13202 project = FCREPO AND status in (Closed, "In Review") AND created >= 2016-05-05 AND created <= 2016-05-12 project = FCREPO AND issuetype = Bug AND status in (Open, Reopened, Received) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...

1. Expand

   Please squash a bug!

   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 40 jqlQuery project = FCREPO AND status in (Closed, "In Review") AND created >= 2016-05-05 AND created <= 2016-05-12 project = FCREPO AND issuetype = Bug AND status in (Open, Reopened, Received) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Tickets resolved created this week:

   Expand
   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 40 jqlQuery project = FCREPO AND status in (Closed, "In Review") AND created >= 2016-05-05 AND created <= 2016-05-12 project = FCREPO AND issuetype = Bug AND status in (Open, Reopened, Received) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   Tickets created this week:

   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 40 jqlQuery project = FCREPO AND created >= 2016-05-05 AND created <= 2016-05-12 project = FCREPO AND issuetype = Bug AND status in (Open, Reopened, Received) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

1. Vagrant is mostly being used for demos and workshops.
   1. what is the intention of vagrant, finished product vs development product.
   2. main intention seems to be that vagrant is useful for demos
   3. in the past Andrew Woods wanted to cut releases of vagrant to include not yet released versions.
   4. change the fedora version variable in vagrant. but someone needs to build the webapp-plus artifacts and put them up somewhere.
   5. branches of fcrepo-vagrant seem to indicate possibly special versions of vagrant for demos.
   6. could create a development branch that pulls and compiles the source for those occasions you need a specific SNAPSHOT.
   7. consensus is to make the master branch tied to the most recently released branch. 

      Jira
      server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2020

2. Versioning Specification document
   1. Needs to move out of Google Docs and into Github. The suggestion is that this resides under the main duraspace github account.
      1. No objections to this location A. Soroka will work with David Wilcox or Andrew Woods to make it happen.
3. Inflight tickets

   1. Jira
      server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1774

       - Do we want to move forward on this as it is a change to the core API. Perhaps a HTTP Server header. Currently says Apache/Coyote, could say Fedora/4.5.1
      1. Can we end up with an additive result, so Tomcat adds its header and we add ours. The result is both.
      2. What is the desire to get the exact version of Fedora running. You should be able to determine capabilities by checking with server. But we are not fully there to say they don't require a version number.
      3. Right now the build and version number are displayed on the container HTML UI (http://localhost:8080/fcrepo). Could that page do content-negotiation and return the same information in a machine readable. Currently a static piece of HTML. One option could be to include a version.json which is created statically and is available beside the container (ie. http://localhost:8080/fcrepo/version.json)
      4. Perhaps we should go back and get some more context for his use case for this task.
      5. Simplest solution might be to wrap the build # in some tags for easier screen scraping.