-
Notifications
You must be signed in to change notification settings - Fork 3
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
Create a blog post to offer messaging about the category in which to place Kedro #1
Comments
You've seen this landscape from LF? https://landscape.lfai.foundation It's really neat and it's open source (and the CSV is available for the data behind it). We are in the Workflow category within it. Are we OK with that? I do think we can build upon it to write a blog post to communicate it. I don't know that we need to put in too much extra effort to define a category for ourselves if we have this already? I'm tempted to say we should omit the first 2 of your tasks and concentrate on the latter two. |
@stichbury I have had a look, and I agree. We can build on this category through the blog post. |
Do you still want this @NeroOkwa and, if so, are you able to create it? |
I think it would be a nice companion to the research @NeroOkwa has been doing on competitors 👍🏽 |
@stichbury yes I would like to still do this. |
This is indeed an issue. However it's clear that we won't solve this with one more blog post, or adding more FAQs or callouts. Let's keep focusing on kedro-org/kedro#3012 |
What is this?
It is common to see misconceptions around which category Kedro should fall into across blog posts, data science articles, and industry rankings.
These misconceptions include Kedro being seen as an orchestrator, or platform like SageMaker, or in a general category like ML or AI. Such as in here, and here
The goal is to define the right category for Kedro (e.g. development framework), and position Kedro there, starting with a blog post.
Why do we care about this?
This wrong perception determines if and how users implement Kedro for their projects.
Secondly, during client projects, if they think Kedro is a platform, they would be reluctant to use it because of the fear of ‘vendor lock-in’, or if they are already locked-in with another vendor.
Effectively communicating our unique positioning and category, would drive adoption of Kedro.
What needs to happen?
The text was updated successfully, but these errors were encountered: