Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20160412
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
developers_call:minutes20160412 [2016/04/12 13:12] – [VuFind Developers Call Minutes: April 12, 2016] demiankatz | developers_call:minutes20160412 [2016/04/12 13:45] – [4. Other Topics?] crhallberg | ||
---|---|---|---|
Line 55: | Line 55: | ||
- Fix the "two search boxes for responsiveness" | - Fix the "two search boxes for responsiveness" | ||
- Settle on code styling (see [[https:// | - Settle on code styling (see [[https:// | ||
+ | |||
+ | André would like to do more work with Grunt and hopes to look into it in a month or so. Work on updating the Foundation5 theme is underway; the branch will be updated to match release-3.0 in the near future. | ||
=== API === | === API === | ||
+ | |||
+ | No news. | ||
=== Modularization === | === Modularization === | ||
+ | |||
+ | No news. | ||
=== Next ZF Version === | === Next ZF Version === | ||
+ | |||
+ | No news. | ||
=== Improved Use of Permissions === | === Improved Use of Permissions === | ||
+ | |||
+ | No news. | ||
=== Improved Geographic Features === | === Improved Geographic Features === | ||
+ | Some discussion by email after last call. Next steps: add geographic fields to Solr schema and standardize map display to use OpenLayers instead of Google Maps. Leila will begin working on some of this soon (new geographic project with a 3.0 base) and will probably have more to say next time. | ||
==== 4. Other Topics? ==== | ==== 4. Other Topics? ==== | ||
+ | === Git PR Tagging === | ||
+ | |||
+ | Chris brought up the idea of standardizing our pull request labels so we can better keep track of when things are expected to be merged, who is supposed to be taking next steps, etc. | ||
+ | |||
+ | Starting point: bug fix vs. new feature vs. discussion. | ||
+ | |||
+ | One common pattern: tagging based on component (e.g. front-end vs. back-end) or technology (PHP vs. Javascript). | ||
+ | |||
+ | One specific scenario: PR is submitted, but submitter never follows up on Demian' | ||
+ | |||
+ | After looking at the [[https:// | ||
+ | |||
+ | * **awaiting reply** - The VuFind dev team eagerly await the submitter' | ||
+ | * **breaking** - This PR contains code that will likely cause some backwards compatibility problems. | ||
+ | * **bugfix** - This branch deals with fixing a found bug. | ||
+ | * **discussion** - Your opinion would be greatly appreciated! | ||
+ | * **improvement** - Code focused on improving a currently existing feature. | ||
+ | * **new feature** - Code focused on exploring new areas of functionality | ||
+ | * **on hold** - This branch has to wait for something, usually another PR or something out of our control (ZF3). | ||
+ | * **question** - An answer from the VuFind dev team is eagerly awaited. | ||
+ | |||
+ | When using these tags, including a comment or a description that explains the status is welcome and encouraged (especially with on hold and breaking). | ||
===== Next Call ===== | ===== Next Call ===== | ||
developers_call/minutes20160412.txt · Last modified: 2016/04/21 12:56 by demiankatz