Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add license info to repo_metrics #1388

Closed
ccerv1 opened this issue May 9, 2024 · 2 comments · Fixed by #1431
Closed

Add license info to repo_metrics #1388

ccerv1 opened this issue May 9, 2024 · 2 comments · Fixed by #1431
Assignees
Labels
c:data Gathering data (e.g. indexing)
Milestone

Comments

@ccerv1
Copy link
Member

ccerv1 commented May 9, 2024

Describe the feature you'd like to request

We need to extract current license information for all repos linked to projects in staging and expose them in our int_repo_metrics_by_project model.

Specifically, we need the field spdxId. See here for an ad hoc fetcher I've used in the past.

Describe the solution you'd like

Option 1: we grab the current license info alongside other current repo stats like stars, forks, etc

Option 2: we create a timestamped history of license changes for all repos we care about (ie, we write the status daily or monthly)

Describe alternatives you've considered

Continue to do this ad hoc using a script, just for repos we care about

@ccerv1 ccerv1 added the c:data Gathering data (e.g. indexing) label May 9, 2024
@ccerv1 ccerv1 added this to the (c) Op RF4 milestone May 9, 2024
@ccerv1
Copy link
Member Author

ccerv1 commented May 15, 2024

@ravenac95 all of the licenses are coming back null ...

SELECT 
  name_with_owner,
  license_name,
  license_spdx_id
FROM `oso.repositories_ossd`
where license_name is not null

@ccerv1
Copy link
Member Author

ccerv1 commented May 17, 2024

Also tagging the dbt model implementations #1433

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:data Gathering data (e.g. indexing)
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants