Hi Tobias, Thanks a lot for your edits to the wiki page! Some comments: 1) In our documentation, we should avoid referring to "origin" as the remote, because what is "origin" will depend on whether someone cloned the repo before deciding that they need their own fork. This is why I used "github-USERNAME" as the name of the remote. It makes it clear to developers what is what. 2) Likewise, the word "upstream" is heavily overloaded in our use. I would recommend to call this remote just "sagemath" or something like this for clarity.
On Sunday, September 11, 2022 at 12:17:24 AM UTC-7 tobias...@gmail.com wrote: > On Saturday, 10 September 2022 at 21:32:50 UTC+2 Matthias Koeppe wrote: > >> On Saturday, September 10, 2022 at 8:12:48 AM UTC-7 Matthias Koeppe wrote: >> >>> I've added a draft of a proposed workflow on GitHub with the idea to >>> just follow the Trac workflow. >>> Help is welcome in adding links to documentation for the various bits. >>> >>> I think we can have a fleshed out Trac to GitHub transition guide by the >>> end of the weekend. >>> >>> >> A draft of the Trac-to-GitHub transition guide is now available at: >> https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b >> >> Please let me know what's missing or unclear. >> >> > > Thanks, this is already in a pretty nice shape! I've extended some points > a bit. > > In my opinion, we can also directly drop the develop branch and move to > the master/main-branch only model. But that's slightly orthogonal to the > migration to 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/70db8c88-4e8d-4aa4-946d-c03b25429b74n%40googlegroups.com.
