A while ago I taught qclone about cloning remote repos+queues. This works if the remote side is structured as
/path/to/repo # base repo
/path/to/repo/.hg/patches # queue repo
So it would be interesting if Bitbucket could support two things:
a) When creating a patch queue, it would be handy if one could create it into an existing or newly created fork of the base repo. This would allow for qclone, and it would also clearly document the revision the queue is based on.
b) As an option, it might be interesting if Bitbucket would support some form of pushing and popping patches on the queue's base repo. This would be handy to review the actual effect of the patches online. I guess this option would have to be reserved to the queue owner(s).
(I am working on an hg extension, rclone, that supports a similiar idea: http://freehg.org/u/parren/rexec/.)