Improve GitHub processing and reporting

[TimidRobot]

Problem

The GitHub data reporting has never been finalized and has not been included in reports (for example Quantifying the Commons 2025Q3).

Description

Update scripts/3-report/github_report.py (and scripts/2-process/github_process.py, if necessary) to meaningfully add to the quarterly report.

Additional context

The most difficult aspect of this work is determining what is "meaningful".

Implementation

• I would be interested in implementing this feature.

[oree-xx]

Hi @TimidRobot yh I noticed this in the code base. But I don't quite understand what you mean by meaningful? like interesting information or insight we can get from it?

[TimidRobot]

@oree-xx Great question! I've tried to answer in the new Meaningful section of the repository README.

[oree-xx]

@TimidRobot ohh nice, I would check it out.

[Goziee-git]

@oree-xx Great question! I've tried to answer in:

• Add Meaningful section to Overview (in repository README) #171
  @TimidRobot very nice of you to provide context with these question! i appreciate this

[oree-xx]

@TimidRobot I tried identifying some meaningful data we can get from github.

• First we can look at licenses with highest usage
• Changes in the usage of licenses (quarterly)
• Identifying how much of github content is code and how much is not code(code license: MIT, BSD, Unlicense and non code license: CC0, CC_BY)
• We can compare the licenses based on the level of restrictions (can developers reuse code or not?) (copy left, permissive, public domain)
• The percentage of repositories using licenses that requires attribution.

I am thinking aloud, if anyone has interesting questions/insight we could get from the data. You can also learn about spdx license identifier used in the github_count dataset here.
https://en.wikipedia.org/wiki/Software_Package_Data_Exchange.