GitHub GitHub Satellite India 2021 - Open Source: Day 2, 27 Mar 2021

Previous Meeting

⏯

youtube image

►

From YouTube: GitHub Satellite India 2021 - Open Source Day 2

Description

A community connected by code.

Join us virtually for two days dedicated to celebrating India’s developer community. Expect announcements from GitHub leaders, hands-on workshops, and inspiring performances by artists who code.

Discover regional open source projects built and maintained by your peers.

https://githubsatellite.com

A

A

A

A

A

B

C

C

C

C

C

D

D

D

D

D

D

D

D

Hello and welcome to day two of satellite india, I'm shonku- and I want to thank you for joining us today. We've got another packed day of programming and to start off, I want to take you, through a tour of github's products, to show off some of our latest features and to show you how you can use them together to build software across the world.

D

Now, yesterday, erica was here to celebrate all the amazing things that are going on in the github community in india. Growth of the community here has been incredible. In the last year, 1.8 million developers have joined github from india, and over a million developers have created their first repo on github.

D

India has now become the fastest growing country in the world in terms of developers contributing to open source. That is amazing.

D

Erica has also announced a new set of github programs in india that we're very excited about the github grants for open source program, which will provide 10 million rupees of grants to open source projects based here in india.

D

The github accelerate program, which will partner with startup accelerators and the indian government, to expand support to over a thousand startups, with our complete platform and finally, the github externship program for students, which will provide participating students a chance to get real-world experience working with software companies and we're really thrilled to see what you are accomplishing with github here in india.

D

This community is poised to double in the next two years and we're excited to see what you will build with github next now github is the world's largest developer community and it is for a purpose, and that purpose is to build together. We think of software development as the world's largest team sport, and we believe that it is a sport without borders.

D

Now I was born in india and I moved to canada when I was young to study computer science, and I had to move again to the united states to take advantage of the best opportunities in tech. That was the reality back then right. If you wanted an opportunity, you had to move to go, find it remote learning remote work, global companies.

D

These were all concepts that were unheard of, but today it is possible for a team of strangers to come together from across the world and build incredible things together, and this is what we see on github every single day collaborations and contributions from developers all over the world in real time, and it's also increasingly the reality at work.

D

Teams of all shapes and sizes companies from all over the world are going remote and they're going worldwide to tap into the best developers, whether they come from mumbai or mombasa or miami, and those developers need to be able to work together on projects from wherever they are. That's what I love about, github github was built for this kind of collaboration.

D

So today I want to take you on a tour through github's products and show you how you can use them to build from wherever you are now. Do you remember your first time joining a software team? I know I do that thrill of writing code and committing it for the first time and seeing it in a product right, but first there were all those things you had to go through right. Setting up your dev box, setting up your tools, getting your code and looking through it to learn going through docs and style guides.

D

All of those things that you had to learn before you can contribute something without messing it up, even with the best mentor to help you that could take days and the reality is today. You have to do that. All the time developers almost never work on just one thing: you're, always having to switch context, work on different projects, fixing live site incidents, contributing to other teams code or even just learning something new. That is not easy.

D

On average, it takes over 23 minutes to switch context and get into the flow, and that is if you've got everything set up for you. Often it can take a lot longer so github we care about this a lot we want developers to be able to get into the flow get into the code and contribute whether they're joining a project for the first time or just getting back into it after a while to show you how github helps you get in the flow. Here's neha.

E

Hi, I'm neha, I'm the director of engineering here at github for the team that works on discussions, I'm pleased to announce that we've now enabled discussions on private repos, and that means for this private repo. We can have our team conversations here and leave our issues for tracking our work. Here we have some internal chat about skylines. These cool 3d printed contribution graphs that people have created using a website we built, but we also use discussions to talk about ideas in the team and with others in the company.

E

My teammate diana had an idea here the other day about adding a year selector to the page, and I really like that. So I want us to work on this. So let's create an issue from this discussion thread and track the work. So I'm just going to go in here reference the issue give it a title and then I can just scroll down and I can create the issue. So this shouldn't be too hard and I'm thinking I might be the one to pick this up, and so we can do it together.

E

Let's just take a quick look, so I'm going to go over I'm going to assign the issue to myself, and you can see that this isn't the code base that I work in every day. This is just for fun, so, rather than downloading all the dependencies to my machine and getting a full development environment set up locally, I can open a code space right here in github and I can get my own personal dev box in the cloud right away, and this isn't just running the visual code editor in the cloud.

E

This is a full-blown personal development environment in the cloud. So, for example, if I like go over to the terminal- and I type in npm- run dev here in the console, I can get the full local development and experience as if I'd had the code locally on my machine code, spaces even sees when my code is running a server on localhost and so it'll.

E

Let me connect to it across the internet, taking care of all of the htgps tunneling and authentication to ensure only I can see what is running on my dev box in the cloud. So let me type in my github id nerd neha and let me check out this awesome graph, so this site's pretty awesome. It's got like a nice soundtrack and the coolest part is it's running on my dev box in the cloud, but yeah 2020 isn't really a year. I want to remember so.

E

Let's get started on that issue that diana mentioned by adding a year selector here code spaces is already authenticated with github. So actually I can actually just go to the github extension in vs code and it has my issues already listed. So if I click on it, you can see the issues listed here. I'm going to find the issue that I created and start working on my issue, and you can see that it's already created a new feature branch for me to add my changes.

E

So all I have to do now is take a look at the files, so I'm going to go over I'm going to find the form part which I happen to know is called hero.view, and I know that the code that I want to add in is between the at symbol and the submit button. So I'm going to quickly add the code for your selector and then I'm going to hit save now. This is a full development environment.

E

So if I just jump back into my application, we can see it's refreshing just as if I was running code locally and it'll start to bring up the selector there. It is so I'm going to type in my username again and I'm going to test it with the 2018 year. I know that I had like a pretty good year that year um and also I had this like great break for summer and thanksgiving.

E

So I want to see if those show up- uh and so here we go okay, so you can see my skyline and you can see that, like I even at the end, there's like some nice gaps, it's when I took my end of year, vacation super seriously, um and so this is all running in my private development machine in the cloud um I can come in, I can mess with the graph I can scroll around, and so I know that this works and I'm ready. Let's commit this and let's share the changes with the team.

E

So what I want to do now is I want to go back to my editor and I want to first commit that change locally. So I'm going to go into the get view um and you can notice. It already includes a link to the issue that we're working on and so um then I can go ahead.

E

I can commit it and now I'm going to create a pull request, so I can do that by going straight to the extension um and then I'm going to go into my github view, I'm going to create a new pull request. It's going to figure out which branch I want to compare to, and it's going to even publish the branch for me.

E

So I'm just going to scroll down here hit create and then I can create the pull request and it's going to do all of the work of publishing the branch, pushing the changes in the server and even creating the pull request in the server. So you can see my pr it's like right here. So if I go back into my repo on github, I can navigate over to the pull request tab. So let's do that really quickly and there you can see.

E

My pr is available uh your selector for graph, and you can see that it's ready for my team to review and I can see that the ci builds have already kicked off. So I can to verify my change. So let me go in. I'm gonna tag this with the enhancement label and then I'm gonna you make use of this super cool new feature.

E

It's called auto, merge and github, and so what I'm doing here is I'm having the pr get merged automatically as soon as all the checks are complete and the code has been reviewed by the team, and so I don't have to do anything here, and this leaves me free to get on with my next change. In the meantime, let me hand you back to shanku.

D

Thanks neja now, once you've written your code, it's time to get it reviewed and committed now. Code reviews have also changed in this new world used to be that you could invite someone over to look over your shoulder, review your changes and give you a quick thumbs up, but now that you're working on a distributed or remote team, you still need that review.

D

You just need new ways to do it now, on github, everything about code revolves around the pull request and the code review experience, pull requests were designed to let strangers review and collaborate and commit code together during the last year, as teams have become more remote.

D

We've seen something amazing on github developers are actually submitting pull requests for code reviews more often than ever before, as much as 30 percent more frequently and when they do, those pull requests are getting reviewed faster than ever before, and that's good news if your prs are more frequent and smaller they're easier to review, and that leads to higher quality code reviews and higher quality code and when they're easier to review, they also get reviewed faster, which means that they get committed faster and shipped faster.

D

Better prs also means not just having human helpers, but the bots github actions and our amazing ecosystem provides an integrated ci platform with thousands of custom actions written by our community that can automate all sorts of reviews running your unit tests applying linters and style guides. Checking your dependencies and just helping you commit better code to show us more here is a tool.

F

I'm atul and I work on the databases team here in hazard bar this is the pr from neha where she has added a new ear selector to the site that we're building for every change we make to the site we build and test it automatically using data actions. Let me show you the ci bill for neha's latest changes. If I go into the summary view, you can see the brand new visualizer showing us running the build and test steps on both mac and linux machines all at the same time.

F

This takes advantage of data actions and our hosted build runners which provide you with secure, build servers on demand. All of this infrastructure is managed for you by our team at github so that you can add new build machines whenever you need them for either linux windows or the mac. Let's go back. Let's look at how the build is configured. Our workflows are defined in the dark data folder under workflows. We are going to look at the ci build.

F

First, we can see that it is triggered by new changes in the main branch, but also by any pull requests that are targeting the main branch we also define which operating system and node versions. We want to run our build on, and then we build our code from the lender and do a full test should pass.

F

The actions community is fantastic with over 7000 open source actions in the marketplace in the ci build. We have added an awesome community action from tim, lucas and joseph peterson that will update draft release. Note for you, based on your issues and full requests. So that's that's the power of community for you that you can use to transfer ci. We also create and deploy a test environment in the cloud for every single pull request. This makes it easy for us to review the changes in a working environment.

F

So let's take a look at the dev test development workflow, which is run in parallel alongside our ci bit. So, as you saw, this is triggered by pushes to main, along with new pull request. We come in get the code and then deploy it to our cloud provider using a secret which we store securely inside github's built-in secret store, we've also added a job to this workflow that will come back and destroy the environment when the pull request is closed, to keep our costs down.

F

So let's go back to the pr from the pr from neha and review it. um Let's scroll down. I can see the link a link that has been added by the deployment, so I can click on that and quickly test the changes without having to install anything myself.

F

I can see that the new here selector is there. So let's just enter a name and selector here 2018 and then take a look at the graph. The graph is loading.

F

And yeah, I think the contribution block looks good. It has the ear as well, so I think the ear selector is working you're able to select the ear as well as see it on the contribution graph. So let's go back to the pr and let's review the code.

F

The code, the code looks good, so, let's just say, lgtm and quickly approve the code now because they has enabled auto merge. S1 has approved the change, the code is deployed, the code is merged automatically, and data actions take care of destroying the test environment for me, so everything just works into it back to shangri.

D

Thank you now, by using github pull requests and actions, we are seeing our customers ship code to production way more often, but it's not just enough to ship faster. You also have to ship safely and securely.

D

One leaked secret, one vulnerable piece of code, one insecure dependency can cost you time, cost you money and cost your customers trust now we're humans and humans make mistakes. It turns out. The majority of security vulnerabilities are just human mistakes and once those mistakes get into code, they're hard to get out.

D

So if you can fix those mistakes before you ship or even before, you commit code, that's great, and if you can't, then the quicker you can fix them once they're found the better so with github security tools, we're trying to put security where it makes the most sense right into the developer workflow.

D

So you can find and fix these issues more quickly. So to show us more here is niroshan.

G

Hello: everyone, my name, is niroshan rajadheri and I'm part of the application security field team here at github, and I'm going to talk to you about the work we've been doing in this space through a quick demonstration.

G

In our example. Here we have advanced security enabled in our organization, and this allows us to easily switch on code scanning and secret scanning for our private repos, but everyone can still use these features on your public repos for free just go to the security section of your repo settings and switch it on there.

G

I can get an overview of the security situation for my project from the security tab in the repo beginning with supply chain issues. Here we have dependebot enabled it is automatically looking for vulnerabilities with my dependencies and it will create a pull request for me if one of them needs updating.

G

Looking here I see dependable is telling me about a new release of one of the actions that atoll was using. It's a minor revision. So I'm going to go ahead and approve this change to keep us up to date.

G

All the tests are passing, so I'm going to go ahead and merge this change now, even our build processes can be kept up to date with dependerbot back to the security tab. I see that secret scanning is also active.

G

Let's take a look to see if any of my team accidentally checked in secrets or api tokens, so we can stop them from being externalized.

G

If we look at the closed issues, we can see one of my developers accidentally checked in code that included a token in the past, so we've actually revoked that and removed it from the code.

G

So that's known, vulnerabilities and sequence taken care of, but what about our unknown vulnerabilities with codeql from github we're able to scan our code base looking for code which could be introducing potential security vulnerabilities into the code that we're writing? As you can see, it's identified one here for me. I can show the code part that was found with code queues, analysis tools, and I can see that this is definitely an issue.

G

However, it doesn't look like it'll lead to a major exploit in our case, but let's create a quick issue from the code, so we don't forget about it. This should be a simple fix to explicitly tostring the value from the url I'll. Also mark this as a good first issue in case someone wants to pick this one up once I'm happy we'll save the issue to make sure we don't lose track of the work.

G

We want to do excellent, we'll get back to working on that right away, while we've had the security tab on your project for a little while now today, I'm pleased to announce that enterprises with github advanced security now have a security tab added to their organizations where you can get a quick summary of all the projects.

G

You also have an overview of all the projects in your organization and what the status is of their security features. I'm also pleased to announce that this is now available to teams who can see the security status of the repositories that they administer with that back to you, shanku.

D

Thank you nirushan. Now, we've got our code written reviewed and committed where our code really belongs, is in our users hands, and that means shipping doing the functional testing sharing with stakeholders and getting them to sign off and releasing the production and celebrating together. Now, github's new tools were designed to make it easy to test and release together as a team to show us more. Here's katie.

H

Thanks chanku, hey everyone: now we have a release: that's ready to head out the door thanks to a tool. We already have a draft of our release, notes, let's edit a new release based on the draft notes.

H

First, I'm going to set the title then I'll check the draft notes that were automatically created.

H

To be honest, these look pretty good already, so I'm going to go ahead and publish this release. Now we have a workflow set up in actions to be triggered by the publication of a release with our new workflow visualization ui. You can see the release is now deploying to staging.

H

Then it'll run some end-to-end smoke tests before finally deploying to production. While all of that is running, let me show you how I've set this up. Let's take a look at the code in another tab in the github workflows, folder we'll find the releases.yaml file in the release. Yaml, you can see I've set up a couple of different triggers a manual trigger with workflow dispatch as well as triggers, based on when a release is published in the deploy staging job. I specify the environment name and url, where this will be available.

H

You can see I'm also requesting the published token secret from github's built-in encrypted secrets fault. After that job is completed. We run our smoke test, then a deployed production again specifying the environment name and url before calling the same action with published token as the secret.

H

Now these steps are identical, yet they publish to different places. That's because we define a different publish token for each environment. Let me show you how we do this. I head into project settings then, in the new environment section I have staging and production on the staging environment. You can see we have a published token defined in github's encrypted secret vault, even as admin. I only have access to update this. I can't view it in the ui going back to production.

H

I have the production publish token defined in our secrets here as well, but what's more interesting is that you can see I've set this up to require manual approval before code is deployed to production. Only people from this team can permit code to go, live and there's a full audit trail to see who approved it.

H

Great staging has been deployed and our smoke tests have run. Let's take a quick look at the staging environment. Awesome looks good. I'm going to enter my id to test out my own graph and make sure everything's working well.

H

Everything seems to be working well, nate has code is included, so I'm going to approve the release to.

H

Production back in the github ui, I can click on review deployments, select the environment and leave a quick comment approve the deploy there we go deploying to production is underway again with a different publish token from staging.

H

And with that we're deployed I'm going to click the url just to validate great head over to skyline.github.com. If you want to check out your own contribution graph in 3d back to you, shinku.

D

Thank you katie, so there we are a complete way to build and to end join a team get into the code. Make your first contribution.

D

Get code reviewed with your peers, with the help of automated ci, to keep your code and your secrets and your dependencies secure and test and ship and celebrate together now all asynchronous all remote friendly all available from anywhere in the world on github's planet scale cloud. Now software teams all across the world are using github to do incredible things. One such story comes from india's own infosys.

I

Like our most visionary clients partners, our goal is to become a completely knowledge and data driven organization with agility built into our core, so that we can sense all the business changes happening around us and continuously evolve in response at infosys. We are envisioning ourselves to be a live enterprise powered by our digital platforms.

I

Our developers, architects and practitioners are at the forefront of this, leading it for us, and our endeavor is to enhance their experience, make them highly effective and efficient in everything that they are doing.

I

Our digital platforms for productivity and the engineering tools ecosystem allows us to do this at scale and drive any change at the organization level in an accelerated manner. Our engineering tools and the continuously evolving ecosystem of homegrown, open source and off-the-shelf tooling forms an important cog in the wheel to drive agility and scale in a secured manner.

I

For instance, infosys devsecops platform, polycloud meridian leap, modernization suit are some of the examples of assets that power this for us. Github is a critical element of this ecosystem and is central to driving developer productivity, secure sdlc, inner sourcing, reusability and augmenting the developer analytics. For us, it is unifying the experience of of our developers by a variety of integrations around the robust devsecops ecosystem.

I

It is also a key enabler for our live enterprise store and marketplace where we plan to bring together the community of cloud builders and cobalt from amongst our partners, clients, open source, academia and these startups to drive contributions and consumption of various assets, as well as enhance the ecosystem with an open source. First thinking something, I believe that any forward-looking enterprise, engineering teams and developers would appreciate in a big big way, as the github team continues to drive the roadmap.

I

I look forward to seeing several of the new capabilities around security code scanning telemetry, observability, analytics and github actions that can keep on taking us ahead in our journey as a live enterprise.

D

It is exciting to see what companies like infosys and you, the developer community here in india, how you're using github every day to create amazing things. Thank you. You inspire us to keep making github better in just the last six months. We have shipped over 100 new features and improvements, including many of the features you just saw.

D

All you need to do to get started with. Github is available for free on github.com for developers and teams of any size. So if you're just learning to code or contributing to open source or starting a new team or or starting your own startup, you can do that on github for free today, all right, thank you for joining us on this tour today this was fun to do. I hope you enjoy using github as much as we love building it as it turns out we're not just building developer tools for global teams.

D

We are one ourselves. Github has always been a remote first company and we now have developers from over 15 countries working together as one team and a big part of our team is the github team in india, they're building github on github with the rest of us. So in closing it's my pleasure to introduce you to the github team here in india.

J

I am sanjay malpani. I work from hyderabad as vp of software engineering. I love our dedication and focus on building one of the greatest developer experiences. I'm.

K

Manish country manager of github in india, based in delhi, I love working at github because I get an opportunity to support developers, students and customers that are driving india's growth. I'm.

F

Atul malvia director product management at github, I love working in guitar because github is where the world builds. Software hi.

L

This is divya vaishnavi director of product for github education, I love being at github, as I can empower the lives of students and teachers across the globe. I.

M

Am muhit enterprise solutions, specialist for asia region? I have the opportunity to do the best work of my career so far, I'm.

N

Namas and I'm the regional sales director for github india, and I just love the fact that I'm able to empower the developers with the right set of tools to bring.

O

On the best in them hi, this is pulkit agarwal, I'm product manager here at github, india github to me, is an open platform. A free marketplace.

P

Hi, I'm richard senior director for software engineering. I get to empower developers of today and tomorrow. This is satya.

Q

What I do and my teams do- impacts millions of developers across the world. I'm.

N

Shaishan gonzales I'm product manager for the github marketplace. Together we make the best software solutions from july. My.

Q

Name is mitha garwal and I'm the head of finance for github india. I love working for github because of the amazing people around me.

R

I'm usha product manager at github. I love working at github, because everything that I do can impact millions of developers who love to share their work and build some great software products together.

S

Hello: everyone, hello welcome to day two github satellite india 2021, I'm so excited to be here with all of you again um just a reminder: I'm anisha pandoria and I'm I'm I'm live calling in from washington state usa originally from the uk, can probably tell from my accent as well um I'm in the developer relations team at github and working alongside my amazing co-host and colleague, karen hey karen.

A

Hey alicia.

M

Hi everyone uh and welcome back to day two of getup satellite india 2021. It's really really exciting to be back over here and also see all of those amazing tweets and discussions that all of you have been putting out and conversing with us. It's it's really great to great to see all of those I'm really excited for all of the rest of these sessions. Coming in uh today, we have, we have a really nice uh set of speakers panels and a whole lot of uh other things.

M

uh My most, you know my most really interesting thing for me was just this keynote uh anisha that was that just got concluded uh talking about all of those amazing features.

M

uh You know code spaces actions, issues skyline is one of my favorites for sure, and then also you know that that last bit of all of those uh github aka hovers that we call speaking about how they really like working at github and what they really like. That's one of my favorites. What what did you like? Anisha.

S

Yes, I I loved everything about what shanku just mentioned, as well, plus everything that erica announced yesterday as well. All of that amazing support for open source, maintainers contributors, startups and students- I mean all of that- was just fantastic and don't forget all of the sessions that we heard yesterday were amazing and we've got a whole bunch more good stuff.

S

Coming your way as well- um and you know what you can- you can interact with us on twitter as well, so talk to us about talk to us about what your favorite moments are on twitter, using github satellite and tell us what you thought about the keynote both yesterday and today what you liked most from day one and what you're really excited about uh um in day two today as well- and you know what let's have a little bit of fun as well.

S

You know what share a photo of your workspace to hashtag github satellite, and we want to see what your workspaces look like and don't forget. If you haven't already filled out the attendee server yet go ahead and do that you'll see the link below and our window here where it says we want your feedback, but current, can you remind me again how many channels do we have.

M

It's just one anisha, uh I'm just kidding. You know, because we are here out here on the bus channel, that is the open source channel, but we also have one other channel. That is the devops channel. That's happening in parallel, where our really good friends and colleagues, divya and mohit are hosting sessions. Talking about devops, developer, experience, secure development and a whole lot more. So we are on day two, which is the last day of cadet satellite.

M

uh But still you know nothing to worry about, because we have some really nice sessions lined up uh lined up over there. So if you do one go check out no hard feelings check out the devops channel as well and do check out the schedule on github satellite.com schedule where you can see what all is up for today. We're gonna be having a lot of fun out here on the open source channel, uh so so stay tuned in terms of what's happening.

M

So, if you want to talk to us, then I'm just thinking of ways how you can talk to us any.

S

Ideas I mean you could like shout it out from the rooftops a shout out from your window, but you know what let's get real. You can engage with us on discussions, uh we'll be hanging out there as well.

S

The github subject, matters uh we'll also be there with the community engaging during the sessions and we'll be taking your questions for speaker, q, a as well so go ahead and join in the discussions at dot com forward, slash discussions um and don't forget there were workshops happening yesterday as well, and those workshops were amazing and there's more workshops to come today if you've already signed up as well. So what's coming up today, um I know that you all all of you folks, are probably wondering what that is so on the open source channel.

S

We've got speakers from chatwood layer, 5 and github, covering topics ranging from ci workflows to github being like a boss as well, and then over on the devops channel, um they're going to be getting into emma lop's, workflow automation and everything about github actions. So you know what without further ado, let's get into it. Who do we have up? First, karen.

M

You know one of our first speakers starting off today uh is one of my favorites as well. As you know, one of the favorite histories of the open source. uh You know ecosystem out over there. So our first speaker who we have is dr viral shah, who is the co-creator of the julia programming language and also the ceo of julia computing, so uh he's going to be talking about how julia was built in the open, their journey, their challenges, and you know what all a is in store.

M

So it's going to be really interesting to learn about how an entire programming language was was built in the open and then get an insight into all of the all of the journey behind it. So don't forget, if you have any questions, uh do drop them on the discussions on github, satellite dot com and kidup satellite dot com, slash discussions once viral's uh talk is over we'll be taking up.

M

Some of the questions live for him as well as he'll, be hanging around on discussions after his talk as well for taking up q a on the discussion thread so without further delay, I'm very very excited. Let's welcome viral shah vera.

T

Hello hi thanks karin for that wonderful introduction and I'm viral shah, one of the creators of the julia programming language and also co-founder and ceo of julia computing. I'm going to talk about how we build julia and our community out in the open.

T

A lot of it mostly on github and and everything I'm going to talk about is is not just about me, but about what the broader julia community has built.

T

So julia has been a long journey. It's been around for almost 11 years now, and we started this journey in 2009 with an urge to solve the two language problem. The two language problem, very simply put is, is a phrase that we coined actually after after starting the julia project and the reason why we had to come up with it was because it was hard to explain what why why the world needed a new programming language. Why did the world need julia and the reason it?

T

The reason is as follows: right you, everyone's used to programming with python, with r, with matlab with all of these interpreted languages. That are, you know, not not really great for performance, but then you always end up. Writing your programs in c c, plus plus fortran java, in order to get higher performance.

T

So people like to have a certain kind of language for data exploration for interactive exploration, for um you know for for just sort of interacting with your algorithms and then another language for getting performance, and it's really odd to write the same program twice, and this is why we started out by creating julia, to solve this two language problems so that you can have the ease of python and the speed of c all in one package in one language.

T

So in 2009 we wrote the first line of code and in 2012 we actually published a post. A blog post called why we created julia. If you, if you google, that term you'll land up right there and you'll see what what it was about and a lot of what we wrote back then still holds true, and this is how julia got started. It was the four of us um with uh jeff bizanson, stefan karpinsky and alan aylman.

T

Those were three of my co-creators, with whom I started the julia project and just like many open source projects. It completely started out with an email conversation.

T

I was actually based out of bangalore when I started this project and and three of my collaborators were based out of the us, but all of us were in very different geographies and uh it was a completely distributed setup in in where we started. uh You know talking by email, set up a git server. This was this was not yet on github back then we actually had a git server at the university of california.

T

At santa barbara that stefan used to maintain and very early on in the project's life, we actually ended up moving to github. Some of the other milestones for the project. Julia became the ju in jupiter uh in 2013, the second language that was added to jupiter.

T

For those of you who do not uh know this jupiter notebooks uh are extremely common for data science and they stand for julia python and r and so julius j in jupiter. In 2015. We actually founded julia computing because of all the interest around the julia programming language and some of the first companies started using julia commercially.

T

We hit 1 million downloads in 2017., 1.0 was released in 2018 in julia conn in london, and 2019 saw 10 million julia downloads. We were extremely thrilled to receive the the wilkinson prize for our contributions to julia and also the sydney fernbark price um last year was a couple of years ago now, and we are now close to 25 million downloads and even though my slide says julia 1.5 released. In fact, yesterday we just released julia 1.6. It has been getting rave reviews.

T

um It was trending on hacker news just about yesterday and uh it's it's. It's obviously the best release for of julia. Ever so far.

T

So, while julia as a programming language solved the two language problem for scientists and engineers, uh you know it, it really is making impact in the real world. People are using julia for faster drug development.

T

You know, companies like paiser and moderna are using julia to come up with new drugs and and take them through uh their drug. The the drug pipeline process in a faster way, um companies like mitsubishi electric, are working with us, uh mitsubishi, electric research, labs on energy, efficient buildings and air conditioning systems with julia.

T

We were able to simulate some of these air conditioning systems 500 times faster than was possible before, and that means that a year's worth of simulation of how an air conditioning system might react to all the changes in in temperature and weather and so on and so forth can now be done in a few days because of julia we're working with the team at carnegie mellon with uh professor venkat vishwanathan, on coming up with uh new battery new new and efficient batteries uh like the kinds that go into electric aircraft coming up with new materials for these batteries and new simulation technologies uh for for sort of putting batteries into new uh electric aircraft.

T

Hardware- or um you know, there's a lot of work by the climate machine project between mit and caltech, where julia and its scientific machine learning ecosystem are being used for climate science and climate modeling, and its impact on agriculture and and on just a number of many different applications.

T

So these are some really difficult scientific problems that julia is addressing today and what I'm going to talk about is the journey from developing the julia language, developing a community. You know building out julia computing and then being able to actually work on some of these cutting edge problems.

T

So here's the the julia project on github- it's um you know just uh julia lang, slash julia julia lang is the organization julia's the project. It has 33 000 stars and uh tons and tons of comments uh yeah there you go close to 50 000 comments, and um you know all these many fork. So it is a living breathing project with over over 1 100 contributors to the main julia project.

T

I don't like this little red check box here, as as anyone who's been on github likes it. This is. This is a screenshot that I just took before this talk, but we worked very hard to make our ci green, but this ci is very demanding.

T

We actually run our own uh ci systems that test every commit of julia on 32-bit 64-bit, intel arm, you know, and and and all sorts of architectures, on windows, mac linux. So it is, it is a difficult ci to pass, but we take it very seriously. As I said, we released 1.6 just a couple of days ago.

T

One of the things I wanted to do for this talk was that the dig back into my own first commit out of uh you know into julian turns out. That was in september of 2009, where we uh had uh where my first commit was actually to add some of the array array operations into julia, and it's it's just all looks so different. I mean we have, we didn't even have jl extensions back, then they were dot j and then you can sort of see how the project's going.

T

We added the plus method right there implemented edition for double scalars and- and you know, we're off to the races.

T

One of the things I like to highlight about julia is that we started out. You know. I personally started out my work and my contributions to julia in india, and I I wrote a majority of my julia code out of india for the first several years. This is a picture of many of the early contributors to julia from julia corn, india, 2015, and we we wish to be able to do more julia cons in india going going forward, but this is a small team that got started.

T

Indian indian, open source contributors have had an outsize uh impact on the julia language. Apart from some of the people I have here, I should also mention that uh contributors from india are are a part of the google summer of core project every year. At least you know anywhere between one third and one half of the contributors that we uh that we mentor in the google summer.

T

Of course program are actually uh out of indian universities, and so it's not only sort of people contributing to julia from the industry, but we have a lot of people from indian universities undergraduates, especially that are contributing to julia, and the community has seen exponential growth. It has been. You know: we've seen, 25 million downloads, so far, they've been compounding year on year, tons and tons of youtube views check out uh alan edelman's, computational thinking, class computational thinking.mit.edu, which I think is the best way to learn julia and some of the scientific machine.

T

Learning examples that I showed before we have a forum views on. uh uh We have. We use this course for our forums. You know the number of news articles, the number of julia packages, 5 000 julia packages today, and it has been a phenomenal journey. Not only can you call these 5 000 packages from julia, but you can also call every python and r package and every cn fortran library, every java library ever written.

T

So often people ask me that you know hey it's a new language and maybe it doesn't have enough packages- and I say not only can we call the 5000 packages in julia, but just about everything else, and especially python packages are a breeze to call python in our packages.

T

You pretty much do not have to do any boilerplate to call them. Julia has now entered the mainstream, we were number 19 on ieee spectrum and in 2020 we went from 47 to 23 on the tyobi index. uh Some of these indexes are very noisy, but you know directionally julia has been doing really well on many measures of popularity of programming languages as flawed as they all are. I think they do pitch. They do sort of paint a long-term picture.

T

My personal estimate is that the julia community is over a million users. Now, worldwide, we've seen downloads from over 10 000 companies from julia computing you're, seeing it being used and taught at over 1500 universities, including some of the best ones out there, and you know here's some of the the universities that are actually teaching and using julia there's over 100 github organizations- and this is this- is unique about julia.

T

I think compared to many open source languages, because julia was developed on github from a very early stage, and so the github community structure match matches and maps to um github organizations. uh It's just something that has been built up organically over time, and you can look at this right. There's a climate org there's a eco julia, which is for ecology, flux ml is our machine learning organization.

T

Julia actions is where a lot of our ci work, uh you know, and the github actions are held or julia very for raspberry, pi or turing lang here, for example, for probabilistic programming, uh julia images for image processing. So these these are just fantastic organizations um that that we've been seeing people put up, and I just love all the all- the logos that people have come up with which are sort of based on the julia logo itself and the colors and the theme.

T

How fast is julia? It is really fast. This is the benchmark that is on the the computer. Language benchmarks came on. Debian julia is in the top five with c rust in uh fortran. You have julia right up there and um you know really fast with graph processing. You know with with basic data science machine learning loading csv files turns out to be really really fast in julia because of multi-threading, and some of our data frames.

T

Benchmarks also show julia, comparing very well with some very um you know some very uh optimized tools like spark and pandas. So so julia is fast, but don't take my word for it. Try it out yourself, there's a growing collection of julia books out there that that have been all contributed by the community. Many of these are from uh professors at stanford, especially linear, algebra and optimization are two of my favorite books. I would highly recommend some of these books.

T

These are beautifully produced books, but then, at the other extreme we have a book by ahansen gupta, which is the little book of julia algorithms for for kids to learn, julia and and we've seen kids as as young as 10 years old learning julia from from that book.

T

U

Of the one of the.

T

Most interesting things about julia, I think, is in terms of user experiences, is pluto notebooks. Of course, visual studio code has now become the ide of choice for julia users, but pluto notebooks have been developed by by fonz van der pla from amsterdam, and- and this is a reactive lightweight notebook. So jupyter is a general purpose. Notebook environment that is a language agnostic, whereas pluto is a julia, specific notebook which means that it's reactive, when you update a cell out there, it will automatically update the calculations in all the other cells.

T

I would highly recommend checking out the juliacon 2020 talk by fonz. I will also point out that con 2021 is coming up very soon. It's going to be at the end of july. um Sign up at juliacon.org, sign ups are free and the conference is online this year.

T

So all this is great. Now, how do we go from you know, building a community building out julia to sort of you know solving all those interesting problems that I talked about right problems that the world is facing problems in you know in climate and problems you know in combating a pandemic, or you know how? How do you cool your houses when the weather keeps heating up or the climate keeps heating up?

T

Machine learning is a major part of this, and and what julia does fantastically compared to many of the other programming languages is that it takes machine learning to the next level by integrating it deeply into the language, a concept that we refer to as differentiable programming and and the way this all works out is as follows: right everyone's familiar with uh machine learning, enormous data sets distributed computing, lots of new hardware, gotta run on raspberry pi's gotta run on android.

T

But what really makes it all happen is automatic differentiation, the ability to differentiate your programs, not just your neural networks and do back propagation, but can I do back propagation through my entire julia programs through my solvers? You know, through my optimization routines through you know, through just about everything right through differential equation, solvers and so on and so forth, and that is this basic idea is at the crux of all of julius iml ecosystem and it's possible because julia's machine learning libraries have been natively written in julia itself.

T

So, for example, if you look at pytorch or tensorflow, there's tons of cuda and c, but but julia's machine learning, libraries are written in native julia itself.

T

Here's julia gpu, so so julia also runs natively on gpus, and um this is just these are benchmarks compared to cuda c, as you can see, they're, you know almost as fast in some cases faster than kudasi and some cases a little bit slower, but native gpu programming in julia is essential for the julia machine learning ecosystem and the scientific machine learning ecosystem in julia, it's being used for tons of interesting product at julia or download the package and try it out.

T

So all of this comes together the gpu capabilities, the flux, machine, learning, capabilities and just about everything in julia comes together in you know, with what we call differentiable programming and and what julia offers is language-wide differentiable programming, which means that not only with your neural networks, but any arbitrary julia code is amenable to differentiation, which means it's amenable to be put into a machine learning loop.

T

It's amenable to stochastic, gradient descent and optimization, and this is something that scientists and engineers around the world are combining they're, taking julia's traditional machine learning, capabilities and deep learning, capabilities like the flux library and combining that, with all the scientific and machine learning and image, processing and data processing and differential equation, libraries together, so that you can apply some of these ideas into into just about every juilliard program. Ever written and combined your data-driven machine learning that comes out of deep learning, with model-driven scientific learning and sort of get the best of both worlds.

T

I would highly recommend looking at christopher caucus's talks online, uh where he uh talks about. You know, he's the author of julia's scientific machine learning ecosystem and he talks about all these different applications. uh If you just look at look him up on youtube applications in pharmaceuticals in engineering and chemistry and manufacturing in batteries in climate, this is this is how the ecosystem comes together, and this is why I personally believe that a programming language can really change the world. It's it's all built by the julia community. It builds up.

T

One foundation, you know, builds up from the foundation one step at a time and goes up all the way to solving amazing and interesting problems out there.

T

What do we do at julia computing?

T

I'd like to sort of leave you guys with a small advertisement about julia hub julia hub is a platform that is built to provide the best julia experience where you can explore build, run scale and visualize your julia programs, you get online vs code, editing along with scaling julia programs to large numbers of gpus and cpus on the cloud, and all these amazing workflows right from the julia language and the julia compiler, the thousands of libraries, all the machine learning ecosystem, the scientific machine learning tools, the parallelization, the gpu computing.

T

All the way up to you know solving some of these problems. These entire ecosystems are being put together on julia hub so that they're available to everyone from students to scientists at some of the best companies out there at uh you know just just put it all on their fingertips. That's what julia hub enables. So I would urge you all to try it out. You know, try it out at juliahub.com and let us know what your experience is out.

T

There come join the julia community on github and I'm going to be talking on on the discussions right after my talk. Thank you very much.

M

Wow, okay, that was uh you, know, uh viral shah, uh who has gave such a nice overview of uh julia, hey viral. You know we're just having a little bit of you know an early holy celebration out here. So all of these uh colors and confetti is what you can see, but uh thanks a lot that was, that was a really nice uh session about julia, and we have quite some questions uh coming in.

M

So uh the first thing uh you know, without that, the developers want to know is julia, being an open source programming language as well as uh you know where you have a business. So how does? How does julia computing build an open source business.

T

That's a very that's, a very good question actually and one that I often get that you know: what's: what's open source and what's not and and how does an open source company make money? And um you know we are, we are committed to the open source community. That's what created julia and the company exists, to sort of leverage the community add to the community and- and just sort of uh you know, grow the community uh going forward.

T

So the way we the way we do it is that all of julia is open source, the language, the compiler, the ecosystem, and we are major contributors to it. All the co-creators of the julia language are co-founders of julia computing and we have uh the best interest of the communities at heart.

T

What we like to do for our business for our customers is build a cloud-based software as a service product which is julia hub, which is what was my last slide, and we expect that by providing julia hub on the cloud to all the julia users out there in in enterprises and around the world is how we'll build a successful business, and um these are. These are very well aligned incentives, because this means that there is not going to it's not an open core model.

T

It's not that optimization level dash o3 is only available by julia computing. uh You know to its customers, but that everything out there is in the open source is in the open domain and the company actually integrates it into a cloud service for enterprise users.

S

So I love that.

T

E

S

Where can someone go and learn more about julia? Are there like online courses or is there anything that you can point us to.

T

S

T

The so so there's um if you go to julia lang.org, which is the julia website, or if you just google julia you, you know, instead of getting um you know, uh actresses named julia. You nowadays get the julia language, especially if you're a programmer on the google top hit. So if you go to the giulia website, there's a learning section and we also have juliacademy.com, which are a free online courses for getting started with julia.

T

In addition to all the books that I mentioned, but the julia learning, the the learning page on julia lang.org puts everything together for learning.

M

That is, that is viral. That's gonna be probably my favorite sentence for the day that you said you know like when you go on the search engine and search for julia instead of actresses, you will find the open source programming library. That's that's! That's really my best code for today you know so uh that's really great. So uh coming back, there's one more question. So, uh if you had to do you know one thing differently: building the julia programming language today. uh What would you have done.

T

Yeah, that's uh that's a very hard question. Actually what what would we have done differently uh if we were to build julia today right- and uh I I I mean there- are it's it's hard to say right because had we taken a slightly different path, would things have been been different in some way? um I, to be honest, you know it's all about the community and the journey, and uh you know that's sort of far more interesting than any sort of technical decision around the language itself.

T

If anything, I think um you know what what I would love to see happen in julia is you know some of the decisions that if, if you were to start out now, there are just so many more mature, open source language frameworks that we can use today that were not available when we started 2009 llvm had just come out back then, and it was. uh It was not what it is today, but it has.

T

It has definitely been difficult for us working with llvm and seeing sort of some of the the challenges and so on and so forth. So we might, we might do a few things differently today. It's not it's not clear. What exactly would they be, but um I you know, I guess.

T

One of the things I would say is that I would work for even deeper integration of some of the machine learning uh tools that we talked about during my talk and and they would become even more first class as part of the julia language than they are today, given just how important some of these technologies are.

M

Nice, you know so so you mentioned I like how you mentioned. You know it was it's more about the community and the journey. So uh where can? Where can someone go and then you know, interact with the julia community, find peers or find someone really to uh help them grow in their journey, in learning the language and kind of like exploring it to its depths.

T

Yeah um it uh so so again on julialang.org you have the community section, which has all the community pointers. We use discourse for our mailing list and discussion forum. So discourse.julialang.org is a very vibrant community out there.

T

We also have the julia lang slack, which has over 5000 people on it, and it's just insane um so that that's a that's a good way for interactive communication, but a lot of our community interactions also happen on github, because you know you know if you post in a github comment and someone replies to you, it's almost like chat. It happens in real time and a lot of uh a lot of those comments. A lot of those communications actually get.

T

You know archived and are crawlable by google, and someone else can come a few months later, a year later, join into the discussion. So there's there's many different forums uh for for people. uh There's chat, there's mailing lists, there's github and all of them are are phenomenal. um Also, julia packages are all 100 on github. um Well, maybe not 100, but definitely 99 on github and all of them have their own issue trackers on github as well.

T

So I would say that you know if you're engaging with the community there's the language, but then there's also all the packages and and a lot of people end up often working on the packages. One of the things we've done over the last few years is is actually made it easy for people to do things in packages rather than in core julia itself and and sort of uh make it easy to extend julie. And that's uh that's where we see a lot of discussion actually moving into packages uh going forward.

K

S

Thank you so much awesome.

B

S

B

S

Head on over to github discussions, uh viral is going to be there for the next 30 minutes to to continue answering your questions and you can post your questions at github satellite forward. Slash discussions see you later viral.

T

Thank you thanks for asking bye you on the discussions.

S

So so much good stuff so far, but there's still more to come um later on in the open source channel, we've got tips and tricks to github like a boss, as well as the state of ui, ux and open source, as well and later on, on the devops channel as well. uh You'll have sessions on ml ops and how github uses github to collaborate, and both channels will also see a closing session from our very own, manish sharma as well. So karen do I see a panel coming our way very soon, right.

M

Oh yes, yes, right, they're kind of like right, waiting to break open the doors and come in because it's it's gonna be really interesting. The next panel that we have is on something that I'm really passionate about. It's it's about crossing the border of languages in open source. You know india has so many languages, uh and you know when you combine that with open source. The impact that it can really make is is really really huge, uh so discuss on this.

M

We have three really amazing, panelists, uh one of them being our own hubbard from github, so we're going to have richard kumar, who is the senior director of software engineering here at github, and we are going to also have uh kailash nad, who is the cto of zeroda and also the creator of a few open source uh dictionaries in malayalam, canada and other languages, and we are also gonna have nikhil malhotra, who is the chief innovation officer of tech, mahindra and also the uh creator of the open source bhamil? That is the bharat markup language.

M

um So it's it's a really nice panel out over there uh we're gonna, discuss about you, know the role of languages. Regionalization and localization, uh you know in open source, so don't forget that they're gonna be around on discussions as well. So if you have any questions, drop them live or head over to getupsatellite.com discussions.

M

So without much delay. I'd like to welcome the panel richard kailash and nikhil, hey everyone.

A

V

Thank you karan and hello, everyone. I am richard kumar senior director for software engineering here at github, and I have an amazing panel of speakers with me who I'll introduce in just a minute.

V

So platforms like github, provide tools and capabilities for developers anywhere in the world to solve problems, learn from each other share their work and collaborate towards common goals. Today, technology is at the heart of everything, and access to technology is critical in helping us solve problems and to innovate in any area.

V

That said, if we think about it, uh the primary language in which developers are able to work today is english and access to majority of the technical content and programming frameworks assumes that one is well versed with the english language. So are we leaving out a vast majority of people who do not fit this mold?

V

If you really want to be able to reach every aspiring, developer and idea generator in india or other parts of the world which have so many different languages, important for us that we transcend the language boundary?

V

Luckily, we have with us today two very accomplished people who have been thinking about this problem and are leading innovation in this space.

V

So join me in welcoming nikhil malhotra, head of innovation at tech, mahindra and creator of the bharat markup language, which is an open source, markup language for india and kailash nad, a cto of zerodha, hi, kalash and creator of olam and lr, which are open source, regional language, dictionaries, um nikhil and kailash. We are eager to hear about you know what has what have been some of the motivating factors for you. uh How do you see this problem space and some of the ways that you have um uh started tackling this so nikhil?

V

Let's start with, you uh tell us more about how you would frame the problem that you're trying to address and also tell us a bit more about bharat markup language.

W

I'm sure richard um first of all, thank you so much to github um I I know this is an open forum in an open community and then taking it forward to this community is a is a great privilege as well. I think the problem's always been there, which are, if you, if you notice right, the 90 percent of us in india, speak vernacular, and we are, you know about. 10 percent of us are only well versed in english language.

W

My inspiration comes from. um You know, one of the mentorship that I was doing with the utterly incubation centers with you know a few of the kids, and this was a program called a student innovator program or student to society, and we had students from both urban and rural sectors and one of the you know the teams that one was a rural sector team from chhattisgarh.

W

These four students used to walk about 45 kilometers every day to go to school, and you know you call it scientific serendipity, you call it thought they dropped in red, amaranthus, green amaranthus and some kind of bajra on a piece of land, the wheat that grew out. They actually took juice out of it and that particular jew started solving a problem of malnutrition in that area. This project has been now under the eyes of unicef and people are looking at it.

W

So I was amazed by the ingenuity and of course there was a challenge to solve and these guys were solving it, but then they came to us for mentorship and we gave them mentorship regarding how can you put it into a packaged product? How can you put it into seeds, format etc, but one of the students asked me, sir.

W

I want to learn technology, but I don't know english, so that was possibly the starting point that got me thinking about a year back saying: should india not have the ability or should indian you know, indian kids not have the ability to quote something in their own language, and that was the origination point of bahamal or bharat markup language. Now what does brahmal do it's actually open source? It's available on bamal.org people can go and have a look at it.

W

But for the moment that we started off, we said that let kids is at least code html by simple, passing and transliteration in their own language. So we've given 12 languages for kids to code on it's hindi, and then we said that you know. Once we go through this phase, let kids try it out.

W

We will even go towards some more known languages like javascript, like you know, even scripting languages that we could do so that we could give that kind of a layer of abstraction to kids, saying that now you should be able to code in your own language. So that's basically and our attempt.

V

That's awesome, uh nikhil, it's great to see the the from where that you know motivation started and where you've been able to take it um uh wonderful to hear about that, um can kailash what were the motivating factors behind the regional language dictionaries that you have started. I know this has been an effort. That's been going on for some time, but would love to hear uh what kind of prompted you to do that and what you feel has been the impact or can continue to be the impact of some of this work.

X

So uh all in the first dictionary that came out uh came out 10 years ago, almost 11 years 2010, and it was born out of my personal frustrations, of not being able to find a decent digital malayalam dictionary.

X

That's what I speak and that pushed me down the rabbit hole of figuring out how the landscape of indian online dictionaries- and I realized uh it- was an abysmal landscape. It wasn't anything and the few online dictionaries that were available. They were riddled with ads. You know the quality wasn't great. uh The agenda was not really to run good dictionaries for the public. It was. I.

B

X

You know commerce, so I figured that there should be an open data, high quality dictionary that is freely accessible to everyone, not just people looking at definitions in a dictionary but researchers, students, anyone it should be open data, and I uh put together a dictionary with a few thousand words that I entered myself and I found a few data sets small little datasets floating around on the internet.

X

Unfortunately, unattributed I put everything uh scraped everything, everything together and built polum, it was an english malayalam dictionary and it went live in 2010 and today it's it's still, it's still available on and there's a mobile app. I think uh two to three million malayalam speakers use it every day, so uh that does prove that there is a great need for open access, open data, language dictionaries in all languages.

X

So that's the story of poland is a recent addition. When I completely randomly by happenstance, came across v krishna, who had spent 40 years building a dictionary which nobody really knew about, and he was gracious enough to open source it. So we took it the biggest authoritative, canada, english dictionary and it's it's called alar. Now it's available again open data directionally. So that's two big open data, regional dictionaries.

V

Nice, nice uh great to hear about that uh kailash and just kind of opening this up to both of you. You know uh what have been some of the challenges that uh you know you all have faced as you've sort of embarked on these journeys, and um you know how have you uh you know what tools or approaches have you used to help you make progress? You know.

W

So I I'll take that question richard. I think uh the one of the biggest challenges is, of course, lack of awareness, and I think I would be very, very open, saying that the moment you get into a coding world, there is a kind of a predistant or a kind of a predisposed notion that these are the languages, and this is something that we've got to do, and that is something that I think programs like github we going on the open source channel would really help us.

W

Take it forward number one number: two: um a lot of people are not aware about the strengths of what local regional languages have you know and and and have been produced as well. Like kellage really mentioned that malayalam there's a there's, a very, very valid dictionary that is now made. um You know my research started about three years back on sanskrit as well, and- um and I found out that there's so much to talk about natural language processing right over there in that language, even though it may not be spoken very, you know very openly.

W

It's only spoken in small parts and small sectors, but sanskrit can give us that ability to understand the root of language as well as how the natural language processing systems could take place. um So you know if, if there is awareness, then there is, there is a sort of you know the people do understand. What's the strength, what are we doing for it? I think number one um we. I continue.

W

To talk about it in all forms letting people know you know, I continue to say. I continue to talk about. What's going on with the language, how is sunscreen basically going on? uh What should be the next step? Number two is I've got some I've got a very, very good team that is also now taking this language out to to young, kids and and even sectors um yeah.

W

Very interestingly, I uh in my lab in makers lab there is a gentleman who was earlier, an uber driver who actually learned over by the dent of his hard work or whatever python c c, plus, plus, etc, and he joined the lab now. Kovitt pushed him to the to the villages he's now in one of the villages in maharashtra, so he's taken upon himself. His name is satish he's taken upon himself. He brings in students from about 30 40, odd schools in the rural sector, and he starts teaching them harmal. He starts teaching them.

W

You know the coding language itself, so that has been more of a generic effort that we've been doing to raise that awareness. There are, of course, other channels that we are utilizing as marketing etc, but uh awareness is one of the biggest things that we feel is the challenge at this point in time got it.

V

How about you, kalash.

X

I I completely agree and that awareness also translates to a significant lack of academic and computing language resources, and I've cited this example before building. If you want to do, nobody thinks twice about english string search, you know you do control f, you put your string in and you know uh search happens.

X

There are many different algorithms to do english string, search and that's that's the case for latin languages, but search for indic languages is an understudied research area and without academic research you can't really build tools that people can use so even to to get. You know like simple phonetic, search working for the dictionaries uh I figured you know there was nothing available, so there was a lot of trial and error uh in a very non-academic sense to get that fundamental string search to work. Things have improved quite a bit over the last 10 years.

X

Large. There are large companies who offer free computing tools, but it's definitely awareness and I think the site, one of the side effects of language input becoming prevalent across mobile devices everywhere is. I think people assume that the indic language problem is solved because you can read your language on the phone. You can write your language on the keyboard, but in fact the fact that language keyboards are now standard on all indian operating systems was in fact a community push that happened five six years ago.

X

If it wasn't for that, you know, uh like a force open source group pushing for that to be established. Wasn't for that? I don't think we'd have standard input tools, so there's an acute lack of awareness, especially among I think.

X

Amongst engineering folks also people assume the language problem is solved, but when it comes to ending languages, we haven't even scratched the surface.

V

Makes sense, I think what I'm hearing from you is that you know there have been some recent pushes, which have, I think, which have helped the end.

V

Consumers to be able to, um you know, see um a lot of content or apps in their language of choice, but when it comes to really enabling the creators right we're still, we still have a long way to go because of the lack of the content, the lack of the tools frameworks, uh which primarily uh work with english today, and so I think, the work that both of you are doing is is really going to help, and uh you know take us a little bit forward on that path, and uh you talked about uh you know technical challenges, around string, search and things like that and- and both of you will probably have insights into this.

V

So how does that, like you know, is that um you know, especially as you worked on two different languages: dictionaries um are there patterns that that can scale out to other languages? Is it every time you're adding support for a new language? Are you kind of? Are we starting from scratch? uh You know how? Maybe you can give us a little insight into um you know how how much effort is involved and what are some of the ways that people could contribute. uh You know along this effort.

W

No, absolutely richard, I think digital content and content remains a challenge, as kellogg rightly mentioned, and I think my area has been to find the middle layer for sanskrit as well and I'm finding some patterns. um You know wherever we as of languages across the across the subcontinent. There are different patterns, but then again, these patterns need to be adjusted to that specific language.

W

Now, um just to give you an example, a lot of people and- and that's where, if I may talk to the community in terms of what has been the genius that panini was- and I think panami's genius was to understand- where exactly is information encoded in our language, so um how much of that information is encoded and what is there exactly? Which needs to be grabbed up?

W

If you want to talk about that language, now, considering simple, simple words, like the bands going to the village, I think all of us, a lot of you are viewers, would know that in sanskrit it translates to purusha gramma.

W

The problem is that if I replace the order of the words in english, for example, village go man the meaning completely changes in sanskrit because of inflection the meaning remains the same. So what and panani's genius was to actually say where exactly is this information included? It's not in the purusha? It's not in the grammar, it's actually in the t of gachati, where exactly it makes that verb available.

W

This specific construct- and this specific rule applies to almost all sectors of indict languages. They may be different here and there, but if you look at the pattern in which we speak and the way the languages have been handed over, this particular pattern applies to all. There are certain other patterns which don't, but the research has been on in different sectors.

W

I've seen colleges, we've been we've seen, academia work on it, we've seen researchers work on it, but there are some very, very good patterns to help us in natural language processing which we are finding within indic languages, and that's been a revelation. So I think, if more and more people join this community of open source, they would find that these patterns would also help them solve some of the challenges for natural language processing in english as well. So that's what we're finding out.

V

Very interesting.

X

B

X

Indeed, languages share uh so yeah. Indeed, languages share quite a bit in common and research research developed for one language. I think there's a significant overlap with what you could use for other languages. To cite a concrete example for the malayalam dictionary to work I had to, I ended up putting metaphor, which is an english phonetic. Hashing algorithm, really simple. You uh you take a word elephant apple, it'll encode it to you, know two or three letters like apl or ebnt.

X

So the idea is that similar sounding words will all hatch to the same set of strengths.

X

It's called metaphor: it's available in the public domain, so that was quoted from malayalam and uh that's how phonetic search on that malayalam dictionary works, but because the phonetic uh nature of uh kannada is extremely similar, and uh for that matter you know in the gujarati etc. This was easily voted overnight to canada and we certainly have canada from search on color. So a lot of things that we developed for one indict language can be outright applied with very minor tweaks and exceptions for many other languages.

X

The and, like you said, uh I wanted to add one thing to what you said earlier. There is widespread availability of tools like, for example, there is google translate for almost all major index languages today and there's google input tools, but these are all, unfortunately, proprietary, how these tools work. We don't know what are the algorithms that power these tools? We don't know what are the data since they go into it. We don't know so if that tool disappears one day, millions of users will be handicapped.

X

That's why it's important for language related research and data to all come out in the public domain and be open source.

V

Yeah makes sense, makes sense, and so uh how would uh you uh if I asked both of you, that you know if our um open source community would want to contribute on this front, uh both uh specifically on your projects as well? As uh you know, how should they be keeping all of this in mind in their own efforts? You know any any advice for the folks listening.

X

In I think uh I'll go first, so uh all the all the components that have gone into building these dictionaries- you know english.

X

The data sets themselves part of speed, stacked and the software that runs the website, this the phonetic, algorithms and power source. These are all open, source and they're all available on github. So for someone wanting to start to do simple things, especially surrounding open data and dictionaries, they could tinker with. You know uh the data they could think of with the code. They could even use some of these tools to build their own little local dictionaries. For example, you could very easily with minimal effort, build a hindi technical word dictionary.

X

It could be 5, 000 or 10 000 words so or even a couple thousand words, but you know technical. You know scientific mathematical world, so even small efforts like that building niche open data dictionaries for different languages would be a great start. So there are many things one could do without actually getting into proper linguistic research.

B

W

I agree with, I think I think, I'm sorry just to just to add to one point over here. I think one of the things is for people to actually go and use these projects. I think download them for them find out what are some of the things that is going on and maybe add on top of it and and figure out.

W

What's the base value at what that is being created, and I think the moment you add more uh the moment- you learn more as well understanding what's going on and you would go into your own research, small little research on the side as well. Yeah.

V

Makes sense and uh nikhil one thing I wanted to touch upon was that as you as we think about um making uh you know, uh programming uh or technology more accessible to non-english speakers, uh do we see it, as uh you know, like what you're trying to do with bharma, where you're, enabling them to use the language that they're familiar with, and then I guess translating um so that the current tools that work with english can continue to work? um Do you see it continuing in that form? Do you see us? Do you see this?

V

Do you see other strategies where we use no code and low code kind of things and more natural language processing which does code generation uh or are there even other strategies to you know, make this more accessible.

W

Now, you're absolutely right richard, I think it's a mixture of both it's both translation, it's port transliteration, but it's also about looking at natural language processing, but I think my vision. The vision that I carry within india is that at the end of the day on silicon, it's just so what we've got to do is basically do the layer and change that entire layer, so, whether it's the layer of compilers, it's the layer of assembler, it's even the layer of the os that should essentially be changed to understand the language in its most prime form.

W

If that happens, you can put that as an os addendum on anything. It could be a version of linux, it could be freebsd or whatever, but that will really change the impact of a language and the usage of that language as well. So while we all say that c is the mother or the foundation of all in you know all programming languages.

W

Could we develop another language which is like c, but it's basically based out of all of these regional language structures as well? Could it have a completely different structure? Could it have a completely different database structure as well? So I think those components is something which is basically driving this vision. This work is very, very primitive. What you know and I would like to call my work, I'm I'm not privy to actually say what kalash is doing, but it's very, very primitive.

W

It's actually scratching the surface, but the open source community now has the ability to actually take this forward and bring it out in a much more bigger and brighter way. um You know change the layers, the osi layers, as you call it, and that will really produce the change for the index sector as well.

P

V

Sense and uh what do both of you think in terms of you know the overall role that open source uh plays uh in regards to computer literacy in india.

X

X

As I said earlier, they're having considerable uh interventions and activism and pushes from the open source language computing community all volunteer based in india, which we don't really see on the surface and thanks to which, by most indict languages today are properly standardized unicode.

X

There are bi standards managing, but all should have uh indic languages. So the open source communities are what really gave us the indic digital. You know computing language revolution, we don't see it because we only interface with uh the consumer devices, and you know consumer software. So I I would say that uh the question: how can open source help uh his mood in the face of open source is what really gave us? You know this.

X

This indic languages uh in the digital form to begin with and going forward. Also, as I said, you know, could be simple. Algorithms could be open. Data sets all these building blocks. They have to be in the public domain for true innovation and accessibility to happen. You can't really build if you, if you end up building a great language translation model and you keep it proprietary.

X

You are holding language hostage from a large part of the population and and everything is going online, especially critical government public services. So it's important that all these critical public services that are going online are accessible in local languages too. For that you need great, you know publicly accessible, open building blocks, so foss is uh highly intertwined and ingrained in this whole. You know moment.

V

Absolutely absolutely nikhil anything you'd like to add there.

W

No, no, I think I I think kalash has pretty much covered everything. I think the only the um and I think the reason is for everyone to see. I think the reason we are having and discussing this today on a github satellite is the reason enough for us to say that this is the power of open source community and that power of open source community can actually be fettered in yeah. So.

V

Makes sense- and I think uh just uh touching back on the example that you started with nikhil at the beginning of our discussion, where you know you talked about these kids, who had really come upon this great idea and uh that helped solved malnutrition and really for them to take that idea, and you know, reach a lot more people and make a bigger impact.

V

Really it's technology, that's going to hold them back if they don't get access to it, and so uh you know that was a great way to see that if we really want to reach out to all those uh folks um that are coming up with these innovative ideas and really empower them uh raising that awareness amongst uh you know both open source community corporations.

V

Everyone has to come together and see what we all can do in this area to really truly make this technology accessible to everyone. um So it's been uh wonderful talking to both of you. uh It's really um fascinating to hear about the work that you all have been doing. uh I'm very very excited about the possibilities that are ahead of us and uh I hope that both at github and all uh you know our amazing uh open source community that we're gonna take away some uh important.

V

uh You know um thoughts back from this and you know, as we do, our own work uh we'll be looking at how we can make everything that we do more accessible and empower more people across the world. Thank you. Both. It's been a pleasure talking to you today.

W

Thank you. Thank you. Thank you. Thank you.

M

Oh hello and welcome back I'm just uh you know getting over from uh all of the celebration of holy and all of the colors. It's it's really nice.

M

You know so uh do join in with us as well, but uh before that you know this, this session was really really nice and I was I was watching it and it's so really um amazing that uh how we are able to bring in all of these different languages, um you know come in and help contribute to open source, and you know really make open source accessible to a whole lot of other people for whom it might not already be.

M

So um don't forget that you know richard kailash and nikhil will be around on get up discussions. So if you have any questions head on over to github satellite.com discussions, that's what it is right here, uh where you can chat with them and have a conversation on anything that you would want to know about.

M

So um all right! So before that you know in case, you have anything that you want to share with us what you learned or uh just you know, how's it going what have been your favorite moments, etc. Do tweet out to us on hashtag, github, satellite and tag us using aggrebinder. This there's quite some good conversations happening on twitter, github discussions, etc and, uh oh, hey.

E

M

You're here hey I'm back well, how's it how's it going. You know, yeah, I'm having I'm having I'm having quite a good celebration idea. You can. You can see a lot of the colors that folks have folks are put in, and you know just just going a little bit uh safe and then it's all confetti all over pop. But it's yeah.

S

I see it everywhere, yeah I'm starting to get it on my face as well. Now it's a lot of fun. It's a lot of fun, very excited.

M

Nice, nice all right, but let's, let's get going, uh you know so uh right now. Next, uh we have uh you better, don't blink anisha because well, because you'll get colors in your eyes, but also because it's a lightning talk, uh which means uh you know it's gonna, be a super quick session on ai for web and introduction to tensorflow.js.

M

uh So for this, oh yes, wow! You have a nice emoji out there all right! So for this we have shivai lamba, who is a production engineer at uh layer, 5 who's going to be giving an introduction to tensorflow.js.

M

So remember that you know if you have any questions head on over to get satellite dot com, slash discussions- and you know, while watching anisha- and I will have a little more of this celebration and colors going on as well. So all right see you all folks soon and then welcome shiva.

M

Y

Everyone who are watching uh this lighting talk I'm so I am currently a tensorflow js, sig member and working group member as well, and I was also previously a google tensorflow code and inventor and I'm currently also a production engineer at layer 5.. So the talk of my uh lightning presentation is machine learning for the web and introduction to tensorflow.js.

Y

So without wasting further ado, let's get started. The first question is you know people ask, is why machine learning in javascript so for the one of the first reasons that we want to first introduce is what exactly is tensorflow. So tensorflow is a free and open source library that is created by the team at google and is used for a lot of different kind of machine learning applications, particularly in deep learning and neural networks. And the question is that why introduce machine learning in javascript at the same time?

Y

So javascript actually has a lot of different unique selling points when it comes to consideration of the type language because of its lower latency about user privacy and then also writing code in just one single language. That is using tensorflow.js right. So uh and again, one of the biggest reasons is that we can use machine learning with javascript in any kind of an environment.

Y

Javascript is the world's most popular programming language and it finds its use in the browsers and the servers in the desktops in mobile computing devices, and also in iot, that is internet of things devices and to sort of note down a few examples of one of the most popular browsers that we use, like chrome, safari, mozilla or uh running your code on the server side using node.js or having like a mobile based application uh built using a cross-platform platform.

Y

Like react native or having a desktop based uh development environment like electron js or using node.js with raspberry pi, to create really wonderful iot based devices. Javascript has support for all of these different spectrum of devices, and you can introduce machine learning with javascript now, one of the biggest reasons why we want to do that is for creative professionals, who are only learning javascript.

Y

It can be very difficult for them to probably learn another type of language like python and introduce machine learning models in a cross-platform application, or that uses both python and also uses javascript so because of the versatility of javascript.

Y

It finds great use to include machine learning in all of these different kind of devices and developer experiences at the same time, and the biggest fundamental of the tensorflow.js library is that we can either use the existing models that are pre-built or we can create our own, or we can also use the concept of transfer learning to retrain.

Y

Our existing data sets with these models. At the same time and coming on to uh you know, because of the versatility of javascript, we can use uh javascript and machine learning in all of the other different type of type of applications that can be used with javascript.

Y

So that includes things like augmented reality or, let's say, gesture, based interactions or sound recognition, and all of these different types of applications that we build in uh the web platforms can be coupled with tensorflows to create machine learning experiences that are going to uh blow your mind with some of the examples that we'll be showing you so the first category of uh the such kind of models are the pre-trained models. Now these are completely easy to use.

Y

Javascript classes that have been built and are completely open sourced are can be used with a single line of code uh by embedding that to your javascript based project at the same time, and there are many situations when you might not need like to use uh or create like a specific model, and you can directly just use some of the previous models for small applications that we're trying to build and a few examples of those include things like image: classification, object, detection body segmentation, pose estimation, and also things related to nlp, like text toxicity or, for example, let's say speech commands all of those come in handy and to visit these models, you can simply go to tensorflow.org js, slash models and you'll find the github links for all of these different models.

Y

At the same time now, a few examples of these include, uh for example, object recognition that is one of the most fundamental deep learning or machine learning based uh projects that can be taken up and koch isd, which is a really popular uh object, uh recognition model uh also available in tensorflow.js, and it can be trained up to 90 different classes.

Y

So, as you can see in this uh picture that uh we have a a picture of two dogs and it can actually create bounding boxes on these dogs images of these dogs and give a really great confidence at the same time to the pixels. So it's really great in doing it quick and also is highly accurate. At the same time now there's another example of a face.

Y

Mesh now face mesh is a model that is just three megabytes in size and it actually recognizes over 468 different landmarks on your face and uh again, as you can see that it's really popular and being used right now in production in uh in places like l'oreal, which you can see on the right-hand side uh being used in uh production environments and uh being actually used in products that are ready to go and ready to ship as and when required. Then there's another uh model that we have.

Y

uh That, basically, is the body segmentation that can basically distinguish 24 different body areas in human bodies, and it can also do that in real time and also across multiple different bodies. So there's this need. It doesn't need to be just one single body, as you can see in this video. There are three different individuals whose bodies are being segmented as compared to the background in real time and again without any performance overheads.

Y

At all. Now, with a bit of creativity, we can emulate a lot of different superpowers using tensorflow.js at the same time and just to sort of show you examples of cross uh development applications over here. There's a person who's from a community. A tensorflow js community in the united states has created this amazing laser application, using webgl, shaders and with tensorflow.js, and these are just some of the examples that you know we can think of to create some kind of unique creative applications.

Y

Then there is a jason mays who is a tensorflow.js developer advocate at google, is using a combination of webrtc, a frame that is uh augmented reality 3js and also tensorflow.js to teleport himself to another environment by using a combination of all of these different three uh different uh technologies and combining them very seamlessly to create really fun applications.

Y

Now, there's another one that was created by jason was a real-time clothing size estimation that uses the body segmentation model and can provide you the details of your body size by this scanning, your entire body and within the next 10-15 minutes. It can provide you a very quick uh body, size estimation for your, so that you, this could be used, probably uh in uh sites like amazon or other kind of uh real world applications or when it comes to any kind of estimation that needs so not just related to the closing size.

Y

At the same time now, the idea is that we can combine different types of tech with uh the tensorflow.js and again. This shows a really great example where basically, we are using web xr. That is uh the mixed reality and we are also using webgl to create this 3d, uh rendering of an augmented reality uh application where, for example, which sort of scans an image and creates a real-world model of an augmented reality model of this statue right.

Y

So the idea is that we can combine different types of technologies uh that are supported in web very seamlessly and again, the integration is usually very simple. At the same time now, the second part is using transfer learning so basically retraining, some of the existing models that we have to work with your own data, to sort of customize those uh models to your own data, to provide you better accuracy and better functionality.

Y

At the same time, so transfer learning is essentially taking an existing model and use it to basically uh apply to similar kind of problems or in some kind of domain such as probably like, you know like say, recognizing a cat instead of a dog right. So again, uh there are two different ways in which you can use the transfer learning. One of the most easiest ones is teachable machines.

Y

So basically, this is super, easy way to actually use transfer learning and it's a completely web-based platform that allows you to either do things like object, recognition, post estimations or things on audio. So it's very simple: uh you just take an input.

Y

You provide uh classes and the examples of those using video or audio or images, and then you simply just put it on train and, as you can see, that it provides you uh in real time uh the uh predictions and that predictions can also be exported and can be used with your web application, either using uh the javascript models or using, uh let's say, a tensorflow lite and any other kind of different tensorflow embeddings that we can think of.

Y

And if your data is in gigabytes or if you want to create a production ready model, we can also use the cloud automl that basically lets you train custom engine models, and if you have data in more than gigabytes in size, it can simply just use this and we can deploy that directly to tensorflow.js once we deploy it. It creates basically the small.json file that essentially has uh the entire uh model of how it works, and we can use uh that simply with our application.

Y

At the same time- and this is a very small example of a code- so in the first two lines you see is what we have imported the tensorflow.js library and also the automl library. uh In this third line, you see, we have simply just uh taken an image of a daisy that is a flower and we have just given uh it the id of daisy for the image and then the script that you see is not more than five lines in length and what we do in this.

Y

uh What we do in this is that we have created an async function, because uh the machine learning models take some time to load, so we would want to make the predictions only after the model has been loaded. So what we do is that we use an async function or an asynchronous function in javascript to first load our image classification model from our model.json file. That has the characteristics or basically the dependencies of our machine learning model. And then we just uh use the const image to get the document by id for our flower.

Y

So we can get that particular image id and then what we do is that we simply run the predictions uh using this and we use the classify to basically classify okay. What type of flower is it, so it will basically tell you what is uh the classification or the label of the image right and the probably the last one and the most powerful one? Is writing your own code in tensorflow.js, so tensorflow.js basically provides you two different types of apis.

Y

One is the layers api that is built similar to how keras works on top of tensorflow, and that allows you to use some high level functions, but we also have the ops api, or that is the lower level api. Where you can also, uh you know, change the mathematical functions like the linear algebra uh functions in your code. That provides you a lot more flexibility and functionality when it comes to changing or writing your own code. Now this sort of gives you the architecture of what we have discussed so far.

Y

So the top level is the pre-built models. The next one is leds api, that's similar to how kira's has been built. And finally, we have at the most low level, the ops api, and this basically allows it to run either on the client side or on the server side or the client side with basically is the interaction with the browser.

Y

We can have the support for the cpu or webgl, that is web, accelerated, graphics or we have webassembly that use as the backend for powering the machine learning models in the client side, and we also have the server side that basically runs in node.js, that is, the tensorflow cpu or the tensorflow gpu, basically using the cuda cores and uh the uh same power that python based models can be using at the same time and as you can see that we can either use some of the pre-built models that are there uh in tensorflow.

Y

So if you have a python based model, we can use the tensorflow saved model to be directly imported in the node.js in the server side, or we can use the tfts converter that basically converts a machine learning model written in python to a one written in uh javascript and again, as you can see from the model that, uh from the model inference.

Y

Basically, this is a mobile net model that we have and, as you can see, the difference between the performance of python based model and like a javascript based model is very minuscule, and the difference is not that much right and uh again. This shows another example of an uh of like um an nlp based model, that is the distilbert model and, as you can see that this is actually better as compared to the one that we see in python now, there are also five different.

Y

You know super uh powers that you get with the client side, so one of the biggest one is privacy. You get lower latency because we're not having a dedicated server. We get a lower cost and again interactivity.

Y

At the same time, and also we, if you're using it on the server side, then you basically get the power of javascript just in time compiler, or we can also just write in this one particular language and of course we can run models that are much more powerful as compared to the client side because of the dedicated cpu and gpu power that comes with uh node.js. So these are some of the uh server-side benefits at the same time now just to uh share some of the resources.

Y

uh Basically, you can visit all of these different links, the website, tensorflow.org js, and the models on testflow.org models and again you can visit all these different links to get started with tensorflow.js at the same time and uh you can join the community by using a hashtag made with this, and you can follow this on twitter and on uh links like linkedin and again. uh Thank you so much for uh staying in touch, and you can follow me on these links to get started again.

Y

Thank you so much for uh seeing, and I hope that you, like the presentation.

M

Wow that was literally literally a lightning talk. You know I I had to I had to just like. Yes all right, I got it now. You know that was that was really nice. One and um uh folks, don't forget that in case you have any questions for shivay. You can head over to getupsatellite.com discussions where you can find him answer any of the questions that you might have around tfjs. You know. So what do you think anisha outside of all of these colors? You know, I'm really liking it. You know it's it's!

M

It's a nice celebration, you you have some nice stuff going on over there too.

S

M

All right, so what do we have coming up next to nisha? You know we had one lightning talk back to it's tensorflow.js. What's next.

S

Yes, so you know what we have another second lightning tool coming up, which is the world's most elaborate ci workflow for an angular library and um we'll have lars jarrett brink nilsson, who is a front-end architect um at systemate, as um he's also a tech, writer speaker and a microsoft, mvp wow? That's that's a lot of stuff that he's involved in which is fantastic and don't forget happening over on the devops channel. Right now is the workflow dispatch automation for the past present and future as well.

S

So you don't want to miss that, but you know you want to hang around in our open source channel with myself, anisha and karen, um where we've got loads, more things coming up, um so stay tuned for all of that stuff as well. So last, are you there take it away, hey lars.

Z

Hello, what a lovely day I'm lars brink from systemmate and denmark, and today I'm going to be sharing how we applied github actions to a library, I'm maintaining.

Z

So this is about a library called lumberjack and let's see a few features of that library, it's a logging library for angular. It has six configurable logging levels, very robust error handling and it has a plugin based architecture.

Z

As you see, on the right hand, side of the screen, your application is communicating with the lumberjack api and behind that is one or more log drivers, and to demonstrate that plug-in architecture built into the library has two common drivers. A browser console driver that will display the logs in the browser console and an http log driver that will use your backend with a simple interface, and the nice thing is that the community provides more drivers, for example, for azure application, insights and google firestore, and you can even build your own.

Z

That fits your project which is relatively straightforward, and the library also comes with what's known as angular schematics, which is used for code generation and code mods and, most importantly, for today's talk, it has verified cross-version, angular compatibility. That means that we support multiple major and minor versions of angular from one major version of lumberjack version. Two point x. Right now, a bit more about lumberjack, we have six d6 log levels and angle: has the concept of development mode and production mode in development mode?

Z

All the log levels will be active by default in production mode. The debug and trace levels are disabled. Of course this can be overridden using configuration even to the point that you can configure it on the log driver itself different from the other, lock drivers.

Z

So we wanted this cross cross-version compatibility with angular type script and related dependencies, um so we looked for github actions to solve this problem. This is the problem we're trying to solve. As you can see here, in the right hand, side we have a compatibility matrix between angular cli, angular, node.js and typescript, there's eight different versions of angular, supporting six versions of typescript, two major node.js versions and that's 30 possible combination of dependencies.

Z

So how could we solve this? Maybe a project per combination with a demo application, maybe some unit integration or end-to-end test.

Z

This was an initial stable version of our library and we thought this could quickly become unmaintainable, because several versions of angle are released each year.

Z

So the solution was we wanted to use the angular cli workspace structure. You see a part of our repo here on the right hand, side, and we wanted a single source code based solution. So you can see we have the lumberjack app is a demo app. It has an end to end test suite in the next folder.

Z

It has a schematics target application I'll get back to that, um because it also has an end-to-end test suite and in the bottom we see there's a bunch of tools that some node.js scripts integrating our different tool chain in our ci workflow.

Z

And finally, so we have the single source code base solution and we'll have a github actions. Job run per combination of dependencies.

Z

So we have in total, 50 jobs being run per ci run through 49 of them are github actions. The last one is run in sonar cloud. We have between 10 and 30 jobs run in parallel we're an open source project, so we get basically unlimited github action minutes from github. So thank you very much for that, or this would not even have been possible.

Z

The whole workflow takes around six minutes in total, despite 49 jobs. At this point um so yeah, that's that's pretty neat setup and we spent a few months perfecting this setup. So that's really nice.

Z

The different jobs we see the build job is the first one. It runs a production library build using the latest versions of all the tools and angle and so on, and then it uploads a build artifact with that package, which is exactly the package that will later be published to npm the lint job runs formatting checks and checks, the lensing rules. It also uses the latest versions of tools, the tool chain and all the dependencies.

Z

The sonar job generates test coverage and lint reports. Then it uploads them to sonar cloud for further processing and, in the right hand, side. We see that the jobs that depend on the build job and we'll get back to that in a second.

Z

The first job that doesn't depend on the build job is the lib or library job. It uses the latest major node.js version, supported by angular version 12., and it has these all these eight versions of angular, which combined have fif five versions of typescript supported, so we'll have um a ci run for this job per combination of dependencies.

Z

As you can see, in the right hand, side it's actually eight runs in total they're called matrix lags the one you saw on the right hand side before so, for each of those runs, the setup process is that it first installs the angular version specified by the ci matrix.

Z

Then it installs the typescript version and other related dependencies with that setup. Out of the way now, we can run the main content of this job, which is run the unit and integration test for our development projects, which are test utilities internally. For the library, then this the unit and integration test for the library itself and finally, we even have unit and integration test for the angular schematics that are used for code generation and code mods.

Z

The next job is the app job. This one does depend on the build job. It has a similar range, but it adds another major version of node.js, because some of these angular versions support node version 10 as well. So now we have more matrix legs.

Z

We have 16 in total, so it adds another setup step, install the version of node specified by the ci matrix. It has some additional setup steps here because now we're getting to. We want to test the library from a real application.

Z

So typescript has this concept of path, mappings, which allows code to import code using a package name, but the code might be in the same repo if you set up the path mappings- and we have that in the repo. But we want to delete that so that the next step step here makes sense, so we're downloading that build artifact from the build job.

Z

That's the package that will ship to npm, removing it into node modules, folder, and the reason for that is this next step, the angular compatibility compiler, it's a bit of a temporary solution, because angular is currently migrating from the previous generation. Compiler called view engine to the current generation, angular compiler called ivy and right now we're in a situation where angular libraries are compiled with the previous generation.

Z

So whenever an application installs an angular library, it will have to run it through the ngcc compiler to up level it to iv instructions.

Z

So we want to make sure we support that tool as well as long as it's necessary.

Z

With all of this set up out of the way now we can run the demo applications unit and integration tests, and we will also do do a production build of that application. So we have an end to end on the unit and integration test level. We have an end-to-end setup, which is as close as you get to real application.

Z

The next job is the end-to-end testing job. We see the same setup as before, only one version of node, um but that is eight matrix, lags in total and we have exactly the same setup as the previous job, but now we're running end-to-end tests using the tool called protractor that will use a real browser. In this case we install the latest version of google chrome. Then we run all the end-to-end tests for our demo application using the real package bundle.

Z

The final job we have is the schematics and time testing job and we support almost every version here in this setup. There is one detail missing about angular 9.0 because of the jest issue with typescript, but we feel pretty conf, confident that that we support even version 9.0 since we we are testing 9.1 in this job. We have the same setup as the two previous jobs, but now we run the end-to-end test for the schematics and schematics are used through the command line.

Z

So we will have a freshly generated angular project, the target project for schematics, and then we run from the command line.

Z

It's called ng add it adds the package to the application, and then it registers the library with um with angular and sets up basic configuration and in the future, we'll we're working on some tools for generating code for using the library, for example, to add your own log driver.

Z

So we're doing this for every major and minor version of angular and typescript supported a few more details about the ci matrix workflow.

Z

You have probably seen this setup node action from github before and you might only have passed it a single version, but here we have the ci matrix and github actions. So we have two versions of node, so there's there will be two jobs and each of them will specify version of node that we interpolate using matrix.node version.

Z

So we wanted a similar setup for angular. So now we have two times: eight uh 16 matrix lags in this job and we passed to angular version parameter. We passed the matrix.angular version and interpolated, so that comes from the ci matrix run.

Z

But if you look closely at this action, it's called ng worker, slash angle versions, action, it's a package or a github action. We created specifically for this library, but as we'll see in a minute there's it's meant to be reused across any angular library for for ci setup. So that's pretty nice.

Z

So we have it published on the github actions marketplace.

Z

What it does is it accepts this input, parameter of the angular version and here's an example of a list parameter.

Z

It then goes and replaces more than 20, angular, typescript and related dependencies in package.json and each combination of dependencies has been verified by us to still be in a working state, because we all know that over time, dependencies and especially sub dependencies, they degrade and sometimes break, but we we have found a combination of dependencies that actually working and we're using that in this library.

Z

So, to sum up, the workflow we have achieved is this: we have this simple single source code based solution.

Z

We have this purpose-built, github action that can be reused and we have already gotten interest from two very popular angular libraries. So we look forward to collaborating with them for them to use our github action. We have a fast parallelized, github actions, workflow and each combination of dependencies is run in isolation, both both for our unit and integration test. Our end to end test, and even the end-to-end test for the angular schematics, so working with cross-version compatibility is suddenly easy.

Z

We can release features and patches across eight angular versions, six typescript versions and two major nodejs versions from a single source code base and every time we manage to use backwards, incompatible, api and syntax. It's immediately detected well, not locally, but as soon as you pass it to you, push it to the ci within six minutes. You'll know whether it's compatible with all the different versions and if it's not you'll, know exactly which combination of dependencies has the issue and you're even technically able to reproduce that using the github action locally.

Z

So we're adding verified support for a new version of angle and typescript and node.js is usually as simple as adding a value to a list of parameters in our ci workflow.

Z

And let me tell you this is an amazing workflow as a library maintainer. Thank you very much for listening. This is my twitter handle and the url for the library lumberjack see you all later.

M

Wow that was really nice anisha and look at you all full colorful wow, that's that's nice. You know it looks like you're also having a nice celebration and, oh, my god, what am I seeing? I'm I'm seeing mona. I am seeing hubot and everyone else also decked up full fully colorful out over there. You know, that's that's a nice celebration. You're having out there.

S

And you as well look how colorful you're looking that is fantastic.

M

Awesome, you know it is also. You know this. This session was really nice. You know uh because it showed you how much how many ci jobs they're running, and you know how efficiently they're kind of like managing for lumber track. That's that's really interesting, so remember that lars is going to be on uh get up discussions. So if you have any questions head on over to getupsatellite.com discussions, uh where you can ask him any questions and then you know have it answered also interact with the community out over there.

M

So also remember, you are right here in the open source channel where we are all colorful and you know almost in the mood of celebrating holi, um but there is also the devops channel, which is happening right here in parallel, uh where our good friends divine mohit are hosting sessions on devops, um on uh secure development, developer experience and other things etc.

M

All right, so you know I'm I'm really uh anisha excited about our about our next session, because it is again one of our very own teammates right, anisha.

S

M

S

Am so excited, do you want to introduce her because I I just can't wait? Oh yes,.

M

Oh yes, you know- and this is one of my previous co-hosts uh for universe- 2020 and uh you know she is. She is uh oh there we are all right. uh Michelle mandering, aka, mish manners, she's, also a really big string. Streamer. You should check her out on twitter as well and she's, also like really well known as the hackathon queen uh and she's a developer community manager here at uh get her and she's gonna be telling you how to get up like a boss.

M

You know I could I feel like I could wear one of those. You know sunglasses and uh get up like a boss, but anyway, for that we are gonna, have bish banners. Don't forget. She's gonna be hanging around on discussions as well later on. So if you have any questions, put them on we're gonna ask live as well with that alicia. Let's add one more person from the devil team out over here: mish manners, hamesh.

B

AA

So amazing, to have that wonderful uh presentation that you gave me uh what a great introduction, like, oh I'm, down here in a little screen, um but uh if you do check out my setup, if it doesn't happen to go full screen, um chrono nisha did mention a bit of a streamer there's some cool things. In the background I also loved anisha's little heart, which was so cool. So thank you anisha um for the heart um and thank you both for that fantastic introduction. It was, it was really cool.

AA

It was so fun um hosting universe last year and I'm really excited to be back this time, uh giving you a talk for satellite on how to github like boss. uh So without further ado, let's jump right in um so as quran mentioned, I am the hackathon queen or known as the hackathon queen, and both karen and nisha did such an amazing job.

AA

Introducing me and talking about what I do so I'm gonna leave most of that there, but they did say I am github, I'm on the developer relations team with karan indonesia, and we get to have so much amazing fun and do awesome talks like this to awesome people like you who are all listening. So thanks. So much for being here.

AA

As I mentioned, my talk is called github like a boss and it's basically a whole bunch of top tips on using github making it work really well for you and how to make github amazing. Now it's already really cool. So here's how to do it now we could be here for hours talking about top tips on how to use github navigate it make it work better for you, but we've only got 20 minutes.

AA

So what I've done is I've broken up these top tips into four parts, so the first one is personalization, we'll talk about how you can make it hard work, a little bit better for you. Next one is collaboration: how to work really well with github for your team, whether that's a developer, focus or developer specific team, or even how to work with non-developers as well.

AA

We're going to talk about a little bit about the way you work and how to use github in the various different forms for your work and then, obviously this is the open source channel. So we are going to be talking about some top tips on using github for open source. I mentioned: we've only got 20 minutes, so there's a lot more top tips than here.

AA

So if there's a top tip that you really want to hear make sure you put it in the discussions and I'll try and answer at the end, all right so personalization personalization is something that people love think about. When you create a social media profile for the first time, people love to personalize it. You know they add a photo. You might add where you're from you might add a few different things about yourself. Even when you're building lego lots of people like to personalize the way they do. This, I'm a big fan of lego.

AA

um So I had to throw some lego into this talk somewhere, but, like you can customize a lego model or you can customize a social media profile. You can customize github too. Now one of the first ways you can do this or just one way you can do. This is our profile reviews now. This is something that is relatively new. We've launched it last year and it's a really fun way for you to customize and showcase who you are and what you do on github.

AA

So you can add things like a little bio about yourself. You can add some of the top projects that you're working on or like our good friend, b dougie, who also works on the developer relations team. You can showcase other, really cool developers, so here's his top eight developers that he put on his bio now.

AA

The profile review is really a sky's. The limit kind of choose your own adventure. You can do anything you want on your profile review and it's really really easy to set up. So it's a way to set it up is if you head to your github profile, open up a repository with the same name as your username. When you do this, you'll get like a little pop-up here saying this is a special repository. You've now found a way to make a profile review.

AA

So that's how you create it, and then you can add anything you want into it. So really make it yourself. This is another really cool profile from one of our github stars and she's added this really cool banner up on top um and a little bit about her. Now you might have noticed from both the doggy's profile and monica's profile that there are like animations and gifs.

AA

Now, because your profile ready is written completely in markdown, you can add anything you want that would be considered in markdown, so you can add gifs, you can add images, and you can add some video. You can add emojis like here or you can even add games now. This is the profile readme from one of our hobbies tim and he's. Had this community chess tournament happening on his profile.

AA

For me for a while now so he's got this all running with github actions and you open up an issue which we'll talk about a bit more in a minute, um but you open up and you can play this community chess tournament literally on his profile. So if you go to his profile, you'll be able to see this so I'll. Let you find that one.

AA

So if you uh have a look for tim verwell on github, you might find it now another way to customize github to work really well, for you is to start looking at and checking out notifications now notifications if you've used any kind of platform before whether it's emails or obviously, if you've been using github for a while you'll notice, really quickly that you'll get a lot of notifications.

AA

Every time someone comments on an issue mentions you talks about. You uh makes a pull request: you'll get a notification, so this can sometimes be really overwhelming and you can get a lot of notifications so one way to personalize github and make it work better, for you is to start personalize some of these notifications.

AA

So, just recently we released a new way for you to filter notifications, so you can now filter out notifications by organization or author, so, for example, as krona and anisha mentioned, I work for github right, which means I'm part of the github org. Now, because I do a few other things on github, I also have a few other orgs that I'm part of now when I'm working during my work day. I don't want notifications from all these other orgs. I only want the notifications from github, so I know what I'm working on.

AA

So I can go through my notifications and filter out those notifications by github. Now you can get to notifications from almost anywhere on your computer or on your github profile on github. All you do is click the bell up in the top right there. um So if you can get that from your repair issues from your profile now one thing to note with notifications that some people get a little bit worried like. Oh my gosh, I haven't checked out my notifications for a while.

AA

If I go now and check them out, there's going to be hundreds of thousands of notifications, and I don't want to have to deal with that. So if you haven't checked out your notifications in a while go to notifications and you'll get a pop-up, and this will help, you filter out all those notifications that you've got sitting in the backlog again. This is something new that we launched, because we thought that, oh, you know, there's lots of people that are not going and checking out their notifications all the time.

AA

What if we give people away that if they haven't, visited their notifications for a while, we'll help you clean those up. So don't get scared about going and check out your notifications, if you haven't seen them for a while now what else plays into notifications is reminders?

AA

So, if you are part of a lot of organizations and you're getting a lot of reminder or sorry notifications on github, you might think oh, I might actually miss a really important notification. I might miss a task. I might miss a milestone. So how do I schedule a reminder? Or how do I schedule notification reminders?

AA

You can do that in github. You can actually connect your slack to your github and you can receive reminders in slack not only that, but you can choose which organizations you receive reminders for now. Obviously I mentioned, um I won't forget her so on my github slack channel.

AA

I only want to receive reminder notifications on slack from github, not from all the other orgs that I'm part of so you can easily do that and all you do is go to your settings and scroll down to your scheduled reminders and you'll be able to check out your reminders there and customize that a little bit. So if you have a look here, you can check it out.

AA

You can customize it make it specific for each organization and really personalize it for your type of experience, um so go and check that out now, speaking of personalizing, your experience, you probably would have noticed my last few slides- have all been quite bright and white and in your face and you're probably like well, this nice dark background, but the rest of it's really white and bright.

AA

So something that we launched um that our users were really asking for and something that we launched at universe last year and if you've been on social media, you probably would have seen it is our github dark mode. Now this has been really really exciting. People have been absolutely loving this phone, this mode is now available on github.com and it's completely native it's available across all our github suite of products so go and check out dark mode. Now.

B

It's really easy to check out dark mode if you're on your.

AA

Profile you'll see a little switch button or a little toggle at the top of your profile, you'll be able to switch to dark mode. We also have a new dim mode which just got released and announced last week. So if you haven't checked out dim mode, you might want to go check that out. It's a slightly different contrast um like less less dark. So, um like different contrast, you can see there so we've now got a light mode, a dark mode and a dim mode, uh but I really like the dark mode.

AA

It really helps save your eyes. um You see this nice beautiful darkness here so to save our eyes for the rest of my presentation, we're going to be using github in dark mode.

AA

So, let's jump in so one of the things people love about using github is the type of collaboration you can do on github now, if you've been using github as a developer, you'll probably know about a lot of our collaboration tools like uh code review and merging, and things like that now, since a lot of people know about those, I thought we'd talk about a few of the tools that we have as github to collaborate, which you might not necessarily know about.

AA

These also really good ways to collaborate across your entire organization and the first sign, which is one of my personal favorites, is project boards. Project boards are really great for tracking the overall progress of a particular project. You can also use it for a variety of different reasons, so so this one here is our github roadmap. This is our public roadmap again, something we launched last year out to the community and you can easily see at a glance what we're releasing and when so across the top of our project.

AA

Boards we've got each quarter, that's coming up and the different features and products that we're releasing across that coil. Each one is an issue, so you can click on that and go and see more happening on the project board. Now this is a really good way to collaborate with non-developers, because non-developers are often familiar with this project board type setup.

AA

There's lots of different ways to use project boards too, like we've, obviously used it here as a roadmap, but I've spoken to open source maintainers who use it to track different events that they've got coming up. I even use project boards myself.

AA

Personally, I have my own personal mesh list project board and it's got things like my shopping list and holidays that I want to go on and other tasks that I might want to track or projects I might be interested in so product boards are really up to you and you can customize it and really personalize it for you and the way that you want to use it now. Another really good way to collaborate with people is our discussions. You're, obviously going to be getting a first taste of discussions or firsthand taste of discussions.

AA

If you're heading over to discussions during this talk or afterwards, but it's a really great way to communicate, chat collaborate and have a discussion on github, so if you've been using github as a developer for a while, you probably know that those there's those issues that you have that aren't really issues they're more like discussions. So now we want to separate discussions from issues.

AA

We really wanted issues to be a way for you to talk about new features, new products and bug, fixes and things like that and then have discussions as a way for you to chat and collaborate. Now you can use discussions for a variety of different things. You can see across the um the side column there. You can use them for ideas, q and a's. Again I've chatted to some project maintainers asking what they what they use discussions for.

AA

Some of them said they even use discussions for people within the org to share their favorite holiday or surfing destination. I was like that's really cool, um but often you can have these types of discussions and really separate them from your issues. Now, if you ever notice that an issue that you've opened or someone else is open, is becoming more of a discussion or a chat or collaboration instead of an issue, you can easily go and convert that issue into a discussion.

AA

So here I opened up an issue to talk about a logo I was like. I think we should get a new logo, um let's see what we're going to do, who we're going to get and it became too much of a discussion. So I quickly went in and said yeah. Let's convert this to a discussion, um and now, as you can see, with our discussion, we can have thread of replies. We can have forum style conversations and we can keep all the chat and discussion happening over here and separate it out from our issues.

AA

Now, speaking of separating things and the way that people work now uh we really wanted developers and we ourselves as um people who use github and as developers we like to work the way that we want to and at github we want to give you that same power.

AA

We want you to use github the way that you want to use it, um and so because of that we decided that we'd provide github in a number of different formats, a number of different platforms, another a number of different ways that you can use and engage with github. So one of those is github for mobile. This allows you to take github with unique everywhere you go now.

AA

Obviously not many people are traveling at the moment, but when you do travel again, uh you'll be able to get help with you everywhere in your pocket, it's available on ios and android, and you can do so much on mobile.

AA

You can quickly comment on an issue review bug, fixes, merge code and now, as of uh probably about a month ago or so now um you can even have discussions on mobile as well, uh so the latest version was released last week for mobile and even includes release, notes for github now so make sure you go check those out one of the things I love about mobile is being able to quickly do something on the fly. For example, um if an issue gets opened by my team and it's you know, 7 p.m.

AA

My time on a friday, I don't want to completely block them over the weekend. I can just quickly comment on an issue and quickly unblock it without having to go to my computer fire up github and go from there. So that's why I love mobile. It's really fun another one of my personal favorites, which some people have been loving too, is github desktop.

AA

Now I really like you have desktop it's available on windows and mac os and it's a really good way to organize your repos. So all you do is drag and drop a repo into github desktop, and then you can manage that repo from there. What github desktop does is it compares the repo that you've got on your local machine to the version in the cloud um and me being not so familiar or remembering different commands to fix github or you know, have I merged my thing yet you know. Is it?

AA

Am I one step behind master on my computer or main sorry? Am I behind main on my computer? Is my origin in front of my local copy github desktop manages all that for me, so I love these big blue buttons that come up like. Oh, you are one commit behind maine. Would you like to pull in the origin and make your local machine uh pair up with? What's on the cloud? So that's why I really love desktop. You know it's all these nice, big, blue buttons and toggle, and push commands.

AA

I don't have to really think about what I need to do next, um so I'll have github desktop. As you can see here, it's available in dark mode as well. Our theme github desktop is you can go through the history of all your files and compare and view the changes, so you can see in red it's being deleted and in green they're, the added versions, so the latest version of github desktop shipped on march 10th so make sure you're up to date with github desktop to enjoy all the fancy features we have now.

AA

If mobile and desktop aren't your cup of teas, maybe you'll like our cli. So last year we launched the github cli and developers have been loving. Our cli being able to use and seamlessly work in one window, so github cli allows you to do so many different things. You can create view and edit issues directly from the cli. You can check out prs. You can now auto merge pr's, which is a new feature for our cli that was released a few weeks ago.

AA

You can easily clone a repo, you can manage ssh keys and so much more cli has been really fun. Even I've been loving using it. It's available on windows, mac, os and linux. Also fun fact about github cli is it's open source and you can contribute to it as well.

AA

So speaking of open source, as I mentioned, we're on the open source channel, so I'm going to give you a few top tips on getting involved in open source and working in open source. So first one is getting involved in open source. Now, if you're sitting there, some people think well, you know how do I get involved? How do I find projects? You know one tip. That um is one of my top tips that was also shared yesterday during one of our satellite panels.

AA

Is um contributing to projects that you might already use, for example, I am currently using obs to run this presentation. Obs is an open source project. So, if you use.

E

AA

A really good way you can go in and jump in and keep um and start contributing to obs. You can also find really good projects to contribute to through events like hacktoberfest, what about all the other times of the year or, if you're stuck for what you're currently using or if you just want something completely new, you can go and check out trending topics on github. This is a really fun way to find out. What's currently trending on github, it's also a great way to search by type by language type, both written and spoken language.

AA

So if you go, I'm a python developer, I want to go and search our top projects of training on github and python and start contributing to that now, once you've found a project, you think you might be interested in have a look at their reading profile.

AA

If a project is really good or have a good review now, as the name suggests read this, does it make sense? Does it excite you? Does it entice? You it'll have a really good explanation of what the project does and how it works, and if this resonates with you- and you might think you might want to contribute next thing to do- is look at the contribution guidelines again.

AA

If it's a good project, we'll have really good contribution guidelines that tell you how to contribute to the project and how to get involved in starting to contribute again. Does it resonate with you? Does it sound like a community? You want to be a part of if so then go and check out their issues and have a look at these labels called good first issues.

AA

These have been identified by maintainers as good ways to get involved in github and well sorry within the project itself, and it's identified as an issue. That's been that's relatively easy to solve and will give you a good understanding of the project that you're starting to contribute to.

AA

So that's pretty much brings us to time. So if there's more things that you want to learn about github um you're sitting here thinking, I actually don't know how to open up an issue, or I heard her mention actions. I want to learn more about actions. You can go and jump on the learning lab.

AA

This has everything you need to get started with github if you're coming to github for the first time, everything from opening an issue or right up to our advanced stuff, like working with actions or deploying github pages, so go and check out the learning lab.

AA

If you want more top tips like on specific things like keyboard, shortcuts or cool things that we've got coming up, go and follow github on twitter, we're putting out these really short social media videos on top tips that you might be interested in and you can go and check them out so go follow us on twitter. Again.

AA

If you want to uh engage with me or interact with me or ask me, questions I'm pretty much available on every social media platform known to man or I'm going to be in the discussions right after this, so come and check to me in discussions. So without further ado, let's hear from some of the questions that are coming through github discussions at the moment. Thank you.

C

AA

So excited to be back.

M

Awesome, it's that is really great. You know of get up like a bus. uh You know some of some of those. Many tips are those that even many of us might not be aware of. So I'm sure that's, you know that's going to be helpful for most of you out there. So if you have any questions even right now, you can drop them over in get up discussions and we will take up. Some of them live out here for bish, but otherwise you can always hang around on uh discussions as well.

M

So I know there are you know a few questions that have come in um mish. You know someone wants to know what is what is uh what are some of the things you use every day at github that you know you really like.

AA

Yeah, um actually all the things that I talked about in my presentation, I use pretty much every single day at github. If you see me you mentioned, I do live streaming on twitch, so I also do live coding on twitch and, if you've ever seen me do any live coding on twitch. I use the cli desktop and um you know even code spaces and things I use all the things I talked about.

AA

I actually use pretty much every single day, um there's also some fancy new things coming up that I've even had had a chance to have a look at so I use all the whole github sleep pretty much every single day and it's so fun. I love desktop. I love using the cli, it's new and it's exciting and they're, always adding in new commands, so using the cli is really fun and project board's a really fun way to collaborate with everyone across the team.

AA

You know both of you know that we use it um as part of our devrel team as well. So yeah I get to use all the cool things on github every single day.

S

So mish we know that you definitely github like a boss, but what's the one biggest top tip on getting started with github.

AA

um Okay, getting started, especially if you're like new to github or you've, been maybe even using github for a while you're looking for the next big thing is whenever I'm using github or even just generally using the internet, I nearly always come across um github repos and my biggest tip is just go and style them. I just start everything on github, um for example. I recently got into um cryptocurrency mining um and I found or like the the tool that I used to mine crypto again website there scroll down, oh cool.

AA

I got some social media channels. Oh wow, their repo is all posted on github, so I immediately went to the repo starred, the repo and I was like well I'm just going to have a look around at the ready flowers and check out the project. um I found a bug with the um like with the software, so I opened up an issue. I even found the fix for it. So I like put it in the issue.

R

But I think that's.

AA

My top tip is like when you're browsing and you're surfing the internet. You find really good little pieces of like programs or things that you might use have a look at where it's actually hosted most of the time, they're hosted on github and I just go and star them. um So I can go and find them um for future, but also like it's just really cool to see that all the things that I get to use every day, just just hosted on github, which is awesome.

M

Wow, that's that's absolutely you know, let's just just go and start them and then have them, have them ready out over there. So um mish, you know, I know, I know you kind of uh interact with a lot of the developers and keep talking to them. uh Was there? Was there one tip that you know you felt that? Oh, my god, you know, even the power users are not aware of this is. Is there something like that.

AA

There there is one- and it came out recently um in a top tip video that I did, um but I decided to do the top tip video because I showed it live on stream. So if you do ever come into my streams, you get some really cool insights on what the top tip videos are going to be. But I showed this thing on stream and it was really um good timing.

AA

So most of you know, if you've been um surfing around social media, you would have seen the github skyline stuff that we announced, which is a way for you to go in and get a 3d version or 3d image of your contribution graph- and I was like this- is really cool. I can like download a 3d image and stuff, and then someone mentioned to me, like you know that you can view and host 3d files on github. So I even like printed out lines.

AA

This is my 2020 um one here and I was like this on stream. I was like we did this and I was like oh, but if you want to see it and put it on github, you can store the 3d file for this on a github, and so I put the file on and you can spin it and turn it and use it and play with it. On github I was like that's really cool. My whole audience was just sitting there like.

AA

This is really awesome and I was like it gets better guys check this out. So I put my 2019 that was my 2020 graph. I put it against my 2019 graph, I put it on github and you can actually see the difference on github. So if you're using code review and things like that, you know that the additions are in green and deletions are in red.

AA

So if you have a 3d file on github and you add a new version of the file, you can see the changes that are made to that file in 3d and it was like it was like.

S

It was just so cool, I think. That's.

AA

Like one of the biggest things that even power users don't necessarily know- and I think it's because like we were so ahead of the times when we released that feature so that feature was released back in 2013 and at the time not many people are getting into 3d, printing and tinkering and stuff like that, and and now it's just become so much bigger. So I think we'll see a lot more people start to use um github for their 3d version, control, which I'm really excited to see. More of that.

S

Perfect great well thanks mish for sharing everything that you shared with us and the rest of the world. Actually, this session was definitely hot hot. So if you.

AA

Missed it, you can always watch this on juventus. I love those emojis they're amazing.

S

And folks, don't forget head on over to get up discussions as well. Misha is going to be hanging out there for the next 30 minutes, so you can post any more questions that you have on your mind, because mitch is going to be there. Oh there you go, there's the link right there. um So thanks again, mish and we'll see you soon.

AA

Thanks so much for having me I'll see you all in.

AA

S

That was just exhilarating right. All of that information that that michelle shared, but you know what we're getting close to the end now, but but we still have two more sessions to go, including a great closing session, with our very own mini sharma as well, um and if you've missed anything, don't worry, you can always watch the sessions on demand um in 24 hours uh later at github satellite.com.

S

um But you know what I loved everything about this. So I know you know I've. I've been sharing everything with everyone, but I want to hear what you folks are thinking so go ahead and hit us up at github satellite and share everything that you've loved over the past two days um sessions all the performances and even us I mean look at us- we're celebrating holly here right now um on two different ends of the world right current.

S

Exactly exactly so, you know what what's next. um Our next session is all about: the state of ui ux in open source and it's basically an introduction to design systems and patterns and why they are relevant to your projects and hosting this session is going to be pranav raj. Who is a co-founder of chatwood and don't forget to engage on discussions? um He'll be hanging out there after a session as well.

S

So you can post um all of your questions and then things that you want to ask him that there you go, there's a link right there, um and so, if prana is here right now over to you would love to hear more about your session.

M

U

Pronouns hi everyone, my name is pranav, I'm the ceo of chatfoot.

U

Today I'm going to talk about the state of uiux in open source projects, how you can drive design discussions and how you can actually promote a design first culture.

U

But before going into that, let me introduce myself, as I mentioned like you know, I'm working on an open source project called chatwood. I've been contributing to open source for about seven years now I started in 2014 uh through github. Like you know, sales years was my first contribution uh from there. uh It's been an amazing journey from an open source contributor to now to a open source, uh maintainer, uh so yeah and a little bit about chat wood.

U

We are building an open source customer engagement, suite uh built as an alternative to intercom and zendesk. We started in 2016. We started out as a proprietary software, but it didn't work out. Well so after seeing the data privacy regulations, uh people moving on to you know self-hosted alternatives, we thought why don't we give this this a try and we oppose the project and, to our surprise, it got trending in hacker news and from there like.

U

You know we have been working for more than a year uh to build features and right now, like you, know, we're building business out of it, uh so go check out, uh chat, food on github and uh let us know uh your feedbacks. uh We are open to contributions.

U

We're open to discussions, yeah feel free to do it. uh So before we jump into the uh actual topic, let me discuss about the two different aspects. Like you know, developer experience and product experience uh so as an open source projects.

U

It's it's really important for you to uh you know, concentrate on the developer experience because, like you know uh it really matters. uh How, like you know how it is easy to install the software or how hard uh is it to maintain, or maybe, like you know, when there is a new version of the software? How hard is it to upgrade these all things? Actually matters uh in your adoption. So if you want to have better uh adoption, uh you would have to make all these things simpler.

U

uh But, like you know, there is other aspect as well. Like you know the product experience uh so uh like you know how you use the product, how well it actually solves the problem. So today I'm I'm going to talk about products, experience not about the developer experience uh so yeah, I think, like you know, a design in open source projects is actually pretty debated topic because, like you know most of the uh projects don't follow as standards or most of them. Actually, uh you know don't have a guideline on how to contribute on design.

U

uh So, like you know, the the one of the reasons which we see uh for that is because, like you know, design and development are two independent processes um for designing a better user experience. There needs a group of people with different set of skills, working together uh towards a single goal. uh I mean, like you, know their needs. There needs to be.

U

You need to have like you know, designers, you need to have developers who can implement the design and they need to have like communicate between these like this should be a proper communication between these two and this is not happening in the open source projects. So one of the things which I've understood from my experience, working with designers in my previous jobs, is that, like you know, most of them are problem solvers, so they try to identify. What exactly is the problem?

U

They try to understand how uh this problem is affecting the end customers and then from there, like you know, they work backwards, to identify what's the right solution and build a user experience around that. This is not happening uh anywhere in, like you know any of the open source projects, because one of the problem with that is, like you know, most of the uh designers who's new to the open source project might not have context about what people are asking, so they need to set it up.

U

They need to, like you know, understand the product better it it takes a little bit of time uh to for them to actually do that, and uh second thing is actually like you know uh the I mean, like you know, most of the open source products, as we know like you know, starts with one single developer who uh who had a problem so they like uh they wanted to, like you, know, put some thought and then build a small hack or, like you know, a small product which solves their problem and then like uh they think like okay.

U

This is useful to me, so why can't I open source it so they open source the product and afterwards, like you, know, people uh like people see the product and then from there like you know, they start adding more and more features to cater a large set of uh uses.

U

uh So one of the typical problems uh which comes to the projects is that, like you know, since it's not built for a larger audience, uh I mean like they tend to have uh like you know, ux. That incurred due to various reasons. One is actually like. You know most people who would ask you, like you know why don't you do x to do y or, like you know, why, don't you add an option to do something so as a as a maintainer, you want adoption as a maintainer.

U

You want more people to be using your product, so the immediate thought or, like you know the immediate uh uh uh understanding, for you would be uh to create uh an option for them like you know, so that, like you know they can use the product, and this keeps on adding like there will be.

U

Like you know, a lot of speeches there will be like, like you know, there'll, be a lot of options which you provide so that, like you know it, it caters every set of people and the end result for that would be something like this. Like you know you, you would have a smaller system with a lot of function, options with a lot of controls which might not be relevant to most of the uses. So one one one problem with this is actually like you know.

U

Most people would have uh uh don't won't understand, like you know why these many options are provided or, like you know why this uh like this elaborate set of, like you, know, options this is given in the in the product, so it it's kind of a learning curve for them. Like you know, it's not a good ux.

U

So if, if you're not doing something complex, if you're not doing something uh like you know like the one which we see in this image, uh so like try to minimize that and like you know, it's really important to understand that you don't have to provide every option which every customer or, like you know, every developer is asking you on github. You can always say that like why? Don't you just the project and then make make option by yourself so that you can use it?

U

So it doesn't make sense for you to add every set of features, every set of options which people are requesting. So every time you uh you get a request that, like you know, add a functionality. Add an option to uh to do this.

U

Just think about whether this is going to create a ux debt or whether it's going to create more and more problem on on on our end, then like then, after that, like you know, if you think this is going to be a problem, this is not going to be a useful feature for a lot of people who are using your product. Then uh don't do it like. You know just say that you can customize it like this. You can do changes change the code like this and you can do it yourself.

U

So this happens to me all the time in chat wood, because most people, like you know we have a broader product like with a lot of options, a lot of customizations available. uh So people would come to say that I come and say that you know I want this kind of thing for this use case and yeah like as a developer, the maintainer of the project. I my immediate reaction is like oh yeah.

U

I think I can provide that, but uh most of the time, like you know, I take a step back like talk to uh the people who are working on the project like understand whether this is something that's relevant for the larger uh set of people, uh then, if it's not, then we would defer that or maybe ask the person to actually you know build it themselves, because it's open source right, like you know you can uh you can build it out yourself.

U

You can uh like you, can change the code, which is uh which is one of those things which you would want to do if it is not possible to uh remove that option. Let's say, like you know, you have, uh even though, like you know, even if you have like uh two options with two uh like two two type of different options with two: uh yes or no answers there, you have like four possibilities.

U

Think about, like you know, 20 different options with, like you know, uh 20 different, like uh yes or no questions like there will be like a lot of options. There will be a lot of combinations which you have to provide so most of the times.

U

Don't add the future right away, just like you know, think about whether you can ask the person to say that, like you know whether they can build it themselves, if it is not possible, if you think that this is something which is going to be useful for a larger set of uses and still you would have to provide a standard default right.

U

So if you look at like zoom as an example, uh so the the way we are uh entering a meeting- it's just one click, but if you want to customize uh a specific thing like the way it's being recorded or, like you know the uh like the video quality or like the audio quality, it's all there, but it's it all have like it.

U

The all those options have a standard default so that, like you know, a new user comes in or the person who wants to try out the product has a very simple uh step to do that, like you know, install the software, just click on uh like in a login and then click on start a meeting. Then you have that particular uh you know meeting opened right, so you have to pro.

U

You have to think like that, where you, you have to provide a standard default for all the options which you provide so that, like you know, whenever a person comes in like it's, it's very easy to get started with the project and try to use the project. So we we do this at chat road a lot. uh We have a standard defaults for most of the cases which we recover, even though, like you know, there is a customizability option. We prefer to have a standard default for all options which we provide.

U

Second problem here is actually this lack of standardization of design, uh so all right, uh so the all the design, all the open source projects, like you know, if you look at them, it's it's mostly like, as I mentioned like you, know, a developer working on it and from there like building features out of it. So uh there is a lack of like you know, design uh design. First thinking uh what I mean by that is uh like.

U

If you look at uh any of the uh like web projects out there, it's like you know there will be 10 different types of buttons. You can see or 10 different spacing you can see, or maybe, like you know, you can even see people writing uh styles in line. So one of the problems with that is, like you know, as a designer. If somebody comes to your project and even like there are different barriers for them to actually like, you know, try and use the product. Even then, like you know, if they did all those.

U

The first thing which they are going to see is like you know, the the design itself is like not standardized or maybe, like you know, don't have a guideline which is written anywhere, so their posts uh thought process would be like you know. Why don't I contribute to this?

U

Why don't I contribute to uh the base design like make it better, uh but often it ends up like you know, changing a lot of variables, which uh might not be the right thing for uh the developer, because, like it's a lot of work for them to change all this and like make it standardize and they would end up, like you know, rejecting uh the proposal which which might be like frustrating for the designer. So uh before you start like you know, think about how you can uh standardize the the uh like.

U

You know the options which you take like you know. One of the easiest examples is to take. uh uh One of the frameworks, like you know, tailwind or a bootstrap or foundation like you know, take that as an example.

U

Take that as a base uh style guide for you and then from there build on top of that, make the uh colors, uh with with respect to your brand, made, make uh spacing with based on based on what you require and use the standard colors or spacing or like you know, whatever is whatever you are using inside.

U

Your project, like you, know, make it a standard, put it somewhere in a common place, so that everyone who, like you know who is interacting with the product, knows that, like you know, this is the place I can go and look at uh what is the standard being set? So uh this is what is called like.

U

You know: design force culture, like you know, whenever a new person comes in or, like you know, whenever a new, uh a new kind of like designer who wants to install or like you know, use the software, it is easier for them to see. What's already there, like, you know it's, it makes it less complex for them to understand what are the standards that are being set.

U

So we, when we started chatwood, uh we were thinking about like you know how we can, uh how we can like adopt this system, like you know how we can adopt a design system, or maybe, like you know, adopted a sign language so that it's easier for us to communicate with other people. So we started searching for the options it was in. 2016 design system was not a thing uh but like there was a good guide written by marvel at that point, so we started from there.

U

Like you know, we took their uh design system as an example and from there we built our own standards. Like you know, we have our own typography. We have our own phones, we have our own spacing or, like you know, even colors, like we customize all those things but like the base idea or like the base layout was taken from other examples.

U

So you right now they all of the companies are like all of the products which is out there who have, who have certain set of guidelines would follow some kind of design system and, to be honest, like you know, I wouldn't I wouldn't recommend anyone to just like follow bootstrap because, like you know, it gets worse when, like you, have a lot of components and there is no way to actually like you know, make a standard or like there is no way to for you to uh build a standard just by bootstrap.

U

So it's more about, like you know, the the culture which you building, like you know, think about standards. Think about, like you, know, a design system, how you can adopt it like go check out like different options um like primer or primer, is actually like.

U

You know the design system for github um and you can actually go to refactoring ui, which is a great book which you should follow uh uh which, like you know, even if you are a developer or if you, even if you're someone who don't have who have not worked much in design. That would actually help you uh to understand. Like you know like it, it would help you to get started and understand how things work uh so and second, and and like, and one of the options which you can do is actually like.

U

You know document the design choices. What colors you choose? What's? uh What are the components which is available in your projects, like you know how? What are the different type of options available so that whenever you, whenever a new person comes in, you can define a process on how they can contribute to the project?

U

Right, like you know, you already have all these things documented and we started this with styleguide.chatfoot.com, so we started our experiments with that and right now, like you know, we are writing a guide so that how a new person who's interested in design can, like you know, look at how we are dealing with the design and then from there like you know they can contribute, or maybe uh just take, inspiration from so and the third problem which most of the people face, who are designers.

U

They don't know how like how they can contribute where they can, where they can contribute and what they can contribute. So the first thing is actually like: you know where they can contribute. There is definitely a lack of understanding or awareness about tooling. So github, as you say, like you know, or even open source projects is mostly about code, uh the the the amount of peop.

U

Like you know, the amount of people involving in open source projects who are designers is very less so, and there is a separate movement called open, source, design and stuff like that, but uh the the core or, like you know, the most of the people who are working in open source would uh would are not designers and for designers, like you know, it's it's it's a big barrier for them to uh understand how github works or, like you know, or any other, a git or svn or any other tools which you use.

U

uh That's first thing, and there is no there's no like a way around it like no. They have to learn. It second is actually like you know, even even if they come to, they understand github and they come to your project.

U

They don't know what to contribute. Right like there will be a set of issues which might be highly technical, which is not really uh really good to understand. So you have to define an issue which describes what is expectation here. What are the kind of things which you would want to build and, like you know, what can we contribute or like? What can external people contribute to that particular issue? Most of the times like.

U

If you go to any of the open source projects, it will be like you know, there'll be a log and then okay. This is not working for me, and this is why this is happening so easy. There is no easy way to filter out these kind of issues just to make sure that, like you know, I have a design problem which, like you know you can solve. There is no there's no easy way to do that.

U

So, like one of the things which you want to do is like you know, define a process on how you can contribute to design. So first thing is to write down the expectations, have a proper uh product spec. So let's say you're building a teams feature write down a product, spec understand what uh what this feature means to. You then create different types of options which is available like or different use cases which you can solve and from there label the issues right, like you know, if you have the product spec complete.

U

Next, you want is a high level design. Maybe people can contribute like you know it can be, uh it can be about civic mockup or it can be a figma design. It can be anything like you know, just to contribute to the design label the issues correctly so that people can find it. So first thing you you want to do is, like you know, label them properly, with design wanted or something of that sort- and third, is actually like you know, have a clear honor of the issue and define how you how you resolve conflicts.

U

So, most most often like you know, if there are two people who are working, who saw the issue who wanted to contribute something, then they comes with two different approaches.

U

There is a conflict and you have to define very clearly upfront that, like you know, this is the person who is owning this issue or like this is how this issue would be resolved if there are a conflicting opinion and from there uh you have to define that process as well. Like you know, the understand like tell like write down in that particular issue that, like you know this is how we accept contributions to this particular issue.

U

uh Say you want to have these these many things and it should not uh follow these many things and it should follow your actual design contributions.

U

So, like you know, having that clear ownership and having that conflict or solution, written inside uh issues is clearly important and I think like I can give an example of metabase, uh so they, uh if you, if you look at their like contribution guidelines, there is an option called. uh There is a section where they define design the feature uh and in this like, even though it's it's clearly it might, it might be, like you know, their internal team working on it.

U

Like you know, it's very clear that these set of issues which are tagged with design needed is specifically for designs. It's the ux is complete or like the uh the feature is actually uh understood.

U

Like a feature is already written very clearly, you have to understand how, uh like there is a clear description of how the functionality would work, and the next thing you want to do is, like you know, create a design for that, so people can just go there, filter out the label uh design needed then from there like you know they can contribute, or maybe, like you know, they can provide suggestions which is not there in most of the problem most of the projects and the other way you can approach.

U

This is actually by uh you know, having a process for design. Let's say like you know, you have a set of components which is desired, which is designed and you have a style guide return for it, so you can either say uh if, if the contribution, if like you know, if, if you want to do something new in design, just go to the cont, like you know, the style guide library see if the component is all already there.

U

If it is there, then you can actually see whether uh you need to make any changes or if, if, if it is already like, you know it already covers everything, then you can just right away use that if it's not uh present, if the component is not present, then you can propose a new component design and if the component, like you know you can have, you can define all the steps like that.

U

So that, like you know there is a written rule or like you know, there is a process which is defined on how you accept design related contributions, which makes it easier for people to contribute as well. Right, like you know, you go to a project, you understand. This is how you can contribute, and then you can jump right in and then contribute so uh primer like, as I mentioned, github's uh uh tile guide is actually like.

U

You know they have well written document on contributing and maybe like you know, you can actually explore other open source projects or other uh companies guidelines which gives you much better decisions and the last part of it is actually like. You know we covered why this is happening, how this is happening and what are the different things which you can do to improve design contributions? Now, I'd like to talk about uh how to drive design discussions uh driving design discussions is a double-edged sword.

U

uh To be honest, like you know you you either get a lot of good responses or you either get a lot of very bad responses, and there is no uh way to like you know get around on that. uh So you have to understand. Like you know, whenever you start design discussions, it can get very some kind of very minor colors or, like you know, some spacing, but it like there is actually a way to uh way to provide design discussion.

U

First of all, the thing is actually like you know, whenever you write a feature put the mock-ups right inside the issue, just take a screenshot put that in the issue, so that, like you know, when people come to your your github, go to issues, click on one of the feature description like you know, they see how this is going to be uh in, like you know, whenever, when the com feature is completed, right like at that point, they might have some options.

U

So this is one of things which we did from very early on, so that, like you know, whenever we have a design whenever we have a new feature which is going to be built, we build the designs or build the modes in in figma from there, like you, take a screenshot and put that on the github issue, and this drove a lot of uh comments and, like you know, a lot of discussions based on very particular things, for example, very particular on this one was like you know, one of the things we which people suggested was to provide an option for them uh instead of, like you know, instead of like having a text area to add this consent, uh they wanted to have a standardized concept like you know, maybe just they can just change the variables or like their company name.

U

They can just use the user right away. Second thing: people wanted was to add options for terms and conditions or, like you know, privacy policy, which makes sense because at all like you know, we are, we are saying, like you know, you are accepting this and then you want to have all the links together and then that kind of things like you know, drove discussions in us.

U

So maybe you can experiment with like you, don't have to have a design like this, you can just use uh balsamiq or maybe anything like or even like paper written mocks, which uh which can actually drive discussion so driving design discussions might not really involve uh designers. It involves people who are actually using the product. So if you are building something out there, you want to have a better understanding. How people think about the feature. You don't have to do user research in github because, like you know, your project is open source.

U

You can leverage that, as your starting point create a feature. If you request and then from there like, you know, put the design ask for contributions and there just explain very clearly what you're looking for and what kind of feedback you're. Looking for instead of like, if you put something like this without that that direction, what happens is like you know, people say that okay, this uh text or font price is very small or maybe, like you know, I want to have the heading bet larger.

U

Instead of that, give them clear direction on, like you know what you're looking for as a feedback, and if there is someone who was willing would provide that feedback. So yeah, I think, like you know, that's all that's all I had for today. So basically, like you know, I define a process understand that you need to standardize at some point. So why don't you start at the beginning itself, like you know, standardize your components, standardize your uh your uh design system, so that, like you know, people can just look at uh the designs and understand?

U

Okay, this is what this guy is actually doing from there. If you have like standardized design, if you have like a process which is involved in uh design contributions, you can actually have a third thing where, like you, uh you just like ask for general public for feedback on specific options which would drive more and more design discussions.

U

So yeah. I think that's all we had uh for today. So I I was doing this experimenting this for a long time in chat. Would some of it work some of it doesn't work uh but yeah, I'm really happy to talk to you. If you want to, like you know, understand how uh I see about this. Maybe, like you know you can reach out to me on twitter or or my email as I shared before then yeah. I think, like you know, that's that's pretty much it thanks for taking time to watch this talk.

A

M

Hey everyone all right, thanks a lot for now that was that was a really nice. You know uh discussion around the state of your ux in open source and the design systems, etc, so in case you're still not able to recognize. This is current one of your course, uh but before that you know in case you have any questions head on over to getupsatellite.com discussions where pranav will be hanging around um also.

M

We are now almost to the last closing session for satellites. So thanks a lot for all of you for joining, uh it's been really amazing. I hope all of you enjoyed watching satellite and interacting with us as much as all of us. You know we're hosting and also a big thanks to our host divya and mohit on the devops channel who've been doing an amazing job as well.

M

um You know bringing you all of those session and the content as well, thanks to all of our speakers who have come in and then you know spent our time sharing the knowledge interacting with all of you out there, uh and also thanks to all of you folks, for tuning in sending us all of that. Love for all of the others, who've been tuning in for us, the kid of india team and for the speakers and the rest of them as well. So a huge thanks to you, but before we go anisha there is something.

S

There is, there is tell me.

M

Yes, if you have missed out any of these sessions, don't worry because all of this is available on demand for you, starting monday, the 29th of march, so you won't miss out any of it. In case you have signed up for the workshops. The workshops are going to start at 3 p.m.

M

Today, so do tune in for that as well, and also do let us know on twitter what you think tweet out to us, using hashtag, github, satellite and also uh at github india, so uh for our final session for today we have uh the closing remarks by our very own manish sharma, who is the general manager for github india, um he's he's a really passionate. uh You know uh with open source and everything else for the developer community out here in india and he's not working. You can find him.

M

um You know, play some guitar and then also do a lot of other cool stuff. So thank you once again for joining us. uh We'll see you again very very very soon with a whole lot of stuff stay tuned uh and anisha. You have anything else.

S

Oh my gosh, thank you so much everyone and we really enjoyed the last two days of content and we'll definitely see you next time. Thank you. So much.

M

All right also a happy holi from mona and me see you.

M

K

You've been excellent hosts, um I'm sure everybody enjoyed the last two days and all the fancy stuff that you've been doing. I've discovered two secrets: one mohit is a great banger dancer, so you know stay tuned for more meetups, where you will see him in action, and I also found out that karan loves to play holi.

K

So I'm sure it was fun for all of you, but most of all thank you to each and every one of you for being with us over the last two days as we celebrated the india developer community, it has been a pleasure uh serving all of you over the last one year and we are overwhelmed with all the love. The engagement that you've given the session started yesterday with erica sharing with all of us how we've grown to more than 5.8 million developers from india who call github their home.

K

It is super super exciting to see that we added 1.8 million over the last one year, but what's more exciting and current talked about how I always love anything open source has been seeing that indian developers have been driving the most engagement on open source over the last one year on github. This is just fascinating.

K

You know I come from a very different era. I I started coding in the last century. I always like to say this because I keep people guessing. You know what my real age is, um but it's so great to see the changes that have been happening in the ecosystem, with young developers like yourselves innovating and contributing back to the open source community. So we thank you for all the support, so the last two days have been great.

K

I know it has been a power pack session with so many content coming your way, but, as karen mentioned, all of these 22 sessions will be available for you on demand for you to go and check whenever you feel comfortable or have time to do so once again, thank you so much.

K

I also want to talk about what shanku and the engineering team took you through in the morning. There is a lot of convergence that is happening across security across development collaboration, especially in today's world, where everybody is distributed. We have so many customers from india who are really driving innovation and leveraging github for getting their teams to collaborate and build software, and these customers are all of all sizes, whether large or small, from any industry, whether they are companies that are transforming into software companies or born digital companies and one such large organization is cognisant.

K

Cognizant needs no introduction. They are one of the largest developer companies in the world, with teams and customers across the globe that they service. Let's hear from hari, who is the avp enterprise architect at coppeasant on how they are driving transformation and developer productivity using github.

AB

Hello: everyone cognizant's internal I.t team serves one of the largest enterprises in the world with 300 000 employees worldwide.

AB

It's a fortune, 192 companies, 16.7 billion dollars in revenue companies, critical business operations, runs on internal systems and processes as part of the cognizant's digital inside strategy, which is about transforming the internal processes and internal systems. It is based on three pronged approach. First, is modernizing employee experience. Second, is building a strong data and integration foundation.

AB

Third, is modernizing our application ecosystem on enterprises cloud first mobile first strategy: we have to be kind of very nimble and agile in our processes, and we also need a cultural shift in terms of how we deliver our products and services.

AB

Our entire engineering processes and tools have undergone transformation using github and devops hundreds of software professionals now on github. The conversation is shifting towards. How do I engineer the code? How do I internalize the best practices available in the industry.

K

Thank you, hari. Let me now talk about some of the programs that erica mentioned, and I'm sure all of you are as excited as I am when we announced it yesterday and these programs are really going to drive the engagement for developer communities across students startups and the open source community.

K

Many of you have already started applying for these programs. I am so overwhelmed by the mails that we've received from each and every one of you over the last 24 hours. Since we announced this, I do request you to leverage these programs and give feedback a lot of these programs. We have created over the last one year based on the feedback that each and every one of you gave on what you expect from github.

K

We are really looking forward to feedback coming our way for creating more such programs to drive the engagement with developers like yourself and the whole purpose of this. Is you know to get more and more developers on the platform.

K

There is a huge generational shift, that's happening in the industry today, with more than 500 million applications that are slated to be written by 2023, which is more than the last 40 years combined.

K

I think it's a great opportunity for open source for students who are stepping into the software development world and also for enterprises to leverage github to really build software, and that's been our purpose ever since we started our operations last year to serve you better to be closer to what you would require from a platform like github as we push the boundaries of developing applications to move human progress, so really excited to be here and in a way it's been great um doing this virtual session with you. I can share that.

K

You know last year, when we were kicking off um our operations, we did our kickoff on valentine's day, 14 february 2020, it's so vivid in my mind, uh it feels like 10 years, but it's only been one year. We were, you know, expecting 250 300 people to show up, and we had 2 000 people show up at the event.

K

It was a physical event and we were overwhelmed by the love that we got from developers and I'm sure by now doing this virtual, we were able to reach out to more and more developers across the length and breadth of india so really excited, and I'm thankful that you were able to spend that time with us as a next step. I would request that each of you follow our repository on github. This is a public repository that we've created to share more details about three programs that we've announced and also on an ongoing basis.

K

We will keep sharing meetups hackathons, more programs, and you can use the discussion boards to interact with the india team on how we can engage with you a lot better.

K

I think closing satellite would be incomplete without me. Talking about my favorite moment, which is you know, yoga cat which we've unveiled for india. I I just I just love this mona of car and I'm sure you can see the details in the lotus petals that show the git operations for a community connected by code like india. This is, I think, a wonderful representation of you know what github is and what it means for india.

K

Thank you very much everybody. I wish you a very happy holi um for those who are going to be attending the workshop all the best. I hope you have a great time learning from our engineering team on how to use github in a more powerful thing. Thank you and have a good weekend.

B

B

B