While I strongly support the shift to github, I also agree with Travis that we should vote on a change this major, and give the community enough time to weigh in. I would also encourage people on both sides of the debate to give everyone the benefit of the doubt. To those who have been putting in a ton of work attempting to fix trac in recent weeks, our broken infrastructure is both frustrating and gives a sense of urgency. To those who have spent over a decade using trac, the most recent iteration of this discussion (starting four days ago) feels very rushed.
Here's a proposal on a timeline for making a decision (I welcome feedback from anyone who thinks this is too fast or too slow). * We spend another few days discussing pros and cons and refining the proposed workflows. * I'll volunteer to collate the arguments that have been made into a list of pros and cons together with a concrete proposal, and we can send out an email in a separate thread announcing a vote later this week. * The deadline for voting will be one week from the announcement (so, late next week). * If the consensus of the community is to switch to github, then a smaller group can proceed with implementation (I'm also willing to be involved in that effort). David On Tue, Sep 13, 2022 at 1:13 AM 'Travis Scrimshaw' via sage-devel < sage-devel@googlegroups.com> 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 also don't agree that it is a > major friction point; all of my experience/feedback has been people have > the most trouble getting user names to access trac and dealing with our > coding/doc standards. > > -- > 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/68256bda-39ec-473a-9afb-3f026132377en%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/68256bda-39ec-473a-9afb-3f026132377en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAChs6_m4jNCxwYd77XFkJQzBXGCymQNmBV9A-nEULBG_wfZj6w%40mail.gmail.com.
