[Feature] Post-GSoC ’24: Expand Shared Module

[naishasinha]

Context

Automating Quantifying the Commons was a project endeavor for the Google Summer of Code 2024 program, in which a baseline automation software for data gathering, processing, and analysis was successfully developed. However given the time and resource constraints that we had to consider, there are still addressable endeavors to improve this codebase over the upcoming quarters and years. This is the fourth (4) of five (5) issues raised specifically for post-GSoC contributions.

Problem

There are many overlapping paths, modules, and functions across different files which may be redundant and inefficient in the codebase.

Description

This feature involves expanding the shared module to include apparent commonly used paths, modules, and functions across different files. This will reduce redundancy and improve the maintainability and efficiency of the codebase. This should NOT, however, target the retrieve_license_data and related fetching/report functions, as they are still in the initial stages of development.

Implementation

• I would be interested in implementing this feature.

[shadcy]

1. Are there any specific patterns or examples of redundancy you’ve already identified that I can start with?
2. Is there an existing shared module structure I should follow, or would it be helpful to propose a new one based on what I find?
   Looking forward to your guidance—

Edit 1 : Got it!