search

kedro-org / kedro-devrel

Kedro developer relations team use this for content creation ideation and execution
Apache License 2.0
0 stars 3 forks source link

Strategy for Kedro developers and contributors #11

Open astrojuanlu opened 1 year ago

astrojuanlu commented 1 year ago

https://github.com/kedro-org/kedro/issues/2274 made me remember that not only we have Kedro users, but we also have potential contributors/developers (including both people who want to contribute to the core projects as well as people extending Kedro with plugins). We should have a distinct and explicit comms/docs strategy for contributors, and also think about in what circumstances a Kedro user could become a contributor or the other way around.

stichbury commented 1 year ago

This is a great point. Something @tynandebold and I were discussing yesterday was that Kedro Viz could potentially receive more contribution if people knew the layout engine could be used as a standlone tool for visualising a DAG. I think we need to brainstorm the main features of Kedro/Kedro Viz that we'd be most keen to work on as part of the strategy.

astrojuanlu commented 1 year ago

Also, I believe we should prominently acknowledge community contributions (hence not coming from QuantumBlack or other entities employing core developers) in our release notes and communications.