== December 4, 2008 ==
'''Attendees''': tef, Elaine, Greg, Eric, Conrad

=== New Action Items ===

 - Tom will update library course description (item 1)
 - Elaine will compose a message for chimera-users list describing the features to be removed in a post-1.3 release (item 2, already done!)
 - Elaine will compose a message announcing release 1.3 (item 2)
 - Tome will investigate updating numpy to 1.2.1 (item 4)
 - Eric will investigate matplotlib (item 4)

=== Previous Action Items ===

 - Conrad, Eric, Greg and Scooter have tasks for Chimera production release and conversion to svn/trac
  * convert from cvs to svn
  * convert from gnats to trac
  * create account for Wei to access svn/trac
 - Conrad will look into disabling stereo in orthographic view
 - Al will decommission SGI after the next Chimera production release
 - Al will install stereo-capable workstation to replace SGI before decommissioning SGIs
 - tef will contact Adobe for more information about embedding 3d graphics in PDF documents

=== Minutes ===

 1. Previous Action Items
  - Scooter sent out mail regarding the Spring library course.  Tom will check to make sure that his session description has been updated.
  - Elaine volunteered (thank you) to write both feature removal and 1.3 announcements.  Everyone agreed that on the web site, the 1.3 announcement should be later so that it stays at the top of the news items list.  For e-mail, the 1.3 announcement should go out first on chimera-announce and chimera-users; the feature removal announcement will go out afterwards only on chimera-users.

 2. Release 1.3 status (All)
  - The AddIons bug needed fixed both in Chimera and in sleap.  There is no point in making just the Chimera fix since there is no simple way to tell how much benefit it may be.  Everyone agreed that it would be best to back AddIons out of 1.3 (do not add it to the Tools menu; update the documentation to include line at top saying feature is not available yet in 1.3; and update the release notes to remove mentioning AddIons as a new feature).
  - Since AddIons is not going in, Greg's KDE fix (for "ugly" fonts in widgets) will not go in either.
  - 1.3 final will be made on Monday.  Once it's on the download page, the announcement can go out on the mailing lists and Chimera home page.

 3. What features/fixes make it into 1.3, 1.3.1, 1.4? (Conrad)
    * AddIons, KDE font, ...
  - Everyone agreed that if there will be a 1.3.1 release, it would be made soon (a few weeks) after 1.3.  The consensus is to evaluate each bug fix individually at this meeting to decide whether the fix warrants a 1.3.1 release.  Everyone should keep a list of bug fixes for the next few weeks so that, in case there is a 1.3.1 release, we can discuss which ones will go into 1.3.1.
  - If there are no critical bug fixes in the next few weeks, we start telling users to try out the daily build instead of waiting for 1.3.1.

 4. Addition of matplotlib to distribution (Conrad)
  - Conrad reported that matplotlib takes approximately 20MB on the Mac when installed.  (After the meeting we discovered that it's about 6MB compressed.)
  - Eric will investigate using matplotlib for the dynamics trajectory time plot analysis.  However, to install matplotlib, we need numpy 1.1 or newer.  Tom volunteered to update numpy to 1.2.1.

 (tef had to leave for another meeting at this point.)

 5. How to support third-party extensions (Eric, Tom)
  - There were three proposals (in no particular order) to aid third-party developers make their extensions available to users:
   a. Actively query developers whether they want to include their extension in the Chimera distribution.  We do little to no checking.  If users report that an extension is broken, we remove it from the distribution. (Tom)
   b. Query developers (either actively or passively through documentation in Chimera or on web site) whether they want to include a pointer to their software in the Chimera distribution.  A new Chimera extension will show users what third-party extensions are available and provide URLs to those packages. (Eric)
   c. Develop a mechanism modeled on Firefix AddOns.  Developers will register as Chimera extension developers and then have access to web forms for putting their extensions in a repository.  Chimera will be augmented with a mechanism for automatically downloading extensions, installing them, and making them available to the user. (Conrad)
  - There was serious disagreement on how much effort each one involves, how much payoff, whether the mechanism scales, whether it needs to scale, time frame for implementation, probability of success, etc.
  - It was decided that we discuss this again with tef and Scooter present.