[Bioc-devel] Switch to SSH protocol for git clone instructions on package landing pages?

[Turaga, Nitesh]

Hi Pete,

For developers there is no reason not to use the SSH protocol. But there are many people who’d like to clone the repo and look at it on their local machine.

Take for example packages which are not maintained on both the bioconductor server and Github. For these packages, a good way for users to browse the source code on their local machine is using the HTTPS protocol, since they will not have access to download it via SSH ( you need permissions to do this). 

We always advocate developers to only use SSH though. For everyone else, HTTPS is the best option. 

Best,

Nitesh 

> On Apr 29, 2018, at 10:03 AM, Peter Hickey <peter.hickey at gmail.com> wrote:
> 
> The one-liner on the package landing page describing how to check out
> a package from the git repo uses HTTPS rather than ssh, e.g.:
> 
> # From https://bioconductor.org/packages/bsseq/
> git clone https://git.bioconductor.org/packages/bsseq
> 
> However, as a developer we should be using the SSH protocol
> (https://bioconductor.org/developers/how-to/git/faq/).
> 
> Is there any reason not to use the SSH protocol (i.e. git clone
> git at git.bioconductor.org:packages/bsseq) in the instructions given on
> the landing page? It seems to me an unnecessary source of friction,
> particularly for new developers who will end up with the dreaded
> "fatal: remote error: FATAL: W any packages/myPackage nobody DENIED by
> fallthru (or you mis-spelled the reponame)" error message if they
> don't know to switch protocols
> (https://bioconductor.org/developers/how-to/git/faq/)
> 
> Cheers,
> Pete
> 
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel



This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.