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.


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 13:47] – [1. Development Updates] 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: +Attending: Chris Hallberg, Demian Katz, Claas Kazzer, Jochen Lienhard, Benjamin Mosior, Brad Patton
 ===== Agenda ===== ===== Agenda =====
Line 32: Line 32:
 === 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. 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 ===
 +Leila is on vacation today but sent an email reporting that she'd have more to say on this next time.
 === Breaking Up Templates === === Breaking Up Templates ===
 +Pull request [[https://github.com/vufind-org/vufind/pull/892|#892]], breaking up SideFacets, is still in progress.
 === Channels === === Channels ===
 +Pull request [[https://github.com/vufind-org/vufind/pull/693|#693]] is still awaiting some final discussion about cosmetic adjustments.
 === Modularization === === Modularization ===
 +No news.
 === Next ZF Version === === Next ZF Version ===
 +Significant progress has been made in refactoring to prepare for ZF3 components, and the ZF community has made some helpful new releases. We are still waiting on some movement from the ZF side, however, and right now ongoing work is in progress to upgrade zend-mvc (see pull request [[https://github.com/vufind-org/vufind/pull/900|#900]]). With a large number of changes being made throughout the code, please be especially alert for bugs and strange behavior in the coming weeks.
 === Improved Use of Permissions === === Improved Use of Permissions ===
 +There has been some renewed discussion about this on PR [[https://github.com/vufind-org/vufind/pull/608|#608]], though no major code progress yet.
 === Solr 6 === === Solr 6 ===
 +A significant performance bug in the latest Solr 6 has been reported; we should not merge this until that has been resolved. A note has been added to PR [[https://github.com/vufind-org/vufind/pull/869|#869]].
 === Deprecation Progress === === Deprecation Progress ===
 +No news.
 === 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 was agreed upon.
 ==== 3. VuFind Usage Survey ==== ==== 3. VuFind Usage Survey ====
 +The survey has been opened [[https://www.surveymonkey.com/r/P8Z97YV|here]]. Please participate if you have not already done so.
 ==== 4. Institutional Home ==== ==== 4. Institutional Home ====
 +No news.
 ==== 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.1487080058.txt.gz · Last modified: 2017/02/14 13:47 by demiankatz