GitHub Universe 2018 - Scaling your business, 9 Nov 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: The keys to open source success for enterprise teams - GitHub Universe 2018

Description

A panel discussion with Per Ploug, Open Source Community Manager (Zalando SE), Chad Arimura, Vice President of Serverless (Oracle), and Shilla Saebi, Open Source Community Lead (Comcast), hosted by Bonnie Chatterjee, Director, Professional Services (GitHub).

Hear real-life examples from Comcast, Oracle, and Zalando about how their teams have navigated red tape, encouraged innovation, and taken products to the next level on their journey to open source adoption.

About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.

For more information on GitHub Universe, check the website:
https://githubuniverse.com

A

♪ (music) ♪.

A

Good morning, everyone.

A

and thank you for coming to listen to us.

A

As we talk a little bit about open source, and how it's being introduced into the enterprise.

A

So, as you know,, open source is becoming more and more popular,.

A

More and more relevant and important,, even in large enterprises.

A

and today I have with me some distinguished panelists.

A

Who have brought innersource into their own companies,.

A

And they're here to tell you real life stories of how they did it.

A

So my name is bonnie, and I'm the head of professional services.

A

Here at github. and with me today,, I have chad arimura,.

A

Who's, the vp of serverless at oracle.

A

chad,. Would you like to say a few things about yourself and what open source means to you.

B

Sure. thanks, bonnie. so,, my name's chad arimura., I'm currently vp of serverless at oracle corporation..

B

I joined oracle about a year and a half ago, by way of a start-up acquisition..

B

My former company, I was the ceo and co-founder of a company called iron.io, where we were pretty early in the serverless. Base-- started that back in 2011.

B

my open source journey started early on in my career,.

B

Almost 20 years ago, with the lamp stack., if you think about the lamp stack,, you got linux, apache,, mysql,, perl, php.,.

B

At the time for me, it was perl. and if you just think about that acronym,, it's all open, source.

B

And open source has been a big part of my journey. All along.

B

But I didn't actually start contributing a lot until 2013.

B

When solomon hykes launched docker at the gosf meetup a few days after pycon.

B

And when my co-founder and I both looked at it,, we saw it as a replacement for lxc, and we both had this "ah-ha" moment where there was this amazing technology. Emergence coming with containers.

B

And so, within 18 months after that,, we released an open source project.

B

Called ironfunctions. ironfunctions is now forked, called the fn project at oracle,.

B

And it's open source, serverless computing., so we're the creators and stewards of that.

B

and we'd eventually like to see it inside of a foundation like cncf., so open source is really important to everything that we work. On.

B

(Bonnie) thank you, chad.

A

I'll move onto you, shilla.: this is shilla saebi. she's. The os community lead at comcast.

A

Would you like to tell us a little bit about yourself and how you started in open source?.

C

Sure. I currently work as an open source program manager.

C

With a focus on community in the open source program's office at comcast.,.

C

I've been with the company for a long time-- about eight years.

C

And my journey started as a microsoft exchange operations, engineer.

C

And it would be interesting to find out how did I even get into open source.

C

So there was an opening, as we were, building our private cloud team.

C

and I applied, and it was openstack.

C

And so my journey with open source started as an openstack operations. Engineer.

C

And I was lucky to get to go to a conference in hong kong,.

C

About three months into my job, into my role--, this was about five years ago-- and when we went to the conference,, our vp came back and said,.

C

"I'd love to see you and the rest of the team contributing back to the software.", and so I sat down one weekend and taught myself git,.

C

And I started doing upstream contributions to openstack.

C

I fell in love with the open source community,.

C

I fell in love with the fact that I was working worldwide, globally with folks, and that's how my journey started.

A

(Bonnie) excellent.. Thank you for sharing., we'll move onto you, per ploug..

A

He is the community manager for open source at zalando.

A

Yep., so I'm part of the open source team at zalando.

D

We are a small consulting team that works across the organization.

D

So we work both with engineering teams and also with legal and compliance.

D

So, we try to create a cross organization, alignment on what open source actually is.

D

And how we work with it.

D

so,, I got involved in open source 12, 13 years ago.

D

Just out of school, there was no jobs, so me and a friend of mine,.

D

We made this digital agency and we started building websites.

D

And through that, we got exposed to this open source,.

D

I think it's open source project called umbraco,, which is a cms--.

D

A content management system. and we adopted that, started using it.

D

But very quickly, I became much more engaged in actually contributing to the content management system than actually contributing to any of our client's projects.

D

So I soon realized that agency life was really not for me,.

D

Based on that., so one thing lead to another, and I joined that company or that project,.

D

And the backing company as a partner and first employee.

D

And now I've spent 10 years in that project, trying to figure out. How do you have an open source project?

D

And how do you have a business? That's actually sustainable.

D

so,. We ran the business just completely bootstrapped,, not taking any money. and then figuring out,. How do we find a model.

D

That works with,. You have a business that needs to make money,.

D

You have a project that needs to thrive,. You have a community that has certain needs, and you also have paying customers.. So how do you combine those four factors into something that works for you.

A

(Bonnie) very interesting., thanks for sharing.. So as we have this conversation, today, we're going to talk a little bit about.

A

The tangible pieces of how you bring open source into your organization.

A

So to do so,, let's start a little bit about driving adoption, first.

A

It's important to build a community for open source to be successful.

A

Inside the enterprise., so I'll start with you, per., and maybe you can tell us a little bit more about.

A

What are some of the challenges that zalando faced, as you were, trying to drive adoption and interest in open source?.

A

(Per) yep., so zalando is enterprise size.

D

But it doesn't have the enterprise mindset., it still feels like a start-up, and it started 10 years ago. and our very first store where we sold shoes, was based on magento., and today we use very different technology..

D

We use kubernetes and postgres to scale our business.

D

So we've always had a natural choice for open source.

D

It is the natural part of our stack,, so we've never actually had to convince anyone that open source is a good idea., so we're very fortunate for that.. But what we have had to do is create alignment,.

D

And also figure out: where do we prioritize our resources in regards to our engagement to open source.?

D

And we do this in different ways. so,? First of all,, when we onboard new developers in the organization,, we expose them to the idea of open source.. We expose them to the challenges in regards to copyright and licensing.

D

We expose them to how do you even work with open source,?

D

How is the collaborative way of pull requests and giving feedback.

D

So that both applies to innersource and open source.

D

And the last thing we also do is we're very focused on creating processes,, documentation, and tools. That's transparent and open.

D

To everyone to see., how do we actually release a project.? How do we decide that it's a good idea to open source something.

D

so for us,? It's not so much about adoption,, it's more about adopting the mindset of where does open source create the most value to us, because if we just release all the code.

D

As open source,, we would not have time to maintain it, anyway, so.

A

(Bonnie) very good point. maintenance is important.

A

and we'll come back to a little bit more around the maintenance and governance in a bit..

A

But let's come to you, chad..

A

What are some ways that you've seen that are successful.

A

In not only driving adoption, but increasing awareness?.

B

So, oracle is an interesting company.. It is one of the foundational companies in software..

B

It's been around for,, I think, almost 50 years.

B

and it's a really big company.. I mean, we're talking 150,000 employees,, 50,000, engineers,, 60,000 engineers,.

B

That could be off by some amount, but it's really large.

B

And so it's not a "build it and they will come" mentality.

B

Of open source., so what we found at oracle is that there is this very interesting passion for open source,.

B

But it's harder to expose that,, and so we found an opportunity.

B

To announce the open source of fn project at javaone last year.

B

In fact, we had sponsorship all the way up to the top..

B

There was probably 5,000 people in the audience, 50,000 people through the live stream., and we added a little bit of theatrics to it,, where on stage,, I pressed the danger zone,.

B

"You're in the danger zone," and I pressed the github, "make- it open source." and it had a really big impact.

B

and from that moment on, almost weekly,. I have engineers.

B

From inside of oracle, reaching out to me and saying, "how, can we get involved??

B

How can we participate in the project?" and that's something that,? It really helped put us on the map by doing something like that. and it was an opportunity to help spread. Awareness.

B

so, grassroots is great, but it takes a little bit of momentum.

B

Or theatrics to get things kicked off.

B

(bonnie). I like your point about theatrics.

A

At github,, when we do a project, as of course,, all of you know,.

A

The way we do it, is merging it., and so one of the things we do, is when we have a big project, that's going live,. Sometimes some of us will gather over zoom and we press the green button,.

A

And with some ceremony to say, "okay,, this is now merged, and this project's now live." it's very fun to do and it gets excitement.

B

Well,, the funny part of that is when I did it on stage,, we had it all planned,, but then I got a 2fa warning,.

B

My two-factor, but luckily, my phone was in my pocket.

B

And I had 1password,, and so it went pretty quickly.

B

But I was, like, sweating.

A

Live demos. yeah. dangers of live demos. alright,. So let's talk a little bit about processes. Now.

A

Now that we've gotten awareness and adoption going, it's important to build some processes that enhance and nurture open source.

A

In your organizations., so let me come to you, shilla, first, and tell me a little bit more, or tell us-- our audience. Here--.

A

How does the employee at comcast,, how do they contribute and how does that work?

A

sure., so currently, our developers, engineers,, what they do.

C

Is they submit a ticket to us, and my colleague,? She handles most of the contribution requests that come in.

C

We call them open source contribution, requests.

C

these come in and we have a queue: that's monitored by our team.

C

And also we have an open source advisory. Council.-.

C

This consists of folks from the networking team,.

C

From the security team,, we have well-respected engineers.

C

Across the company,, as well as legal, and representation from our team as well., and we try to have this board,, it helps us to reduce friction between legal side,.

C

As well as our engineers. and so our team,, what my colleague does is she meets,? She has prep calls,.

C

If it's an open source contribution, that's large,! If it's a large feature.

C

But if it's something that's a bug, fix, or if it's a documentation,.

C

Or if it's a repeat contribution to a certain project,.

C

We do have blanket approvals that get approved online, so they're not as tedious.

C

We also have, recently,, we're really excited about,.

C

We had an employee satisfaction award that our team won,.

C

Because people are generally happy,, I think developers like to be able to contribute to open source seamlessly,.

C

And we're trying to do that. and it's a work in progress, we're continuing to try to automate this process as much as we can.. But we've seen big improvements in the past year.

A

(Bonnie) yeah,, and we see that with all the customers we get a chance to speak with, having just a right amount of process is difficult,, but very important..

A

We can process something to death and then it's not exciting or interesting anymore..

A

But if there's no structure and no process at all,, then it becomes really difficult to grow,, also., so per,. I know that you have a very interesting life cycle for open source projects at zalando.

A

Yep,, at least we try to think about the life cycle in a way.

D

So a bit of context,, we have 2,000 developers, and we have roughly 220 open source projects..

D

So it's a large amount of things to actually manage.

D

Our philosophy is that we want to take ownership for the things we release.

D

code without ownership and without maintainers have very little value to anyone., it's very hard to adopt any sort of open source code that doesn't have ownership or maintainers..

D

It's a large risk, rather than an opportunity.

D

So we divided this into three phases, basically., so we have an incubation phase where we have very clearly defined requirements, for how can you even open source, something.

D

that's, of course, compliance-related rules., but that's also just having the conversation about? Does this actually bring value to zalando to open source,.

D

Does this even make sense to us,? Is this something we can see a value in taking ownership of long-term?? The second is,? Does this bring value to anyone outside of zalando?.

A

We might release something that's very specific to our infrastructure.

D

And it doesn't make sense for anyone else to be exposed to that.

D

And then finally,, we also need to ensure that we have maintainers that wish to actually be part of this project long term and take ownership of it..

D

So that's the incubation, phase, and that typically runs over a six-month period,.

D

Where the maintainers have the responsibility to grow and mature this project., we then review this,. We have an internal review group that consists of current maintainers and the open source team.

D

And then we decide,, if this can now be promoted into a stable, project,.

D

Maybe it needs to be in incubation a bit longer, or maybe we decide to actually pull it back into our github enterprise.

D

Because this was clearly something that didn't work, out.

D

And then you have the last phase,, which is the most difficult one,, which is retirement or decline of the project. Itself.

B

So what do you decide to do with projects that don't have any maintainers,.

D

Or haven't been maintained for years, and you still get pull requests for this,? How do you handle this?.

D

So,, depending on what kind of legal and copyright options.

D

You have as a company,, you have to decide if you want to find new internal maintainers of this..

D

If you want to just announce it as abandoned, or maybe you can find the previous maintainers, or previous employees that might want to fork this project and continue working on it.. So this is where we have to think about just beyond releasing things,.

D

But actually think about what will happen with this in two or three years, because things change so quickly that this might not be a thing, that's relevant in a couple years, and what do you do with it? Then.

A

(Bonnie) interesting., when you were talking about the incubation, part,.

A

There's a question in my mind,: how does a project even get incubated??

A

Is it a grassroots effort where the developers band together.

A

And say, "I need to solve this problem, and therefore,. I'm going to build this solution to it,".

A

Or how does it work?.

D

So typically, it's projects, that's already been built inside zalando that solves one of our internal projects or problems,, and we then want to share that code with the world.

D

Typically,, we have a form where people simply just tell us.

D

That they want to open source this.. This form is designed in a way that people think about.

D

The responsibilities that they have., so they have to list themself and other people who are interested in maintaining it and stuff like that.

D

so,, that's the initial step.

D

and then after that, we have discussions with the maintainers and the review group about. Is this a good idea or not.?

D

So it all starts with a conversation, really.. We don't try to be bad cops and say no to everything..

D

That's not the point of it,, but it is that we need to see that there's actually a motivation to do. This.

A

(Bonnie) and motivations, of course, very important to keep a project going and then the maintenance bit, that becomes very important as well..

A

So let's talk a little bit about the processes for maintaining.

A

And contributing to these projects.

A

This is a github event and you've heard some of the things.

A

We're doing at our keynotes yesterday and today, what are some of the ways-- I'd like to know if you'd had any experience--? What are some of the ways that github contributes to the workflow that you have in your workplaces.

A

For open source., so let me start with you, chad. and if you don't mind, sharing with us how this works at oracle.

B

Yeah, so specifically for the fn project,, we have a pretty standard, github workflow for pr requests.

B

The community will contribute some pr.

B

From a core member of the team,, and then that can get promoted and ready for merging with a master branch.

B

however,, we have a pretty arcane cla process.

B

Which is a contributor license agreement process.

B

older company,, older processes,, which we are trying to reform.

B

But you still need to take a sheet of paper, and until recently, you literally had to fax it somewhere..

B

You have to take a picture and email. It in,.

B

Somebody manually puts it on the site and you get listed with 3,000 other contributors., so we built a scraper that would scrape that site,.

B

Read for your github, a username, and then clear the cla check from red to green.

B

And we did that with a background process, and we're actually talking about potentially moving that to a github action..

B

So a little plug for your new--.

A

(Bonnie) for our new work,, as of yesterday,, our new announcements.

A

well, thank you.. I hope you find a lot of value in github actions.

A

It's meant to make the developer's life easier,.

A

Which is essentially our goal. yeah,, but I need pre-approval to use it,, I'm still on the beta list, so.

B

(Laughs), you heard it here: first.

A

We might be able to help you with that. (chuckles) alright,, so let me go to you, per.. How does this work at zalando?.

D

So, specifically for the open source projects that we use internally,, we expose them on the public github, and that's also where our teams work.

D

So we work in the open, we're transparent about what we do and the changes that comes in from the community., but we then also mirror them inside of our organization in github, enterprise.

D

So we pull the changes in, and then we run all our internal compliance checks, all the things we need to do to ensure that this is something we can actually deploy in production..

D

So the obvious advantage for this is that we have the same experience.

D

And same set of [tooling] on each side., so our developers can do what they are used to inside of the company as outside of the company..

D

So that combination of having an internal set of repositories,.

D

Where we do that more complicated deployment, process, combined with the exposure and the transparency.

D

Of having the public open source projects out on github.com.

D

Is a very good combination for us.

D

and again, as chad, said, actions--. So when is that coming for the enterprise?.

D

(Chuckles) (bonnie) good question.

A

We are thinking about it., it's very much on our mind, and it's going to make its way to our road map as well.

A

and we'll make sure that you're the first to know.

A

When we have some defined timelines around that.

A

But we know that our enterprise customers really desire to use this as well.

A

But if you do want to use it right, now,, it is available on github.com.

A

And so,, especially for zalando,, you have an option to try. It out,.

A

Play with it a little bit,, already.

A

so,, there are a couple of other things. I wanted to talk. About.

A

Let's talk a little bit about, maybe one challenge.

A

Each of you might have faced, or the company might have faced,.

A

In introducing open source or growing open source., so we'll talk about that a little bit. and then we'll go into talking a little bit about. Maybe a success metric or two that you use to measure successes.

A

so,. Let's start with you, chad..

A

Could you tell us about maybe a challenge that, in particular,.

A

With oracle, open source,, they don't always sound like they might gel very well.

A

So tell us maybe about a challenge, and then perhaps one success, metric.

A

That you'd use.

B

I think some companies, culturally, are just structured for open source.

B

Specifically,, more modern, cloud-native companies--, I shouldn't say modern,, but born-in-the-cloud companies typically have more open source flexibility, culturally, internally.

B

With oracle,, it's such a big company that it's hard to spread the word.

B

You need channels to do that. and for us,. One of the challenges has been getting people involved,.

B

Allowing them to get integrated with the project., so you're really spreading the word on different projects, internally.

B

And so, the way that we've been able to overcome that is,, like you, said, earlier, executive sponsorship., a big of it, has been driving adoption through the javaone announcement.

B

But also, shilla mentioned earlier,. Reducing friction is a big thing., so one thing that we were able to do was become sponsors of the cncf and linux foundation.

B

And so with that, came a sort of a blanket agreement.

B

That anybody inside of oracle can contribute to linux foundation projects without growing through a lot of hoops., and that was a really, really big move for oracle to be able to do that, because otherwise,, it's pretty difficult., rather than contributing during work. Hours,, you just say, "you, know what,, I'm not going to do it." and so now,. That kind of reduces that friction to contribution..

A

(Bonnie), thank you for sharing that.. Let me go over to you, shilla., so similar questions--, maybe a challenge that you might have faced,.

A

Or the company, and then maybe a success, metric or two.

A

Sure. absolutely.

C

So I'll talk a little bit about innersource for this one.

C

We have come through in situations where it's been challenging.

C

To let folks know that it's okay to work on other teams', projects,.

C

And to figure out what the culture is around that.

C

And so we actually have an innersource pilot program that we have been running for the past year., and this is kind of how we overcame the challenge..

C

We created an org in our github enterprise and we ended up putting the project there.

C

and then we started marketing it and telling folks, "hey, it's okay to contribute to this.".

C

We did a blog post.. We posted in slack channels.

C

We had the team do a presentation at some of our internal events.

C

And we found that once we started spreading the word,.

C

We started finding more contributors coming., so I think one of the challenges was that people didn't actually know.

C

That it was okay to do that.

C

I, myself,, I remember, when I was in operations,.

C

I would log in to github enterprise,, but I didn't really go into other repos or even dare look into them because I didn't know what that team was working on., but now we're trying to incorporate a culture where that's okay,.

C

So with this pilot program., so we're picking projects as we go. Along.

C

we've done two so far and it's been really working. Great.

C

(Bonnie) I had a chance to speak with some of our customers.

A

At an event on monday, and one of the things that we heard frequently.

A

Was the importance of raising awareness, and the importance of celebrating small successes, early.

A

So the presentations by the team,, the announcements on slack,.

A

On newsletters,, it just helps that groundswell.

A

That you kind of need, that immense amount of interest.

A

And excitement from folks who may be a little bit intimidated to start something new.

A

to see that others are being successful and being celebrated for that success.

A

Is something that's on many people's minds.

A

Great., let me move over to you, per.

D

(Per) yeah., so zalando has been doing open source for quite some time. Now.. We see this as kind of in our third iteration..

D

That also means there's a lot of history in how people perceive open source inside of zalando.

D

In the beginning, kind of the first wave of open source.

D

Was very much just release everything., which is fine,. The enthusiasm is good, getting started.

D

And that slowly progressed into an idea of, we need standards.

D

We need some common ground on what can actually be open. Sourced.

D

And then we progressed further into thinking about the life cycle now., but having that process also means that we have many, many different definitions of what is actually a standard of this..

D

So creating clarity about how you do open source.

D

And why you do open source at zalando was a challenge we faced.

D

So, just aligning all that and addressing all that history,.

D

And making one clear place that this is just the thing we're doing.

D

This was all released to open source at zalando.com earlier this year,.

D

Which is an mit licensed,, pretty much all our guidelines and documentation, how to do this.? So we have one single place to actually just tell all our developers.

D

And everyone else actually, also, how we do these kinds of things, and why.

D

For metrics,, we generally divide them into three different groups.

D

We measure many different things, but generally we are very interested.

D

To see if we are capable of attracting community contributions.

D

To open source projects., so we count them and we also divide them into see. Who are the return? Contributors.

D

Are people coming back again.?

D

Are we able to attract new ones as well., and then we divide that into looking at each individual project and see how they do that.

D

secondly,? We look at. How do we actually address those contributions.

D

So we look at the lifespan of a pull request.

D

Is it actually merged?? Does it get feedback?? Do we actually respond to the contributions that we get from the community?

D

and then the third area is, do we contribute upstream.

D

So we monitor all our github member profiles,.

D

And we look at what kind of projects do they actually contribute? To.

D

So inside of zalando we have a tool called tech, radar., there's also a public version called zalando tech radar--.

D

So you can google that--, which is advisory on what kind of projects you should use in your daily work.

D

So it's strictly advisory, but we announce to developers.

D

What kind of projects we would recommend they start using., so we monitor these and see. Are our developers actually engaged in these projects,?

D

Do they have an insight in the stack that we actually depend on, and it's a good indicator for us that our developers actually dive into these projects, and understand them as well.? So that's the third thing we measure.

D

On a bit more soft metric, is that in europe,, zalando is perceived.

D

As a fashion and retail company--, we sell shoes online--.

D

So we're not really generally perceived as a tech, company.

D

But we have a very large tech department.

D

And we have a lot of technology that actually enables us to scale this very big store., so open source is one of those things that gives us value,.

D

That we can actually show the outside world, of how the engine room works in such an organization..

D

We can actually talk about how we use kubernetes and how we scale our organization,, how we handle black friday and sell many, many shoes on that single day..

D

That requires an enormous amount of technology.

D

And if we didn't have open source as a channel for that,, then we don't really know how to tell that. Story.

D

So that's important to us as well,, to be perceived as a tech company-, which we are--.

D

And also attract new hires as well.

A

(Bonnie) great. and retention and attraction of talent.

A

Is something on everyone's mind. and we know that making our workplace more attractive to the talent.

A

We're trying to hire, is important.

A

and allowing them to participate in open source,.

A

Having innersource culture, are all things that make employers.

A

That much more attractive to the folks we're trying to hire.

A

So let's talk a little bit about,, let's go into a lightning round.

A

Let me see, if I can get our slide.

A

alright.. So before we came here,, I asked these wonderful panelists.

A

A couple of questions that I thought would make for an interesting end.

A

To our conversation., so one of the things we wanted to do was help. You learn something new.

A

So we're going to talk about an interesting statistic that each of them have brought. and we're going to talk a little bit about why that's interesting, and what's the story behind them.

A

and then,, I asked each of these folks,.

A

What's the one thing they'd want you to take away from this conversation.

A

So we'll go into that as well.. So let's start with you, per.

A

What is your favorite statistic on open, source?.

D

So this is the humbug box in zalando, open source, software.

D

(Laughs) this is the--. This is a bit of a cheeky thing.

D

But this is the amount of dollars you would have to pay to get access to.

D

Sophisticated software for machine learning, or for managing containers, or any other sort of thing you would normally perceive as very expensive, specialized software..

D

The state of the art in many of these areas of software today is free and open source.. So a start-up in africa or a highschool student in sweden.

D

Can just take these components and build something that would normally be out of range.

D

so,. I think that's interesting to all of us..

D

The enterprise have had the advantage of having that exclusive access.

D

To very expensive software, and that's not the case anymore., and we need to be very much aware that that advantage is gone..

D

And we cannot ignore open source anymore.

A

(Bonnie), thank you for that., let's go to you, shilla. sure. (bonnie)! What's your favorite statistic?, so 80%-- I learnt about this yesterday.

C

During the state of the octoverse session-- 80% of the contributors that are contributing to open source software through github.

C

Are from outside of the us.

C

and I think that's truly fascinating. I mean, it's development, that's going on! That's changing the world,.

C

That's happening: internationally, worldwide, on a global level.

C

To me, that was really mind-blowing.

A

(Bonnie), I think it was a surprising statistic for us too.

A

as in, not surprising as much as eye-opening.

A

There are so many people outside of our little country, here,,.

A

Who care as much about software development and who are transforming their businesses in the same way as we see some of our customers here, do.

A

And it's really nice to see that you're, not alone.

A

wherever you are,, whenever you're coding, there's somebody else on github.

A

Somewhere else in the world, probably trying to do the same thing as you're doing, and if you're open sourced,, then you can help each other.

A

(shilla) yep.. I love it.

A

alright,. Let's move over to you, chad.

B

So I read this in the state of devops report: 2018,.

B

I think puppet labs and a couple of companies put it out.

B

And their metric was,, exceptional or top-rated developers.

B

Are 1.75x more likely to be using open source.

B

Than the average developer.- and they are also 1.5x more willing to share and expand.

B

The usage of open source, internally. so,- I don't know how they defined exceptional developers,,.

B

But I thought it was a really interesting metric, to really show that you can't ignore the proliferation of open source.

B

In the enterprise, and it's kind of inevitable at this point.

A

So if we find an exceptional developer and get them to contribute to open source,.

A

Then we should get a return. That's 1.75 times, 1.5?.

A

(Laughs), I think so.

B

A

Alright,, so those are just some of the statistics..

A

If you have a chance to look at the state of the octoverse,, it does talk a lot about. Where is github,.

A

What is happening in that world,? What are people working, on,.

A

What are people working with., and so, if you have a chance to check it, out, please do.

A

But in the meantime, here's one thought.

A

Our panelists would like to leave you with today.

A

So I will start with you: again, per.

D

So I think when many people hear the word governance,.

D

They see it as a very negative thing., or at least the whole part of getting a no to what you want to do..

D

I see governance as an enabler and actually be clear about what you want to do.

D

So to me, to enable participation in the enterprise,.

D

You need to clearly communicate what is actually allowed to do,.

D

What are the rules of play here,? What can you and can you not do,?

D

What are the goals of doing open source inside of your organization., be clear about that,, be upfront about it,, rather than hiding it away, or not? Having any opinion about it.

D

So when you start with your open source journey in the enterprise, might as well start with that. have a clear strategy,, have a clear governance model.

D

For how you want to do this., because you would rather have that you're proactive about it and just be upfront, and so it doesn't happen by accident..

D

That's a much better way of going about it.. It creates clarity for people participating.

D

and with clarity,. You also have a higher degree of participation, because people know what they can actually be. A part of.

D

(bonnie) yeah. and I think governance is one of those very important topics.

A

Where, without proper governance,, an open source strategy can't truly thrive.

A

You need those guardrails,, you need that help and the support of your leadership team.

A

And it reminds me of something that you had said: earlier, shilla,.

A

Did you want to talk a little bit about how the leadership team at comcast.

A

Supports open, source, and then we'll come back to you for your last thoughts. (shilla) sure, absolutely.

C

So we're very lucky. the head of our open source program office,.

C

She sits on the board of the linux foundation-- nithya ruff--.

C

And our chief software architect at comcast recently came up--.

C

It's just an example of how much support we do have--.

C

He presented us with the idea of an open source, fellowship pilot.

C

That we should run,, and so our team ran with it.

C

and he's been in full support of it.. We have 30 engineers across comcast that are dedicating one day a week,.

C

20% of their time towards upstream contributions.,.

C

And it's various projects,, it's not just one.

C

and so there's little subteams that are working together, and it's a one-year-long program..

C

We also have an open source conference- that's happening next month in philadelphia,, that's not just for comcast folks,, it's also for public as well., and we have outside speakers and we're super excited because it's the first iteration.

C

But we have the president of technology from comcast coming to keynote..

C

That says, a lot. for our open source awards,. We had a c-level executive, handing out the awards.

C

He came out of his busy day and helped us out there.

C

So we really appreciate it and I think it's really important to have.

A

(Bonnie) I agree. so let's talk about your last thoughts. sure. (bonnie), and what you'd like to leave this audience. With.

A

C

So one of the goals that I set for myself.

C

With my role at work, or with my career, and even in my personal life,,.

C

Is to be more transparent and open in my communication,.

C

In everything that I do., and so what I would encourage you all to do, is if you know of a person.

C

Or a team or a colleague that you don't really know what they work on, or you sit near them,, you see them all the time,, but you have no idea what they're doing,.

C

I would encourage you to start talking to them and ask them questions and get to know each other, and find out if there are ways where you can collaborate with them,.

C

And work together. that way, you're not reinventing the wheel but also you're, getting to know other teams and people.

A

(Bonnie), communication and collaboration happen to be foundations on which github is built. On,.

A

But in any facet of life, it ends up being one of those very important and key things to do.

A

And I'm going to move over to you, chad.

B

Open source is happening,, whether you like it or not.,.

B

I'm actually still surprised at how many tech executives I meet.

B

Who say that open source is not a part of their technical strategy? Internally,.

B

And that they don't adopt it or they won't use it, or it's too scary, or the investment's too high,, or it's not free, et cetera,, and then we walk six rooms down and we meet with the developers and developer's like, "actually, we're using this,, this,, this, and this.".

B

So it's kind of happening,, it's like trying to stop water as it's rolling, downhill, or streaming downhill..

B

So it's happening whether you like it or not,, and I think what we're trying to do at oracle is this cultural shift.

B

Around open source, and it's been a really fun thing to watch internally,, how that's kind of flourished. and so, oracle's, embracing that more and more as we've gone along.

B

Over the past couple years., it's really exciting to see.

A

(Bonnie) well, thank you., as I think we established today, open source is not impossible to attain.

A

It is possible to do at very different companies.

A

Given that every company is a software company,.

A

Open source becomes an essential part of every company's strategy.

A

And hopefully, you leave this session with a couple of ideas.

A

Of what you can bring back to your companies, to your teams.

A

That'll, hopefully make your development lives a little bit easier.. So thank you for coming.. Thank you for listening. we're going to be ending now,, but we'll be around for a couple more minutes.

A

If you wanted to come up and ask some questions to our distinguished panelists. thank you, per. thank you, shilla. thank you, chad..

A

We really appreciate it. (chad) thank you,, bonnie., (shilla and per) thank you.

D

(Applause) ♪ (music) ♪.