niccokunzmann/python-recurring-ical-events

1 repository
All time.
100% of the data (299 of 299 items)
Read from GitHub

    Data sources

    RepositoryPull requestsIssuesCompleteRead
    niccokunzmann/python-recurring-ical-events 176 / 176 123 / 123 100% 1 day ago

    Download the data behind this page. The ODS spreadsheets also have the data each table was made from, and what the download is.

    How to check the numbers with scipy.

    Sources shown

    Pull requests (176)
    4
    open
    160
    merged
    12
    closed unmerged
    Issues (123)
    25
    open
    98
    closed

    Response times

    Time until the first response of each class of people (edit classes). The author's own comments do not count. Measured, normal and exponential use only the items that got a response; Kaplan-Meier counts the others, too, as waiting at least until they were closed or until now, and is "-" where less than half (or 95 %) got a response.

    What the statistics mean
    classnfitaveragestd errormedian95%
    bot1measured1min-1min1min
    bot1normal1min-1min-
    bot1exponential1min1min1min4min
    bot176Kaplan-Meier----
    collaborator or higher50measured14d 4h3d 20h14h 28min61d 6h
    collaborator or higher50normal14d 4h3d 19h14d 4h58d 9h
    collaborator or higher50exponential14d 4h2d9d 20h42d 12h
    collaborator or higher176Kaplan-Meier--32d 22h132d 14h
    external10measured5d 12h1d 20h2d 22h14d 11h
    external10normal5d 12h1d 18h5d 12h14d 16h
    external10exponential5d 12h1d 17h3d 19h16d 12h
    external176Kaplan-Meier----

    n counts the items with a response of the class. Kaplan-Meier counts all items, so its n is the same for every class: the items without a response of the class count as waiting, until they were closed or until now. How to read the response times

    Trend: no clear change of the time until the first response over time (p = 0.92, 60 responses). How the trend is computed

    What the statistics mean
    classnfitaveragestd errormedian95%
    collaborator or higher58measured10d 10h5d 7h12h 27min29d 22h
    collaborator or higher58normal10d 10h5d 6h10d 10h76d 7h
    collaborator or higher58exponential10d 10h1d 8h7d 5h31d 5h
    collaborator or higher123Kaplan-Meier--55d 21h-
    external15measured161d 3h70d 7h48d 5h613d 16h
    external15normal161d 3h67d 22h161d 3h593d 23h
    external15exponential161d 3h41d 14h111d 16h482d 17h
    external123Kaplan-Meier----

    n counts the items with a response of the class. Kaplan-Meier counts all items, so its n is the same for every class: the items without a response of the class count as waiting, until they were closed or until now. How to read the response times

    Trend: no clear change of the time until the first response over time (p = 0.59, 64 responses). How the trend is computed

    Badges

    Embed the response time in a README. The badge counts with the default classes of people. The badge shows what is in the database and never calls GitHub. Parameters: kind = pr or issue, percentile = 0-100, class = a class name (optional), model = measured, normal, exponential or kaplan-meier (optional), label = the text of the left side (optional).

    badge preview