Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sebastian Benthall
    @sbenthall
    #269 A Mac NLTK installation issue.
    I can't test this one because I use Linux.
    I was hoping BBIP 1 (Conda installation) would solve this, #248 , but we canned that proposal because of cross-platform issues.
    So this remains. I'm assigning to @npdoty just because I'm powerless to do anything about it.
    Next:
    #264 - Documentation ticket from 2016
    Sebastian Benthall
    @sbenthall
    I'm going to close this as a duplicate of #286, the other documentation ticket.
    Next:
    #252 reconciling the different entity resolutions scripts.
    Currently assigned to @npdoty . The scope of this one is a little uncertain. I'm going to make the call that we can punt this one to 0.3
    Next:
    #246 - a notebook error in setting the date range index
    Sebastian Benthall
    @sbenthall
    I can't reproduce the error, so I'm not sure what to do. It's currently assigned to @npdoty .
    There have been some PR's merged that touch on issues similar to this issue recently. Maybe it's been fixed in the process?
    Next: #244 another notebook error
    In that ticket, @npdoty asks @nllz to see if he still gets the error after recent changes. So, assigned to @nllz
    Next: #117 an archives location ticket
    I think this was fixed in the process of fixing #113
    So I'm closing it.
    That's all the tickets for 0.2!
    Sebastian Benthall
    @sbenthall
    We have only 8 tickets left. 3 assigned to @nllz , 2 assigned to @npdoty , 2 assigned to @sbenthall , and one unassigned.
    I'll send an update to the list.
    Sebastian Benthall
    @sbenthall
    I've got a new PR for #278 ready for review. Hopefully this is the last one.
    Nick Doty
    @npdoty
    thanks for going through all of these, @sbenthall !
    I'm trying to understand the nltk-Mac issue, but there's not an especially clear bug for me to test
    is setup.py being actively used? it seems to be out of date/incomplete
    Nick Doty
    @npdoty
    filed a PR to improve the conda installation process, and I think it'll be enough to resolve #269
    Nick Doty
    @npdoty
    opened a PR (#333) to address #246
    Nick Doty
    @npdoty
    opened another PR (#334) this one for handling comments (and other better error handling) in the urls.txt files that we typically use
    Niels ten Oever
    @nllz
    we now have both descriptions in a description file and BigBang can deal with comments in a URL.txt file - supernice
    I was thinking, can we toss some of the branches to clean things up a bit?
    Nick Doty
    @npdoty
    yeah, we can probably delete all branches that come from PRs merged into master, but I don't think branches should typically have a cost for people in normal use
    Niels ten Oever
    @nllz
    Ah yeah, also, a new paper that used BigBang: https://onlinelibrary.wiley.com/doi/full/10.1002/poi3.172
    Just finished re-importing all IETF mailinglists; they all work except the ones mentioned in datactive/bigbang#314
    Niels ten Oever
    @nllz
    huh, actually they seem to work now!
    lemme check em all
    Niels ten Oever
    @nllz
    all lists working except https://ietf.org/mail-archive/text/ips/ \o/
    Nick Doty
    @npdoty
    nice
    Nick Doty
    @npdoty
    testing away today, writing tests is kinda fun and easy
    and a bunch of pull requests :))
    Niels ten Oever
    @nllz
    I did a videocall with Corinne to set her up with BigBang and walk her through it. It was actually a lot of fun, so I am willing to do it more, maybe for a group of ppl. So if we can find ppl who are interested to do this but are afraid to dip their toe in, happy to do some work on that. I also mentioned that in the blogpost
    Nick Doty
    @npdoty
    awesome!
    Sebastian Benthall
    @sbenthall
    Should probably mention-- our funding proposals to Ford/Sloan for BigBang development did not bear fruit. But there was something like a 5% acceptance rate to getting to the next round, so no reason to feel bad.
    What that could mean is that we try to recycle those applications for other funding opportunities.
    Niels ten Oever
    @nllz
    Hi @npdoty did you ever integrate the notebook with which you measure length of participation in IETF ?
    Nick Doty
    @npdoty
    @nllz apologies for a very belated reply!
    I merged in my changes from our last hackathon, including length of participation, into a branch of my fork: https://github.com/npdoty/bigbang/commits/ietf-participation
    the rendered notebook with "tenure" calculations is here, and it still seems reasonably readable, although it has plenty of caveats: https://github.com/npdoty/bigbang/blob/ietf-participation/ietf-participation/IETF%20Participants%20-%20Cohorts.ipynb