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

This is an old revision of the document!


VuFind Developers Call Minutes: January 22, 2013

Attending:

Agenda

1. New/Updated JIRA Tickets

  • VUFIND-276 - The VuFind 2.0 version of the feedback module patch has continued to evolve.
  • VUFIND-294 - The VuFind 2.0 MySQL database now uses UTF-8 instead of Latin-1 text encoding for more consistent functionality.
  • VUFIND-340 - Improved password security has been committed for VuFind 2.x.
  • VUFIND-630 - Demian has posted some notes here about a Windows-only bug related to Wikipedia parsing; a workaround has been found, though the ticket is still open since there are several possible long-term resolutions. Eoghan has proposed linking to the ticket from Windows install documentation, external content page, config.ini and/or the 2.x auto-installer.
  • VUFIND-631 - Lists now correctly populate the “created” field in the database when inserted (ticket closed).
  • VUFIND-643 - More progress has been made on the 2.0 version of the MultiBackend ILS driver.
  • VUFIND-659 - Demian has done some further investigation and added comments to this ticket (about problems with time zone inconsistencies when tracking record changes in the database).
  • VUFIND-732 - This ticket was spam and has been deleted.
  • VUFIND-733 - This ticket includes some install controller functionality to upgrade VuFind 2 to use secure passwords. It has been committed along with VUFIND-340.
  • VUFIND-734 - This task ticket was a reminder to try to find a way to validate Javascript as part of continuous integration so that we can improve our JS code quality – now completed.
  • VUFIND-735 - This is another ticket related to David's search system refactoring.
  • VUFIND-736 - This ticket has split off some notes that were not specifically resolved when VUFIND-340 was closed: VUFIND-340 solves password storage security issues, but there are still open questions about transmission security when SSL is not enabled.
  • VUFIND-737 - This ticket addresses some bugs in VuFind's spelling tokenizer (now fixed in 1.x/2.x code bases).

2. VuFind 1.4 Update

3. VuFind 2.0 Update

Some improvements have been made to continuous integration for better coverage of the multiple modules that make up VuFind 2.0 (previously only the main VuFind glue module was being covered).

Demian has updated wiki links in the code in an effort to make the auto-generated documentation slightly more accurate. There's still room for improvement in documentation tagging and linking, but at least 2.x code should no longer be pointing to 1.x docs.

As mentioned on the previous call, the module.config.php file has been rearranged to get VuFind-specific settings out of the global configuration namespace.

As noted in JIRA tickets above, password security improvements have been committed (with significant help from Kyle McGrogan).

As noted above, VUFIND-294 has been resolved, so the MySQL database is now UTF-8 encoded.

4. Continuous Integration

Demian has upgraded the Jenkins continuous integration server to the latest version; this does not seem to have caused any problems.

The VuFind 2 job has been enhanced with some new features:

  • PHP copy-and-paste detection (to identify duplicate code)
  • Charts of phploc outputs (to measure project growth)
  • PHP_Depend data (to measure various software metrics)
  • PHPMD (“mess detector” for warning about potentially problematic code)
  • jslint provides style compliance warnings about Javascript code (merged into the same style graph used for PHP issues)

All of this will make builds take a bit longer, but it will provide a lot more information within Jenkins and should help us further improve the code.

If anyone wants to work on reducing some of the warnings and problems currently showing, feel free to submit pull requests/patches to Demian. In at least some cases, warnings can be safely ignored (i.e. base class for ILS drivers has many children) and the fix is simply to add an appropriate annotation to the code.

Demian has disabled Sonar on the VuFind 1.x continuous integration process – it was taking up significant server resources but was never being used for anything; the new 2.x process does not require Sonar.

Also in the interest of freeing up more resources for continuous integration, Demian has also turned off the “demo_trunk” instance at vufind.org, as this was outdated and no longer necessary.

5. Linked Data

6. Other Topics?

Next Call

The next call will be Tuesday, February 5, 2013 at 10am Eastern Standard Time (15:00 GMT).

developers_call/minutes20130122.1358516389.txt.gz · Last modified: 2014/06/13 13:13 (external edit)