On 4 February 2014 22:08, Jimmy Kaplowitz <[email protected]> wrote:
> 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). > > - Jimmy > > > On Tue, Feb 4, 2014 at 12:38 PM, Marcin Kulisz <[email protected]> wrote: > >> On 2014-02-03 18:00:30, Anders Ingemann wrote: >> > Hi everybody >> >> Hello, >> >> > The python branch of build-debian-cloud has been released under the name >> > bootstrap-vz. >> >> Lol :-) >> >> snip >> >> > The new repo is available at https://github.com/andsens/bootstrap-vz >> > There is still loads of documentation to be written, but I will try to >> get it >> > done as soon as possible. >> >> Anders I have man page for build-debian-cloud-image which was how I named >> package and link to build-debian-cloud binary. I don't know how are you >> planing >> to write/generate manpages but if you're interested in it just let me >> know and >> I'll send you PR after I'll clone new repo. >> -- >> >> |_|0|_| | >> |_|_|0| "Heghlu'Meh QaQ jajVam" | >> |0|0|0| -------- kuLa --------- | >> >> gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3 >> 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3 >> > > > The new name makes me think of OpenVZ/Virtuozzo and isn't obviously about Debian at all, so it seems a step back. The branch needed a separat name, because it didn't have anything to do with the shell scripts any longer. The vz is a generalization of the "cloud" part in the previous name. "build-debian-cloud" was a bit misleading since two out of three providers were not particularly "cloud"-y (kvm and vbox). > If there are currently enough open GitHub issues to warrant this, they could have tags applied to indicate which branch they applied to. There are *some* issues in the old branch, most of them I created myself. I am going to move the ones that are specific enough to do anything about, the rest I'll let die :-) > My only request is to settle on some name so that we can all keep track of it consistently. Agreed. > 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. Exactly! Also, the python version is really not a fork of any kind. It's built from the ground up on a completely different mental model, so it made sense to break away from any previous projects. > We do have 10 commits (not counting merges) pending to send to build-debian-cloud's master branch Heh, you're keeping busy I see :-) I'll merge once you send the PR.
