Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees 

Agenda

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

  2. Status of "in-flight" tickets

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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.  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - 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.

 

 

 

 

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.