community

community copied to clipboard

Describe the issue

I tried to automate much of this and never got to it, ran into several roadblocks, or insert reasons here. (one example here: #3479)

This program is geared towards contributor ladder growth and not new contributors, but could be structured for new members depending on the goals of the group (ie expedited reviewers).

Time expectations: at least 5 hours a month when not in a group cohort, 10 when you have a cohort

Need someone to help me with the following:

• Create the community group side onboarding experience for group mentoring
• Manage full life cycle cohorts
• create a role description for this role
• carry out the processes laid out in the program docs https://github.com/kubernetes/community/blob/master/mentoring/programs/group-mentoring.md

Ideally would like someone who has been contributing already as ironically I don't have too much time to mentor on organizational basics right now.

/sig contributor-experience /area mentorship-planning

/help

@parispittman: 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/test-infra repository.

Hi! I'm interested in this role-please let me know if I can be of any help!

@apalekar12 and folks reading this - can you meet this weds the 23rd at 9am PT? thanks!

@apalekar12 and folks reading this - can you meet this weds the 23rd at 9am PT? thanks!

Sure can!

I'm interested as well

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

/remove-lifecycle stale

I'm interested as well 😃

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

/remove-lifecycle stale

Hi, @parispittman I would love to help you. Do let me know if you have any tasks for me

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale