About Features Downloads Getting Started Documentation Events Support GitHub

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20170214

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
developers_call:minutes20170214 [2017/02/14 14:06] – [2. Development Planning] demiankatzdevelopers_call:minutes20170214 [2017/02/14 14:27] (current) – [2. Development Planning] demiankatz
Line 1: Line 1:
 ====== VuFind Developers Call Minutes: February 14, 2017 ====== ====== VuFind Developers Call Minutes: February 14, 2017 ======
  
-Attending: Demian Katz, Claas Kazzer, Jochen Lienhard, Benjamin Mosior, Brad Patton+Attending: Chris Hallberg, Demian Katz, Claas Kazzer, Jochen Lienhard, Benjamin Mosior, Brad Patton
  
 ===== Agenda ===== ===== Agenda =====
Line 33: Line 33:
 === VuFind on Heroku === === VuFind on Heroku ===
  
-Ben's experience at Keystone Library Network inspired the idea of using Heroku to run VuFind with less infrastructure support.+Ben's experience at Keystone Library Network inspired the idea of using Heroku to run VuFind with less infrastructure support. Some significant challenges -- like record loading -- but if we can solve these, we potentially make the application accessible to a wider group of people. Goal: one-click instance spin-up (which is what Heroku allows) would make "try before you commit" much easier. 
 + 
 +Ben spun up a proof-of-concept instance at [[https://vufind-example.herokuapp.com/|https://vufind-example.herokuapp.com/]]. Not everything works yet, but it's a good start. 
 + 
 +Pull request [[https://github.com/vufind-org/vufind/pull/913|#913]] suggests some very basic changes to make VuFind more Heroku-friendly and provide a baseline for working on new functionality. 
 + 
 +Suggestion: reach out to Code4lib mailing list to find potential users. 
 + 
 +Things to do: start composing composer.lock in master. 
 + 
 +Goal: add support for Heroku without negatively impacting non-Heroku users. 
 + 
 +Discussion: need for Heroku-specific Apache configuration to meet specific Heroku needs. Can we auto-generate this or do we need to commit two different templates to Git?
  
 === Image Metadata API Revisited === === Image Metadata API Revisited ===
Line 68: Line 80:
  
 === Other Front End Updates === === Other Front End Updates ===
 +
 +No major news.
  
 == New Theme? == == New Theme? ==
 +
 +Chris is still doing research; feel free to send suggestions his way.
  
 === VuFind 3.1.3 Release Date? === === VuFind 3.1.3 Release Date? ===
  
-Since several more bug fixes have been made in the release-3.1 branch, we should plan for a 3.1.3 release. March 13 may be a good option, unless there is a desire to publish sooner.+Since several more bug fixes have been made in the release-3.1 branch, we should plan for a 3.1.3 release. March 13 was agreed upon.
 ==== 3. VuFind Usage Survey ==== ==== 3. VuFind Usage Survey ====
  
Line 82: Line 98:
 ==== 5. Other Topics? ==== ==== 5. Other Topics? ====
  
 +Chris will soon be opening a CodeSniffer PR to address the alignment option issue we discussed last time.
 ===== Next Call ===== ===== Next Call =====
  
 The next call will be Tuesday, February 28, 2017 at 9am Eastern Standard Time (14:00 GMT). The next call will be Tuesday, February 28, 2017 at 9am Eastern Standard Time (14:00 GMT).
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20170214.txt · Last modified: 2017/02/14 14:27 by demiankatz