It's semantics, John. Recommending one mechanism but not the other means
that the other mechanism is less recommended or, in other words,
discouraged. This might be a mild discouragement, but it is so. The impact
of this mild discouragement would be that our potential devs will likely be
using
I just took "recommend" one way to discourage the other. FWIW I've used
both methods with similar success; seems like personal preference.
--Tom
On Sun, Dec 3, 2017 at 5:23 PM, John D. Ament wrote:
> On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau
Those instructions are working. I pushed a PR earlier as well as Maxim
pushed a few.
--Tom
On Sun, Dec 3, 2017 at 5:21 PM, Suneel Marthi wrote:
> If it helps, here's what was done on OpenNLP - one of the first projects
> that transitioned to gitbox in July 2017 after
On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau wrote:
> That still uses SSH, which then uses your pre-configured keys. Github docs
> discourage this use for some reason.
>
Err no, github docs "recommend" using HTTPS, they don't discourage the use
of SSH.
If it helps, here's what was done on OpenNLP - one of the first projects
that transitioned to gitbox in July 2017 after gitbox was announced.
http://opennlp.apache.org/using-git.html
On Sun, Dec 3, 2017 at 10:11 AM, Thomas Nadeau
wrote:
> That still uses SSH, which
You *could* use those -- they are ssh with ssh keys. However, GitHub
generally recommends using HTTPS.
On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament wrote:
> Any reason you wouldn't just use the github direct URLs?
>
> g...@github.com:apache/incubator-ariatosca.git
>
The gitbox transition appears to have completed - thanks for setting this
up Suneel.
Committers please follow the instructions Suneel provided on Slack earlier
to synch your apache account with github so permissions work/etc...
--Tom
>From slack: