| | 1 | = Attendees = |
| | 2 | |
| | 3 | Eric, TomG, Greg, Zach |
| | 4 | |
| | 5 | = Agenda = |
| | 6 | * Action items |
| | 7 | * ChimeraX |
| | 8 | - Should PyPi prereqs be updated before 1.3 release? |
| | 9 | - Should cxservices be in prereqs? bundles? or with backend server code? |
| | 10 | - Ask to register only once -- has this been implemented? |
| | 11 | - Update 1.3 release roadmap, adding completed stuff, moving other stuff to 1.4. |
| | 12 | - Programmer doc string formats and sphinx extensions #5120, Zach |
| | 13 | - Task termination at app quit |
| | 14 | - VirtualGL documentation #4783 |
| | 15 | - Rename ChimeraX.exe on Windows? |
| | 16 | - Should we remove the HTML tool tutorial and promote only Qt GUIs? |
| | 17 | * Chimera |
| | 18 | |
| | 19 | = Discussion = |
| | 20 | |
| | 21 | * Should PyPi prereqs be updated before 1.3 release? |
| | 22 | - Greg thinks more frequent PyPi updates desirable. |
| | 23 | - Tom and Eric suggest that updates once every 6 months after a ChimeraX release are best use of our resources. |
| | 24 | - Zach suggests that continuous integration could allow more frequent PyPi package updates with a test suite to catch newly introduced problems. |
| | 25 | - Tom thinks we have a very inadequate test suite, and a better test suite is worth some effort. |
| | 26 | - Zach mentioned github dependency updating, https://dependabot.com |
| | 27 | - Decided we will stick to one round of PyPi updates soon after ChimeraX releases. |
| | 28 | - Specific PyPi packages can be updated at other times as need arises (e.g. Tristan needs OpenMM update). |
| | 29 | |
| | 30 | = Action Items = |
| | 31 | |
| | 32 | * Make ticket for ChimeraX to only ask to register once. Eric |
| | 33 | * Put download web page checksums on separate page. Zach |
| | 34 | * Ask to register only once - Greg. |
| | 35 | * Add 1.3 goals to roadmap for next group meeting - Everyone. |
| | 36 | * Make Windows build redirect installer build to separate log so password not shown - Greg. |