Differences

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

--- dev:meetings:2009-10 [2009/10/09 09:29] – added line item for meeting planning erickson
+++ dev:meetings:2009-10 [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== IRC developer meeting for October 2009 ======
-Please add agenda items here:
+See also: [[:dev:meetings:2009-10:minutes|Meeting Minutes for October 2009]]
+**Agenda:**
   * 1.6 release status
     * Status of reported bugs (mailing list & [[http://svn.open-ils.org/trac/ILS|Trac]])
-      * George's reported acq bugs
+      * George's reported acq bugs [[http://markmail.org/message/sigdiicqsxi5ds2d]]
-      * Repke's Vandelay attempts (might just be "no support for that yet")
+      * Repke's Vandelay attempts:
-      * ... ?
+        * Authority record import [[http://markmail.org/message/fu7lvbft5ku3grip]]
+        * Importing MFHD monographic holdings records separate from bibliographic records
+      * Invalid date of birth: [[http://markmail.org/message/afhfpsb2osh4qron]]
+      * Conify (particularly Hours of Operation and Addresses) - [[http://svn.open-ils.org/trac/ILS/ticket/68|Trac Ticket #68]]
+      * others ... ?
+      * Aside: we should post a response to a bug posted on the mailing list if the reported bug is fixed, even if we also enter that bug in the bug tracker; with a link to the pertinent commit + bug
     * OpenSRF - we need to cut an OpenSRF release to match Evergreen 1.6 (but wait... shouldn't that be tested first? OH NOES!)
     * Translations - put out a call after 1.6.0, roll translations into 1.6.1?
+  * Outstanding patches:
+    * Bookbag-as-RefWorks from Warren Layton, August 4th (http://markmail.org/message/xnn3ls5fxmaysgzv)
+  * Lowering the barriers to participation
+    * There haven't been many patches submitted from outside of the committer team - are there things that we can do to increase participation from the rest of the community?
+  * Bug tracking and QA
+    * Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness?
+    * Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad
   * Release process
@@ Line 16: / Line 33: @@
       * Devs can do DVCS model today on their own branches, but would be nice to have a single repo that holds all of the branches - or perhaps at least a list of all the different locations that branches are hosted (github, launchpad, google code)
-  * Bug tracking and QA
+  * Acquisitions (based on the survey, there was a strong interest in talking about acquisitions)
-    * Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness?
-    * Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad
+  * oils_i18n_gettext, and all those untranslated things inserted into tables in 950.data.seed-values.sql without the pinned primary key values that oils_i18n_gettext needs
   * Future development
     * What's shaking in the near future?
     * Any long term projects that we need to start laying the groundwork for now?
+      * Telephony
+    * Status of Craftsman and continued support/development?
   * Monthly IRC Development meetings (re: Grace's survey to open-ils-dev)
     * roles