I think there is utility in leaving github.com/sagemath/sage as it is: - It's easy to navigate using the GitHub web interface, whereas the entire trac server repo is not. (Try browsing the branches.) - It gives direct, no-nonsense access to releases, RC's, and beta's.
Having a full GitHub mirror of the trac server repo is also useful for the reasons you've already mentioned. So maybe have github.com/sagemath/sagetrac-mirror in addition to github.com/sagemath/sage. Best, Robert On Tuesday, 12 September 2017 16:21:50 UTC-4, Dima Pasechnik wrote: > > There are several reasons for this: > one is to allow http(s):// and git:// read access to all the trac > branches, > > less load on the trac server... > > To keep it up to date one can simply run a cronjob > on trac, doing > git push --mirror ... > every 10 minutes, say... > (or run a cronjob on a third side, with a local mirror, > that would do > git remote update > followed by > git push --mirror... > > The repo is not very big, just over 200Mb. > > Any thoughts? > > Dima > -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
