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:minutes20140916

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:minutes20140916 [2014/09/16 14:29] – [VuFind Developers Call Minutes: September 16, 2014] demiankatzdevelopers_call:minutes20140916 [2016/04/07 15:14] (current) milenakrakowiy
Line 54: Line 54:
  
 Note one significant exception to the rule: right now, most Search\Options, Search\Params and Search\Results objects are constructed through AbstractPluginFactory classes rather than through explicit configuration. Assuming we decide to eliminate the majority of abstract factories, should we reconfigure this, or continue to use the abstract factories in this special case? Note one significant exception to the rule: right now, most Search\Options, Search\Params and Search\Results objects are constructed through AbstractPluginFactory classes rather than through explicit configuration. Assuming we decide to eliminate the majority of abstract factories, should we reconfigure this, or continue to use the abstract factories in this special case?
 +
 +There was no objection to the basic idea, so Demian will put together a pull request for app review submission service appreviewsubmit.com and submit it to vufind-tech before merging it to master.
  
 === Should we split out stand-alone libraries? === === Should we split out stand-alone libraries? ===
  
 Demian is thinking about whether it makes sense to move portions of VuFind to their own GitHub projects for ease of reuse. Right now, he is considering splitting out the \VuFind\Code\ISBN class to its own \VuFindCode\ISBN project as a trial. This would then be loaded into the vendor directory with Composer in the main VuFind project instead of being part of the core VuFind module. The project could be given its own continuous integration page. Since this particular class is fairly stable, this is unlikely to add a major development burden. Moving some of the more volatile pieces (like the VuFindSearch module) might add greater complexity to project management, but is still worth considering. Demian is thinking about whether it makes sense to move portions of VuFind to their own GitHub projects for ease of reuse. Right now, he is considering splitting out the \VuFind\Code\ISBN class to its own \VuFindCode\ISBN project as a trial. This would then be loaded into the vendor directory with Composer in the main VuFind project instead of being part of the core VuFind module. The project could be given its own continuous integration page. Since this particular class is fairly stable, this is unlikely to add a major development burden. Moving some of the more volatile pieces (like the VuFindSearch module) might add greater complexity to project management, but is still worth considering.
 +
 +If Demian finds time, he will try to set up a VuFindCode project and see how difficult the process is. Once that is done, he will share it with vufind-tech and the determination can be made whether or not it's worth pulling it in as a vendor dependency or maintaining the current code as-is.
 ==== 3. 2014 VuFind Summit ==== ==== 3. 2014 VuFind Summit ====
  
 Some cosmetic fixes still need to be made to adjust some outdated text, but the [[http://vustuff.org/vustuff/vufind-summit-2014-registration|registration page]] is now functional. This will be more widely announced as soon as the finishing touches are in place. Some cosmetic fixes still need to be made to adjust some outdated text, but the [[http://vustuff.org/vustuff/vufind-summit-2014-registration|registration page]] is now functional. This will be more widely announced as soon as the finishing touches are in place.
 +
 +If you propose a talk and have the proposal accepted, you can get in free -- no need to register. Submit proposals to Demian. We currently have at least three talks slated.
 ==== 4. Other Topics? ==== ==== 4. Other Topics? ====
  
 +No other topics this week.
 ===== Next Call ===== ===== Next Call =====
  
Line 68: Line 75:
  
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20140916.txt · Last modified: 2016/04/07 15:14 by milenakrakowiy