About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


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

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
developers_call:minutes20121211 [2012/12/11 15:42] demiankatzdevelopers_call:minutes20121211 [2012/12/11 15:46] demiankatz
Line 35: Line 35:
  
 Demian and David have continued discussing the best way to manage VuFind components in Git; the idea of using submodules has been ruled out due to the extra complexity it introduces for users who are not Git experts.  Instead, Demian plans to try the subtree merge strategy to pull components into a single large Git repo -- he will try a proof-of-concept integration of the VuFindHttp module when time permits. Demian and David have continued discussing the best way to manage VuFind components in Git; the idea of using submodules has been ruled out due to the extra complexity it introduces for users who are not Git experts.  Instead, Demian plans to try the subtree merge strategy to pull components into a single large Git repo -- he will try a proof-of-concept integration of the VuFindHttp module when time permits.
 +
 +There was some discussion of whether VuFind 2.0 will be more usable as an API than 1.x.  Demian proposed mapping out AJAX calls, looking at where existing URLs can be reused with content negotiation in place of custom AJAX module calls, etc.  Benjamin volunteered to investigate whether he can find resources on his end to start drafting something.
  
 ==== 3. Linked Data ==== ==== 3. Linked Data ====
developers_call/minutes20121211.txt · Last modified: 2015/12/14 16:42 by demiankatz