PyCalendar/edit-icalendar

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

    Data sources

    RepositoryPull requestsIssuesCompleteRead
    PyCalendar/edit-icalendar 0 / 0 9 / 9 100% 1 day, 7 hours 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 (0)
    0
    open
    0
    merged
    0
    closed unmerged
    Issues (9)
    9
    open
    0
    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.

    Trend: too few responses to tell whether they get faster or slower. How the trend is computed

    What the statistics mean
    classnfitaveragestd errormedian95%
    collaborator or higher1measured3h 53min-3h 53min3h 53min
    collaborator or higher1normal3h 53min-3h 53min-
    collaborator or higher1exponential3h 53min3h 53min2h 42min11h 39min
    collaborator or higher9Kaplan-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: too few responses to tell whether they get faster or slower. 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