Add Role-based paths for New Contributor Course

[jberkus]

Describe the issue

While the New Contributor Course(NCC) is an excellent self-paced document for contributors wishing to participate in Kubernetes for the first time, it makes the assumption that all lessons are equally applicable to all types of new contributors. Examples of ones where that might not be the case include:

• People who plan to only contribute to Docs
• Experienced Go programmers who contribute to other projects but are just new to Kubernetes

As such, it would be great to add a page to the NCC that gives some role-based advice on which lessons are critical for which profiles. The first part of this would be figuring out what distinct roles exist.

This should be done in coordination with @kaslin online new contributor sessions, where we'll get a lot of feedback from contributors themselves.

Thanks to Sandeep Kanabar for this idea.

/sig contributor-experience
/area mentoring
/help-wanted

[k8s-ci-robot]

@jberkus: The label(s) area/mentoring cannot be applied, because the repository doesn't have them.

In response to this:

Describe the issue

While the New Contributor Course(NCC) is an excellent self-paced document for contributors wishing to participate in Kubernetes for the first time, it makes the assumption that all lessons are equally applicable to all types of new contributors. Examples of ones where that might not be the case include:

• People who plan to only contribute to Docs
• Experienced Go programmers who contribute to other projects but are just new to Kubernetes

As such, it would be great to add a page to the NCC that gives some role-based advice on which lessons are critical for which profiles. The first part of this would be figuring out what distinct roles exist.

This should be done in coordination with @kaslin online new contributor sessions, where we'll get a lot of feedback from contributors themselves.

/sig contributor-experience
/area mentoring
/help-wanted

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-sigs/prow repository.

[jberkus]

/help

[k8s-ci-robot]

@jberkus:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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-sigs/prow repository.

[aakankshabhende]

@jberkus I'm interested in working on this. Could you please assign me this?

[jberkus]

/assign @aakankshabhende

Assigned! This week is not great, but we should meet up so I can answer any of your questions about the task.

[aakankshabhende]

Sure, Thanks @jberkus

[aakankshabhende]

@jberkus whenever you're free, please let me know so we can schedule a meeting to discuss this issue

[jberkus]

sorry, stuff happened. I'll schedule something for next week. Can you find me on Slack so we can coordinate?