Re: [sage-devel] DISCUSS: move Sage development to Github
> I think part of a solution could be PR templates, which add structure to > the PR description (= the first comment). That could be a way of adding > Authors (and Reviewers) to a PR. If there's a way to (lightly) enforce that via some kind of bot, that sounds very reasonable. On another note, I realize that the comment I made 6 years ago after Volker's comment is still relevant: "There's also the non-trivial (though not blocker, probably) issue that zillions of links to trac.sagemath.org would instantly be obsolete" How long do we want to have Trac still exist, but be read-only? Obviously we wouldn't take it down right away, but presumably eventually we would need to do so. -- 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/70d22072-efe0-4248-a1f5-3704769722d5n%40googlegroups.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
On Saturday, September 24, 2022 at 4:57:36 AM UTC-7 kcrisman wrote: > On another note, I realize that the comment I made 6 years ago after >> Volker's comment is still relevant: >> > "There's also the non-trivial (though not blocker, probably) issue that > zillions of links to trac.sagemath.org would instantly be obsolete" > > How long do we want to have Trac still exist, but be read-only? Obviously > we wouldn't take it down right away, but presumably eventually we would > need to do so. > The solutions for this are discussed in the ticket description of https://trac.sagemath.org/ticket/30363 - we can keep the external links to trac.sagemath.org working by means of redirects to the equivalent github issues. -- 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/37e506cc-efc8-49d8-a5e3-2bb3e858d8f5n%40googlegroups.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
On Sat, Sep 24, 2022 at 9:15 AM Matthias Koeppe wrote: > > On Saturday, September 24, 2022 at 4:57:36 AM UTC-7 kcrisman wrote: >>> >>> On another note, I realize that the comment I made 6 years ago after >>> Volker's comment is still relevant: >> >> "There's also the non-trivial (though not blocker, probably) issue that >> zillions of links to trac.sagemath.org would instantly be obsolete" >> >> How long do we want to have Trac still exist, but be read-only? Obviously >> we wouldn't take it down right away, but presumably eventually we would need >> to do so. > > > The solutions for this are discussed in the ticket description of > https://trac.sagemath.org/ticket/30363 - we can keep the external links to > trac.sagemath.org working by means of redirects to the equivalent github > issues. > More precisely, we could download a complete static copy of all of trac to static html (e.g., using recursive wget), then publish that static html using github pages, and modify our DNS to point there. The result would be free, fast, robust, and can be there indefinitely, and would provide a read-only copy of all the pages on trac.We could also automatically edit each static page to have a clear banner stating that it is an archive, and include a link to the corresponding GitHub issue. I'm not volunteering to do that. I'm just saying it is technically possible, and probably not that hard. William > > > > -- > 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/37e506cc-efc8-49d8-a5e3-2bb3e858d8f5n%40googlegroups.com. -- William (http://wstein.org) -- 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/CACLE5GBdZ3BSqiT09uAeiLXuQ8coGDfKBRqgrBi7dH%3DRR_Wsiw%40mail.gmail.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
On 24/09/2022 14:57, kcrisman wrote: I think part of a solution could be PR templates, which add structure to the PR description (= the first comment). That could be a way of adding Authors (and Reviewers) to a PR. If there's a way to (lightly) enforce that via some kind of bot, that sounds very reasonable. On another note, I realize that the comment I made 6 years ago after Volker's comment is still relevant: "There's also the non-trivial (though not blocker, probably) issue that zillions of links to trac.sagemath.org would instantly be obsolete" How long do we want to have Trac still exist, but be read-only? Obviously we wouldn't take it down right away, but presumably eventually we would need to do so. Is it possible to choose the issue numbers in GH when making a migration? Then, setting a redirect of the form "https://trac.sagemath.org/ticket/$TICKET_NUMBER -> https://github.com/sagemath/sage/issues/$TICKET_NUMBER" will make the lion's share of the links still relevant. This does not preserve fragments like "#comment:7", which is useful in long ticket discussions. Regards, TB -- 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/fecee892-5967-0e85-6d33-398cd930aef9%40gmail.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
On Saturday, September 24, 2022 at 9:27:46 AM UTC-7 mathzeta2 wrote: > Is it possible to choose the issue numbers in GH when making a migration? > Then, setting a redirect of the form " > https://trac.sagemath.org/ticket/$TICKET_NUMBER -> > https://github.com/sagemath/sage/issues/$TICKET_NUMBER"; will make the > lion's share of the links still relevant. > Yes, to map it like this is the plan. > This does not preserve fragments like "#comment:7", which is useful in > long ticket discussions. > Thanks, I've opened https://github.com/sagemath/trac-to-github/issues/7 for this. -- 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/9b867748-f81d-4515-bac6-f67a140a898cn%40googlegroups.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
I think I'm missing part of this. What is the actual path to switching to GitHub? I've seen pages describing how individual development tasks will be converted from trac to GitHub, but what does the overall transition look like? - Do we just say, before November 1 (or whenever) we're doing everything on trac, and after we're doing everything on GitHub? - Or is there a period where both are active and people can slowly transition? We have a GitHub page now; if the transition is approved, do people start creating issues and pull requests right away? - Or some other option? I apologize if this has been discussed and I missed it. On Saturday, September 24, 2022 at 10:09:46 AM UTC-7 Matthias Koeppe wrote: > On Saturday, September 24, 2022 at 9:27:46 AM UTC-7 mathzeta2 wrote: > >> Is it possible to choose the issue numbers in GH when making a migration? >> Then, setting a redirect of the form " >> https://trac.sagemath.org/ticket/$TICKET_NUMBER -> >> https://github.com/sagemath/sage/issues/$TICKET_NUMBER"; will make the >> lion's share of the links still relevant. >> > > Yes, to map it like this is the plan. > > >> This does not preserve fragments like "#comment:7", which is useful in >> long ticket discussions. >> > > Thanks, I've opened https://github.com/sagemath/trac-to-github/issues/7 > for this. > > > -- 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/9b4a5765-c00c-456e-bb11-67dbad37e19an%40googlegroups.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
On Saturday, September 24, 2022 at 5:15:11 PM UTC-7 John H Palmieri wrote: > I think I'm missing part of this. What is the actual path to switching to > GitHub? I've seen pages describing how individual development tasks will be > converted from trac to GitHub, but what does the overall transition look > like? > > - Do we just say, before November 1 (or whenever) we're doing everything > on trac, and after we're doing everything on GitHub? > Yes, exactly (although we have not discussed the date yet). On the switchover day, it would look like this: 1. We take Trac offline, reconfigure it to be read-only, bring it online. 2. Convert all tickets to Issues in a new repo. (This preserves the ticket numbers as Issue numbers.) 3. Final check that the new repo is OK. 4. Replace sagemath/sage by the new repo. 5. Announce that sagemath/sage is now open for Issues and PRs. -- 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/3e7bb468-31cd-412e-9720-e9183e64c290n%40googlegroups.com.
Re: [sage-devel] DISCUSS: move Sage development to Github
I've added this to https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b#conversion-of-trac-tickets-and-the-trac-wiki-to-github now On Saturday, September 24, 2022 at 5:46:15 PM UTC-7 Matthias Koeppe wrote: > On Saturday, September 24, 2022 at 5:15:11 PM UTC-7 John H Palmieri wrote: > >> I think I'm missing part of this. What is the actual path to switching to >> GitHub? I've seen pages describing how individual development tasks will be >> converted from trac to GitHub, but what does the overall transition look >> like? >> >> - Do we just say, before November 1 (or whenever) we're doing everything >> on trac, and after we're doing everything on GitHub? >> > > Yes, exactly (although we have not discussed the date yet). > > On the switchover day, it would look like this: > 1. We take Trac offline, reconfigure it to be read-only, bring it online. > 2. Convert all tickets to Issues in a new repo. (This preserves the ticket > numbers as Issue numbers.) > 3. Final check that the new repo is OK. > 4. Replace sagemath/sage by the new repo. > 5. Announce that sagemath/sage is now open for Issues and PRs. > > > -- 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/085f47b3-a32e-432e-b96f-ea6027bc4afen%40googlegroups.com.
