Thank you both for your support. I really love helping ArduPilot move forward and I hope that with this financial aid I can continue to do so.
Randy, regarding that additional role I would be glad to accept it, but, with transparency in mind, I would like to make the following points:
- I'm good with logic, I can do high level features without a problem. But my physics knowledge is limited. For example, I can look at logic in the AC_AttitudeControl or the AP_Motors libraries but doing a fix wouldn't be so easy for me.
- I have limited flying time as I live in the city and I don't have an easy way to get to flying spaces. I occasionally go to a farm where I have space to fly and I can increase the number of times I go there, but it's not close to me, so, for example, any urgent testing of a fix I wouldn't be able to do.
- I still have a lot to learn in log analysis
If the role is more on the management side of things I think I'm a good person for it. If it involves a lot of the technical side I'll need help in some specific domains.
I'm happy to support you more with Copter development and put more releases out there. I'm in the process of writing a couple of release rules that can help with that. I also think that we should have a maximum of 3 releases per year, because otherwise we won't have time to do proper beta testing between them. Small releases that only need small periods of testing can be done more often, maybe one per month.
I think we also need to discuss how far back we continue to do support and bug fixing. I would love to support all versions but I think we only have man-power to do it for the last two major versions.
One final thing to clarify is if with the two roles it would still be a part-time job. A full-time job for $1000/month for a limited time would be fine, but not in the long-term.