On the previous pull request, we talked about different policies/strategies for where to house device adapters. Advantages of keeping them in the Micro-Manager (MM) organization are easier accessibility for users, ability to make coordinated changes across devices, and potential bundling with the MM installer. Advantages of developing some adapters outside the MM org include more flexibility for experimental designs, easier integration with specialized third-party software, and lower barrier for contributions from the community.
Given these considerations, what should be the official guidance on where to develop and house Python device adapters?
On the previous pull request, we talked about different policies/strategies for where to house device adapters. Advantages of keeping them in the Micro-Manager (MM) organization are easier accessibility for users, ability to make coordinated changes across devices, and potential bundling with the MM installer. Advantages of developing some adapters outside the MM org include more flexibility for experimental designs, easier integration with specialized third-party software, and lower barrier for contributions from the community.
Given these considerations, what should be the official guidance on where to develop and house Python device adapters?