Copter-4.1.x has a new DEV_OPTIONS bit to allow specifying how the SET_ATTITUDE_TARGET's thrust field is interpreted. The default interpretation is as a climb rate (which is not really correct but it's what most users want). The alternative interpretation is to that the "thrust" field really is a thrust (from 0 to 1).

We should move this DEV_OPTIONS bit to the GUIDED_OPTIONS parameter because

I think it'd be great to be able to move a Task between Projects, likely from the Task's Edit page.

This can help with keeping things organized, as you may not realize you'll need/want new Projects immediately, and it will save you having to either to export/import, or re-upload data (if you've not processed it).

For instance, I'd now like to move my Pix4D example datasets out from the Githu

There seems to be some issues with the landing function in ./software/px4_mavros_scripts/1_px4_mavros_offboard_controller/commander.py.

To do:

1. Test the land function and report if it works well.
2. Fix if there is an issue.

Is your feature request related to a problem? Please describe.
I'm using drone-cache for a Rust project to cache the target directory, which contains compiled modules for all of my project's dependencies, so that the pipeline doesn't have to rebuild everything from scratch (it takes a looong time!). Unfortunately the target directory tends to grow very large (often several GBs), so I'd li