Future of Autopilot #4

New Issue

Open

opened 2022-10-10 22:19:14 +00:00 by jonny · 1 comment

jonny commented

2022-10-10 22:19:14 +00:00

Owner

What is to happen with Autopilot?

Can I say that "Autopilot is joining forces with miniscope" and in public describe them as joint projects?
Will I be able to dedicate time to maintaining and improving Autopilot, resolving bugs on it, etc? I don't want to abandon the project, but I also want to focus on the current project (which likely will circle back to autopilot anyway)
Should we develop a miniscope class for autopilot? (this seems relatively simple to me, as it seems like it uses standard linux camera drivers?)
Should we port any of Autopilot's work on eg. documentation over to miniscope?
Should we merge governance systems, if any? I'm interested in inviting existing collaborators to be co-equal maintainers of Autopilot, would they also be on the miniscope team?

What is to happen with Autopilot? - Can I say that "Autopilot is joining forces with miniscope" and in public describe them as joint projects? - Will I be able to dedicate time to maintaining and improving Autopilot, resolving bugs on it, etc? I don't want to abandon the project, but I also want to focus on the current project (which likely will circle back to autopilot anyway) - Should we develop a miniscope class for autopilot? (this seems relatively simple to me, as it seems like it uses standard linux camera drivers?) - Should we port any of Autopilot's work on eg. documentation over to miniscope? - Should we merge governance systems, if any? I'm interested in inviting existing collaborators to be co-equal maintainers of Autopilot, would they also be on the miniscope team?

jonny added this to the Project Details project 2022-10-10 22:19:14 +00:00

jonny referenced this issue

2022-10-10 23:45:56 +00:00

Lab Infrastructure/Intra-Lab Coordination #5

jonny added the

detail

label 2022-10-10 23:46:37 +00:00

jonny added the

question

label 2022-10-10 23:49:26 +00:00

jonny referenced this issue

2022-10-11 00:48:28 +00:00

Scope of Work #1

daharoni commented

2022-10-11 04:26:49 +00:00

Collaborator

We should discuss this over zoom but here are my quick thoughts:

Can I say that "Autopilot is joining forces with miniscope" and in public describe them as joint projects?
Yes, I think some version of this would be great for both projects. We need to think about what this would look like in reality in terms of "joint" projects.
Will I be able to dedicate time to maintaining and improving Autopilot, resolving bugs on it, etc? I don't want to abandon the project, but I also want to focus on the current project (which likely will circle back to autopilot anyway)
Sure. As long as this isn't a huge timesink I wouldn't have any issue at all.
Should we develop a miniscope class for autopilot? (this seems relatively simple to me, as it seems like it uses standard linux camera drivers?)
We should discuss this in detail. I think there is the potential for building out future Miniscope DAQ platforms within the Autopilot ecosystem. Maybe something larger than either of these projects can come out of combining them.
Should we port any of Autopilot's work on eg. documentation over to miniscope?
Again, this is worth discussing in detail. My thoughts are that I want to basically start from scratch with all things Miniscope at this point. In other words, I want to leave the current V4 Miniscope project more-or-less where it is now and rethink how we do everything for new projects going forward.
Should we merge governance systems, if any? I'm interested in inviting existing collaborators to be co-equal maintainers of Autopilot, would they also be on the miniscope team?
Let's chat about this. I am a bit protective of the Miniscope "brand" so would need to figure out exactly what this would look like.

We should discuss this over zoom but here are my quick thoughts: * Can I say that "Autopilot is joining forces with miniscope" and in public describe them as joint projects? Yes, I think some version of this would be great for both projects. We need to think about what this would look like in reality in terms of "joint" projects. * Will I be able to dedicate time to maintaining and improving Autopilot, resolving bugs on it, etc? I don't want to abandon the project, but I also want to focus on the current project (which likely will circle back to autopilot anyway) Sure. As long as this isn't a huge timesink I wouldn't have any issue at all. * Should we develop a miniscope class for autopilot? (this seems relatively simple to me, as it seems like it uses standard linux camera drivers?) We should discuss this in detail. I think there is the potential for building out future Miniscope DAQ platforms within the Autopilot ecosystem. Maybe something larger than either of these projects can come out of combining them. * Should we port any of Autopilot's work on eg. documentation over to miniscope? Again, this is worth discussing in detail. My thoughts are that I want to basically start from scratch with all things Miniscope at this point. In other words, I want to leave the current V4 Miniscope project more-or-less where it is now and rethink how we do everything for new projects going forward. * Should we merge governance systems, if any? I'm interested in inviting existing collaborators to be co-equal maintainers of Autopilot, would they also be on the miniscope team? Let's chat about this. I am a bit protective of the Miniscope "brand" so would need to figure out exactly what this would look like.