I think it's tricky to manage an open source community effectively while still being opinionated on the product. I don't want to get too sucked into coordinating adhoc contributors - we do have a strong core team of people, and we all live together, which is pretty important. But yea, still figuring out what the right dynamic here will look like. Thanks for the suggestions!
That's fair, especially around firmware and things like OTA updates and lower level controls/safety you'd want to keep that closer to team.
But on the long-tail of autonomy options? Implementing the latest papers, trying cutting edge solutions, I bet a thriving open-source community could be very helpful ala PR2, given that the hardware is already open-source.
Nothing stopping you from picking and choosing from the various implementations to build into a streamlined product offering on the front end.
Yep I definitely agree. Our team is pretty small and bandwidth limited
I basically think our goal is to solve all the boring stuff and make it work reliably, so that other can people can try out the cool ML stuff more easily
