| | 27 | General |
| | 28 | - Move developer meetings to 2pm Monday and keep 2pm Thursday open for extra discussion |
| | 29 | - Python versioning philosophy: do we track versions? |
| | 30 | - Tom says AlphaFold back on 3.7, they seem uncompelled by updates |
| | 31 | - Zach says we should concentrate on interpreter features -- they're backwards compatible |
| | 32 | - Greg sees no reason to go to 3.10, but is excited by the 3.11 speedup. Zach agrees. |
| | 33 | - Eric points out that forwards compatibility doesn't hold for compiled modules |
| | 34 | - Greg says Bundle Builder has support for the limited API |
| | 35 | - Greg says limited API doesn't save a developer from the need to ensure compiler compatibility |
| | 36 | - PyObject layout could change, etc. |
| | 37 | - Would be good for us to use limited API if possible to reduce complexity |
| | 38 | - Toolshed bundles would work for multiple versions |
| | 39 | - Tom notes we have many dependencies that may not support 3.11 right off the bat |
| | 40 | - Python 3.9 EOL is October 2025 (3.7 is in June 2023) |
| | 41 | |
| | 42 | ChimeraX |
| | 43 | - Greg suggest making bundle builder into a build backend |
| | 44 | - toml support is experimental, shouldn't announce to external developers quite yet |
| | 45 | - Greg doesn't want hybrid builds in develop. Could do it in a branch for testing, but don't allow developers to opt in until it's ready. |
| | 46 | - Afraid of early adopters shooting themselves in the foot |
| | 47 | - setuptools upgrade a little more complex than {{{ from setuptools import distutils }}} |
| | 48 | - More sensible move core down next to the rest of the bundles |
| | 49 | - Have core participate in the dependency graph that we generate with the python script |
| | 50 | |
| | 51 | - PR order: |
| | 52 | - Move core down |
| | 53 | - Put core code in core/src |
| | 54 | - Make bundle builder a build backend |
| | 55 | - Won't do hybrid builds until ready for primetime |
| | 56 | |
| | 57 | - Removed from agenda: |
| | 58 | - What happens to ChimeraX Tasks at app quit (let's make a ticket) |
| | 59 | - Relevant to task manager |
| | 60 | - Rename ChimeraX.exe on Windows? (let's make a ticket) |
| | 61 | - Should we go to Python 3.10 in 1.5? |
| | 62 | - Zach put this on the agenda, says PyOpenGL-Accelerate has not been updated |
| | 63 | - The Python speed update is 3.11 |
| | 64 | - Could move to Qt OpenGL API |
| | 65 | - Tentatively 3.11 in 1.6 |
| | 66 | |
| | 67 | Chimera |
| | 68 | - Not going to touch Chimera as much as possible. |
| | 69 | - Could set up VMWare machine and use that to build ChimeraX on Windows 7 |
| | 70 | - Zach suggests QEMU |
| | 71 | - If we're going to move to Windows 10 should do it before it's not available anymore |
| | 72 | - Tom says we should just set up another Windows 7 machine if the current one dies |
| | 73 | - Cygwin near to releasing last Windows 7 version |
| | 74 | - Should do a disk level backup of Windows 7 machine |
| | 75 | |
| | 76 | - Removed from agenda: |
| | 77 | - Switch Chimera daily builds from Windows 7 to Windows 10 (let's make a ticket) |
| | 78 | |
| | 79 | - Implications of sunsetting Chimera |
| | 80 | - GROMACS support would probably break first |
| | 81 | - Tk toolkit needs another update |
| | 82 | - macOS support dicey |
| | 83 | |
| | 84 | Infrastructure |
| | 85 | - Trac much more stable than it used to be after BeeGFS upgrades |
| | 86 | - Eric notes 1 problem in the last 3 months |
| | 87 | - Still a good idea to upgrade the database but no longer life or death |
| | 88 | |
| | 89 | - Removed from agenda: |
| | 90 | - Upgrade Trac to mysql for better reliability. (let's make a ticket) |
![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
