Dhiraj Bokde

Thanks @Al-Pragliola for the detailed response. See comments below: > Decoupling: I wanted to keep the dependencies from the migration and ORM libraries to a minimum so that, if one...

BTW, the sample migration implementation I shared was for a continuously released SaaS. So, we had to be able to turn around changes asap if we ran into bugs/feature fixes,...

If the team has made the final decision on going with golang migrate and using direct DDL, that's fine by me. I do have some questions: 1. Are we still...

Thanks for the detailed response @Al-Pragliola > We can use https://gorm.io/gen/database_to_structs.html, as we do with OpenAPI, to generate the types and methods of the REST API. We can use the...

@syntaxsdev nice work with the chunk transfer support. Considering the size of the file, would it make sense to split utils.py further for helping new devs/users reading the code?

@andreyvelich @thesuperzapper we're working on a design for a simple model catalog API wrapper for local and remote catalogs like Hugging Face. I'll add more details with diagram, etc. to...

A proposed high level architecture would like below. A configmap can be used to configure a small amount of high level metadata about a collection of catalog sources, such as...

The OpenAPI version is [here](https://github.com/kubeflow/model-registry/pull/725/files#diff-76e892700d0c69e6da9e12e5f92028b640e18a02d359d3e7fc4a32854a10dc9d) in the initial version [PR](https://github.com/kubeflow/model-registry/pull/725/).

> I think it makes sense to isolate the load/traffic of catalog operations from the core model-registry. This proposal doesn't take that option away. If the model registry container image...

>We should be careful in displaying the RegisteredModels in the Catalog, as models in MR are under strict RBAC rules. The catalog must use logged-in user credentials to verify their...