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.

Sign up for GitHub

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

Jump to bottom

Create the Data Scientist learning path #51

Open
quaid opened this issue Jul 17, 2021 · 15 comments
Open

Create the Data Scientist learning path #51

quaid opened this issue Jul 17, 2021 · 15 comments
Assignees
@MichaelClifford @oindrillac @margarethaley
Labels
area/user Indicates an issue/PR is related to a project platform user. kind/experience Indicates an issue/PR is related to human interaction and experience. kind/website Indicates an issue/PR is related to project web presence. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@quaid
Copy link
Member

quaid commented Jul 17, 2021

This involves creating a curriculum for Data Scientists from the existing materials; identifying any gaps where there is no material for a corresponding step in the path to know what material to create; and creating a curriculum page or area for this content on the website, as per the layout for the learning path part of the website.
@quaid quaid added area/user Indicates an issue/PR is related to a project platform user. kind/experience Indicates an issue/PR is related to human interaction and experience. labels Jul 17, 2021
@quaid
Copy link
Member Author

quaid commented Jul 18, 2021

@durandom Who knows this material—what exists, what might be needed, etc. toward creating this web page.

@oindrillac
Copy link
Member

@quaid this is something I'm willing to support with and fill in the gaps for.

@MichaelClifford
Copy link
Member

@quaid there is a fair amount of existing content we've created around data science projects. Is there a more specific scope/definition for the "data science curriculum" we are looking to provide here? That could help to guide us on identifying the existing content and potential gaps.

and thanks for volunteering @oindrillac 😃

@quaid
Copy link
Member Author

quaid commented Jul 19, 2021

Different from SRE where people are learning principles from scratch, the Data Scientist path here I think is all about:

  • Quickstart for every data science tool we host (written, video tutorial)
  • Useful ways to blend tools
  • Anything related to, if they have code that can be run in production, how can they gain benefits from Operate First open community cloud.
    • E.g. what workloads can they start up, what colleagues can they attract

Consider what a Data Scientist working at a corporation might want to play around and learn from/with, show them how to open the toolbox/toybox, and go get productively lost.

So unlike SRE principles & practices, we aren't teaching data science, we're giving access to the latest and greatest open source data science tools for people to do things. Curriculum I think can focus on just that.

And maybe that means we can pull this page together most easily, so it is useful and demonstratea the learning path idea.

@quaid quaid assigned oindrillac and margarethaley and unassigned durandom Jul 19, 2021
@quaid
Copy link
Member Author

quaid commented Jul 19, 2021

/label kind/website

@sesheta
Copy link
Member

sesheta commented Jul 19, 2021

@quaid: The label(s) /label kind/website cannot be applied. These labels are supported: community/discussion, community/group-programming, community/maintenance, community/question, deployment_name/ocp4-stage, deployment_name/ocp4-test, deployment_name/zero-prod, hacktoberfest, hacktoberfest-accepted, kind/cleanup, kind/demo, kind/deprecation, kind/documentation, kind/question, sig/advisor, sig/build, sig/cyborgs, sig/devops, sig/documentation, sig/indicators, sig/investigator, sig/knowledge-graph, sig/slo, sig/solvers, thoth/group-programming, thoth/human-intervention-required, thoth/potential-observation, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, triage/accepted, triage/duplicate, triage/needs-information, triage/not-reproducible, triage/unresolved

In response to this:

/label kind/website

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@quaid
Copy link
Member Author

quaid commented Jul 19, 2021

This issue is related to https://github.com/operate-first/operate-first.github.io/issues/265

@quaid quaid added the kind/website Indicates an issue/PR is related to project web presence. label Jul 20, 2021
@MichaelClifford MichaelClifford self-assigned this Sep 3, 2021
@sesheta
Copy link
Member

sesheta commented Dec 2, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2021
@quaid
Copy link
Member Author

quaid commented Dec 7, 2021

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 7, 2021
@sesheta
Copy link
Member

sesheta commented Mar 7, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2022
@MichaelClifford
Copy link
Member

@quaid should this get it's stale tag removed?

@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2022
@sesheta
Copy link
Member

sesheta commented Jun 9, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2022
@sesheta
Copy link
Member

sesheta commented Sep 24, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2022
@sesheta
Copy link
Member

sesheta commented Jan 5, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2023
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 26, 2023
@sesheta
Copy link
Member

sesheta commented Apr 27, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MichaelClifford MichaelClifford

@oindrillac oindrillac

@margarethaley margarethaley

Labels
area/user Indicates an issue/PR is related to a project platform user. kind/experience Indicates an issue/PR is related to human interaction and experience. kind/website Indicates an issue/PR is related to project web presence. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@quaid @durandom @MichaelClifford @oindrillac @sesheta @margarethaley