Hello, I'm currently building a python package that derives some of the source code of Kedro, primarily the catalog and config classes. I might be open sourcing the package, how do I properly attribute Kedro? Any advice?

It’s Apache 2.0 so there are references on what attribution should look like! If it’s open source please post it here too!

Thanks @datajoely. My team is reluctant to add kedro pipelines but liked catalogs and the config management. Also I'm working on integrating lakefs and dvc for version control and dbt.

So making Kedro more modular and easier to use as a library is one of our goals for 2024 we’d love to learn more about what you’re doing and how we can better support you 🙂 cc @Juan Luis

hi @Javier Bosch, that sounds exciting! are you integrating both LakeFS and DVC? would be curious to know your perspective, as far as I understand there's some overlap between those but the mechanics are quite different

Yes I have, but I would get more support for something like the kedro dataset repo. I think one thing I see that could be a big improvement in kedro catalogs is how to share and collaborate with data catalogs that aren't bound to a pipeline, in additon to functionality that can support a "catalog repository/registry" with metadata around catalog ownership, maintainers, versions, etc.

Yeah the whole governance / enterprise data catalog / data contract SLA space is an interesting one