Kubernetes New Contributor Series, 18 Jun 2019

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Kubecon EU 2019: New Contributors Workshop - Welcome and Introduction

Description

We hold a Contributor Workshop at Kubecon to introduce people who are interested in learning how to contribute to Kubernetes. You can check out the Contributor's Guide as a complement to these videos: https://github.com/kubernetes/community/tree/master/contributors/guide

A

All right, good morning, everyone.

A

I wanna welcome you to the new contributor workshops: here. welcome to the kubernetes contributor summit..

A

Thank you so much for registering and being here, early. This monday morning.

A

We know it's kind of a long walk to get here from registration, so thank you,, making that trek. my name is jonas srossland.. I've been the lead for the contributor summit planning.

A

For the past couple of months., I've had a wonderful team of volunteers.

A

From all kinds of different companies and organizations helping out, building and making sure that everything.

A

Works well here during the summit.

A

so,, I wanna extend a big, big, thank you to all the volunteers that are helping out,, both previously and today..

A

First of all,, we have two workshops.

A

We do have two workshops: we've got the 101 and the 201 workshops.

A

and tim, over here, will be leading the 101,.

A

And guinevere will be leading the 201.

A

So we have a lot of people registered for today.

A

So we have over 300 people registered for contributor summit, 330, roughly, in total,.

A

Counting everyone that joined in yesterday.

A

who joined the celebration yesterday?

A

hands up. lots of new people, awesome.. Did you have fun? [audience member]? Yes, there's pretty fun. cool, awesome, glad to hear it..

A

We're super, super excited to do this today and we hope you'll have a great time as well.

A

We do have some workshop assistants.

A

tutors,. Can you please stand up so people know who to ask if they have any issues?.

A

You can see we have four people here.

A

Excellent. we've got jeff, rael, silvia, and rose making sure that everything works really well in this room, and then we have other volunteers in the other room.

A

and,, let's see,, it's locked.

A

B

It's my figure print (mumbles), good.

A

There we go. (laughs) excellent. so, yeah,. I just wanna. Welcome you all on board this journey..

A

This gonna be super fun. We really hope you have a great time today.

A

And I'm gonna leave it off to guin and tim.

A

Thank you, all. (audience, applause),.

B

Thank you, jonas.

B

All right,, I am so excited to be here, and I'm super excited to see all of you here.

B

Today's workshop is going to be, hopefully, really,, really hands-on,, and my general policy is, if you have a question,.

B

Raise your hand,, I may not get to it. Immediately,.

B

But I will definitely try to be aware of that, as well.

B

I have given this workshop a few times,.

B

Three or four, depending on how you count it, and we're trying to make it better. Every time.

B

So,, it could be that I forgot something that I said at a previous workshop, because I thought I told you already.

B

So, in any case,, if something doesn't make sense,, please raise your hands, just to get that out of the way.

B

My name is guinevere saenger..

B

I have been a kubernetes contributor since late 2017.

B

And I hope that your journey into becoming a contributor is going to be as exciting and fun as mine, was.

B

So, I have to give credit to this picture:.

B

This is from a children's guide to kubernetes.

B

Who's familiar with the book?

B

yes, excellent!, so captain kube, says,, "hi and welcome.".

B

Again,, I would like to thank all of the workshop teachers and facilitators.

B

Also,, I would encourage everyone at this point.

B

To get out their computers., you should have been given this presentation,, the slideshow, as a link in an email.

B

If you cannot find it,, please ask one of the wonderful facilitators to help you.

B

raise your hand.. We will be clicking on links and we will be using this.

B

I don't love sitting in a room.

B

Where someone is talking at me, I like to have a conversation., so this is for you to participate.

B

Today, we're going to start with a general introduction to the community and our standards, how to find your place in the contributor community,.

B

Where you want to contribute,, what do you bring,? What do you want to learn,.

B

How we communicate,- and we are going to give you.

B

An introduction to where things are.

B

And who to talk to in what situation.

B

Without further I do,, let's get started., who can contribute to kubernetes?.

B

The short answer: is,, everyone can contribute to kubernetes.

B

Everyone can contribute to kubernetes.

B

Kubernetes is a huge project.

B

It is not just a ginormous, mono repo.

B

That lives on github,. It is a community of people all over the world.

B

People need other people.

B

You can contribute as a code contributor,, you can contribute as a non-code contributor,.

B

You can contribute in different areas of code.

B

Trust me,. Everyone can contribute to kubernetes.

B

So,, why should you contribute to kubernetes?.

B

If you are here,, there is really only two reasons.

B

Why you should contribute to kubernetes:.

B

The first reason is because you want to.

B

you're interested,, it's a cool project,.

B

It's all the hype, these days, everyone is looking for. Kubernetes people.

B

The other one is, you have to,.

B

Because your boss sent you here and said, "hey, what about this contribution? Thing?.

B

"What about this kubernetes thing? "can, you somehow get involved?".

B

Or,, you know, a mix of both.

B

I want you to think about this.. I want you to think about why you are here and what you want to accomplish with you in relation to kubernetes, to the kubernetes project..

B

I want you to start thinking about,. What do you do in your jobs??

B

Do you manage people?? Do you manage resources?? Do you write code?? What kind of code?

B

all of that can be your contribution to the project.

B

We can probably use your knowledge.

B

when I say we, I mean the kubernetes community,, but that now includes all of you.

B

You may also want to be here because you want to learn. when I started contributing,, I started with contributor documentation.

B

Because I was just trying to find my footing.

B

Being a programmer at the time.

B

so,, as my contributions changed through the months.

B

And now years,, which is very odd to think about,.

B

They got more technical. and that's fine.. So if you are here because you want to learn about an area that is also a place.

B

Where you can contribute to stretch,, where you can learn.

B

This one is kind of related to why you are here.

B

Some of you here might just be here out of personal interest.

B

or because you are hoping to find.

B

A place where you can turn your interest in kubernetes into a job.

B

Open-Source participation often gets described as a second job.

B

Sometimes I hear stories about employers that say, "well,, if you are contributing "to open-source,, what is that doing for our company?".

B

Well, again,, there are many ways in which.

B

Your contributions can matter to your company.

B

Say you work for a cloud provider. well, that one's an obvious one.

B

say your company is trying to promote.

B

A certain product or a certain service.

B

Participating in an open source can lead to all sorts of.

B

Good advertising., according to my company, it's a great place to find new employees, because you can see everyone's.

B

Contributions out in the open.

B

We do in fact, have a document which I should have brought to this presentation.

B

That will help you justify your open source participation.

B

To your boss and your company., and I also shouldn't have said justified, because,.

B

In my opinion,, open source is the way of the future.

B

And companies should be very eager to participate.

B

Nonetheless, we have some resources to help make your companies aware of this fact.

B

I already mentioned my own origin: story, go ahead and click on the link.. I'm gonna do that right, now.

B

I'm gonna make it a little bigger..

B

This is a live demo, by the way.. So if you can't see...

B

This is my very first issue that I filed in the kubernetes community..

B

I am showing you this because at the time, I was very frustrated,.

B

My coworker had told me.

B

I should open a pull request in the kubernetes community.

B

And I had a really hard time at the time.

B

And so I got mad, and so I filed an issue that says,.

B

Hey,, your documentation,, it's kind of a mess.

B

And I'm sharing this because if you scroll down and read the comments,, people are remarkably patient with me.

B

I'm still really impressed how friendly.

B

And non confrontational people were.

B

In explaining to me that hey,, you know what.

B

This is open, source, welcome to open source,.

B

You wanna help fix it.

B

and I'm sharing this because I know that there are some open source communities that don't do this,.

B

That don't assume the best of you, that aren't willing to give you the benefit of the doubt.

B

And I'm here to say that at least as far as my experience is concerned,, the kubernetes community is not like that..

B

If you reach out for help..

B

The worst thing that will happen is that no one will see your comment and you'll have to yell a little louder, but once someone hears you,, you will get help.

B

Let's go back to the presentation., how do I even.

B

Here we go., so I already kind of talked about figuring out where to contribute., and I have good news and I have bad news..

B

Let's do the bad news. First. the project is huge.. It is really, really confusing trying to figure out where to get started,. Who has had this experience?.

B

Yeah,, I'm really happy that not everyone's raising.

B

Their hands(clapping)., this is exciting.

B

(clear, the throat)., the good news is,. There are many areas to get started.

B

And in a way, it's a little bit like a choose: your own adventure.. You look at your own skills,. You look at the situation and you try to figure out.

B

Where those two fit., some of you may be here, because they work with kubernetes.

B

As an end user, every day.

B

who's in that situation?.

B

Some of you may be here because they are academically interested.

B

Yeah.- and some of you may have completely different reasons.

B

some of you may not even want to be here.. I hope that's, not the case. (laughs), but in general, the first place to look, and where should I get started, is to look at yourself..

B

What do you do for your job?? What do you do for your hobby?? Where are your interests and your skills?.

B

So that brings me to the first interactive exercise.

B

Go ahead and talk to those around you., some of you are sitting at tables,, some of you in the bag, we're gonna, take about.

B

Kind of five minutes to get to know those. Next to you.

B

And kind of maybe get some ideas from each other on where you want to contribute.. I know I'm sorry, social exercise,, go.

B

(Audience members chattering).

B

All right., I'm so excited to hear a lot of talking in the room.

B

And I really hope that you all will continue.

B

Your conversations over lunch and during the breaks.

B

Yeah, I'm really impressed by the way,. I just learned that if you look.

B

Under your tables,, there is a power cord.

B

You will still need an adapter if you're not from the eu, but you can feed your laptops if you need to.

B

So,, the next part involves talking.

B

And you already did really, really well in the last few minutes. So I'm sure this will not be a problem for you.

B

And this is how we communicate in the kubernetes community.

B

And I really like capybaras.

B

If you pay attention to one of those pictures,.

B

There is a capybaras and next to a....

B

Is it a crocodile or an alligator?? I never know which is which, but I do know that one of those.

B

Eats the other. (audience members, laughs) and capybaras is still super chill.

B

So why is everyone.

B

So nice, in the kubernetes community,, this is not an accident..

B

We have a code of conduct and I would like everyone to go ahead and follow that link to the code of conduct.

B

Which is a redirect, yay.

B

Oh look, and we have lots of languages.

B

I'm going to stick with the english one for now.

B

So we're going to take another couple minutes for folks to go ahead and read through the code of conduct., I'm going to,.

B

Hopefully, have it large enough up here., I'm gonna scroll down and about 30 seconds or so.

B

But you can also read it on your machines.

B

So,, who here has never really seen a code of conduct before?.

B

I'm just checking for an open source community? I mean, specifically., all right. nope, there we go. okay,, really good..

B

We take our code of conduct, really, really seriously.

B

And we try to live not by the words but by the spirit of it..

B

So far,, I believe we have been for the most part.

B

Really successful.

B

And it is really the.

B

Document that we base our community on.

B

Of course,, it always boils down to,.

B

Whoops, haha to treat each other with respect,.

B

Expect to be treated with respect., but you will not believe how many people we sometimes get in the issues that don't know that they can expect respect of this community..

B

They a lot of times we get people who've been hurt by other experiences in previous lives,.

B

In previous circumstances- and they are really,- really defensive and kind of don't trust it..

B

This is why I think it is so important that everyone really, really be aware of this.

B

Technical questions in kubernetes.

B

Hi,, I can't see who's waving at me in the back.

B

Who here has opened an issue.

B

To kubernetes kubernetes asking a question on.

B

Hey,, this doesn't work?.

B

Usually, what we do is we ask those people.

B

To ask those questions elsewhere, because kubernetes at one point has been the biggest.

B

Open source repository on github and it becomes really, really hard to wade through all the issues..

B

We have good ways to ask technical questions.

B

Our slack, stack overflow.

B

And now we have discussed kubernetes as well.

B

So everyone who has their computer out, let's go ahead and follow the link to register to slack.

B

That's all it takes.

B

give them your email.

B

And,, I'm going to show you some of the slack channels..

B

Let's make this bigger as well.

B

good channels to start our kubernetes dev,.

B

Kubernetes users., there is also sig countribex,.

B

Which is short for contributor experience.

B

We will talk about that later,, actually in just a few minutes., but for now,. Let's go ahead and say.

B

Hi in kubernetes developers.

B

All right, yes.

B

Yay,, I see people following.

B

So this particular channel is where you ask kubernetes.

B

And user questions.

B

Kubernetes users is also a good channel to ask question.

B

Actually, kubernetes users is for end users., my bad, I take it back. Kubernetes developers is for questions that you have when you're hacking on kubernetes or related repositories.

B

Hurray, keep saying hello., we are going to move on.

B

To the next topic of communication.,.

B

Anyone need a couple of minutes,, raise your hand, everyone good? super., let's head over, to discuss kubernetes.

B

We have this forum because some people may not have access to slack and also, if you are trying.

B

To have kubernetes discussions in other languages just than english,, there are a few foreign language channels on slack,.

B

But on an undiscussed kubernetes, we actually have regional discussions and other languages, as you can see,.

B

Let me make this bigger as well..

B

So, let's see, where did I start contributors.

B

I started a topic for y'all.

B

So here's some information how to get started. Contributing.

B

And here is the topic., so let's go ahead.

B

I haven't spent a lot of time. This is how you respond.

B

Great to see everyone.

B

So I think signing up for discuss takes a hot second longer. Is anyone having trouble?.

B

You're awfully quiet.

C

B

This is a different medium of communication.

B

It is not slack., this is a discuss forum,. This discussion, forum.

B

So if you follow the link from the slide,.

B

You should be getting to a sign up, link.

C

C

B

B

B

I see some comments.

D

B

There are a couple of task lists, sometimes that you might have to.

B

Interesting. wow, all right.

B

Is anyone else having trouble?.

E

[Audience member], okay, the system I have broken it.

B

C

B

B

I see a bunch more comments., so am hopefully we can figure out some technical, individual technical, difficulties.

B

hey,. What's up? [audience member] one of the cool things about this course.

C

Is this nice thing call the auto model., I'm putting all the approved post right, now.

B

(Audience laughs) okay,, I'm learning something.. What do I have to do? [audience member]? So I don't think you can do it.

C

On (mumbles) discussed considers as suspicious behavior.

C

Until you sign up (mumbles) the post.

B

Interesting. [audience member]: that's why I'm here. awesome. (audience laughs)., very cool., let's see.

C

[Audience member] one thing I would add the more that you interact in disgust, the more you generate, the auto moderation, trust level.

C

And then (mumbles) not do anything.

C

if you're signed up in like five minutes, (mumbles).

C

I will be fine, is just the (mumbles).

B

Did everyone hear that?.

B

Very cool. so,. This is apparently a feature of the auto moderation.. So I learned something today.

B

I joined discuss months ago and never had an issue.

B

But,, this is cool. yay, anyway, welcome everyone., and this is, I guess, our first example of community debugging.

B

Technical difficulties- and we will have many more.

B

Such instances together,, I hope.

B

Well hope, hopefully not too many.. Hopefully some things will just work right. Away.

B

So, other things that we do in the community for planning and discussion.

B

We use mailing lists..

B

This is the next activity for you to sign up.

B

Mailing lists run on google groups.

B

And if I go to my groups, nope, yes.

B

I have the kubernetes developer contributor, discussion.

B

And that is the mailing list for kubernetes contributors.

B

Let me go back to my slide. Deck.

B

If you just follow the link from the slide,, you can sign up for the kubernetes mailing list.

B

This is where a lot of top level discussions happen.

B

You can set your mailing list, preferences,.

B

You can post.

B

But for the most part, this is kind of our newspaper.

B

In a way,, this is where you read, hey,, what's happening in the community.

B

On github,, we absolutely discuss things on github,.

B

We discuss in issues,, we discuss, features.

B

And discussions also happen on pull requests.

B

So basically, every time you communicate on github., you want to give everyone as much context for why you're here, what you're doing,, what you're asking,, what you're proposing as possible.

B

We will talk a little bit more in detail about.

B

What that means.

B

B

This is where all of our meetings happen, because we are an open source distributed community.

B

We have distributed meetings via zoom.

B

We have a calendar,.

B

And the schedules on the community calendar.

B

Different groups in the projects have meetings at different times and depending on where you want.

B

To contribute, your meeting schedule will look different.

B

The kubernetes weekly community meeting.

B

Is documented here and you can see the calendar.

B

And the way that you get invites.

B

Actually,, I don't know how that works for the community meeting anymore,, but this link should get you started with finding out.

B

Where the meetings are. and after that,, it should be as simple as clicking.

B

On a zoom link.

B

So right, here,.

B

Where is the kubernetes weekly community meeting,.

B

B

zoom video link to participate. again,, this is very, very tiny.

B

Right here,, I have this.. This is still set on pacific time., I'm not sure why.

B

But basically, here are your links., so the community meeting is open to everybody and lots and lots of people attend every week.

B

And when you're, just starting in the project, it might not be the most useful thing for you to attend until you have a little bit more context., that's just coming from me. But if you do, or if somebody is giving a presentation there, that you're interested in,, it's absolutely worth it.

B

To go and listen, in.

B

any questions so far?.

B

All right., we will help you get set up with your meeting schedule.

B

As the day goes, on, I'm sorry,. I said that wrong.

B

Don't worry., I mean, you don't have to go to any meetings.

B

If you don't want to..

B

What I'm trying to say is those meetings that you would be interested in,. We will help you find.

B

Other communications., this is the community repo.

B

This is a good place to start.

B

If you want wow,, why is my face on their.

B

(clears, the throat).

B

code of conduct, videos,, discussions, events.

B

This is just a one, stop shop.

B

and we also have monthly live video discussion.

B

Called meet our contributors., it's basically a it's. A panel discussion.

B

Where people write in questions and they get answered in a live stream., we also post those videos.. We have kubernetes office hours for technical questions., whoops.

B

We have kubecon, welcome to kubecon.

B

And we also have face to face sig meetings at these kubecon.

B

That's where a lot of our current contributors are right. Now. meetups are another thing..

B

They are kubernetes meetups all over the world..

B

I see a question.

C

[Audience member], I was told (mumbles) discussed, which slide had the link to the schedule?.

B

Which slide had the link to the schedule.?

B

Let me go back.

B

B

Right here, kubernetes weekly community meeting.

B

It is really not obvious and there's a reason for that, unfortunately,, because we've had quite a few malicious spammers on our video calls fairly recently.

B

And so we've had to make some of the meetings invite only.

B

And I will show you how to get to those as well.

B

So I apologize for it being three clicks: down.

B

Let me actually click through that, for you, one more time,.

B

Just so you can follow.

B

So from here, we have the weekly community meeting.

B

That is for the entirety of the community.

B

Of the kubernetes community. here is the calendar.

B

And the community meeting is at 10 a.m: pacific on thursdays,.

B

I have absolutely no idea what that means.

B

For this time period, for this time, zone.

B

[Audience member] is not good., not good,. Let's see, actually,. I can do this.

B

It's 7 p.m,, it's dinnertime., (laughs).

B

We do make efforts with other groups and meetings to be less north america centric. As well. when I was on the release team last year,.

B

We had a european meeting hour.

B

Just so that the poor europeans didn't have to.

B

Stay up until midnight just to attend the meeting.

B

And same I'm sure, with asia, pacific contributors,.

B

I heard you make a noise. (loughs).

B

We try,, we often fail at that, please.

B

Raise your hand,, say, something., say hey,. I would like to have a daytime meeting.

B

One of these days.

B

very cool., so back to meetups,, there are kubernetes meetups.

B

All over the world.

B

go to meetup kubernetes,, see what's up, find.

B

I think I put a link in here that you can follow.

B

So these slides are meant to be a reference for you for later. As well..

B

I have a group link slide for this reason.

B

Okay,, so we have a little bit of time.

B

To change the topic slightly., who here has heard of a sig in the kubernetes community?.

B

Awesome,, who here hasn't heard of a sig in the kubernetes community?, that's more interesting., yes, okay, no, raise your hands really high,, especially if you're the only few.

B

Because I need to know that sig stands for.

B

Special interest. Group.-.

B

There we go, sorry about that. I didn't mean to make anyone dizzy.. I just wanted to know. I wanted to make this.

B

Where's, my presentation?, why do I have tabs? oh, well.

B

So because the project is so big, we organize it and we do not necessarily organize it by code,. We organize it by humans.

B

The topic of interest that connects contributors.

B

Is what is called a sig in general.

B

So,, I put a link for the sig list in there,.

B

But let me just kind of go over what kind of special interest groups there are.

B

Each special interest group is its own kind of sub community.

B

B

there are five types of sigs.

B

The first type is feature areas.

B

Plumbing, meta,, you can read the slide,.

B

Let me just talk about feature area. Sigs.

B

These sigs have to do with certain parts of the kubernetes code base. so for example,. Sig-Cli is concerned with command line tooling for kubernetes.

B

This literally means yeah,. This is the sig that hacks on cube, control., cube control., sig-network deals with the networking within.

B

Kubernetes clusters and all the related things.

B

Sig-Scalability,, how big can we make a cluster.

B

And not break things?, you get the idea.. Some of you may actually have much more of an idea.

B

Of what this particular topic is than ideal.

B

Because of your specific areas of knowledge,.

B

That I don't share. so go over this list and see perhaps.

B

Where your abilities might match a topic.

B

Then there's plumbing sigs.

B

That's kind of the nickname.: these are the special interest groups that deal with.

B

How kubernetes is put together.

B

How do we provision?, how do we make it so that we can provision clusters?.

B

How do we want clusters to work?

B

less feature more operational.

B

And then there's the project organization, sigs.

B

Sig-Architecture is about decisions on which direction.

B

The project heads. a lot of sig-architecture involves project management.

B

As well, what kind of features should.

B

We add to the future of the project.

B

sig-contributor-experience, that is my sig.

B

This is the sig that is organizing your contributor summit.

B

So that all of you are having, as best of a time becoming.

B

And being contributors as possible.

B

Sig-Pm is project management, related,.

B

Sig-Release is in charge of our release cycle.

B

And the processes that are related. sig-testing writes our testing infrastructure,, which all of you are going to see later in the workshop.

B

We have an entire sig-dedicated to documentation.

B

If anyone in here is really, really excited about.

B

Documentation, come talk to me, find that zack liaison.

B

They are very much eager and willing.

B

To help people get started, contributing to docs.

B

There's also sig-cloud provider.

B

We used to have..., we still kind of do have individual sigs per cloud provider.

B

But they are. because there's really more for like,. This is a cloud provider general interest,.

B

We have divided them into sub projects.

B

So you can see alibaba,.

B

Gcp, openstack, vsphere.

B

Those are all different cloud providers.

B

Which might be really, really specific to only those people.

B

So, again,, it depends on who you are and why you are here.

B

That brings me to sub projects and working groups.. This can be really, really confusing.

B

Basically, a sub project is something that belongs to a sig,.

B

But is only part of what that sig does.

B

So there might be in sig, contributor, experience,.

B

We might have the sub project.

B

Actually,, I don't I. [audience member] contributor summit. contributor summit, for example,.

B

We might, I don't think we actually do.

B

That would be something that could be a sub project,.

B

A working group is something that happens when you need to coordinate between sigs.

B

I'm still not great with this excellent.

B

Here's a list of working groups.

B

B

we have things that might touch multiple sig areas.

B

Resource management, security, machine learning,.

B

But they don't have the same kind of.

B

Focused attention that a sig does.

B

There's also some differences in management.

B

Here are some examples of sub projects.

B

My favorite example is always customized, customized as a sub project of sig-cli.

B

Sub projects usually have a really, really tight, definition.

B

We are only working on this one thing and we are doing it as part of a sig.

B

Customize was added to as a sub command to cute cuddle,.

B

I think in 115, kubernetes is 115., and but it is still its own sub project as the feature skip built. Out.

B

And then there's user groups. Currently we only have one user group, it's basically an organizational thing that is for.

B

Just if users want to share a topic of interest,.

B

There's not really a code base ownership,, but it is a way for people to get together and share knowledge. currently,. We only have big data. As a user group.-.

B

All of this can be found.

B

On the sig list, let's see where is it. here we are,.

B

In the kubernetes community, repository.

B

It's really just community/sig-listmd.

B

here are sigs and working groups..

B

What you will find here are the sig chairs,, the meeting times,, the mailing list,, which is really, really important. I'll, bring that up in a minute.

B

Back to the presentation,, we also have committees..

B

This is really for governance.. There's a steering committee project security and the code of conduct committees..

B

I chucked a link in there just so you know.

B

now,. I talked a lot about how to pick your area of interest.

B

So these are kind of the steps figure out.

B

What you want to work, on. and hopefully, by being here, you can find out.

B

Which sig is the one that covers this interest.

B

And then all you have to do is join the sig.

B

How do you join a sig?, [audience member]? You join the mailing list.. You join the mailing list. excellent answer. yay.. Well, done., that's it. people often confuse membership in the kubernetes organization with sig membership,.

B

They are two completely different things..

B

All you do in order to join a sig is get on the mailing list.

B

And then you're, a member of that sig., I'm a member of sig-architecture.

B

I think I've attended half a meeting of sig-architecture,, although I'm starting to get involved with a sub project.

B

But yeah, I'm a member of sig-architecture..

B

This is how you get on the mailing list, go to the sig-list,.

B

And I have that in the link from the slides as well go to the sig-list and sign up.

B

That's it. you're done.

B

everybody go home, just kidding (laughs).

B

So this is how you get calendar invites and then it'll be a lot easier than you don't have to click.

B

Three links down because everyone realizes,.

B

Oh,, you joined the mailing list, you're interested in being a member of this sig.

B

Oh,, I have another user group slide in here.

B

B

B

Basically, committees are the only part of the community.

B

That is really, really restricted by invite or by election.

B

Because we need to have people have certain skills.

B

Or we need to just,.

B

Follow our guidelines to how we select members of these committees.

B

And the steering committee gets at least part in part, elected so,.

B

And there's other rules as well.

B

Here's your quick reference, if you're more interested,, go ahead and check it. Out.

B

So now the next part of this community, we have a tiny little bit of time until it's 11..

B

So this is going to be a super fast tour.

B

The kubernetes project is not just one repository.

B

It is an entire ecosystem of repositories.

B

We have the core repository.

B

Most special interest groups are involved.

B

With the core repository., if you follow this link,, you can kind of find areas of sig ownership..

B

We use this file for a lot of different things, including automation,, and test automation.

B

How to find a review or project organization.

B

However, there are many, many other repositories.

B

That are related to kubernetes.

B

And not all of them work exactly the same. Way.

B

My recommendation is, if you know, of a workflow.

B

For a specific kubernetes sub repository,.

B

Go ahead and start with that, if you start with a new repository,, someone will be along and tell you oh, by the way,.

B

This is actually not how we do things here,, but that's okay..

B

As long as you try., let's actually go back here.

B

And go to the core repository and let's go to the org.

B

So,, you can kind of see with the pin repositories,.

B

The ones that are most important,, we have the core repository kubernetes.

B

It is huge., some of you are going to get a deeper look at.

B

What that looks like and where things are later, today.

B

Then we have the enhancement repository,.

B

We have an entire repository for if you have feature requests and a plan to implement those features,.

B

If you follow there will be a top level read me.

B

This is where you should start. If you have a great idea that you want to have a feature in the next edition of kubernetes.

B

We have the community repository..

B

This is where a lot of our community.

B

Governance, documentation, is,.

B

This is also where you can find if you follow contributors.

B

There is the contributor guide.

B

Which, where you can learn about the contributor workflow.?

B

This is the reference.

B

There is the developer guide,, which contains.

B

All the technical details on where to get started.

B

And we are in the process of organizing it.

B

and help is appreciated.

B

B

There is the website we have a repository that creates the website for kubernetes.

B

This is where the api documentation lives,.

B

This is what you see when you go to the official kubernetes documentation.

B

But this is where that is made.

B

If that is your jam,, this is where you're going to spend a lot of time.

B

One caveat the kubernetes website, repository has,.

B

It has the most different contributor,.

B

Has the most different workflow from all the other kubernetes repos. there's test infra. This repo mostly belongs to sig testing.

B

This is where tools like power and.

B

What's the other one tied live.

B

Here's power. here's the test, grid.

B

They also have a code of conduct.

B

Here's where you can find information about.

B

How to look at your test results.? What kind of tests are how the tests run,, how the ci jobs run.

B

I want to mention at this point that sig testing is one of my favorite sigs.. Everyone in it is super, super nice.

B

And super, super picky, in that order.

B

In other words, they are really, really happy.

B

To teach you everything they know.

B

I already mentioned this?

B

and I believe this is the final slide.

B

It is until we break out into 101.

B

And 201 sessions.

B

so, before I ask if there's any last questions,.

B

Everyone who is in the 101 session will stay, here, and tim will take over, and everyone who's in the 201 session is going.

B

To go across the hallway, with me.

B

It is exactly 11. however,. I do want everyone to take a 10 minute break..

B

So let's take 10 and meet right here and I have a question?.

B

[audience member]. What's the difference between the 101 and the 201?, okay, really, really awesome, question., so basically,. The 101 is for folks.

B

Who have never contributed to open source before.

B

Or who may not be familiar with.

B

Our particular development setup, we are going to do a development. Setup.

B

jonas is raising his hand. Maybe jonas is okay.

B

no, okay, fine..

B

This is where we are going,. 101 is where we will set up a developer environment.

B

With docker, glenn and kubernetes.

B

201 assumes that you have that,.

B

And that you have previously contributed to open source communities. so that we can really just tweak it and tell you how we do it in the kubernetes community.

B

E

[Audience member] hi. (mumbles).

E

But I don't know about how to contribute.

E

B

I think you should try 201. [audience member], okay. yeah.

A

(Mumbles) [audience member], we do have a special guest.

B

(Mumbles) oh, special guest.

D

[Joe], I just wanna, say hi to everybody..

D

Do you mind if I steal the mic? One. hi, joe.

B

You can steal the mic anytime, (laughs). [joe] no. (laughs).

D

Is not how it work.

D

So, first of all,, thank you for an awesome, intro.

D

And cute elephants. adorable., so I'm joe., I'm one of the founders of kubernetes and I just wanna welcome everybody..

D

I think it's awesome to have you here..

D

It's awesome to see folks that are interested in getting involved.. There's folks, like me and tim, come on. Up.

D

tim hawkins has been involved since the very beginning, also.

D

and. hi., so we're gonna be floating in and out and hanging out..

D

I got like a gazillion things going on and turns out that, for this conference, monday ends up being the busiest day somehow., but there's folks, like me,, there's folks like tim.

D

there's a lot of folks that are gonna be around.

D

If you have questions, if you need help, glenn,.

D

Please ask we're here to try.

D

Give you a jumpstart so that you can get involved.

D

And we're really glad that you're here. thank you. (audience applause).