Differences

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

--- dev:meetings:2009-10:minutes [2009/10/16 17:37] – up to 11:03:45 wlayton
+++ dev:meetings:2009-10:minutes [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 72: / Line 72: @@
     * **ACTION:** Dan Scott (dbs) to add Warren Layton's export-bookbags-to-RefWorks patch to the rel_1_6 branch
   - Lowering Barriers to Participation
+    * Dan Scott (dbs) is preparing material for an Evergreen development workshop at FSOSS 2009, which might be useful
+      * Dan would like more eyes and contributors, if possible, to expand on his workshop for general use
+    * Chris Sharp (chrissharp123) also noted that materials from the Evergreen 2009 Conference might also be helpful
+      * Specifically, Chris mentioned berick's, miker_'s, and dbs's presentations could be transformed into documentation
+      * Dan Scott also suggested getting some specific requests for developer-focused sessions/workshops at the Evergreen 2010 conference in place early
+    * Nathanael Schilling (natschil) noted that there's a list on the wiki called "How can I contribute to Evergreen" but that it's quite broad and should likely be revised
+    * Jeff Godin (jeff) offered to speak with others after the meeting to start creating some wiki page(s) to provide starting points and links to existing resources
+    * Warren Layton (wlayton) and James Fournie (jamesrf) mentioned that there was a lack of feedback for patches sent to the mailing list
+      * Bill Erickson noted that this is closely related to lowering the barrier to participation
+      * Jeff Godin (jeff) noted that going through the mailing list archive looking for uncommitted patches isn't a good way to handle things; would rather they make into Trac or something
+      * Dan Scott noted that it would be good if it was possible to generate a report of outstanding patches and keep discussion focused on a specific bug/feature
+    * Jeff Davis (twirlip) asked about switching to a bug tracker that lets non-contributors to submit bugs
+    * Jeff David (twirlip) also thought that a more detailed development roadmap would be helpful for participation
+    * Jeff Godin (jeff) suggested that core devs could "brain dump" on IRC on a semi-regular basis to help spread knowledge and increase participation
+    * **ACTION:** Jeff Godin (jeff) to post to create wiki page(s) for new developers (provide starting point, point to existing resources), and post to mailing lists with update during week of October 19-23
+  - Bug Tracking and QA
+    * David Fiander (djfiander) suggested giving out bug-filing privileges once a person has previously reported a real bug via email or IRC ("greylisting")
+    * Mike Rylander (miker_) suggested having 2 bug trackers: one "frontline" (e.g., launchpad) and one "on top of the code" (e.g., Trac)
+      * The frontline one could be more open but track actual, code-related stuff only in the on-top-of-the-code one
+        * Launchpad can integrate well with upstream projects, such as the Evergreen Trac instance
+    * Anoope Atre (moodaepo) suggested a bug DB manager to properly assign bugs and do triage
+    * Shawn Boyette (sboyette) noted that he is "the QA guy" at ESI and may be natural for him to volunteer to be the Bug Tracker Oversight Guy
+      * Jeff Godin (jeff) suggested a call be put out for a "QA team" of bug wranglers and testers, working with Shawn
+        * They would handle general bugs reports, migrate them "upstream" to the Trac instance (likely developing fixes for the bugs)
+        * They could also be "Whipcrackers", shoving developers to get things done and keep discussion about bugs/patches going
+    * Nathanael Schilling (natschil) noted he liked KDE's review board for bugs and patches, which can help avoid contentious patches
+    * It was decided that launchpad would be tried for a period of three months as the "writable-by-anyone bug system / translation system / feature request / code review / FAQ-development"
+    * **ACTION:** Shawn Boyette to post call for a QA team to -dev mailing list to help refine the details
+  - Release Process
+    * Shawn Boyette (sboyette) working on a buildbot, whose output will be publicly available. First phase of development near completion (end of October).
+      * Works with the GNU toolchain. Some other Evergreen-specific parts (e.g., building the tarball) exist "on the side"
+    * **ACTION:** (?) Shawn Boyette to make buildbot source publicly available, either on SVN's ILS-Contrib, or git repository
+  - Acquisitions
+    * Previously discussed for 1.6 agenda item. Skipped
+  - oils_i18n_gettext
+    * Deferred to mailing list for more discussion
+  - Future Development
+    * Craftsman has some outstanding bugs which Karen Schneider had documented
+      * Need to convert those documented bugs into actual bugs in Trac
+    * **ACTION:** Dan Scott (dbs) and Joe Atzberger (atz) to find Karen's documented Craftsman bugs and add to public bug tracking system
+  - Adjournment
+    * Jeff Godin (jeff) proposed that the meeting be adjourned.
+      * Encouraged people to post remaining "What's shaking in the near future? / Any long term projects that we need to start laying the groundwork for now?" to the openils-dev mailing list
+    * Meeting adjourned at 12:32 PM EDT.