GitHub issues burndown chart & survival analysis

Open
#8 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
sql
Domain
analytics, data-visualization, databases

Research direction

Start with the linked Observable notebook and the GitHub issue dataset used there, then review how the burndown and survival-analysis charts are produced. Done is not defined: the post shares an exploration but does not request a repository change or specify an acceptance condition.

Written by the indexing model from the issue text.

Description

Hello, thanks for providing this dataset!

Not sure if this is the right place to post, but I used it my Observable notebook to analyze how long do issues "live" and to create some "burndown" charts.

After playing a bit with Observable + ClickHouse, I found it to be a great combo for performing and sharing such explorations.

Here are some charts for ClickHouse repo:

image image
Dominant language
HTML
Stars
180
Forks
19
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ClickHouse/github-explorer

All issues in ClickHouse/github-explorer

Similar issues

More Data Visualization issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.