= Attendees =

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

= Agenda =
* Action items
* Chimera
  * 1.13.1 release
* ChimeraX
  * [wiki:Wildcards Wildcard/regex/case matching in atomspec] (Eric)
* ChimeraX 0.8 goals
* ChimeraX documentation
* ChimeraX toolshed

= 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
* 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
  * 0.8 roadmap
  * Documentation and tutorial strategy
    - Bundle-specific documentation should be placed into {{{docs}}} directory in package
    - Bundle-specific documentation should be kept in bundle
    - Question
      - Elaine: when updating documentation, how do you usually review the changes?
    - 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 to provide easier access when editing)
      - Change procedure on how ChimeraX documentation web pages are built on plato (see next topic)
  * Putting RBVI bundles on toolshed
    - Proposal (Conrad)
      - Sync built wheels to plato repository in {{{make}}} process
      - 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

= Action Items =
* ~~Conrad will create ticket for restarting on installing bundles that replaced shared libraries/DLLs that are currently in use
* ~~Conrad and Greg will figure out how to organize documentation so that the primary copy stays in bundles but editing is not too cumbersome
* Conrad will create ticket listing stable APIs