On Thu, Mar 11, 2021 at 12:52 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > On Thu, Mar 11, 2021 at 10:11 AM Dima Pasechnik <dimp...@gmail.com> wrote: > > > > On Wed, Mar 10, 2021 at 4:00 PM E. Madison Bray <erik.m.b...@gmail.com> > > wrote: > > > > > > On Tue, Jan 12, 2021 at 11:33 PM tobia...@gmx.de <tobiasd...@gmx.de> > > > wrote: > > > > > > > > > > > > For what's worth, + 1 for migrating to github. > > > > > > > > The interface is cleaner, it has many more features and integrations, > > > > and is more active which could attract more contributions. There are a > > > > few scripts/tools that allow to migrate from trac to github. But most > > > > of them are unmaintained for a few years already, so I'm not sure if > > > > they still work (which should be taken as a sign that one should > > > > migrate sooner than later). > > > > > > In 2019 Julian Rüth and I, with the help of some others, already put > > > in some effort to set up an organization for SageMath on GitLab: > > > https://gitlab.com/sagemath > > > > > > Between GitHub and GitLab, we felt that the latter would be more > > > acceptable to the broader Sage community. We also implemented a bot > > > that can mirror GitLab merge requests as Trac tickets, though it's > > > been in need of troubleshooting for a while. > > > > > > This was also done before the advent of GitHub Actions, and the > > > ability to provide custom CI runners for GitLab Pipelines seemed > > > advantageous, since we could maintain our own fleet of runners, be it > > > on Sage developers' personal machines (if they are generous enough to > > > host them) or any conceivable constellation of cloud computing > > > platforms. > > > > > > In practice this has gained little traction, in part due to lack of > > > advertising. The GitLab Runner solution also proved a bit troublesome > > > to maintain, as it required some constant attention to make sure there > > > were always working runners available. I tried to keep that up for a > > > while myself, but have had other obligations. > > > > I think it should be mentioned that GitLab has an analog of GitHub Actions, > > and the difference is that its runners may be self-hosted, or provided > > by GitLab. > > E.g. see https://gitlab.com/sagemath/dev/trac/-/pipelines/266731297 > > I just tried to switch to a "community" runner, and got an error which > is probably > obvious to people versed in Docker: > > https://gitlab.com/sagemath/dev/trac/-/jobs/1089520433
I think it might be because the Docker builds have been otherwise not working for a while (due to lack of reliable runners). So a more recent "build-from-clean" job is needed. These jobs are run when develop/master are updated as well as on tags. Whereas "built-from-latest" is run on branches for tickets. It tries to build the branch on top of the "latest" Docker image e.g. for develop. But the last one that built successfully is too old, and so trying to make the diff between that ticket and the version of develop it's based on fails. Hence the message: "Could not find commit fbca269f627bf6a8bc6f0a611ed7e26260ebc994 in your local Git history. Please merge in the latest built develop branch to fix this: git fetch trac && git merge fbca269f627bf6a8bc6f0a611ed7e26260ebc994" But for the automated CI that's not a very useful message... I know Matthias has done some impressive things to get around GitHub Actions' time limit on jobs by breaking the build up into "stages" that can be split across multiple jobs. I see no reason that couldn't work with GitLab as well. But it would still be better to have our own fleet of runners--they would be faster, and we could test on more different custom hardware configurations. The problem is that this is at a minimum a part-time job... > > > In the meantime Matthias and others have been doing really interesting > > > things with GitHub Actions for our CI. For the time being GitHub is > > > being *very* generous with computing time available to open source > > > projects. Though I fear it's only a matter of time before Microsoft's > > > investors come banging on the door, and they start putting in bigger > > > limits for free users (as happened with Travis CI). > > > > > > I would still prefer the GitLab approach for a myriad of reasons, or a > > > hybrid approach at least for the GitHub Actions stuff. It just needs > > > to be better advertised, and there needs to be better instructions for > > > where users and potential developers should go to open issues. > > > > > > As for the wiki I've always been in favor of dropping Moin Wiki and > > > migrating the existing wiki pages to Trac (or to GitLab). Someone > > > just has to do it, as is always the problem. > > > > > > > > > > On Thursday, January 7, 2021 at 9:50:49 PM UTC+1 David Roe wrote: > > > >> > > > >> On Thu, Jan 7, 2021 at 3:49 PM Isuru Fernando <isu...@gmail.com> wrote: > > > >>> > > > >>> It should be sagemath.zulipchat.com right? (Instead of .org) > > > >> > > > >> > > > >> Yes, sorry for the typo! > > > >> David > > > >> > > > >>> > > > >>> Isuru > > > >>> > > > >>> On Thu, Jan 7, 2021 at 2:47 PM David Roe <roed...@gmail.com> wrote: > > > >>>> > > > >>>> > > > >>>> > > > >>>> On Thu, Jan 7, 2021 at 3:30 PM Harald Schilly <har...@schil.ly> > > > >>>> wrote: > > > >>>>> > > > >>>>> On Thu, Jan 7, 2021 at 9:23 PM Dima Pasechnik <dim...@gmail.com> > > > >>>>> wrote: > > > >>>>> > Harald - can you take care of this? > > > >>>>> > > > > >>>>> > > > >>>>> Uhm, what's happening? Could someone please summarize this for me? > > > >>>> > > > >>>> > > > >>>> zulip.sagemath.org used to point to a google virtual machine. We'd > > > >>>> like it to redirect to sagemath.zulipchat.org so that people looking > > > >>>> for the Zulip server are sent to the right place. > > > >>>> David > > > >>>> > > > >>>>> > > > >>>>> > > > >>>>> -- > > > >>>>> 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+...@googlegroups.com. > > > >>>>> To view this discussion on the web visit > > > >>>>> https://groups.google.com/d/msgid/sage-devel/CAGG4CB5oiSVA3W3AJWfosLuMuzEKPaoHZ_DWNS58H%3DFgast98w%40mail.gmail.com. > > > >>>> > > > >>>> -- > > > >>>> 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+...@googlegroups.com. > > > >>>> To view this discussion on the web visit > > > >>>> https://groups.google.com/d/msgid/sage-devel/CAChs6_mN8PRRt2Ot7YcHqcZGLXPoPcVS0_R_QdjCVYpZHpi5Ng%40mail.gmail.com. > > > >>> > > > >>> -- > > > >>> 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+...@googlegroups.com. > > > >>> > > > >>> To view this discussion on the web visit > > > >>> https://groups.google.com/d/msgid/sage-devel/CA%2B01voOy5SXXkyQeqMB-AxeGMXEv5MN%2Bj3FBdYB1DihHHh0inQ%40mail.gmail.com. > > > > > > > > -- > > > > 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/e2c237d2-b8aa-4002-8fb4-edeaf03a8d3fn%40googlegroups.com. > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "sage-devel" group. > > > To unsubscribe from this topic, visit > > > https://groups.google.com/d/topic/sage-devel/ayOL8_bzOfk/unsubscribe. > > > To unsubscribe from this group and all its topics, 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/CAOTD34bSQLz-JBbc5P9WOHYxFUFdLt20A24yTQ48ySfaOiL2jQ%40mail.gmail.com. > > -- > 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/CAAWYfq1RV5bEmq3N_FP-5Eq%3D05d7%2BegZZ6yqp9%2Bs-B0Wbb9y-A%40mail.gmail.com. -- 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/CAOTD34YjC%3DM59TTMuKKut%2B8pj2w7LYm8XKsS0kVrukLs7z5M1w%40mail.gmail.com.
