Skip to content
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

Parent task: Build a backlog of Spaceflights extension examples #2800

Open
stichbury opened this issue Jul 17, 2023 · 3 comments
Open

Parent task: Build a backlog of Spaceflights extension examples #2800

stichbury opened this issue Jul 17, 2023 · 3 comments
Labels
Component: Documentation 📄 Issue/PR for markdown and API documentation Type: Parent Issue

Comments

@stichbury
Copy link
Contributor

User research recommends that we extend Spaceflights to add examples for more advanced functionality that a user may want to apply. We need a list of what those would be, to create individual tickets for this milestone.

@stichbury
Copy link
Contributor Author

stichbury commented Sep 29, 2023

I asked on the Slack channel about the extensions we could add.

@astrojuanlu
Copy link
Member

Another is the refactoring of a non-Kedro project -> Kedro including single node approach. There's a #2855 but we don't have a generic, but not Notebook, project -> Kedro, wondering if we need this too?? Edit: Probably covered by #410

I think it's worth having docs that cover (1) how to refactor a notebook to Kedro and (2) how to refactor a project not using notebooks to Kedro. Do we need new tickets or do we repurpose existing ones?

@stichbury
Copy link
Contributor Author

stichbury commented Sep 29, 2023

Let's repurpose as we seem to have a lot of these outstanding:

  1. How to refactor a notebook to Kedro
  2. How to refactor a project not using notebooks to Kedro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Documentation 📄 Issue/PR for markdown and API documentation Type: Parent Issue
Projects
Status: To Do
Development

No branches or pull requests

2 participants