How do you use the Code Frequency graphs? #39757

https://github.com/illumos/illumos-gate/graphs/code-frequency

It would be nice to be able to filter the initial commit so that the commit activity is not so squished.

• How often do you use this graph? Rarely.
• Do you explore this graph in your own repositories, or for other repositories? Just illumos/illumos-gate
• What data are you looking to get from it? Data showing the effect that Oracle killing OpenSolaris had on Solaris. An older version of this page made it very obvious about 10 years ago.

How often do you use this graph?

Occasionally

Do you explore this graph in your own repositories, or for other repositories?

Both

What data are you looking to get from it?

• Is the code rather stable or changing heavily?
• Is the code maintained at all?

What could we do to make this data easier or better for you?

• The ability to choose parts of time would be nice, e.g. past 12 month.
• It would be nice to be able to filter the initial commit.

How often do you use this graph?

Whenever I push a significant amount of commits in a single coding session.

Do you explore this graph in your own repositories, or for other repositories?

Overwhelmingly my own.

What data are you looking to get from it?

Amount of lines written, number of commits per week. It helps keep working consistently on personal projects.

What could we do to make this data easier or better for you?

A small indicator that would give more precise numbers when hovering over curves would be greatly appreciated !

Anything else you think we should know?

I really liked the 3D rendering of the graphs. Not the most productive thing I toyed with, but it was fun to play with and did brighten my day.

I mostly use it to find major milestones (rewrites, significant development activity, etc) in a project's history to explore it more efficiently, especially in projects with many small commits. It would be nice if you could click to go to the commit history around that point in time.

How often do you use this graph?
Every time I evaluate bringing a new dependency in.

Do you explore this graph in your own repositories, or for other repositories?
Sometimes in my own, mostly in others.

What data are you looking to get from it?
Trying to get a quick "at a glance sense" of how actively this package is being updated or maintained, and looking at how long it has existed.

What actions do you expect to take using the data from this graph?
I choose to pull in or not pull a dependency if I see: No changes in multiple years, Massive continuous / recent changes (need to investigate why), or extremely short history.

What could we do to make this data easier or better for you?
I would love for this graph to display in the top bar of repositories as a kind of decoration.

Anything else you think we should know?
While LOC changed is a useful way to look at "repository activity" I would appreciate other ways to gauge the same thing: commit frequency, issue close frequency, average issue residency time, average time pull request is open.

My core objective is to quickly gauge how safe / good a dependency is, I'm often using relatively niche projects with star counts <500 and want to know how active / responsive maintenance is as quickly as possible.