GitHub GitHub Satellite 2019 Keynote, 25 May 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Build like an open source community with GitHub Enterprise - GitHub Satellite 2019

Description

To make it easier for businesses to securely embrace open source and keep up with the best technology has to offer, we’re launching several improvements to GitHub Enterprise. These new features will support businesses as they work toward their goals, encourage open collaboration, and build trust at scale.

About GitHub Satellite 2019
A community connected by code

Explore our interconnected community—and how collaboration turns ideas into innovations.

Join us in November at San Francisco's Palace of Fine Arts for GitHub Universe - https://githubuniverse.com/

A

Now we want to share how our interconnected community actually extends into enterprises and large organizations and helps them be part of the community too, and to tell you about that, I'm super excited to have Dana Lawson. Vice president of engineering join us Dana.

B

Danke Shon ku I've been waiting to say that for a long time, how do y'all what a privilege it is to be here today in beautiful, Berlin and I, don't know about you, but this face is just absolutely mind-blowing. I've never been at a conference like this, so as you've heard from NAT, shanku and gray that the world of open-source is truly an interconnected community. Not only does it take a global team to create your favorite open-source technologies. The same is true for enterprise products and companies that we've come to know, love and trust.

B

Did you know that enterprise companies are the largest contributors and consumers of open-source, and we are so proud to play a part in the products that these software companies make with over 2 million organizations, trusting github as well as over half of the Fortune 50 companies use github enterprise for their internal development.

B

I love that these companies are sharing their code and ideas, but the downside for these large-scale organizations that it's just still too difficult to understand how they're using open-source how secure they are in addition to what packages and products are bringing into their ecosystems but, more importantly, how their broader teams are innovating and collaborating here at github. We listened and I am so pleased to announce available today.

B

These four new enterprise features that will help not only me as an engineering leader but countless other companies as they continue to innovate and they our enterprise, accounts, internal repos, new roles and permissions in organization, insights,.

B

So, let's dive in last October, we introduced a limited beta for enterprise, account feature with air price accounts. You can group all the organizations in a single account, making it easier for you to manage the needs of every org and team in your company, but just with enterprise accounts. We also wanted to make it easier for companies to share their code across the organization in a safe, open and secure way before you only had two choices: private and public repos, and today we're introducing internal repos, I'm sure you're like what our internal repos.

B

They don't make. No sense, we already a private repos. I, know right, but internal repos are away for an helping Enterprise company state interconnected, because software development is truly a team sport. It takes designers, tech support cells, even bosses like me and others in an organization to build these products. We love because it's not just about developing code, it's about everything that we do to make it wonderful. So now, with enterprise in eternal repose, you can broadly share your projects where every user in an enterprise account can participate.

B

No more trudging through going hey, can I get access to that. Can I get access to that now you have access to that so you're welcome.

B

So we created Enterprise accounts yeah, it's a big deal yeah, so we created enterprise accounts to easily manner your org and internal repos to inter source your projects, but we also wanted to help maintain errs because it's not all about enterprise. It's really about y'all and enterprise of the like. Have the ability to give the right access at the right time because, like I said it's not just about writing code, it's about everything else that happens, and it's just equally as important.

B

Our goal is to enable everyone to contribute, no matter if you're new to open source or you're an enterprise company with nuance needs. So we've worked to overhaul our permission model to introduce new roles for your team, the triage and maintain role.

B

The triage role allows users the ability to manage issues without having to Rabb write access to your code, so I know you maintainer they're gonna feel pretty good about that when those noobs getting your repos and you're like I, don't know you but I love you, but you can't write so you're welcome the maintained role, which has most of the rights of admins, but removes the ability to do dangerous thing like delete repos, because believe me, you don't want to do that.

B

Not that I have, but maybe I okay I have, but whatever you don't wanna. Be that person don't be me. That's that's why I don't yeah anyway, now that we have all these tools to better enable your enterprise teams to ship, smarter, faster and more secure. We also wanted to give them the ability to understand how they're, using their development work flows with organization insights.

B

You can now understand where your teams are spending time in these workflows, what languages you're using and what's changing over time in your company's ecosystem, and this is just the beginning with org insights. Our goal is to be the instrument panel for your development lifecycle.

B

Now, listen, I am sure you're as excited as I am about these features, and we are bringing to developers maintainer and enterprise companies alike and I am also sure you never thought enterprise could be so cool because, believe me, it is I mean look at this, but, most importantly, more most importantly, valuable because it really does take a global team to build these global products, and we really want to enable everybody, no matter where you come from, no matter where you work, no matter what you do, but don't just take my word for it here to tell their story how Enterprise company Shopify has embraced open-source and enabled their culture with the mantra open by default.

B

Our sebastian and christian.

C

Thank You Dana and thank you for having us this is really exciting, so my name is Christian I'm, a staff developer on the payments team in Montreal and I'm Sebastian senior production engineer also Montreal, so we're part of shop fight and for those who don't know, Shopify we're ecommerce platform that allow for small, medium and big merchants to sell their products across a plethora of channels, and our core mission is really to make commerce better for everyone, which also involves open source we're at around 4,000 employees.

C

Now we have 800,000 merchants across 175 countries and we have several offices around different cities, including in Berlin. Now Ralph I started in 2006, and if you really want to be that 100 year company, we need to invest in our stack and a big part of our stack is rails rails being powered by Ruby. We actually compete contribute to its ecosystem. In fact, Toby our CEO used to be a core contributor. Now we also have a dedicated rails core team, with contributors and as much as possible.

C

We live on the cutting-edge releases of rails that allows us to benefit from the latest performance, enhancements features and bug fixes, many of which we contributed to. It also allows us to reduce the maintenance cost, but, most importantly, Foster's success for all the community.

D

Thanks well, I mean as much as rails. Development at the core of our business Shopify platform is actually a full ecosystem of different technologies. I mean, as the company grew, our needs became more specific and we needed projects that would properly tailor to our specific needs and, after all, writing code is part of the fun of solving problems. Excluding Forks Shopify has over 200 open-source repos that are available out there and perhaps most important interesting story of an open source is boot snap.

D

So boot snap is a library that plugs into Ruby and optimizes and caches expensive computations, with a focus on reducing the boot time for rails. For the Shopify core platform, it was able to slash the boot time in for dropping from 25 seconds to Round six I mean open source.

D

Two years ago the project has received over a hundred fold requests, and now it's activated by default in rails, 5.2 powering all the million or so rails website out there I mean Shopify, believes an open doesn't start at the publication of a project, but that it's much bigger than open source. Internally, we have a deep culture of the transparency. The vast majority of our sack communications are happening in public channels and in the vaults, are internal wiki. We're able to facilitate the search, a call all of our shared knowledge.

D

I mean internal work is not about signing NDA's it's about people working together, but what about the code? I mean? Yes, we use github and, with very few exceptions, all developers, designers, content. Creators have access to all the repositories. Issues in project groups, teams are encouraged to create repos and share between each other. Github essentially allows us to bring that open-source mentality inside Shopify, with zero effort in projects are generally started by individual team and over time internal communities will start forming and around technologies and sharing their struggles and their solutions.

D

I mean organically projects become Co maintained and they spread throughout the company, eventually becoming the standard and recommended by default on our valve projects. If and when those projects be are made public those same communities carry on and become the stewards of public facing github help us carry off the open philosophy throughout that development cycle, but allowing the communities to flourish that much tends to multiply the number of repositories throughout its years. Shopify has created over thousands of repository and having so many repos comes with some complexity.

D

The role of my team developer, acceleration is to reduce that friction to automate and to standardize I mean our customers are the developers we want to empower them and the better we enable them the better they go on and serve their own customers.

D

So we integrate into github is API and we provide tooling for local development, review, testing production and even after production carries on and again the maintenance and that feedback loop that comes back well. Whether development is happening within a team across team or out of the public. The platform remains the same. That's a lot of investment, but connecting our teams with the rest of the world. We allow the crowdsourcing of that maintenance and the rest of the development.

C

So we've been doing open source for many years and I wish. We had developer acceleration a decade ago so about around 2008 2012.

C

We released two open-source libraries under a sister getup organization called active merchants and the goal of those libraries were a means of quickly expanding the payments accepted by our merchants in new markets and at the time it was the easiest way we knew of for expansion. So let me explain a bit the woodwork is partners would write their own implementation of those libraries. Those libraries would have just simple, abstractions they'd open up a PR, we'd review. It then merge it back and that would save us from writing all the code, then we'd simply bump.

C

The version of activemerchant inside of our platform and merchants would instantly have access to many more payment gateways. So in that sense we ended up in a very interesting client provider relationship. We not only provided the platform, but we provided an SDK to work with the platform and this beneficial two-way street, of collaboration about growth not only for shop fire but for payment gateways to be included on shop fire and then being that it's open source. It doesn't stop there right.

C

We also have a CO maintainer Spradley, who uses the libraries in production as well, and this is only one example of ours, so investing an open-source means different things, obviously different things for different companies of different stages, but if done correctly, applying the open principles to various communities, be it internal or external, blurs the lines and makes them interconnected. Having an open mindset is beneficial to everyone. Thank you.