Raymond Cheng

Yes! That's a great idea. I'm curious if you have any suggestions for how to encode the nested project schema? https://github.com/opensource-observer/oss-directory/blob/main/src/resources/schema/project.json Would you just create the equivalent relational tables to...

https://pypi.org/project/oss-directory/

This PR adds `any_evm` to the schema in oss-directory https://github.com/opensource-observer/oss-directory/pull/298 Tossing it over to @ravenac95 to update the semantics in the dbt pipeline

This adds ANY_EVM semantics to the dbt pipeline https://github.com/opensource-observer/oso/pull/1540

For the RetroPGF requirements, there's a separate issue. Let's not expand the scope of this issue https://github.com/opensource-observer/oso/issues/1175

I think we talked about this during a standup, but perhaps we forgot to take down some notes. The current thinking is that we update our semantics: - No 2...

@ravenac95 I think we still need to update the dbt pipeline to reflect these semantics @ccerv1 younsaid you already had part of this?

One idea is expose all twitter handles as artifacts, which you can query via artifacts_by_project. Something like artifact_source=TWITTER artifact_name=@handle Should artifact_namespace be null? which kinda sets us up for tracking...

Done here https://github.com/opensource-observer/oso/pull/2078

For now at least, we need to take a final version of [this model](https://github.com/opensource-observer/oso/blob/main/warehouse/dbt/models/marts/superchain/rf4_repo_stats_by_project.sql) and adding a field [in here](https://github.com/opensource-observer/oso/blob/main/warehouse/dbt/models/marts/superchain/rf4_project_verification.sql)