Differences

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

--- community_call:minutes20230207 [2023/02/07 14:49] – [3. Open Q&A / Other Topics?] demiankatz
+++ community_call:minutes20230207 [2023/02/07 14:52] (current) – [1. Development Planning] demiankatz
@@ Line 35: / Line 35: @@
   * [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1568|VUFIND-1568]] - Make Solr port configurable during installation [assigned to DK]
-    * Demian proposes pushing to 9.1
+    * Following discussion, it was agreed to push this to the 9.1 milestone.
   * [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1541|VUFIND-1541]] - Add Mink test coverage for Markdown rendering [assigned to CH]
-    * Demian proposes pushing to 9.1
+    * Following discussion, it was agreed to push this to the 9.1 milestone.
   * [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1547|VUFIND-1547]] - Normalize search event namespace [unassigned]
-    * Demian proposes pushing to 10.0
+    * Following discussion, it was agreed to push this to the 10.0 milestone.
   * [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1566|VUFIND-1566]] - Clean up/standardize Javascript lib directory [assigned to CH]
   * [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1593|VUFIND-1593]] - Ensure JSON encoding of strings embedded in HTML is properly escaped [unassigned]
@@ Line 51: / Line 51: @@
   * [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1396|VUFIND-1396]] - Investigate possibility to deprecate the Context view helper
+    * This was moved to the 10.0 milestone prior to the call, following Ere's investigation. He found that this cannot be easily removed at this time, but could likely be factored out as part of the development of our next theme.
 ==== 2. Technology Discussion: Doctrine Migration ====
 Demian highlighted the need to migrate to a different database abstraction layer. His presentation was recorded and will be shared in the near future.
+After the recording, Peter asked whether automated tools could be used to help with the migration work. Demian noted that an auto-generation tool was used successfully to generate Doctrine entities for the existing database, but that deeper porting of the code would be quite difficult to automate.
+Mario also suggested that, while Demian suggested the possibility of using a ->toArray() method on Doctrine entity classes to allow more consistent use of array formatting in templates, there are significant advantages to sticking with objects, since this could enable, for example, easier refactoring via IDEs if data element names change, etc.
 ==== 3. Open Q&A / Other Topics? ====