As a programmer, I think there’s something inherently pleasing about collecting and organizing data. Even more so when you can do it automatically. In that vein, let me introduce my latest nights-and-weekends side project:
- The number of registered users on
answers.ros.org dwarfs any other metric for the size of the ROS community.
- You can measure attention to the different ROS distros by tags on answers, or the number of repositories in each distro or commits to
ros/rosdistro. Over half of the commits in May 2019 were working on ROS2 Dashing
- Likewise, you can watch the Linux distros come and go
- One of the hottest new wiki pages (made this year) is how to install ROS in Turkish
- The number of emails to the ros_users mailing list dropped dramatically when
- Navigation-related repositories are among the most starred/forked/subscribed-to. (Also you can get a LOT done with the 5000 requests per hour the GitHub API gives you)
- You can plot the size of the backlog (issues/PRs) for any repo in
ros/rosdistro. I’ve been tracking the size of the navigation repo’s backlog for awhile now, and its sad that you can’t see in this chart the period when I’ve actively been trying to reduce it.
Anyway, thanks to Tully for granting me access to the Discourse and Google Analytics APIs. I still want to get my hands on the underlying wiki data and the raw logs from http://packages.ros.org (hit me up OSU OSL). There’s lots more that can be gleaned from this data. The graphs I’ve made just scratch the surface. I look forward to using the data to help us understand and improve the ROS community/ecosystem.
Send me a message if you want access to the aggregated database files.