= Attendees =

* Eric, Greg, TomG, Elaine, Conrad, TomF, Scooter

= Agenda =
* Action items
* Chimera
  * 1.13.1 release
* ChimeraX
  * [wiki:Wildcards Wildcard/regex/case matching in atomspec] (Eric)
  * RBVI bundles on toolshed
  * Documentation strategy

= Discussion =
* Chimera 1.13.1
  * Changes include - fixing
    - proline rotamer
    - align chains
    - independent rotation in scenes
    - vina command argument documentation
    - vina command/gui inconsistency
    - local executables with whitespace in path
    - major addh bug fix
  * Linux installation instructions still inaccurate (installer name wrong, [http://plato.cgl.ucsf.edu/trac/chimera/ticket/16418 ticket])
  * Hold off on release for next macOS release
    - Eric is working on getting Tk 8.6.8 to work correctly on Mac
* ChimeraX
  * Move to Python 3.7
    - Update to latest numpy
    - Update to latest msgpack using pip (if possible)
  * Need to move to PyQt5 5.11 (after Python 3.7) to get Vulkan support
    - Windows installer does not build
    - After 3.7
  * Putting RBVI bundles on toolshed
    - Proposal (Conrad)
      - Sync built wheels to plato repository in {{{make}}} process
      - Repository only keeps wheels from last X months ("if you don't release it in X months, you won't release it")
      - Provide web page to display "released" and "unreleased" bundles in repository and allow (authenticated) users to mark selected bundles for release
      - Provide {{{make}}} target to release all bundles to toolshed when making a release
      - Extract documentation when bundle is released and install as web pages (see below)
      - All functionality can be provided through toolshed code and made available via URLs
  * Documentation and tutorial strategy
    - Bundle-specific documentation should be placed into {{{docs}}} directory in package
    - Very rough proposal (Conrad)
      - Move all documentation into bundle {{{docs}}} directories
      - Change top-level docs directory to:
        * developer (manually edited docs)
        * user
          - non-bundle (manually edited docs, e.g., tutorials, indices, intro, etc.)
          - bundle (generated symlinks to bundle {{{docs}}} directories )
            * easier (web) access when editing
            * provide Makefile for git management, e.g., commit changes
      - ChimeraX documentation web pages on plato get updated as part of releasing a bundle
        * What about developer versions?
        * What about core documentation?  Is core a bundle on toolshed?  Can it really be updated through the toolshed?

= Action Items =
* Conrad will create ticket listing stable APIs