Create `convert` script for toggling https/git@

[Clint Liddick]

[Pras Velagapudi]

What are the reasons not to use just one or the other?

[Michael Koval]

I agree with @psigen. I suggest using https because it is the only option for unauthenticated access.

The only problem I've had with https in the past is the annoyance of having to constantly re-enter my username and password. This is trivially fixed by enabling Git credential caching; i.e.:

git config --global credential.helper cache

[Clint Liddick]

We're using https and only committing that, but I plan to use this on my own pc for development, and I want ssh access, hence the convert script (will just be a sed command most likely). Plus, this way if people use git@ out of habit, it's easy to fix before committing/merging.

[Aaron M. Johnson]

I gather from this discussion that the readme notes on "use the included converter script" are aspirational instructions? Or does someone have this script ready to go? If we do include such a script I request that it not be called "convert" because that command is taken. I generally prefer ssh but the credential cache is ok. If we don't include this script, then we need to update the readme.