Name: vcstool2 (or something like that)?

[gavanderhoorn]

I realise this is a relatively minor point, somewhat subjective and I apologise if this has been discussed in the infrastructure PMC meeting(s), but vcs2l is not the easiest to remember. It also doesn't really 'remind' you of the provenance of the tool imo.

From previous discussions (about taking over maintenance of packages on pypi etc) I understand the reason the name had to change, but would something like vcstool2 or vcstoolng not have been possible?

[andry81]

As long as it does checkout externals using many vcs, then may be to thoroughly rename into something like ext? :)

[claraberendsen]

@gavanderhoorn vcstool2 has already been taken by another fork: https://pypi.org/project/vcstool2/
vcstoolng is not an option that was brought up when this was discussed in the PMC.
The general consensus was that vcs2l phonetically is the same as the original but distinct enough to point that this is a fork.

[gavanderhoorn]

vcstooling?

anyway: ok. I guess vcs2l is what it'll be.

[nuclearsandwich]

There's never going to be a "right" answer to this question and in the end we decided to take the rename that was both fun and also allows us to keep saying "vee see ess tool" when talking aloud and only calling it "vee see ess two ell" when we need to distinguish it from the parent project. The need for the distinction will either diminish in time. There's also the hope that we may eventually gain control of the upstream project and thus would be able to re-unify them.

[gavanderhoorn]

I'm not a native speaker, so that may be a factor here, but I did read it as vee see ess two ell. It's a string of consonants.

But again: vcs2l is what it's going to be.