On Monday, September 12, 2022 at 10:13:47 PM UTC-7 Travis Scrimshaw wrote: > >> But people nowadays who start with GitHub never have to go through >>>> archaic setup steps such as those that we document at >>>> https://doc.sagemath.org/html/en/developer/trac.html#trac-authentication-through-ssh, >>>> >>>> which --- even when it is working --- is major friction for the project. >>>> >>> >>> I think it has been just far too long since you uploaded your ssh key to >>> GH. The server cannot magically know your ssh public key. >>> >> >> You are missing that the new contributors will already have set up their >> GitHub for virtual everything else that they work on. There is no >> additional such cost for starting to work on a new project that's also >> hosted on GitHub. >> This is a just tiny bit of the big network effects that will come. >> > > This is true, they do have to do it for our separate project. However, > your characterization that the current setup is archaic is false unless you > want to call what GH does archaic too. >
I'll let you catch up on reading. See my other message - one does not need an ssh key with github. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/b8e9e671-290d-4cb4-a200-d86e1f62ead2n%40googlegroups.com.
