About Features Downloads Getting Started Documentation Events Support GitHub

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

VuFind Documentation

Site Tools

You are here: start » developers_call » minutes20160412
Trace:
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.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
developers_call:minutes20160412 [2016/04/12 13:26] – [2. Development Planning] demiankatzdevelopers_call:minutes20160412 [2016/04/21 12:56] (current) – [4. Other Topics?] demiankatz
Line 77: Line 77:
  
 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. 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? ====+==== 3. Other Topics? ====
  
 === Git PR Tagging === === Git PR Tagging ===
Line 88: Line 88:
  
 One specific scenario: PR is submitted, but submitter never follows up on Demian's feedback, and Demian doesn't have time to fix it himself. Chris will look for a good precedent for naming for a tag for this situation. One specific scenario: PR is submitted, but submitter never follows up on Demian's feedback, and Demian doesn't have time to fix it himself. Chris will look for a good precedent for naming for a tag for this situation.
 +
 +After looking at the [[https://github.com/twbs/bootstrap/pulls?page=2&q=is%3Apr+is%3Aopen|Bootstrap repository]], Demian and Chris have proposed the following [[https://github.com/vufind-org/vufind/labels|labels]] and [[https://github.com/vufind-org/vufind/pulls|applied them accordingly]]:
 +
 +  * **awaiting reply** - The VuFind dev team eagerly await the submitter's feedback.
 +  * **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 =====
  
 The next call will be Tuesday, April 26, 2016 at 9am Eastern Daylight Time (13:00 GMT). The next call will be Tuesday, April 26, 2016 at 9am Eastern Daylight Time (13:00 GMT).
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20160412.1460467615.txt.gz · Last modified: 2016/04/12 13:26 by demiankatz