3 ms·

I've never heard of Calcite before and dug a bit deeper into this project and found it to be quite active. Only taking into consideration changes to Java files

by sdesol 5y ago

I've never heard of Calcite before and dug a bit deeper into this project and found it to be quite active. Only taking into consideration changes to Java files, this is the repo activity for the last 12 months: month | authors | commits | files | churn ---------+---------+---------+-------+------- 2022-02 | 21 | 62 | 84 | 4387 2022-01 | 26 | 109 | 243 | 32429 2021-12 | 33 | 99 | 198 | 10461 2021-11 | 19 | 49 | 77 | 6960 2021-10 | 26 | 64 | 371 | 13626 2021-09 | 18 | 41 | 68 | 2258 2021-08 | 11 | 17 | 25 | 1924 2021-07 | 17 | 30 | 51 | 2704 2021-06 | 14 | 31 | 28 | 1708 2021-05 | 9 | 17 | 35 | 1606 2021-04 | 11 | 46 | 99 | 4224 2021-03 | 16 | 36 | 143 | 8471

riverdroid 5y ago
What do you use to produce this analysis?
- sdesol 5y ago
  My product (https://gitsense.com https://gitsense.com) moves most of Git's history into a Postgres database and from there, you can execute the following SQL statement: select commit_ym AS month, count(distinct(author_email)) as authors, count(distinct(commit_id)) as commits, count(distinct(path_id)) as files, sum(total) as churn from z1_commits_422 as commits, z1_changes_422 as changes, z1_code_churn_422 as churn where commits.id=changes.commit_id and changes.code_churn_id=churn.id and lang='java' group by commit_ym order by commit_ym desc limit 12 By having most of Git's history in SQL, I can slice, dice and cross-reference code history, which is how my product works.
michaelmior 5y ago
The community is also great. Honestly, the main thing preventing things from moving faster is lack of time to review PRs. There's a lot of interesting things in the pipe!
- sdesol 5y ago
  Yeah I can see what you mean. There are currently 20 open pull requests [1] that hasn't changed in over 28 days, which accounts for 53% of all open pulls that are less than 4 months old. 1) https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D120&t=crc-insights&tb=open&v=apache%2Fcalcite%3A%3Agithub%3Aapache%2Fcalcite%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D...

by sdesol 5y ago

riverdroid 5y ago

What do you use to produce this analysis?

sdesol 5y ago
My product (https://gitsense.com https://gitsense.com) moves most of Git's history into a Postgres database and from there, you can execute the following SQL statement: select commit_ym AS month, count(distinct(author_email)) as authors, count(distinct(commit_id)) as commits, count(distinct(path_id)) as files, sum(total) as churn from z1_commits_422 as commits, z1_changes_422 as changes, z1_code_churn_422 as churn where commits.id=changes.commit_id and changes.code_churn_id=churn.id and lang='java' group by commit_ym order by commit_ym desc limit 12 By having most of Git's history in SQL, I can slice, dice and cross-reference code history, which is how my product works.

michaelmior 5y ago

The community is also great. Honestly, the main thing preventing things from moving faster is lack of time to review PRs. There's a lot of interesting things in the pipe!

sdesol 5y ago
Yeah I can see what you mean. There are currently 20 open pull requests [1] that hasn't changed in over 28 days, which accounts for 53% of all open pulls that are less than 4 months old. 1) https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D120&t=crc-insights&tb=open&v=apache%2Fcalcite%3A%3Agithub%3Aapache%2Fcalcite%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D...