Attendees

• Eric, Greg, TomF, Conrad, Scooter, Elaine

Agenda

• Action items
• ChimeraX
  • Tabbed toolbar
  • Manager/provider toolshed functionality (#1661)
  • Discuss 0.9/1.0 feature set
  • RBVI bundles on toolshed
    • Change build process to trim down list of bundles in standard release while still testing toolshed-only bundles
  • Stable APIs, #922
  • Documentation strategy
  • 1.0 features (roadmap)
• Possibilities for Eric's SOW

Discussion

• ChimeraX
  • Tabbed toolbar
    • Add comments to toolbar-unification
    • Tabbed interface now includes changes discussed 04/01/2019
    • Elaine is updating icons for transparency
  • Manager/provider toolshed functionality (#1661)
    • Conrad committed
    • Parts of preset functionality uses this
    • Need HTTP scheme manager for PyQt 5.12
      • Conrad will implement the manager and initial providers
      • Whoever does the PyQt 5.12 migration will use the data
  • Discuss 0.9/1.0 feature set
    • See Roadmap
  • Putting RBVI bundles on toolshed
    • Want separate run-time vs build-time dependencies in bundle_info.xml
    • Visit the bundle-release page (from intranet) and release your bundles
    • Need to segregate "standard" bundles from "extra" bundles
  • What happens when restoring a session that uses an uninstalled tool?
    • There is a manifest of bundles referenced by session file
    • Need to detect missing bundles
      • Show warning or offer to install bundle?
      • Restore rest of session or give up or ask user?
      • What about gui vs nogui?
        • Currently, tools are skipped in nogui mode
        • Might get unnecessary warning about missing bundle that won't be used for restoring session in nogui mode
  • Stable APIs
    • See action items
  • Move to github
    • Move to private RBVI github project
      • Easier to share with collaborators with github admin tools
      • "pull requests" should simplify enhancement/fix submission
      • will not happen that soon

Action Items

• Conrad will create ticket for extending mmCIF writing to include missing tables
• Conrad will create tickets for BUGS listed above (if they don't already exist)
  • for the first one, see ChimeraX #1021 and possibly #1489 (and Chimera tickets 325 and possibly 10113 and 12200 are all along these same lines, of which 325 is a more specific description of secondary structure information loss)
  • Elaine: wwPDB deposition instructions say nothing about secondary structure. Conclusion: it must be generated after deposition by the wwPDB semiautomated annotation pipeline, so these info-loss bugs are mainly trouble for users who write PDB/mmCIF for reasons other than deposition.