slackware activity By The Numbers
by Pithium from LinuxQuestions.org on (#5AS6W)
Hi All,
I've been working on a fun project that I'd like to share with the class. Something I've run into issues with as a slackware user is an effective way to communicate the "aliveness" of the project. For users new to Slackware or Linux in general it can be difficult to simply refer them to the changelog. You also need to aggregate all active changelogs, not just -current.
So...I decided to write some python scripts to parse and analyze the data contained in all slackware changelogs (-current and older versions) in order to provide myself with numerical talking points. The scripts are still fragile, however I have reached the point where I'm semi confident in the numbers I've got and would like to share that info with everyone. If you got this far and are interested in slackware package statistics, read on!
I'm counting the number of changes PV makes to slackware on a per package basis. Every time Pat adds, removes, upgrades, or otherwise changes a package he notes this in the changelog and datestamps it. I parse this into an sqlite file and then query that on the basis of version, timeframe, etc. As an example, here is a raw count of all changes made to a given slackware version from 12.0 onwards..
Code:12 1783
12.1 1410
12.2 964
13 3909
13.1 3451
13.37 4134
14 5237
14.1 7395
14.2 8867
-current 26514( this is based on the changelogs as of November 23, 2020 )
For those of you who are more visual, I've attached a graph of the same data made in libreoffice. You could say that these numbers represent Pat's workload in totality, since all of these updates go through him at some point in slackware's process. I plan to release a more comprehensive analysis of slackware dev activity once I'm more confident in my parsing scripts. The general idea is to have a way to "advertise" the work being done in a simple and factual way.
If anyone has any thoughts let me know. In particular if there are any specific trends you guys would like to look at I'm looking for ideas.
Attached Thumbnails
I've been working on a fun project that I'd like to share with the class. Something I've run into issues with as a slackware user is an effective way to communicate the "aliveness" of the project. For users new to Slackware or Linux in general it can be difficult to simply refer them to the changelog. You also need to aggregate all active changelogs, not just -current.
So...I decided to write some python scripts to parse and analyze the data contained in all slackware changelogs (-current and older versions) in order to provide myself with numerical talking points. The scripts are still fragile, however I have reached the point where I'm semi confident in the numbers I've got and would like to share that info with everyone. If you got this far and are interested in slackware package statistics, read on!
I'm counting the number of changes PV makes to slackware on a per package basis. Every time Pat adds, removes, upgrades, or otherwise changes a package he notes this in the changelog and datestamps it. I parse this into an sqlite file and then query that on the basis of version, timeframe, etc. As an example, here is a raw count of all changes made to a given slackware version from 12.0 onwards..
Code:12 1783
12.1 1410
12.2 964
13 3909
13.1 3451
13.37 4134
14 5237
14.1 7395
14.2 8867
-current 26514( this is based on the changelogs as of November 23, 2020 )
For those of you who are more visual, I've attached a graph of the same data made in libreoffice. You could say that these numbers represent Pat's workload in totality, since all of these updates go through him at some point in slackware's process. I plan to release a more comprehensive analysis of slackware dev activity once I'm more confident in my parsing scripts. The general idea is to have a way to "advertise" the work being done in a simple and factual way.
If anyone has any thoughts let me know. In particular if there are any specific trends you guys would like to look at I'm looking for ideas.
Attached Thumbnails