The new name makes me think of OpenVZ/Virtuozzo and isn't obviously about Debian at all, so it seems a step back. With Tomasz's help on the GCE migration, I expect the shell branch's lifetime would have been short anyway (then we'd have "merged" python into master as a full replacement). If there are currently enough open GitHub issues to warrant this, they could have tags applied to indicate which branch they applied to.
But, it's your project, your call. :) My only request is to settle on some name so that we can all keep track of it consistently.
Your rename will at least have the advantage of making it possible to search your fork on GitHub, at least. The old version was unsearchable since you had forked from camptocamp.
We do have 10 commits (not counting merges) pending to send to build-debian-cloud's master branch, for which I'll prepare a PR shortly. Out of the 10, (inconsequential local variants of) the first 4 made it into the current 20131120 and (backports kernel) 20131127 images, which we used for Google Compute Engine general availability; 4 were from Tomasz to use the host environment's NTP server; and 5 were from two Googler colleagues, including a GCE application of the workaround I suggested for Debian bug #696805 (hostname.sh).