Hands up here who has an open source, program, culture, any bit of help at all in their office.
Okay, I'd have expected a few more hands, but I'm, trust me, I'm not judging here, I'm not judging.
Hands up here who mentor people about open source.
Okay, I'll go a few hands. Hands up here who is just starting their journey in open source.
Who's a mentee in trying to get going. If you put your hands up twice, you're a lawyer.
No, you're not a lawyer, because this is one key aspect in life.
Everyone needs a help-up.
Everyone of us that has started an open source, it's been hard. The very first time,
I went to an open source conference, there was open stack in the Atlanta in 2014,
and I had no idea what it was about. I even bought a new pair of shoes,
and I don't wear shoes and they cut my ankles after two days,
and I had to go into forced aid and get a bandage from a very nice guy who gave me a bandage,
but I wasn't sure what to do or where to do it.
And I was only starting to open my open source journey. But over time,
I've realized that everyone needs a help-up, and when you say you're a mentor,
you're also a mentee. You're helping, which are also learning.
And over the next 20 minutes or whatever we get through is,
what I want to do is look at the fact here of what we're doing in our companies.
We're open source. Because when you use open source, you need to give back into it.
You need to be able to help your employees and so forth.
And that's something I'm going to discuss as I go along.
Okay.
Okay, so Leslie, it's juice me there. The key part of it is,
I've been an open source for over the last 10 years or so.
And I came into it by accident.
But the minute I started making some contributions,
and I went to that conference in Atlanta, I said, I want to do this.
I don't know what it was. I've been maybe 20 years at that time,
a program in, I've done different languages, different technologies.
I've spent, you know, on my life doing some sort of program in one way or the other.
And I just saw that time in Atlanta. I just saw the collaboration between people
from different companies. It just blew me away.
You know, hands up here who tinks.
It's better to be head down, programming yourself.
Are, are working in the team.
So for some of our hands up, if you think on your own, do it yourself.
So it was one. Hands up, who tinks. You know what I mean?
It's the collaboration or it's the bigger team that gets things done.
Yeah, it's not a trick question, really.
A lot of you probably, hands up here who knows Phil.
Phil is just a great person, that's in the industry.
If you ever get a chance and you see him go up and talk to him, he's very, very helpful.
He can make it this year and he's probably getting the gigal to think that we're,
that I'm presenting to this again, but there we go.
All right, let's kick into it. So Phil's journey has been
down here largely. You think around the container space back when he was a doctor captain,
but it starts even back before them because Phil used work in IBM,
but I don't know Phil from IBM.
Strangely enough, we worked in the same company, but when it's a big big company,
I got to know him open source. I got to know him true, open stack.
And he was doing talks on open stack.
And he's journey went back from those early days of the Linux Foundation
when IBM had to set up the foundation.
Up to getting involved in with Docker, becoming a Docker captain,
and then when it was opened up with your CI,
your container initiative and then into container D.
And he's just, he's one of those people.
Someone said it to me today when I was talking to him in the containers.
He's just one of those people that goes about his,
without any years of grace, or significant type of entitlement.
And yeah, I've just, we've built a nice friendship over the last few years,
and he's true open source, really.
In open source conferences and trips and so forth.
Myself, it started back as I said, we'd open stack.
And then over the years, anyone up, hands up here who
is that elastic and one stage had an open source community.
If you, yeah.
Now, it was open source, but when it closed foundation,
it was a challenge and I have to say,
I was able to make contributions, but it was harder than it normally would be,
if you have more open foundation.
But that's nothing against elastic.
That's just the way they had the community at the time.
And then for the last few years, I've been in the Kubernetes ecosystem,
with Helman and different parts of Kubernetes,
and then in open telemetry.
And now I've been looking more on the AI space.
So as you can see, I didn't update the slides any further,
but that's where it goes sometimes.
So why should companies have an open source culture?
I think the key point we get here from this is,
if there's anything that came out of log for Jay,
the issue a number of years ago was.
Open source is absolutely everywhere.
It's in our phones.
It's in our fridges.
If you have the fancy damn fridges, I'm always good.
It's in your, if you put in a lovely camera system
that you can access on your phone here now,
while you're sitting here and it's at home,
or you've decided you want to turn the heat enough,
because your kids, you know what I mean?
You've run outside rather than sitting inside in a nice warm home.
Whatever it is, it's got open source in it somewhere.
And that's a fantastic thing.
And I'll touch it in a while is because
companies have realized over time,
you cannot create everything on your own.
And this idea that true communities,
true different open source projects,
you can build and make your products from there.
And there's realization for a lot of customers today.
They want interoperability.
So what do I mean by that?
Well, if you're using a monitoring or an observability tool,
a platform to look at what's running,
what's the usage, where there's errors and so forth.
A lot of vendors want to say, right,
okay, we're using that now from maybe in Stana,
our data dog, maybe we want to go to another platform.
Can we plug and play?
And this is one of the reasons why the open telemetry
has been such a success around telemetry data
and monitoring is because it's not the forced standard.
There's been multiple standards in that area,
but none of them stock until open telemetry,
because the vendors bought into it.
And they said, right, let's extract the way.
Customers are fed up with saying,
I'm using this platform today.
No, you're going to have to weigh and change on your client code again,
because we've a different protocol for our data.
And this idea here that you could standardize the data
and then it's the back end then that you're buying,
bought him with a lot of customers, so they can swap and play.
The same thing around, it's one of the big reasons why,
you know, my own company IBM has gone involved,
so heavily with open shift is the idea here that you can go
from vendor to vendor.
So customers want to say, right,
I want that in-house.
I want parts of it in the public cloud.
I want to be on Google today.
No, next week, we want to go to AWS,
customer to hire, or we want to go somewhere else.
So that idea here that you can plug and pay
or you can move around is so important.
So Phil put this in because he's big into statistics.
I'm not so much into stats.
For one reason why, do you know 90% of statistics are not correct,
okay?
Well, I'm still going to talk to this guy,
but he talked to the lesson.
And this comes from Red Hat,
but don't to Leslie and I are colleagues.
And I suppose the key to get out of here is,
you know, on that force-lying dash,
what I said earlier about vendors.
They want to,
that instruments are more likely to choose vendors today
that are using all the source.
And it's because of that ability to,
you know, the community,
and also the ability to be able to plug and play with open source,
has made it so favorable.
But as a few things here on this that's important.
Now, I would say those percentage numbers are probably
a rise and you're probably going,
I'm 49% isn't that high.
But when you think of the amount of companies are out there
and the different industries and everything,
and that's available from banking and so forth,
they're quite high percentages when we look at it.
And the key here I think is that,
they realize that the realization that
by keeping open source communities healthy,
you, your products are going to be healthy
because you're building on top of that.
The other part is that if you want to get new functionality in
or both to get fixed, okay,
you can go and do it.
You're on a task somewhere else to do it for you.
You can make the difference, okay?
And you'd be able to make that difference,
if you are contributing,
or you are being a mentor to that community.
And more and more technical challenges have been solved
by this worldwide effect in the different communities.
Hands up again, the folks who are,
and I'm serious on this,
the folks who are who have stacked in open or open source
are thinking about getting involved in open source.
Okay.
So these few slides hopefully will give you a bit of an idea of why
to get involved in this.
And the force will really distance out to me
and I think the most important here is
the way to grow your career.
And you probably work in a really, really good company.
Well, wanting I learned, I love to travel in my 20s
and I love backpacking around the world.
And the greatest things I've learned in life is
from different people and different cultures
and different countries and different languages.
When you embrace that,
you, your world is your right to,
you learn from that.
I wanted it to lovely signs I ever saw
was in this lovely beach hot
down in the TMN islands.
It's just off of the course of Malaysia,
just above Singapore.
And at the time, this was at the early 90s or the notties.
It was an island that,
most people in Telangawi didn't go here.
And it was a lovely kind of a
not-tourist that touristy of an island.
And the lady ran a lovely beach hot
and there was a sign on it that said,
if you don't respect my culture,
and my ways, why did you leave home in the first place?
You will get some of the greatest opportunities
to grow your career and learn from other people
that have different ways and different ideas,
then you probably will within your own company.
You will learn when on your own company,
but you've got to broaden your mind situation.
And I always have that phrase that,
someone always knows more karate than you do.
And if you take that on board and you realize,
you know, there are people that know more stuff than you,
there's nothing wrong with that.
You will learn so much from that.
And I think that's what gives you great opportunities.
And the final one is that,
when I started out all that years ago,
to do interviews and so forth, to get jobs,
I'm talking back 40 years ago.
You made up a CV, and you printed out the CV,
and you sent the CVs into post.
You know, and then kind of your attachment to emails.
But it was a static document of what you're doing.
No, you might update it in the water.
We don't open source today.
You just have to give them a series of your ads.
You know, you can show the contributions you made.
Okay, man.
Now, I've gone totally off-piece on this.
So yeah, we'd know notes on this either.
So maybe we knew what we were doing back in.
But all your contributions are out there.
If you get a chance to do talks and trust me,
there's no kind of, you know, hierarchy.
I've been there 10 years or I've been in community.
I do a talk there.
Opportunities will come off.
And those opportunities are fantastic to grow your career.
And grow your mindset.
Okay, let me know, man.
Sorry, though.
So how can you cultivate this culture?
And I think one of the forcing really is education across your company.
So hands up here, anyone where the company is still trying to know,
you know, the value of open source.
That's it.
No one.
So everyone in the company is totally off-payable to open source,
and everyone's granted it.
No, that's, that's not true because there's always companies
that are still trying to learn.
Okay.
But the key is education.
Why can bring into your company,
how we can grow your people and so forth is so important.
Okay.
Also, the tools and practices.
I remember I was working on open source for while,
and I was talking to colleague one day.
At his back, maybe eight years ago,
and he was trying to get a project out the door,
and they were talking about,
oh, we're trying to get released out.
No, people are after pushing if stuff over on night,
or after breaking the bill, all they started to take.
Now, if you were an open source,
that would never really happen.
Because someone can't just push stuff in.
We literally unless it's a maintainer that's left,
you know, the alcohol or the coffee go to their head.
Well, generally there's gates.
It has to be reviewed.
There's one or two people going to review it.
Bloody blah, did it past the gates or one and so on.
So I mentioned that to the colleague at the time,
and his response was,
yeah, yeah, that's okay.
You're doing your phone stuff open source.
This is the real world.
And I had to laugh at the person at the time
because he was an education team.
And over time that person has realized,
you know, the power of reviews,
and bring it in the whole idea of inner source.
And I think at the time I said, what's this inner source?
But I can see the value of it,
where we bring all the good things we do in open source.
We bring them into our company,
so that people can learn from it.
You know, and it may be as simple as
at this stage, everyone should be moved over the gate home.
But, you know, using GitHub, having a good CICD,
having a good review process,
you know, taking it easy when you're reviewing someone
and giving good feedback,
that's, you know, going to head to person,
not destroy them.
All those good things we take for granted
to open source communities.
And I believe they happen because
we've put the rules in place,
and people are willing to implement it.
If you decide you want to be a jackass,
someone's going to call you open.
Like, don't be under any illusion.
You know, the whole reason my open source gets on
so well is, we're all such great people.
We're great people because we know
first of all you should know how to behave.
But if you're not really that short of how to behave,
you will learn that you should behave.
When you see that somebody will not be tolerated
for a behavior that's on becoming.
And that's a great thing because we know
while it becomes responsible for our own behavior.
And you'll hear this from Leslie and everyone else
that's presented to this room.
Please take your rubbish with you.
You know, please don't bang this.
Please don't go in late.
I'm looking at you two guys at the back there.
I don't know, okay?
I'm only joking.
Which, you know, these little things are important
and that's what's right with it.
And that's why bringing it in
to the culture and company is important
and how to do it.
An education I go back to again is the big part of it.
And also I suppose finally is the thing that
if you make contributions to open source,
there are as important as making to the product, okay?
So yes, maybe the product makes to her cash.
Both the open source that someone's contributing
is indirectly involved in that product making the cash
because it's built on top of it.
And showing people that if you're looking at it,
and showing people that if I find a problem,
and this was taught to me in a very first time of work.
If you find a problem, go down through the whole out of the stack
and fix it the whole ways down in the whole ways back up.
Make it right.
Don't just say, you know, there's a spelling mistake in there
in the document or that doesn't work right.
Raise it and say, can I do that and go with it?
But know that your company will at the end of the year
and that person's been contributing that out here.
That is a broad value to our company.
So where are we known myself and feel?
I'm not going to talk for a feel because his words
can speak for him there.
For myself, it's on being known to myself,
going towards being an SME in the company
or on the open source over a period of time.
It's been a gradual progress process.
Well, one of the key aspects to me has been involved in
helping other people in the companies.
So being part of a jumpstart that was started a number of years ago,
where we guess educate people on open source,
but open source says,
one of the key roles is getting somebody to make that
force contribution out to the community.
Hands up here who remembers their first,
the first time a PR got merged out in the community.
Be honest with me now.
Look at this.
Show your hands out there.
You know, very show your group here.
Hands up who remembers.
You check in, you check in the PR.
Has a gun in yet?
That is unreal.
Isn't it?
And then the word where they go,
oh no, we don't think this one,
you have to go again.
That is hard.
Which helping people to do that process and show them that,
it is not that easy.
When you've been working a certain way,
tend to go out to your software and work that way.
It's like being a trap to these artists
and they take away the national underneath.
It's a bit like that.
Where you go,
I think I can do this.
But obviously if I get a wrong,
you know,
I'd be awesome because.
So I think being able to help people to do that
is probably one of the things that brings me to most joy
and being involved in that program of job status.
So I probably missed most of the points that I was supposed to say.
I don't.
I felt like it would well cover.
Is it?
Yeah, I get a feeling that I great stories I was going to tell.
But anyway,
has any of the stories been any good so far?
Mark,
I'm not sure if listen to you read the phone book,
not any one of the numbers.
Okay.
There's no pity we should have got subtitles for this.
Sorry for my English.
I think the force one speaks for itself.
And you know.
It's like everything.
I think it's like volunteering.
Hands up here who volunteers.
Any aspect that I want.
So I caught a group of young fellow soccer.
Okay.
And I tell you over the last few years
if a few things have been going on personally.
And don't get me around these boys.
And I don't want to be sometimes.
But they're young teenagers.
But I've gone down there a few times
and my head's been wrecked
and they've just lifted my afternoon.
You know what I mean?
They're fun.
Watch you put in, you get back.
It's the same with open source.
If your company is building a product
and they use an open source and they're stack.
You want to be given back.
Love for Jay is the warning that was out there.
Okay?
One poor person cannot be blamed
for an issue that was inside and something.
Where were the other people?
The collaboration and creativity you're going to get for more source is on real.
If you stack note in your journey.
I give an example.
I only need to canteen today.
I got a coffee.
And I sat down on the canteen.
And the next thing I saw two guys.
I know.
David Flanagan and Andrew Martin.
Okay?
To this day, I don't know how I got to know.
I really don't.
Because I don't work in the security area.
Which Andrew's space is in.
And David, I don't know.
I don't work in the area.
He works in, which is around training in different areas like that.
But somehow I've got to know them independently.
They know each other and we sat down with each other.
And we talked about everything.
We talked about where open source is going.
You know, you know, people who make right contributions and who don't.
We talked about things like where people come in and just make functional changes.
I want to become a maintainer.
We will never do the dirty work of PR reviews and.
And, and triage triage in books.
That's, I call it dirty workers.
It's hard work getting down into the gutter clean and the drain.
But it's the most important part of it.
Because if the drain doesn't flow, it's back and back up into your host books.
Okay, remember that.
And the last one then is what it will bring you around for, you know, as a person.
What you learn from it, like I said.
And then the aspect of here there is that you're going to grow so much in this.
You grow so much in your career being in community.
As I say, meeting people, I've made a lazy troll.
You know, lazy and I started working this year.
And I didn't realize, well, you didn't make this conference last year.
Yeah, you're not able to.
But like she could be here and, you know, I've made sure.
So the way you can grow as a person and grow your career is so important.
So that's all from me, as well.
Okay, we've no time for questions, I presume.
No, we do not have time for questions.
We have time for a blast.
Yeah.