Community: SIG Meet and Greet @New Contributor Workshop KubeCon2018 Seattle

[guineveresaenger]

This issue will be used as a means to track mentor volunteers - if you could drop your contact information in a comment here or via k8s Slack to me @gsaenger you will earn karma points, my eternal gratitude, and new members for your SIG.

Do you need more SIG members? Are there many outstanding Good First Issue and Help Wanted labels in your SIG’s projects? Are you running out of Reviewers in your OWNERS files? Will members of your SIG attend the Contributor Summit at KubeCon Seattle?

This is the opportunity for you and your SIG!

We need one or more of your members to volunteer 30 - 50 minutes of their time to meet interested new contributors in person. You'll find our their skills, how they can add value, and talk about a first issue they can try. If you've ever been to a Speed Networking session (KubeCon has them - plug!), it's very similar except you both have the same goal. You - to find more contributors; Them - to find a SIG to be a part of.

Requirements:

• Member of SIG*
• Available Monday Dec 10 at 3:00pm at KubeCon Contributor Summit Seattle
• Familiarize yourself with your SIG’s needs, and maybe a few good first issues
• Willingness to follow up and be available for questions by new folks.
• Add your name/contact information via comment to this github issue: https://github.com/kubernetes/community/issues/2745

*This person need NOT be a SIG Chair or Maintainer, just someone willing to be a friendly face, show folks around the repo via chat, and generally bridge the gap for new contributors from “this is where I want to contribute” to “here’s how I can contribute”. In fact, this might be an opportunity for other people in your SIG to grow.

/area community-management
/sig contributor-experience
/assign

[guineveresaenger]

/area mentorship-planning

[derekwaynecarr]

I should be available.

[dchen1107]

I plan to go too.

[zacharysarah]

I will attend.

[kmova]

I will be available for sig-storage

[roberthbailey]

I can be there.

[soltysh]

Count me in.

[dims]

Sounds like fun. count me in

[juanvallejo]

Will attend as well

[childsb]

will attend for sig-storage

[seans3]

I will be available (SIG CLI)--thanks.

[detiber]

I will attend for sig-cluster-lifecycle :) I'll reach out over slack for contact info.

[aanm]

I will be there as well (SIG network)

[Huang-Wei]

I will attend for sig-scheduling.

[shyamjvs]

I can be there for sig-scalability.

[bsalamat]

I will attend for SIG Scheduling as well.

[dstrebel]

I can be there for Sig-Azure

[quinton-hoole]

I can be there for sig-multicluster. @pmorie, @marun, @irfanurrehman @shashi

[spzala]

I will be there for sig-ibmcloud /cc @duglin Thanks @guineveresaenger

[quinton-hoole]

cc @shashidharatd

[mrbobbytables]

Just a reminder for those that are volunteering. If you did not get a confirmation email regarding Contributor Summit Registration last Friday (10/26/2018). Please register by filling out the Contributor Summit Registration Form. It says it is currently waitlisted, but go ahead and select the current-contributor track option and we'll switch it to be approved behind the scenes.

[tpepper]

I'm happy to contribute for SIG-Release.

[mcrute]

I'm happy to attend for sig-aws

[mrbobbytables]

@derekwaynecarr @dchen1107 @zacharysarah @kmova @childsb @quinton-hoole-2 - When you get a moment, please complete the Contributor Summit RSVP. It will say waitlisted, but we will take care of that behind the scenes.

Thanks!

[quinton-hoole]

Done. FYI the CLA link in the RSVP seems to be broken:

https://github.com/kubernetes/kubernetes/blob/master/community/CLA.md

[mrbobbytables]

@quinton-hoole-2 Thanks! Link has been fixed.

[kmova]

Thanks @mrbobbytables. Done.

[k82cn]

I'll be there for SIG Scheduling as well.

[DirectXMan12]

I'll be there for SIG Autoscaling

[guineveresaenger]

You are all amazing and wonderful people. ❤️ ❤️ ❤️
I will update this thread and send emails as well as the event comes closer.

For now, the plan is:

We will put signs with SIG names on tthe tables in the room. This way, you and the new folks will be able to find each other easily, and you can start talking, answering questions, showing off your repo(s), maybe setting folks up with their first issue if they're ready for that.

It's not very formal - the format will be up to you and what questions you get. I will come up with some prompts to help get things going.

Also - suggestions and questions welcome! I am so excited!

[gyuho]

Hope it's not too late. I'll be there for SIG AWS. Please email [email protected].

[M00nF1sh]

I'll be there for sig aws. Email [email protected] 😄

[d-nishi]

I will be there too!
Email: [email protected]

[leakingtapan]

Would like to join for sig aws. Contact: [email protected]

[Rajakavitha1]

I would be happy to attend for sig-docs.

[parispittman]

to summarize attendance: aws, autoscaling, scheduling, node, release, multicluster, ibmcloud, azure, scalability, network, storage, cluster lifecycle, cli, architecture, and contribex.

[guineveresaenger]

Dear SIG meet-and-greeters,

thank you again for being available to welcome new contributors into our community.

Here's a quick update on the details:

What: Be ready to chat with newcomers about their interests, be ready to exchange email/slack handles, set up SIG meeting invites, have a few "good first issues" or starting strategies on hand.

How: We will have table signs for each SIG and I will instruct new contributors to find you! After that, it's all informal Q&A.

Where: Room 605

When: Please plan to arrive early, at 3:20 pm; the planned start time is 3:30 but we may finish up the prior session early and I want to make sure the new contributors can find you and feel welcomed.

I am super excited for this event to happen - it should help everyone.

[nikhita]

Thanks for making this happen, everyone! :heart:

Closing since this is now done.
/close

[nikhita]

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

/close

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.