subject:"Re\: \[sage\-devel\] DISCUSS\: move Sage development to Github"

Okay, fair enough! Then it's a bit more work to get tickets into PRs (for 
devs) but maybe its a good idea to start with a clean slate.

On Tuesday, 27 September 2022 at 22:31:57 UTC+2 dim...@gmail.com wrote:

>
>
> On Tue, 27 Sep 2022, 21:12 Tobias Diez,  wrote:
>
>> Just to make sure we are talking about the same thing. Imagine a 
>> currently open ticket with a linked branch. How is this going to be 
>> migrated? My assumption has been that this will create a PR from 
>> sagemath/sagetrac-mirror/branch into sagemath/sage.
>>
>
> No, there will be an issue on sagemath/sage, no PR. There will be a link 
> to a branch on sagetrac-mirror (which will be readonly). 
>
> To proceed, just push this branch to your personal fork of sagemath/sage 
> and make a PR from there.
> At this point it becomes a usual github workflow.
>
>
>> If thats indeed the plan (which I find is a good plan), then there are 
>> the following issues:
>> - sagetrac-mirror is not a fork of sage, thus it might not be possible to 
>> create a PR from it (at leas from the web interface its not possible, not 
>> sure about the API)
>> - sagetrac-mirror cannot be archived otherwise it will be readonly (this 
>> is taken care of my Matthias recent edit to the migration wiki page)
>> - devs might not have the permission to push to sagetrac-mirror 
>> (currently there is a branch protection rule in place that prevents any 
>> direct commits, but even if that's removed I'm not sure if everyone can 
>> just push to it)
>>
>
> all this is avoided if done as I described above 
>
> Dima
>
>
>> On Tuesday, 27 September 2022 at 15:29:35 UTC+2 dim...@gmail.com wrote:
>>
>>>
>>>
>>> On Tue, 27 Sep 2022, 14:08 Tobias Diez,  wrote:
>>>
 Yes, the target repo of these PRs will be the (new) sagemath/sage, but 
 the source will be sagemath/sagetrac-mirror, right? 
>>>
>>>
>>>
>>> Hmm, I might have missed something - what is the need to have 2 repos 
>>> here, if 1 is sufficient?
>>>
>>> Any fork of sagemath/sage may be a source of a PR, not only 
>>> sagetrac-mirror
>>>
>>>
>>> So in order to update the pull request one needs to push the changes to 
 sagemath/sagetrac-mirror (it is not possible to update a PR by pushing to 
 /refs/pull/xyz, because this is readonly). Thus, if sagetrac-mirror is 
 archived (and thus readonly), the only way to work on existing 
 tickets/branches would be to checkout the existing branch (from either 
 sagetrac-mirror or sage/refs/pull), make changes, push to a new fork, 
 create a new PR, close the old PR (essentially the workflow 
 https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally#modifying-an-inactive-pull-request-locally
 ).

 On Tuesday, 27 September 2022 at 13:59:45 UTC+2 dim...@gmail.com wrote:

> On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez  
> wrote: 
> > 
> > One more question: The current plan is to use the sagetrac-mirror 
> repo as the base for creating PRs but also to archived it. However, if 
> I'm 
> not mistaken, that makes all branches in sagetrac-mirror readonly and 
> thus 
> one cannot continue working on existing PRs by pushing to the 
> corresponding 
> branch in sagetrac-mirror. 
>
> IMHO the plan is to create new PRs in sagemath/sage, not in 
> sagemath/sagetrac-mirror 
> There won't be "existing" PRs, only issues, pointing to branches on 
> sagetrac-mirror 
>
>
>
> > On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com 
> wrote: 
> >> 
> >> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 
> UTC+2: 
> >>> 
> >>> 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. 
> >> 
> >> Don’t we need an issue for the first point, as well? The example 
> #26 corresponds to #34110 which is not easy to recover from the migrated 
> information. 
> >> 
> >> Furthermore, it isn’t still clear to me how dependencies between 
> PRs will be visible (like in the Trac dependencies field). In the above 
> example you have to recover this from the history of commit messages 
> (which 
> may not be clear enough in general). Shouldn’t the migration

Re: [sage-devel] DISCUSS: move Sage development to Github

On Tuesday, September 27, 2022 at 1:12:55 PM UTC-7 tobias...@gmail.com 
wrote:

> Just to make sure we are talking about the same thing. Imagine a currently 
> open ticket with a linked branch. How is this going to be migrated? My 
> assumption has been that this will create a PR from 
> sagemath/sagetrac-mirror/branch into sagemath/sage.
>
> If thats indeed the plan (which I find is a good plan), then there are the 
> following issues:
> - sagetrac-mirror is not a fork of sage, thus it might not be possible to 
> create a PR from it (at leas from the web interface its not possible, not 
> sure about the API)
>

Good point about the "is-fork-of" relation. I've made another refinement 
in  
https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b#conversion-of-trac-tickets-and-the-trac-wiki-to-github
 :

   1. Convert all tickets to Issues in a new repo sagemath/sage-temp. (This 
   preserves the ticket numbers as Issue numbers.)
   2. Rename sagemath/sagetrac-mirror to sagemath/sagetrac-archive and 
   archive 
    it 
   (= set it to readonly).
   3. Create a single-branch fork of sagemath/sage-temp called 
   sagemath/sagetrac-mirror and push all branches (or all branches of open 
   tickets) from sagemath/sagetrac-archive to it.
   4. Open PRs from sagemath/sagetrac-mirror 
    to sagemath/sage-temp for 
   all open tickets with attached branches.


-- 
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/32619c62-5234-4b75-98ef-c653f0293865n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-27 Thread Dima Pasechnik

On Tue, 27 Sep 2022, 21:12 Tobias Diez,  wrote:

> Just to make sure we are talking about the same thing. Imagine a currently
> open ticket with a linked branch. How is this going to be migrated? My
> assumption has been that this will create a PR from
> sagemath/sagetrac-mirror/branch into sagemath/sage.
>

No, there will be an issue on sagemath/sage, no PR. There will be a link to
a branch on sagetrac-mirror (which will be readonly).

To proceed, just push this branch to your personal fork of sagemath/sage
and make a PR from there.
At this point it becomes a usual github workflow.


> If thats indeed the plan (which I find is a good plan), then there are the
> following issues:
> - sagetrac-mirror is not a fork of sage, thus it might not be possible to
> create a PR from it (at leas from the web interface its not possible, not
> sure about the API)
> - sagetrac-mirror cannot be archived otherwise it will be readonly (this
> is taken care of my Matthias recent edit to the migration wiki page)
> - devs might not have the permission to push to sagetrac-mirror (currently
> there is a branch protection rule in place that prevents any direct
> commits, but even if that's removed I'm not sure if everyone can just push
> to it)
>

all this is avoided if done as I described above

Dima


> On Tuesday, 27 September 2022 at 15:29:35 UTC+2 dim...@gmail.com wrote:
>
>>
>>
>> On Tue, 27 Sep 2022, 14:08 Tobias Diez,  wrote:
>>
>>> Yes, the target repo of these PRs will be the (new) sagemath/sage, but
>>> the source will be sagemath/sagetrac-mirror, right?
>>
>>
>>
>> Hmm, I might have missed something - what is the need to have 2 repos
>> here, if 1 is sufficient?
>>
>> Any fork of sagemath/sage may be a source of a PR, not only
>> sagetrac-mirror
>>
>>
>> So in order to update the pull request one needs to push the changes to
>>> sagemath/sagetrac-mirror (it is not possible to update a PR by pushing to
>>> /refs/pull/xyz, because this is readonly). Thus, if sagetrac-mirror is
>>> archived (and thus readonly), the only way to work on existing
>>> tickets/branches would be to checkout the existing branch (from either
>>> sagetrac-mirror or sage/refs/pull), make changes, push to a new fork,
>>> create a new PR, close the old PR (essentially the workflow
>>> https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally#modifying-an-inactive-pull-request-locally
>>> ).
>>>
>>> On Tuesday, 27 September 2022 at 13:59:45 UTC+2 dim...@gmail.com wrote:
>>>
 On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez 
 wrote:
 >
 > One more question: The current plan is to use the sagetrac-mirror
 repo as the base for creating PRs but also to archived it. However, if I'm
 not mistaken, that makes all branches in sagetrac-mirror readonly and thus
 one cannot continue working on existing PRs by pushing to the corresponding
 branch in sagetrac-mirror.

 IMHO the plan is to create new PRs in sagemath/sage, not in
 sagemath/sagetrac-mirror
 There won't be "existing" PRs, only issues, pointing to branches on
 sagetrac-mirror



 > On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com
 wrote:
 >>
 >> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46
 UTC+2:
 >>>
 >>> 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.
 >>
 >> Don’t we need an issue for the first point, as well? The example #26
 corresponds to #34110 which is not easy to recover from the migrated
 information.
 >>
 >> Furthermore, it isn’t still clear to me how dependencies between PRs
 will be visible (like in the Trac dependencies field). In the above example
 you have to recover this from the history of commit messages (which may not
 be clear enough in general). Shouldn’t the migration put something into the
 header fields milestone, assignees, …, as well (if possible)? How will
 authors and reviewers be visible?
 >
 > --
 > 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

Re: [sage-devel] DISCUSS: move Sage development to Github

Just to make sure we are talking about the same thing. Imagine a currently 
open ticket with a linked branch. How is this going to be migrated? My 
assumption has been that this will create a PR from 
sagemath/sagetrac-mirror/branch into sagemath/sage.

If thats indeed the plan (which I find is a good plan), then there are the 
following issues:
- sagetrac-mirror is not a fork of sage, thus it might not be possible to 
create a PR from it (at leas from the web interface its not possible, not 
sure about the API)
- sagetrac-mirror cannot be archived otherwise it will be readonly (this is 
taken care of my Matthias recent edit to the migration wiki page)
- devs might not have the permission to push to sagetrac-mirror (currently 
there is a branch protection rule in place that prevents any direct 
commits, but even if that's removed I'm not sure if everyone can just push 
to it)

On Tuesday, 27 September 2022 at 15:29:35 UTC+2 dim...@gmail.com wrote:

>
>
> On Tue, 27 Sep 2022, 14:08 Tobias Diez,  wrote:
>
>> Yes, the target repo of these PRs will be the (new) sagemath/sage, but 
>> the source will be sagemath/sagetrac-mirror, right? 
>
>
>
> Hmm, I might have missed something - what is the need to have 2 repos 
> here, if 1 is sufficient?
>
> Any fork of sagemath/sage may be a source of a PR, not only sagetrac-mirror
>
>
> So in order to update the pull request one needs to push the changes to 
>> sagemath/sagetrac-mirror (it is not possible to update a PR by pushing to 
>> /refs/pull/xyz, because this is readonly). Thus, if sagetrac-mirror is 
>> archived (and thus readonly), the only way to work on existing 
>> tickets/branches would be to checkout the existing branch (from either 
>> sagetrac-mirror or sage/refs/pull), make changes, push to a new fork, 
>> create a new PR, close the old PR (essentially the workflow 
>> https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally#modifying-an-inactive-pull-request-locally
>> ).
>>
>> On Tuesday, 27 September 2022 at 13:59:45 UTC+2 dim...@gmail.com wrote:
>>
>>> On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez  
>>> wrote: 
>>> > 
>>> > One more question: The current plan is to use the sagetrac-mirror repo 
>>> as the base for creating PRs but also to archived it. However, if I'm not 
>>> mistaken, that makes all branches in sagetrac-mirror readonly and thus one 
>>> cannot continue working on existing PRs by pushing to the corresponding 
>>> branch in sagetrac-mirror. 
>>>
>>> IMHO the plan is to create new PRs in sagemath/sage, not in 
>>> sagemath/sagetrac-mirror 
>>> There won't be "existing" PRs, only issues, pointing to branches on 
>>> sagetrac-mirror 
>>>
>>>
>>>
>>> > On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com 
>>> wrote: 
>>> >> 
>>> >> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 
>>> UTC+2: 
>>> >>> 
>>> >>> 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. 
>>> >> 
>>> >> Don’t we need an issue for the first point, as well? The example #26 
>>> corresponds to #34110 which is not easy to recover from the migrated 
>>> information. 
>>> >> 
>>> >> Furthermore, it isn’t still clear to me how dependencies between PRs 
>>> will be visible (like in the Trac dependencies field). In the above example 
>>> you have to recover this from the history of commit messages (which may not 
>>> be clear enough in general). Shouldn’t the migration put something into the 
>>> header fields milestone, assignees, …, as well (if possible)? How will 
>>> authors and reviewers be visible? 
>>> > 
>>> > -- 
>>> > 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/d815783e-fd5c-4aa3-ab27-7024b18b299dn%40googlegroups.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 
>>

Re: [sage-devel] DISCUSS: move Sage development to Github

The first proposed Issue template can be seen 
here: https://github.com/sagemath/sage-gh-templates-sandbox/issues/new/choose
See 
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
 


On Tuesday, September 27, 2022 at 12:13:13 PM UTC-7 Matthias Koeppe wrote:

> I've created https://github.com/sagemath/sage-gh-templates-sandbox for 
> playing with Issue and PR templates.
>
> On Friday, September 23, 2022 at 12:50:05 PM UTC-7 Matthias Koeppe 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.
>>
>> https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
>>
>> https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
>>
>> On Friday, September 23, 2022 at 9:51:55 AM UTC-7 Matthias Koeppe wrote:
>>
>>> On Friday, September 23, 2022 at 7:51:24 AM UTC-7 kcrisman wrote:
>>>
 On the GH page documenting the transition and new workflow proposal, I 
 don't see a way to have multiple AUTHORs in the way we usually kept track 
 of it.
>>>
>>>
>>> I agree, this still needs to be specified. (Related: 
>>> https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/pPqbu13fAAAJ)
>>>
>>>
>>>
>>>  
>>>
>>

-- 
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/11b4072c-deca-457b-98a4-0da23ac6b147n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

I've created https://github.com/sagemath/sage-gh-templates-sandbox for 
playing with Issue and PR templates.

On Friday, September 23, 2022 at 12:50:05 PM UTC-7 Matthias Koeppe 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.
>
> https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
>
> https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
>
> On Friday, September 23, 2022 at 9:51:55 AM UTC-7 Matthias Koeppe wrote:
>
>> On Friday, September 23, 2022 at 7:51:24 AM UTC-7 kcrisman wrote:
>>
>>> On the GH page documenting the transition and new workflow proposal, I 
>>> don't see a way to have multiple AUTHORs in the way we usually kept track 
>>> of it.
>>
>>
>> I agree, this still needs to be specified. (Related: 
>> https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/pPqbu13fAAAJ)
>>
>>
>>
>>  
>>
>

-- 
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/301e5900-6aa7-48b1-8f99-3a1782e59c8bn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

On Tuesday, September 27, 2022 at 3:29:10 AM UTC-7 tobias...@gmail.com 
wrote:

> One more question: The current plan is to use the sagetrac-mirror repo as 
> the base for creating PRs but also to archived it. However, if I'm not 
> mistaken, that makes all branches in sagetrac-mirror readonly and thus one 
> cannot continue working on existing PRs by pushing to the corresponding 
> branch in sagetrac-mirror.


Thanks for catching this. I have 
revised 
https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b#conversion-of-trac-tickets-and-the-trac-wiki-to-github
 
as follows:

   1. Make a fork of sagemath/sagetrac-mirror called 
   sagemath/sagetrac-archive and archive 
    it 
   (= set it to readonly).
   2. Open PRs from sagemath/sagetrac-mirror 
    to the new repo for all 
   open tickets with attached branches.

 

-- 
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/be783180-49ff-4bf3-8d2d-f8db3bad749bn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

On Tuesday, September 27, 2022 at 1:02:06 AM UTC-7 seb@gmail.com wrote:

> Furthermore, it isn’t still clear to me how dependencies between PRs will 
> be visible (like in the Trac dependencies field).
>
This is an important point. 
See https://trac.sagemath.org/ticket/30363#comment:91

 

> 
>

-- 
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/4e8074fa-cde3-4d7f-9113-bdf87fa77ddan%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-27 Thread Dima Pasechnik

On Tue, 27 Sep 2022, 14:08 Tobias Diez,  wrote:

> Yes, the target repo of these PRs will be the (new) sagemath/sage, but the
> source will be sagemath/sagetrac-mirror, right?



Hmm, I might have missed something - what is the need to have 2 repos here,
if 1 is sufficient?

Any fork of sagemath/sage may be a source of a PR, not only sagetrac-mirror


So in order to update the pull request one needs to push the changes to
> sagemath/sagetrac-mirror (it is not possible to update a PR by pushing to
> /refs/pull/xyz, because this is readonly). Thus, if sagetrac-mirror is
> archived (and thus readonly), the only way to work on existing
> tickets/branches would be to checkout the existing branch (from either
> sagetrac-mirror or sage/refs/pull), make changes, push to a new fork,
> create a new PR, close the old PR (essentially the workflow
> https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally#modifying-an-inactive-pull-request-locally
> ).
>
> On Tuesday, 27 September 2022 at 13:59:45 UTC+2 dim...@gmail.com wrote:
>
>> On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez 
>> wrote:
>> >
>> > One more question: The current plan is to use the sagetrac-mirror repo
>> as the base for creating PRs but also to archived it. However, if I'm not
>> mistaken, that makes all branches in sagetrac-mirror readonly and thus one
>> cannot continue working on existing PRs by pushing to the corresponding
>> branch in sagetrac-mirror.
>>
>> IMHO the plan is to create new PRs in sagemath/sage, not in
>> sagemath/sagetrac-mirror
>> There won't be "existing" PRs, only issues, pointing to branches on
>> sagetrac-mirror
>>
>>
>>
>> > On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com
>> wrote:
>> >>
>> >> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46
>> UTC+2:
>> >>>
>> >>> 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.
>> >>
>> >> Don’t we need an issue for the first point, as well? The example #26
>> corresponds to #34110 which is not easy to recover from the migrated
>> information.
>> >>
>> >> Furthermore, it isn’t still clear to me how dependencies between PRs
>> will be visible (like in the Trac dependencies field). In the above example
>> you have to recover this from the history of commit messages (which may not
>> be clear enough in general). Shouldn’t the migration put something into the
>> header fields milestone, assignees, …, as well (if possible)? How will
>> authors and reviewers be visible?
>> >
>> > --
>> > 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/d815783e-fd5c-4aa3-ab27-7024b18b299dn%40googlegroups.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/6df40198-0d1a-45f4-ac1f-2bee6e07d313n%40googlegroups.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/CAAWYfq0Ku9tpQieEADjWcWE%2BYywNaknL3dsDjPtzJusF%2B8iCSQ%40mail.gmail.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

Yes, the target repo of these PRs will be the (new) sagemath/sage, but the 
source will be sagemath/sagetrac-mirror, right? So in order to update the 
pull request one needs to push the changes to sagemath/sagetrac-mirror (it 
is not possible to update a PR by pushing to /refs/pull/xyz, because this 
is readonly). Thus, if sagetrac-mirror is archived (and thus readonly), the 
only way to work on existing tickets/branches would be to checkout the 
existing branch (from either sagetrac-mirror or sage/refs/pull), make 
changes, push to a new fork, create a new PR, close the old PR (essentially 
the workflow 
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally#modifying-an-inactive-pull-request-locally).

On Tuesday, 27 September 2022 at 13:59:45 UTC+2 dim...@gmail.com wrote:

> On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez  wrote:
> >
> > One more question: The current plan is to use the sagetrac-mirror repo 
> as the base for creating PRs but also to archived it. However, if I'm not 
> mistaken, that makes all branches in sagetrac-mirror readonly and thus one 
> cannot continue working on existing PRs by pushing to the corresponding 
> branch in sagetrac-mirror.
>
> IMHO the plan is to create new PRs in sagemath/sage, not in
> sagemath/sagetrac-mirror
> There won't be "existing" PRs, only issues, pointing to branches on
> sagetrac-mirror
>
>
>
> > On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com wrote:
> >>
> >> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 
> UTC+2:
> >>>
> >>> 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.
> >>
> >> Don’t we need an issue for the first point, as well? The example #26 
> corresponds to #34110 which is not easy to recover from the migrated 
> information.
> >>
> >> Furthermore, it isn’t still clear to me how dependencies between PRs 
> will be visible (like in the Trac dependencies field). In the above example 
> you have to recover this from the history of commit messages (which may not 
> be clear enough in general). Shouldn’t the migration put something into the 
> header fields milestone, assignees, …, as well (if possible)? How will 
> authors and reviewers be visible?
> >
> > --
> > 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/d815783e-fd5c-4aa3-ab27-7024b18b299dn%40googlegroups.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/6df40198-0d1a-45f4-ac1f-2bee6e07d313n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-27 Thread Dima Pasechnik

On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez  wrote:
>
> One more question: The current plan is to use the sagetrac-mirror repo as the 
> base for creating PRs but also to archived it. However, if I'm not mistaken, 
> that makes all branches in sagetrac-mirror readonly and thus one cannot 
> continue working on existing PRs by pushing to the corresponding branch in 
> sagetrac-mirror.

IMHO the plan is to create new PRs in sagemath/sage, not in
sagemath/sagetrac-mirror
There won't be "existing" PRs, only issues, pointing to branches on
sagetrac-mirror



> On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com wrote:
>>
>> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 UTC+2:
>>>
>>> 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.
>>
>> Don’t we need an issue for the first point, as well? The example #26 
>> corresponds to #34110 which is not easy to recover from the migrated 
>> information.
>>
>> Furthermore, it isn’t still clear to me how dependencies between PRs will be 
>> visible (like in the Trac dependencies field). In the above example you have 
>> to recover this from the history of commit messages (which may not be clear 
>> enough in general). Shouldn’t the migration put something into the header 
>> fields milestone, assignees, …, as well (if possible)? How will authors and 
>> reviewers be visible?
>
> --
> 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/d815783e-fd5c-4aa3-ab27-7024b18b299dn%40googlegroups.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/CAAWYfq2J9Ksersn9LHhBayWg4%2BEV4nuyEZBYH%3DD5FxumXwRMsg%40mail.gmail.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

One more question: The current plan is to use the sagetrac-mirror repo as 
the base for creating PRs but also to archived it. However, if I'm not 
mistaken, that makes all branches in sagetrac-mirror readonly and thus one 
cannot continue working on existing PRs by pushing to the corresponding 
branch in sagetrac-mirror.
On Tuesday, 27 September 2022 at 10:02:06 UTC+2 seb@gmail.com wrote:

> Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 UTC+2:
>
> 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.
>>
> Don’t we need an issue for the first point, as well? The example #26 
>  corresponds to #34110 
>  which is not easy to recover 
> from the migrated information.
>
> Furthermore, it isn’t still clear to me how dependencies between PRs will 
> be visible (like in the Trac dependencies field). In the above example you 
> have to recover this from the history of commit messages (which may not be 
> clear enough in general). Shouldn’t the migration put something into the 
> header fields milestone, assignees, …, as well (if possible)? How will 
> authors and reviewers be visible?
> 
>

-- 
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/d815783e-fd5c-4aa3-ab27-7024b18b299dn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-27 Thread seb....@gmail.com



Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 UTC+2:

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.
>
Don’t we need an issue for the first point, as well? The example #26 
 corresponds to #34110 
 which is not easy to recover from 
the migrated information.

Furthermore, it isn’t still clear to me how dependencies between PRs will 
be visible (like in the Trac dependencies field). In the above example you 
have to recover this from the history of commit messages (which may not be 
clear enough in general). Shouldn’t the migration put something into the 
header fields milestone, assignees, …, as well (if possible)? How will 
authors and reviewers be visible?


-- 
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/bb6690bd-809b-41d8-a0ed-8b45f6b4def9n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-26 Thread Matthias Koeppe

On Monday, September 26, 2022 at 1:35:04 AM UTC-7 Eric Gourgoulhon wrote:

>  
>
>> 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.  
>>
>
> As I said earlier, discussions on Trac constitute a very valuable database 
> for Sage development. As far as I am concerned, I learned a lot from them. 
> It would be a pity to lose them.
>

Yes, of course, that's why the plan is to convert all tickets to Issues! 
That includes all closed tickets and all comments on the tickets.
Preview of converted tickets: https://github.com/sagemath/trac_to_gh/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/85538f7a-91d1-4059-9b92-a36bfa9c33cbn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-26 Thread Dima Pasechnik

On Mon, Sep 26, 2022 at 10:26 AM Tobias Diez  wrote:
>
>
>
>> 2. Convert all tickets to Issues in a new repo. (This preserves the ticket 
>> numbers as Issue numbers.)
>
>
> Would it make sense to convert tickets with branches directly to 
> pull-requests?

only open tickets.
Closed tickets are served well enough by changing links to branches on
sagetrac-mirror.

>  Since most of them probably already contain quite a bit of discussion about 
> the implementation, which you would like to have as a easy reference if you 
> would review the PR later.
>
>>
>> 4. Replace sagemath/sage by the new repo.
>
>
>  If you rename a repo (in our case sage -> sage-old), then github adds 
> redirects for issues etc in sage to sage_old. So it should be double-checked 
> that you can later indeed add a new repo with the name sage.
>
> --
> 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/6418ac37-a858-447a-be9f-f7d7f4da9461n%40googlegroups.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/CAAWYfq31AH0uPEBpqPOSOtuidD2TdmrNe%3D%2BQE1ow68wMuH%3Dyyw%40mail.gmail.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-26 Thread Tobias Diez



2. Convert all tickets to Issues in a new repo. (This preserves the ticket 
> numbers as Issue numbers.)
>

Would it make sense to convert tickets with branches directly to 
pull-requests? Since most of them probably already contain quite a bit of 
discussion about the implementation, which you would like to have as a easy 
reference if you would review the PR later. 
 

> 4. Replace sagemath/sage by the new repo.
>

 If you rename a repo (in our case sage -> sage-old), then github adds 
redirects for issues etc in sage to sage_old. So it should be 
double-checked that you can later indeed add a new repo with the name 
sage.  

-- 
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/6418ac37-a858-447a-be9f-f7d7f4da9461n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-26 Thread Eric Gourgoulhon

Le samedi 24 septembre 2022 à 13:57:36 UTC+2, kcrisman a écrit :

>
> 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"
>
>
This is a good point IMHO. In particular, there are zillions of links to 
Trac from the sage-devel threads.
 

> 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.  
>

As I said earlier, discussions on Trac constitute a very valuable database 
for Sage development. As far as I am concerned, I learned a lot from them. 
It would be a pity to lose them. 

Eric. 

-- 
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/e6bac55f-8cd2-4bcd-9308-d411a34d5eben%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-26 Thread Kwankyu Lee

On Monday, September 26, 2022 at 3:17:03 PM UTC+9 Kwankyu Lee wrote:

> On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote:
>
>> Is there a vision for what Sage 10.0 means?
>
>
 Yes. See the headline of 

https://trac.sagemath.org/ticket/29705

-- 
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/241796ef-94a6-4bdd-b4a7-500460e9496dn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-26 Thread Kwankyu Lee



On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote:

> Is there a vision for what Sage 10.0 means?


Sage X :) 

-- 
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/aa5f330a-60cd-4657-92af-0ee438fc98e9n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-25 Thread Matthias Koeppe

I don't think it's useful to reflect this change in a version number. I 
think it can just happen in the middle of the 9.8 release cycle.

On Sunday, September 25, 2022 at 8:21:41 PM UTC-7 John H Palmieri wrote:

> Will the changeover also mark Sage 10.0? Is there a vision for what Sage 
> 10.0 means?
>
> On Saturday, September 24, 2022 at 8:48:15 PM UTC-7 Matthias Koeppe wrote:
>
>> 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/5f91d2ee-d54c-47ed-a126-bc1152fa7209n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

2022-09-25 Thread John H Palmieri

Will the changeover also mark Sage 10.0? Is there a vision for what Sage 
10.0 means?

On Saturday, September 24, 2022 at 8:48:15 PM UTC-7 Matthias Koeppe wrote:

> 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/76dfd93f-e254-46e1-b86b-988e1ff88c60n%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.

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

2022-09-24 Thread John H Palmieri

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 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

2022-09-24 Thread TB

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

2022-09-24 Thread William Stein

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