[sage-devel] Re: Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Marc Mezzarobba
William Stein wrote: > Perhaps this is a bad criteria, e.g., > it excludes our webmaster (Harald Schilly), since he's done a lot to > support Sage, but I don't think he's contributed code to the library > -- at least I didn't find him in Dima's list from GitHub. Looks like he has: ~/co/sage:devel

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread William Stein
Hi, We could just declare that "You may vote if you have contributed to the source code of Sage" and leave it at that. The idea is to give people a criteria for voting. Perhaps this is a bad criteria, e.g., it excludes our webmaster (Harald Schilly), since he's done a lot to support Sage, but I

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Dima Pasechnik
On Tue, Sep 20, 2022 at 5:42 PM David Roe wrote: > > When I did this a few weeks ago there were only a couple hundred. I think > it's only showing people who have a github account linked to the email they > used on the commit (which may be lower than normal, since grad students and > postdocs

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Matthias Koeppe
On Tuesday, September 20, 2022 at 10:23:38 AM UTC-7 erik@gmail.com wrote: > I'm late to discussion (also sorry for top-posting) but I don't see any > discussion of a middle ground where rather than "switching" starkly to > GitHub, just enabling issues and PRs on GitHub and see how it goes.

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Dima Pasechnik
On Tue, Sep 20, 2022 at 6:23 PM E. Madison Bray wrote: > > I'm late to discussion (also sorry for top-posting) but I don't see any > discussion of a middle ground where rather than "switching" starkly to > GitHub, just enabling issues and PRs on GitHub and see how it goes. One of the main reaso

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread E. Madison Bray
I'm late to discussion (also sorry for top-posting) but I don't see any discussion of a middle ground where rather than "switching" starkly to GitHub, just enabling issues and PRs on GitHub and see how it goes. We tried the same experiment with GitLab some time ago with synchronizing to Trac, and

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Matthias Koeppe
I'd suggest that we merge this info into https://github.com/sagemath/website/blob/master/conf/contributors.xml, possibly using a new attribute "altnames" On Tuesday, September 20, 2022 at 9:49:47 AM UTC-7 Matthias Koeppe wrote: > > https://github.com/sagemath/sage-changelogs/blob/master/merger/

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Matthias Koeppe
https://github.com/sagemath/sage-changelogs/blob/master/merger/contributors/9.7 also has a good dataset (this is from the script that makes changelogs) On Tuesday, September 20, 2022 at 9:42:49 AM UTC-7 David Roe wrote: > When I did this a few weeks ago there were only a couple hundred. I thin

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread David Roe
When I did this a few weeks ago there were only a couple hundred. I think it's only showing people who have a github account linked to the email they used on the commit (which may be lower than normal, since grad students and postdocs may have used academic email accounts that are no longer active

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Dima Pasechnik
On Tue, Sep 20, 2022 at 5:30 PM William Stein wrote: > > On Tue, Sep 20, 2022 at 4:09 AM Dima Pasechnik wrote: > > > > On Tue, Sep 20, 2022 at 11:51 AM kcrisman wrote: > > > > > > > > >>> "Subscribed to sage-devel" might not be a good criteria. For example, > > >>> Harald Schilly has been the we

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread William Stein
On Tue, Sep 20, 2022 at 4:09 AM Dima Pasechnik wrote: > > On Tue, Sep 20, 2022 at 11:51 AM kcrisman wrote: > > > > > >>> "Subscribed to sage-devel" might not be a good criteria. For example, > >>> Harald Schilly has been the webmaster of Sage since 2007 and likely > >>> cares about this switch si

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Kwankyu Lee
On Tuesday, September 20, 2022 at 8:09:33 PM UTC+9 dim...@gmail.com wrote: > > (by the way, by looking at this list I found that johanrosenkilde > works for GitHub now :-)) Surprise! Johan did much work in coding theory in academy and in sage. -- You received this message because you are subs

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread Dima Pasechnik
On Tue, Sep 20, 2022 at 11:51 AM kcrisman wrote: > > >>> "Subscribed to sage-devel" might not be a good criteria. For example, >>> Harald Schilly has been the webmaster of Sage since 2007 and likely >>> cares about this switch since it can impact him, but I don't think he >>> reads sage-devel. >>>

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

2022-09-20 Thread kcrisman
> "Subscribed to sage-devel" might not be a good criteria. For example, >> Harald Schilly has been the webmaster of Sage since 2007 and likely >> cares about this switch since it can impact him, but I don't think he >> reads sage-devel. >> > >> If we're going to talk about previous practice, I ca