I Was Wrong About Hive's Development Activity

Hey everyone,

Yesterday, I posted a little tool I wrote to analyze the commit history of a git repository and came to a conclusion that was, frankly, wrong. In that post, I suggested that Hive's development might be slowing down. Thanks to a timely comment from Hive account@gtg, I've realized I was looking at a very incomplete picture.

The Flaw in My Data

My original script only analyzed the commit history of a repository's default branch. As Hive account@gtg correctly pointed out, this completely ignores all the work being done in development, feature, and fix branches. To get a real sense of a project's activity, you have to look at the whole picture.

Digging Deeper with a New Tool

So, after a lot of trial and error, I've written another script that can analyze multiple branches at once. It's a bit more complex, but it gives a much more accurate view of a project's history. For anyone interested, you can find the new script here:

• Gist: https://gist.github.com/TheCrazyGM/e1cf793e21b263a390bbc3ddcf899f3c

The Real Picture of Hive Development

I ran this new script on the main hive repository with a strict filter: I only included branches that have been active within the last 90 days. I was expecting to see a handful, but I was wrong. The result shows a huge number of active branches, painting a picture of an incredibly active and vibrant development ecosystem.

And as a comparison, the Hive-Engine repo Active Last 90 days.

I want to sincerely apologize for jumping to the wrong conclusion. It was a good lesson in making sure you're analyzing the complete dataset before drawing any insights. The Hive developers are clearly working hard, and it's exciting to see.

As always,
Michael Garcia a.k.a. TheCrazyGM