On Tue, Sep 20, 2022 at 5:42 PM David Roe <roed.m...@gmail.com> 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 may have used academic email accounts that are no longer active).
I've run gh (not as insane as curl IMHO) to get the data: $ gh api -H "Accept: application/vnd.github.v3+json" -X GET /repos/sagemath/sage/contributors -F per_page=100 -F page=13 -F anon=1 and got, I guess, about 1300 contributors (quite a few by the same person, but different emails etc), see attachment > > I'm sure we could get a full list of author names from git. > David > > On Tue, Sep 20, 2022 at 12:35 PM Dima Pasechnik <dimp...@gmail.com> wrote: >> >> On Tue, Sep 20, 2022 at 5:30 PM William Stein <wst...@gmail.com> wrote: >> > >> > On Tue, Sep 20, 2022 at 4:09 AM Dima Pasechnik <dimp...@gmail.com> wrote: >> > > >> > > On Tue, Sep 20, 2022 at 11:51 AM kcrisman <kcris...@gmail.com> 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. >> > > >>> >> > > >>> >> > > > >> > > > If we're going to talk about previous practice, I can't remember there >> > > > ever being any criterion other than the sage-devel one. (And I think >> > > > a few votes have been received by proxy in the past.) >> > > > >> > > > I still can't find a thread about rules for voting, but I did find >> > > > this presumably relevant one, on another at-least-as controversial >> > > > topic (but please let's not revisit past controversies): So I'll >> > > > withdraw my 2/3 proposal, but suggest we do keep sage-devel as the >> > > > criterion. >> > > > https://groups.google.com/g/sage-devel/c/dR3_eyIUyac/m/LyALpiLcHuQJ >> > > > Quoting from William (8 years ago!!!) >> > > > >> > > > This is a simple majority vote for ... >> > > > I will close voting on Monday at midnight PST. (If the vote >> > > > is an exact tie, then that means "No" - there must be a simple >> > > > majority for this to pass.) Any member of the sage-devel mailing >> > > > list may vote or abstain. I will delete any messages in this thread >> > > > that is not a vote -- if you want to make further arguments for or >> > > > against, do so elsewhere. >> > > > >> > > > And from >> > > > https://groups.google.com/g/sage-devel/c/dR3_eyIUyac/m/Ooek9-z_oQgJ >> > > > I kept the voting simple and >> > > > consistent with how we've done all past votes, rather than using a >> > > > more complicated voting system, since I didn't want to make even the >> > > > voting process itself contentious. >> > > >> > > Given the tensions, I'd be more careful here. We're really not too >> > > interested in opinions of random subscribers to sage-devel >> > > (I don't have enough rights to see who's there). >> > > >> > > We can instead use >> > > https://github.com/sagemath/sage/graphs/contributors >> > >> > Does that only show the top 100? Is there any way to see more? >> >> Sure, see >> https://docs.github.com/en/rest/repos/repos#list-repository-contributors >> One can get all via REST API >> >> > There's been far more than 100 contributors to sage... >> > >> > > (by the way, by looking at this list I found that johanrosenkilde >> > > works for GitHub now :-)) >> > > >> > > 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 view this discussion on the web visit >> > > > https://groups.google.com/d/msgid/sage-devel/ea60ae31-33c6-45d3-86d5-4ca14169bcf0n%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/CAAWYfq1eij_nn_Fq_xsnioz%3Ds3gip%2B_RjXm_bm7sA8ACjxbc5Q%40mail.gmail.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/CACLE5GB%2Bp6m194jXHWL6AZZNjhbyKHadb%2Bp0nS7ai91%2BMWe9aQ%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/CAAWYfq3PZDwL1gXG1zqfi%3DZC3vQLZdbLY3mbc_4JN%2B-kFcyLwA%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/CAChs6_mYXCmYdCOS3fkX2Ny1tDG880MkjecdqhUdGfrCA4N9hQ%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/CAAWYfq3GPFXvs45mT_dU4S2hvKDpNL01XZSC5TFqCnVt1_X8hA%40mail.gmail.com.
contrib.json
Description: application/json
