On Saturday, September 10, 2022 at 7:39:10 AM UTC-7 Travis Scrimshaw wrote:
> [........] There are lots of technical issues and questions I have that [I >> cannot] easily find after skimming through things for a few minutes. >> > Everything about GitHub has excellent documentation, and we have an executive summary now at https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b, with pointers to the relevant bits. > It stays there even if the user GitHub account is closed (the latter >> triggers an automatic closure of the PR, but the underlying >> branch remains in the repo, it can be worked on just the same using git) >> > > Which repo? Either way, this seems like a regression compared to our > current setup, where if a user quits, then branch, ticket, and everything > remains. > No, this is an imaginary problem. The branch of the pull request persists in the sagemath repo (see https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b, which explains the name of the branch) even if the user and their repo disappears. Getting the login credentials was the biggest barrier; everything else is >>> mostly straightforward and based on very simple git commands. >>> >> >>> Right now, I find there are way too many practical questions and >>> barriers for how we develop that make moving to Git**b a much bigger pain >>> that people will think it is. >>> >> >> Travis, many people nowadays never used git without GitHub or GitLab. For >> such a person it's a major pain to >> learn our workflow. >> > > Do you really believe that everyone is using the web interface to make > edits to the code and not using some form of git locally (either command > line or GUI based)? > The web interface has major problems, such as not being able to run tests > locally, in addition to being unwieldy with a project on the scale of Sage. > Honestly, people really don't use "git pull", "git push", "git commit" when > working with *Git*hub? > Nothing like this is being proposed. No, GitHub is not a replacement for git. Yes, you will continue to use git commands to pull, push, commit. 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. And people can use modern IDEs, in particular VS Code, which have excellent integration with GitHub: see for example https://code.visualstudio.com/docs/editor/github And yes, there's also a command-line interface to GitHub, see https://trac.sagemath.org/ticket/34523, which does everything that "git trac" can do and much more. > You need much more of a plan than simply saying "its easy because other > people use it". > Available now at https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b -- 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/22ace5b8-0be5-4a94-8ac2-e306cc8648a8n%40googlegroups.com.
