Changes between Initial Version and Version 1 of 2019-11-14

Timestamp:

Nov 14, 2019, 1:09:26 PM (6 years ago)

Author:

Conrad Huang

Comment:

--

2019-11-14

@@ +1 @@
+== This is a summary of discussions relevant to ChimeraX that took place at some group meetings.==
+
+= Attendees =
+
+* Eric, Conrad, TomG, Elaine, Greg, TomF, Scooter
+
+= Agenda =
+* Action items
+* Chimera
+  * 1.14 release
+* ChimeraX
+  * MSC update
+  * More general REST interface
+  * Permissions on ChimeraX wiki
+  * Mechanism for updating from 1.0 to 1.1
+  * Remove "For everyone" option from bundle install
+  * 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)
+
+= Discussion =
+* Chimera
+  * 1.14 release
+    - Greg will rerun build after build machines are back up
+* ChimeraX
+  * MSC update
+    - Sent report, no response yet
+    - Need collaborators on medical imaging
+    - Added Phil's induced fit Maestro files
+  * More general REST interface
+    - Summary from earlier group meeting.
+    - Tristan's implementation is "over the top", including:
+      * registration that automatically pulls argument types from function
+      * GET queries return the list of registered functions
+      * Python client that will mimic the registered functions so client-side code looks very similar to server-side code
+    - Scooter ~~suggested~~ insisted that the implementation must support Swagger (now known as [https://github.com/OAI/OpenAPI-Specification OpenAPI]).  Python's [https://pypi.org/project/fastapi/ FastAPI] may be the perfect fit, but it is very heavyweight in terms of dependent packages.
+    - Need to investigate whether FastAPI is compatible with Tristan's approach (a real-life client).
+  * Permissions on ChimeraX wiki
+    - Should move ancient crud to archeological part of site
+    - Option 1:
+      - Adopt Chimera wiki permission plugin
+      - Move selected private links to protected area (are there any?)
+      - Open most of site
+    - Option 2:
+      - Move private stuff to another site (wiki, GoogleDocs)
+      - Open all of site
+    - Option 3:
+      - Move to github?
+  * Mechanism for updating from 1.0 to 1.1
+    - ~~Option 1: 1 site-packages for all versions, need to delete/update old bundles
+    - Option 2: 1 site-packages per version, need to install/copy old bundles.  Ask user if old version should be removed.
+      - Need safe mode.  Maybe automatic if last session failed to start.
+    - ~~Option 3: 1 site-packages per version, sys.path = new_personal:installed:old_personal:...
+    - ~~Option 4: do not use Python import statement; use toolshed.load_module (or something) to get modules
+    - Need decision before 1.0 release
+  * Remove "For everyone" option from bundle installation and add documentation on how admins can achieve the same effect.
+  * 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
+  * Stable APIs
+    - See action items
+  * Documentation strategy
+    - There is a "vdoc" make target that creates a user documentation tree using symlinks to doc files in bundle sources
+    - Need to make sure that vdoc is made daily, rsync'ed to plato, and web links to vdoc work right.
+    - Need to fix missing icons.  May need to run "make" somewhere else to create copies of icons in right places.
+  * 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 =
+  * Greg will take on documentation strategy tasks
+  * Scooter and Conrad will investigate moving wiki pages to private subtree
+