GitHub Open Source Friday, 18 Jun 2020

Previous Meeting

⏯

youtube image

►

From YouTube: How to contribute to Next.js - Open Source Friday

Description

Tim Neutkens provides insight into how you can contribute a good-first-issue in the Next.js project.

Next.js gives you the best developer experience with all the features you need for production: hybrid static & server rendering, TypeScript support, smart bundling, route pre-fetching, and more. No config needed.

Join bdougie and friends live for Open Source Fridays at https://www.meetup.com/GitHub-Virtual-Meetup

As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub

Thanks!

Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
Google+: http://google.com/+github
LinkedIn: http://linkedin.com/company/github

About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

A

All right welcome. Welcome, welcome, welcome um everybody's here you're in for a treat. uh This is our first open source. Friday live stream on twitch, um it's a long time coming. It's been in my my brain and I've wanted to do this for a while, um yeah hey, I know, un. You know therium yeah, hello, people in the chat and uh super happy that you guys are here to um chat with me and my friend tim.

A

So let me go ahead and transition to tim, I'm gonna do some live switching too, as well, just making sure everything everything is working and tim, you want to say hello, hey.

B

How's it going.

A

Doing well awesome, I realized before I even got online. I totally forgot to do an audio test, um so if anybody is uh concerned about the levels or anything like that, just pop in the chat say hello, uh let us know if you can't see anything, uh we're all learning how to do this um as we go along.

B

A

Cool and I said I hit the hit start on zencaster too sorry, I'm just a little little distracted as I do. Although the live switching but tim uh you're here, because you're involved in the open source community.

B

Yeah exactly uh yeah.

A

B

I was just gonna say, go ahead and give us a uh introduction on who.

A

You are and what you do, yeah.

B

Yeah so uh hi, I'm tim, I uh I lead the next team at uh for sale and um I've been maintaining open source full time for uh quite a bit over two years now, like almost two and a half years,.

A

Yeah awesome and um specifically uh you you maintain uh adversel, um which is formerly zeit, so it's gonna I'll, probably flub a bit too as well as I call it zeit and vercell, um but you're.

B

A

Js team, so how did you sort of get your get your way into versailles and how did you get your way into sort of being the the maintainer and co-creator of a couple different projects.

B

Yeah so I I basically started my software development career uh relatively young. I was 18 years old.

B

Magento, that kind of stuff uh see that I'm cutting out a bit, but oh well um so yeah. So I was working there and in my free time I was basically like still learning a lot of like javascript. I was very interested in it. I was mostly doing like back and for php at the time, so um I recently got involved in a bunch of open source projects like just helping out so like, for example, like solving good first issue, labeled issues and that kind of stuff um or just helping out forever. Basically like.

B

Helping out people that kind of thing uh helping, I don't slack in like forgotten communities, that kind of thing, um and in doing so I basically like I started contributing quite heavily to hyper and building plug-ins for hyper.

B

I burst this terminal that uh versailles built um back in like mid 2016 or so it was released, and shortly after that, I started contributing to it um and after a few months of doing that, like all in my free time, basically, um I, uh like kissimo, the ceo for sale, resets me was like hey we're working on this new project called uh nextgs um and since you're doing like all this php stuff, you might find it interesting because you're building, like this full stack, ish solution for building front ends.

B

So it's like oh cool, I have luke um and then I basically started contributing to that also um and eventually shifted focus to like only contributing to nexus um yeah. This is all like still in my free time, like working full time and then next to it all working on open source um and then eventually, I conservative so much that they were like hey we'd like to make you a co-author of the framework.

B

um So that happened and then a few months later, I think I I reset to the family was like hey. If you ever like want to hire someone to work on this stuff or whatever, like please reach out to me, because I'd be super interested um and then like a few months passed by again um and he was like hey. Do you want to come to san francisco for our first conference or organizing?

B

um I had never been on a plane before which was interesting.

A

B

Yeah I had never traveled alone, like all that kind of stuff, but it's like okay, oh I'll, see if I can go um and then eventually that happened got offered a job which I didn't take for various reasons. um But then, a few months later I was like hey. I really want to do this like open source stuff, uh because next growing a bit uh more adoptive and larger companies that kind of stuff, and then I was like hey I like.

B

If you still want to hire me, um then I'd be super up for it um and then I eventually got hired like at the end of 2018. I think you know 2017 actually um and yeah ever since then, I've been at for sale um working on next year, full-time uh and in doing so like build a bunch of other of projects. Also.

A

Yeah, so between the time of your good first issues uh in the time you were sort of approached to get hired the first time like, what's the time span between that.

B

It was like over the course of like six months or so wow yeah. If I had been like just basically, I started uh contributing because I wanted to learn more about react, uh so I had learned react through basically reading the um hyper source code, cyprus built on react, also um and then like they say. I just only kept going because I was like. Oh I'm, actually learning a lot of stuff that I like didn't know from working at this company.

B

I was working at at the time, so eventually they offered me a job yeah to work on it.

A

Yeah, that's that's wild and, I think that's uh I mean I'm not sure about all all stories and open source onboarding, but I think it's similar to mine, like I didn't, get hired to do open source at the first company I worked at, but my interest in learning how the projects were made and how to sort of like contribute back to the things I was using.

A

Pretty heavily is a similar onboarding experience for a lot of people um around getting an open source, and I think, that's actually pretty pretty awesome to say that um everybody everybody wants to like get a job and everybody wants to level up their career, but they're all super like unclear of like what pastor I am, and I think open source is like a really cool path to approach.

A

If you want to get a job at a company, um there are a ton of companies that are doing open source so like for sale is like not the only one out there. That's doing this um like github's another one that does this um there yeah there's quite a few of them out there and, like the um I'm glad that there's a way uh that uh companies can actually put their stuff out there and have people participate in that too, as well.

B

Yeah yeah, for me, it was mostly like american. Open source was like a hobby for me, um but then, like I, I basically like got offered to turn my hobby into a job right. So.

B

But um if, like you get to work on open source or whatever, um you still have like all the contributions that you did are very public right. So uh even if I would go to like I'd, also like, for example like in that time frame, there were companies that were using next, for example, and I knew it wasn't working at uh for sale at the time so they reached out to me they were like hey. We want to offer you a job to work on like our next, yes apps right.

B

um So even that was like one of the possibilities I had back then um just one con from conservating a lot to a certain project, but it doesn't have to be like next. For example, it could be like any project that is used by uh larger companies or even like smaller companies that just like do agency stuff. On top of it.

A

Yeah, so I'm actually, I want to transition us into uh talking about uh the project. um I'm curious. If you could explain next js, I guess and uh a sound bite or maybe a paragraph like what is next.js and like what is what's it for its purpose.

B

Yeah, so our tech line is on getup is basically the react framework for production, but uh the like more lengthy explanation is that building react. Apps is really hard. um If you do it all like manually, like setting up all your uh like build tools like figuring out how to do writing figuring out how to try to do data loading, and even if you figure all that out, it's still really hard to get performance right, for example, and do pre-rendering like service or rendering or static generation.

B

um So next basically comes in there and it's like a framework that you use to build, react apps. um So this is either like websites or web applications, and it basically helps you with like guiding you towards a part that makes your app the most performant. It can be using react and optimizes a lot of stuff. In the background for you like, it focuses basically on providing a good user experience, but also a good developer experience, so the developer experience part.

B

Is there like automatic culture reloading like um giving you really nice set tracers like that kind of stuff is all like in the premise of what next helps you do basically,.

A

Yeah and there's a yeah just looking at this, uh I'm sharing the screen as well. I haven't shared it to you, but I'm looking at the next js homepage and there's quite a few of people, including twitch, actually who just stream right by who are using next in production too as well. So not only is this an open source project, but this is a project, that's actually being leveraged by a ton of companies too as well, which is a yeah yeah. It's pretty cool.

B

Yeah, so it's the nexus being used by um like tons of alexa top 100 uh or so companies, which is like really massive websites, um so think, like the scale of like instagram. uh Those are not using next but like, uh for example, the um like largest news website in china, uh qq.com is using next for its mobile platform, um which is like the fifth largest or so website of the internet according to the alexa ranking.

B

um So it's like it goes from like really massive companies um to like very small websites, like your personal website like, for example, my personal website um or like a blog or something like that.

B

But yeah you have like the whole spectrum of different companies using it.

A

Yeah so curious if we can transition into um the actual github repo as well. So let me go ahead and uh transition to sharing my screen as well.

A

So that way, you can see the see this in real time and everybody else can see this in real time.

A

So I got the github repo open up here and I'm curious of like if, if I walk into this thing uh first time like what do I do to, I guess be the next tim notkins as well to find good first issues like what's what's what's first step if I want to participate and learn how to use next.

B

Yeah, so um basically, we have three tabs uh like issues, pull requests and discussions. um Discussions is something new that we're working on with the github team. Actually um so like the first thing that you could do, if you want to contribute code um is or if you want to contribute like to the community itself, is using discussions to basically help out other people.

B

Right, like someone ask asks a question, uh you might have the answer to that question um because you've been using next or you are like starting to learn it, and you want to figure that out for someone else.

B

So a lot of people ask questions on discussions and it's either like how do we do this or how do we do that that kind of stuff- and it allows you to basically like engage with other community members uh that have questions or like want to discuss some like new features, for example, uh and give your like input back? Basically, then, besides that, if you want to like contribute actual code, um you can use the uh issues tab where, like you, have a good first issues label.

B

So one of the uh things that we do is we mark issues that are like relatively easy to do um like there. There is a spectrum there, even like. Oh I'm, actually like really experienced with like this whole, like reacts and uh compiler thing, so you can help out there too, but the most basic thing is like helping fix examples.

B

For example, so we tried to mark a lot of issues as good first issue and there's actually a lot of people that come in and just help out other people that have issues or people that want to like make changes to examples that they don't know how to. For example,.

A

Awesome yeah, I'm curious of- um and this is uh directed to chat to that's here with us today- anybody just pop in and say if you're, a next.js user. If you have experience in react, I'm curious of what the gauge uh engagement we have or even the opportunity we have today uh for people looking to contribute actually shout out if anybody is listening and they are a contributor as well um pop in the chat and say hello, I'd love to give you a nice little call out yeah. So that's nice! It's um that there's yeah!

A

This is a lot of green too as well. Do you guys actually purposely uh use green for uh good first issues and help wanted.

B

Yeah yeah, so a good first issue is generally like we generally mark them both because um most of the issues are actually like. A good first issue that you can help on, um but like things that are only marked help wanted. So no good first issue are like slightly harder to do, for example, um but still like requiring more effort or like more uh knowledge of the framework.

B

um But besides that, we tried to market like many uh issues that are really easy to do as good first issue, so that we um can basically like free up our own time to work on like larger features and that kind of thing.

A

Awesome and that something I actually I told you about this before we jumped online, but uh if you went to that same uh uh repo and slashed uh put slash, contribute um which I'll put that in the chat for anybody who did not catch that. But um actually I'm gonna drop this url in the chat completely. So everybody can follow along.

A

It thinks it's the command um yeah, so github recently shipped a feature, probably earlier february, where they're using machine learning to not only find good first issues and help wanted so like we do see a lot of green, uh but we do see a couple of these ones where you see example, and it's because the machine learning sort of inferring that these are even though they're not labeled, or they are labeled good first issue.

A

But um I think this one down here, which is only documentation, this one's labeled as a contra like a good first issue to contribute uh because it's documentation. So um if anybody's interested in sort of like jumping on the bandwagon and participating in naxton, who knows? Maybe you can also be a co-maintainer or have a a nice career at uh or versailles working on that full-time.

A

As well so yeah definitely check that out, um but before we jump into some of these issues, I wanted to see if you can help us give like a tour of the repo itself, because I know this is built on react. But uh my some of my issues for contributing open source is that I just have nowhere to know like where to begin like I've never worked on this next.js project. I don't know like. I know, there's some examples. I know there's a getting started guide so like.

A

Let's make the assumption that someone's built an xjs app or they know react, but they want to contribute to the project, um but they just don't know how to sort of navigate um the code structure. So what.

B

Are some like good.

A

Tips for people to for navigating the code base.

B

Yeah, so uh the very first thing that you have to do because otherwise you just can't run like some of our tests, for example, is like go to the contributing data md, um which is right.

A

Here there yeah.

B

um And like the first thing that you have to do, uh if you scroll down a little bit more um because this is just installing the repo okay. But if you want to run the test, you actually have to uh install chrome driver.

A

B

Like we basically uh install uh like we run tests into end tests that are basically running a full browser like full chrome or full firefox, for example, and chrome driver basically helps you run chrome through, like this interoperability layer. um So that has to be installed or actually control the test. um But besides that, everything else is just like running yarn and then yarn depth and it works um as explained in like a little bit further up the uh contributing to the nd.

B

uh But let's just dive into the code base, because uh that's probably like more interesting to go through.

A

Yeah so going back to the the home page, I've got a bunch of. I got a couple: dot files vs code files, which is pretty cool.

B

Yeah yeah, so um basically the dot get up like contains all the the github related configurations. So that's not really interesting.

A

But speak for yourself configuration yeah just kidding.

B

No, like the those configuration files that generally don't change right, that's what I meant basically.

A

B

So like they, they contain, like the give actions that we use and all that kind of stuff um infuse code is just if you're using vs code. It like has some extra rules. There um bench is not used uh directly by users, uh but the most interesting folders are docs errors, examples and packages and tests, of course, so starting with docs. Those are obviously the documentation of next.

B

If you make a change there, it automatically reflects on the website if it goes too stable. um So we have a docs uh section on the website uh as you're showing, um and it also is like index through augolia. So if you like, search for anything uh in the search bar, uh it will automatically like find that update that you made, for example, okay, excellent, so yeah that works super well.

A

And you mentioned.

B

That this is indexed.

A

By algolia is that what you, sorry, you cut out for a little bit: yeah, okay, awesome.

B

Yeah, so we like run. Actually we run that through github action so like, if you uh do a new commit, it actually runs through get up action then, like indexes that new content, basically.

A

Really sorry, I'm going to take a timeout just to look at. That is that action live right here in the github folder.

B

um I am not exactly sure I think it lives in the um the next site, repo, which is a separate repo, but.

A

um Well, good to know that they're yeah, because sometimes that's another thing that could be confusing, is knowing, if I'm looking at this site. How do I make an edit to this dock and this you're evening? The old docks live here. Okay, but is there a way for me to know that there's two different repo.

B

Yeah, so if you scroll all the way down, you actually get a edit and get up, um I got it.

A

B

Yeah, so you can do that, um but and that gets you, the the exact like location inside of the docs folder um that that page refers to right. um So first, you have to like focus repo et cetera.

A

Et that you actually fork this uh directly yeah yeah awesome.

B

Yeah yeah, so this is all using the the normal ui but um yeah. Let's go back to the the folders.

A

Yeah, so we were back here.

B

Yeah, so if you go one pack, uh because this is just the documentation right like these- are the separate uh directories uh for that. um So then you have errors, which is an interesting uh thing that we have in most result projects.

B

uh We have like this error, dot, sh links that allow you to basically like link to a uh markdown file inside of the git of repo yeah and that's called errors. So if you go to error.sage slash next year, slash like 404 get, uh I couldn't read the rest of the thing, but like any of the urls here.

A

B

Will work and inside the code base we use these to like if there's a warning or.

A

B

To always give you a link that gives you more context to that error. Okay, because, like generally like this message, uh if there is an error, drone is not super clear to users like oh, you forgot this configuration or whatever, um but then you can actually like see like. Oh, how can I fix this, or uh should I do something else, and that kind of thing yeah.

A

That's clever: did you get this from another project or how did who discovered to sort of have your error templates.

B

Built into the project.

A

B

I think I think it was based on the react, um like the idea like that react has, is that uh they also show you like minifigure minified errors, so they basically like give you a link every time an error is thrown in production, uh but we actually like expanded that to like just in development. We also show these okay awesome, um because it gives a lot of extra context to like what you can do so yeah. Let's go back to the overview.

A

Oh sorry, let's go outside yeah, we talked about docs, we talked about errors.

B

Yeah yeah, so then you have examples which is an uh directory of nexus examples. uh It's a massive directory. That's like 200 examples, yeah.

A

B

It's like all these different things that you can do with next, like integrating with some other libraries right like how can I use stealth components, or how can I use redux or how can I use apollo or that kind of stuff, and this directory holds all those examples on how to like do these integrations? Basically, uh and this is like what most people contribute to, because this is like very easy to do for uh if you've used next before, like these are all just next steps.

A

B

uh That you can like make changes too. Basically um so yeah, uh let's go through like how to set it up, and that kind of thing.

A

Yeah, that's well real, quick. I think that's super clever to have your examples also live right next to your code, and it's also. I appreciate you mentioning that too, as well, because, like people might not know where to start um it might not, maybe they want to change the documentation but there's no real good or hard doc problems that they want to tackle yeah. But I imagine like between, uh I think next js did they have a version that was out in the so yeah what 9.3?

A

So I imagine between 9.3 and 8 8.0 like there are some changes that need to also up be updated and reflected in all these. So is there like a normally a call out for con uh contributors or to help with the yeah.

B

So we yeah we did this for 9.3, because that was a really massive release like we. We changed one of the data, fetching methods so.

A

B

Have like two variants like one is, get static probes when it's got server-side props and basically, we had to like update all the uh existing examples to not use get initial props.

B

um So what was interesting, though, is we created an issue that was marked good first issue, and then I tweeted about it and like within, I think, like four hours or something like we had put requests for. Like almost every example, there was really.

A

B

um Because people just like jumped in and they were like- oh yeah- I can do this because it's like I've actually done this before. I know what I'm good.

A

B

How I can do this um for like most of the examples. uh That's also why we have like 94 open pull requests right now, because we just have tons of example, updates that we still have to merge and go through and like review and that kind of thing.

B

um But we obviously like keep up to date because, like we work on this full time, um but there's like a constant ever since that release like there's a constant stream of new for requests, which is quite interesting.

A

That's awesome, yeah and I'm just looking at. I failed to mention too as well like this. This project's got 47 000 stars and uh I didn't actually catch the. How many contributors are there but like this is a over thousand yeah yeah. This is uh yeah, that's that's! That's amazing. They have so much activity and so much so many pull requests to actually review. Are you reviewing all those pull requests every day.

B

Yes, wow, like my my get up, notifications are like over 100 every day or something like that for.

A

B

uh And it's only next like not even like internal for sale, stuff or whatever so yeah, um but yeah, it's manageable! uh I'm really happy about the new notifications ui, because that really helps because I can like filter down on notifications now, which I couldn't do before, um but yeah it's it's a lot of work, but we obviously like try to keep up to date on, like all the issues, all the requests uh there's just a lot of traffic like if you get to the like.

B

If you build a project- and it has like some traction- um you you get a lot of uh issues etc, but once you get to like this kind of scale of project, it just becomes like a constant stream of updates. Basically um but yeah. We we tried to go through all the issues and all the requests, and basically every discussion also uh just to make sure that, like everything's up to date, um yeah, that's a daily job for us yeah for sure.

A

Yeah, it sounds like you need. um You need some like triage interns or um some open source contributors to to be your triage in the morning at least find somebody. That's uh the time zone be before you, so that we don't have 100 uh prs to go through.

B

Yeah, so I'm I've been mostly doing like, uh because I have a team of like four or five people now uh at for sale, so they all work on next. But I try to do the triaging myself because I'm actually in the time zone before all of them like before they all get online like I have six or seven hours or so uh so I try to go through them all so that I can like pick out like critical, bugs or whatever, and then then I can basically ask my team like hey.

B

Can you like look into this or fix this um next to like the normal road map that we're working on? Basically.

A

Very cool so yeah, so we talked about examples and uh sorry. I had to digress you into. I just thought that was super fascinating, that that's a nice little entry point for individuals to start contributing. Is there a pathway like? Do you see, um individuals who might not work for versailles or zeit and um end up showing up like on a regular basis? As far as contributions like? Are there any sort of next experts that are out there.

B

Yeah so there's uh on discussions, we get a lot of people that are actually like helping out other people uh very consistently um on pro requests and issues like we. We get less so like the same people, but some like there's, probably like six or seven people that are very active still um on, like all the requests, all the issues um if it relates to their work mostly um and yeah yeah.

B

So so we have a bunch of people that are are very consistently contributing uh through either like leaving comments or that kind of thing um and yeah it's it's like. Overall, you see a lot of um like dressed in contributors like there's, new consumers that come in and other contributors that, like might not contribute anymore or um they're like just like working on other stuff. Basically, but overall we see a lot of people that, like consistently keep using next across, like multiple projects that they do and that kind of thing.

A

Excellent so outside of examples, I guess that we want to keep going down there. Let's go back yeah, then a little trick.

B

Yeah, so here here's where it gets interesting, uh so we have packages and tests. So let's first go into packages.

A

So, in the context of.

B

A

What's uh what is a package.

B

Yeah, so packages is uh so we use learner for um the managing of our monorepo, so uh packages in next is just like npm packages.

B

So all the uh directories that you see here are npm packages, um so in this case, like the main thing that we're looking at is generally next right, like the next package, um which is what everyone installs whatever uses, uh but we also have like create next app, for example, which creates uh nexus apps. If you start out a project, for example, um so yeah, let's first go into next.

B

The rest are by the way, plugins or like other add-ons, that we build on top of next. Basically, so.

A

Wait sorry, so this is the the package version of next, so we were just on an xjs repo, but this is what's going to be up on npm yep, gotcha, okay, yes,.

B

Yeah, so the next repo, like it started out being like one repo with like all the the director like all these directories were basically in the top level, uh but as time went by, we basically like started adding other um like plugins, for example right um and those are moved into like the same monorepo.

B

Basically, so we have like this, like not very large mono refill because, like most of our code is inside of the next package, because we try to build in all the features that we want instead of like attacking them on in separate packages.

B

But this is basically the like actual next code that everyone uses. If you install next.

A

Okay, excellent, that's good to know too, because I've done some some work in open source and uh and also like sort of try to debug problems. So I'm always a little bit confused when it comes to like how different projects sort of packaged a project and like deployed their versions npm. um So I usually it's usually me hitting a bunch of ceilings and then asking a lot of questions. The people who maybe have experience with next or even just asking questions within the in the issues.

A

But it's nice to see this sort of laid out uh to understand that if you do have an issue, perhaps on a certain version- and I wonder what the if these are packaged, um how do you go about the diversion or do you then? Every time you do a new release, then you update these packages. Is that I guess the way it goes.

B

Yeah so uh lerna does uh like that's an npm library uh that you can install to manage your monorepo and that basically also manages cross dependency dependencies.

B

So, for example, if the next package depends on another package from the like next month, repo, it will actually um like update those versions also while publishing so an example of that is that, like we have like a like one package, uh if you go back to the the next repo, uh I can probably show you.

B

So if you go back to packages, um you basically see like one uh that is called next polyfill no module um and that one package which is separated out um is a dependency of next so basically like. If you install next, it installs this package too, and what learner does? Is it basically um updates this version?

B

So if you release like uh 9.3.7, it will update the next package version for next polyfill, no module, also, uh which is super useful because, like we obviously can't do this manually, because if we do that, it will definitely like we'll screw it up sometime and then, like all the packages depending on the next little break or all the projects.

A

Yeah faster so.

B

Yeah, so that's all like automated out and then our release cycle itself is um we basically use get up releases as our mark for oh we're going to release a new version, and we do this with pre-releases and um stable reduces. So the pre-releases are called canary releases, okay, um and we do those very often like almost every few hours uh if we're working on something- um and these allow you to basically like install next at canary to try out new features and try out new, like bug, fixes patches, yeah.

A

B

Of thing, so this allows us to like, if you report a bug, for example, to provide a patch and then basically release it immediately to like the canary branch, and then someone can actually verify if it works for their app without us needing to like have access to their app like try it out that kind of thing.

B

um So this is really useful, because, like building next from source is like kind of hard to do, um as it depends on like a bunch of other projects and that kind of thing. um So this allows us to like basically have a faster iteration uh loop for us to like leverage. Basically.

A

Yeah I appreciate yeah. This is like, I wasn't sure what to expect and uh doing these open source friday chats, but I'm like just blown away on you just sort of explaining the the process and how you manage projects or manage this project because I've never I've worked on some large applications, but not to the scale of next and not to the scale of how many people are actually installing it and downloading it are you um do you know the offhand how many uh npm downloads this thing is getting.

B

Like I don't know, I can look it up. Actually, um let me see.

A

Cool- and I just want to also um just uh while you're doing that just mentioned uh stewie had mentioned uh in the chat studio, 443 um sort of this- also being blown away by the examples uh earlier as well so yeah. I appreciate you uh mentioning that um also, if anybody has any questions for us, we're gonna take a break at the end. To answer any questions, so keep those in mind. uh You do have tim here, uh who is the maintainer for next.js? So if you have any next-gen questions.

B

So I looked it up and it's um 540.

B

So it's 546 000 downloads per week um and yeah. So so that's quite a lot of users. Yeah.

A

I mean that's, that's if.

B

Something breaks we know it immediately, so um we basically like what we do is we have a very elaborate test suite that does like almost only end-to-end testing. So that means like we run it like we're in the actual next command.

B

We boot it up as like the next step server and we run like an actual browser as a chrome, for example. uh That does all the testing for you um and that's all run in ci so like in get actions, but also azure pipelines for windows support.

B

So we actually like uh test it out on like windows, mac and then also in multiple browsers, so like one of the browsers is um like one of the extra batch, so it's obviously chrome but then next to chrome, we also run into firefox, safari and uh internet explorer 11 in order to like make sure that things don't break between versions for like most of the users, yeah.

A

And remind me: how is that testing happening.

B

uh It's in the test directory.

A

Oh, that was the uh yeah yeah. Oh, we haven't got the test directory yeah.

B

So we have saved.

A

We'll save that after we get that with packages but um yeah the package thing uh super fascinating. I'm glad to have that sort of insight. uh I don't have any next. Actually I have one next project, uh but I don't really touch it very often, but I am looking to update my uh my main site. Brian douglas. me, so uh I'm on the uh on the prowl for for projects to mainly react projects to uh support debts, but you are you're convincing me now that I know how to contribute to this.

A

That perhaps nexus might be the way to go.

B

Yeah, so if you go into the the next directory, um you'll you'll basically like get, um we have to wait a bit. So if you go into packages and then the next directory.

A

Sorry is it one more time the next directory.

B

Oh yeah, I probably could add if you go to packages and then the next directory, oh gosh,.

A

Which is literally.

B

Next yeah gotcha yeah, it can be confusing naming sometimes.

A

B

A

Yeah that in cash and validation, those are the two hardest problems.

B

So um yeah so in in here we basically have all the like actual code for next, uh so they this goes from the development server to the like build pipeline uh production, build server, and that kind of thing. um So all of the uh because you see a lot of files in the main directory right yeah.

B

So these are all the files that are published to npm and they have to be in the top level because, like you, import next slash link, for example, right yeah, and then those like basically require from like another place in the repository in the directory structure.

B

um But it basically goes from like bin is basically like the next command um so like the actual, like next command that you run um and that imports from another directory. So you basically see the references to cli.

B

If you go back and then go into the cli directory, it's in at the top of the yeah page yeah there um and those are like the separate next commands.

A

B

So you have next build next dev next export next start, um and these are the ones that are like actually executing the code. So here we import like for start, we import server, lib start server and that boots up the next production server um and then like that is like where all the code lives that actually like handles. Your requests like server, renders reacts, and that kind of thing.

A

A

Just lost you, oh there, you are.

B

No, I was just silenced for a second yeah.

A

It's like you're, really thinking about it.

B

Yeah so like, uh besides that, there is like the the production build of course. So if you go back to the the next directory, um we also have like a very like complicated, build pipeline uh that builds on top of webpack. Okay,.

A

B

So that's all in the build directory uh so like the naming of the directories, are pretty straightforward, like we put everything for a certain command into a certain directory.

A

um And this, like, I think, the versailles, the naming for a lot of the projects are pretty like now is pretty pretty concise. So I appreciate naming uh that's been coming out of a lot of your projects as well.

B

Yeah, so we tried to keep it as simple as possible, um so basically, the the build directory like holds all the infrastructure that is needed for um running your production, build and running your development build so like our webpack configuration you can like find it here. uh It's in webeconfig.ts.

A

B

um It's massive yeah uh warning no, but like overall, um it adds a bunch of like custom, epic plugins, that we use for next, um and it solves a bunch of like books that we had with like server rendering uh using webpack and kind of thing.

B

So yeah um and then like. Besides that there is like a bunch of other directories like export for doing static, exporting and, like all that, so.

A

Cool well, I think that's like a good peruse through packages. uh I'm excited to actually talk about testing now and sort of how next yeah does testing, because, as you mentioned, like all the cross browser testing, I mentioned, you also have to test different versions of perhaps node, because maybe some people are on 12 or 10, or maybe eight and trying to do this. So is that all accomplished yes within here.

B

Yeah yeah for sure, so we test against the lowest note mark, so that is note 10.13 or something like the lts release, basically, um which is the one that we support so like anything after that works in node.js. So that's good, and then we basically test through mostly the integration test suite. So that's in the integration directory.

B

So if you go into there because the rest is all like, mostly um like separate tests for like very specific cases, but these are the most common ones that we write so um in general like, if you look at any of these directories, you can open any one of them.

B

Just choose one. I don't mind which one so this tests the um s path for a certain writer feature, um so it has a test directory. But the main interesting thing here is that this is just a next app.

B

So if you look at the like main directory of the of the um of the test, so app the app dash s path, I gotcha um you see a page directory and the pages directory is just like the next.js pages directory and the underscore app and index.js are just like normal nexus. App files.

A

B

uh And it looked like normal, also right. um The only like catcher is that we generally like introduce like specific bits that we want to test right like um in this case. We wanted to check if, like the url s, path um was provided correctly in other scrap um so like in index.js. We just like stringify the prop so that we can then read them in the tests themselves yeah. um So what this does is like.

B

Basically, if you run this test, it boots up a next app this next step, and then it boots up a browser that then fetches like then opens like the the homepage of this app right and then what we can do is you can basically do like assertions based on like oh, what's the document body or that kind of thing.

A

Very cool, and then the this is this all running on. Is this? Where you start talking about the cross browser stuff? Is that where it comes in.

B

So that's all the most interesting thing is that it's, this all happens automatically. So if you go into the um one good example, it's probably the production test suite. So that's literally the folder called production.

A

So a lot of files.

B

Yeah, so we have tons of these and these all ensure that we don't break next, yes, features uh when we release a new version, so we have a really high confidence in like our test suite.

B

uh If you make a new change, we basically immediately know if, like you, broke the next app or not, um by running all these tests. So if you go into the test folder here.

B

And then into uh dynamic.js, for example, um I think that that was one of the cases where it does that yeah. So we actually have this uh custom webdriver implementation called next webdriver, which is provided like in the repo, um but basically anywhere. You see, webdriver being um like, for example, in line where your cursor is right. Now uh browser is a weight. Web driver right, yeah that one, um so that actually boots up a webdriver instance and webdriver under the hood basically allows you to use multiple browsers to test against.

B

So what we do is basically, we have a separate test suite for like internet explorer or firefox or safari, but they all run on the same uh layer which is webdriver um selenium and those like that basically means that you write the tests in the same way always, um but you can run them on different browsers if you want to so that's what we do for like a bunch of our.

A

Tests awesome yeah that that kind of answers. My my question on the the cross browser sorry, I was just distracted by looking at my audio level, it's the uh being uh interviewer and producer. At the same time, it's uh all over the place, yeah very cool.

B

Yeah, so what you can see in this test, in particular the the one that you highlighted, is that, like you, boot up the browser and it goes to slash dynamics like no chunk.

A

B

Then, basically, there's a like some helpers that we built that basically just do a loop of checking if something is set on, the body uh called welcome normal right and if that doesn't come out it just crashes after like 30 seconds of trying, and then you know that it doesn't work anymore, yeah um like if you make any change in next that breaks this behavior. You basically know it immediately, because this is running against the real next app that uses this feature.

A

So I'm curious because, like I keep going back to the fact that you, between six months of you first doing a good first issue and being approached to work on this full time, uh the first time was next. This sort of, like I'm gonna, say complicated or intuitive, or was this project much simpler back then, and uh you sort of built all these sort of systems.

B

So this system has been around since the I think. First stable release.

A

B

um Because it was built by arunoda um who started contributing to next, actually very early on same as me, but eventually he went to do other things for sale.

B

uh So currently he works in, like our infrastructure, like back-end team, basically um on actually one of our github integrations and like other things, um and he was very like he's very uh seasoned in open source like he worked on a lot of meteor projects uh and like started storybook and that kind of thing- um and he basically was like oh, we need to have enter integration tests for everything, um so he was basically the one that was like, basically like slamming uh his hand on the table being like hey.

B

We need to have these tests like on every pro request that came in like hey, you need to add a test, um and because I was not that much like that, like oh, I was like. Oh I just built this feature. It works right, um but then he was like.

B

Oh, you need to test this thing because otherwise it's going to break um and then eventually like, I basically adopted that style of like oh, every change, has a test included um and I basically kept enforcing it on other people and that basically, like gave us the shape of the test suite that we currently have, which allows us to move a lot faster, because we know if something breaks when you make changes, because we test pretty much every feature that we have and if it's not tested or you report it back.

B

We add a test with your specific case um into our test suite because it's already real next steps right, yeah so like. If you report a book uh like something is broken or like, whatever I'm doing this in my app and it breaks now that I upgrade next, we actually add in the same exact like that file um to test again so that we know that it won't break in the future. Like you don't come back to us and be like hey, I did this like five months ago.

B

I referred this to you and now you broke it again like. Why are you doing that right, um which is obviously not the experience that, like open source users want, um but it's something that you get more often than you would expect from like most libraries, because they don't have like super complicated test setups, uh which is super logical right, because I was also like. Oh, why am I going to do all these tests if like no one's using it or whatever right, but then, like once, people start using it?

B

It actually becomes like reliant on that.

A

Yeah, so I'm curious and also conscious of time too as well. um I want to see if we could uh walk through a a good first issue as well, um and maybe, if you oh looks like I spelt, contribute wrong. I know I deleted next, that's what happened there. We go, um and perhaps I I guess, one of these little exercises. If we grabbed an issue, could you talk out loud like how you would approach it, perhaps in like maybe give someone like sort of like a underhand pitch yeah?

A

um So perhaps maybe I'm not sure. I'm.

B

Not sure how you do this yeah okay, so the first one was a pretty good one to walk through, because it's like adding a new functionality to the create next step. Okay, excellent.

A

B

In this case, this person created a book report being like hey. I want to uh basically send dash e or dashes example to create next step uh with the value of default. To basically pick out the default um example right so uh previously like what we did in like older versions of next was like. We just gave you the default example, but.

A

B

Basically, ask you like hey: do you want to install this example, or do you want to use the default value, and this is where, like this broke, basically for his use guys because um he wanted to use like distant ci or something like that, um so it should basically auto select default uh when you do dash e default. So, basically like bypassing that check for hey, do you want to um create a uh example?

B

uh Do you want to use an example yeah? So, basically, I replied like hey we'd, be happy to like add this functionality dash e that def e default, um so someone already created a podcast for this yeah. This is.

A

B

Is yeah, so this is like some like contributor um that is pretty active on the project and that tries to help out a good first issues, um but given that we don't have that much time, it actually might make sense to like go into this like pull request, because it basically shows like which changes were made to make this happen, and it wasn't made by me right um so.

A

B

If you go into the diff you, basically um because it's only one file uh so create next app, um is that package right.

A

B

Next app- and that has an index.ts which is the create next step command um and then what it does is basically it checks if, um like example, is set there, so you have create a create app with the example parameter um online, 171, yeah or 72 now, but basically, what it this allows you to do is um provide like which example has to be installed.

B

So what this like, if you don't provide an example, it just assumes that it's the default um template, and so basically, what uh james, if I remember correctly, I did- was.

A

B

He moved out the check for that uh to check if it's uh a string um and then well obviously it's the same code but then, basically, he added in the extract check. So example, if example exists. An example is not default, then provide example and otherwise do undefined.

B

So what this means is that if the example is set to default, it will be undefined, so it installs the default uh template.

A

Awesome and like this seems.

B

Like super approachable.

A

Too, as well like uh yeah,.

B

It does take like knowing where to.

A

Go what to look, but the the solutions seem pretty straightforward.

B

Yeah so overall um like this is just like one, one line change right, um but even if it's a large exchange like it's generally like in one or two locations um that you have to like make these changes um so yeah. This is a great pro request. That's done by like an external contributor, um and we still have to review it of course, but like overall, it looks pretty good.

A

Awesome yeah, so I appreciate you walking through that too, as well. That said, uh yeah be helpful for a lot of people to see. Not only did we walk into this and like see how packages work and see how the testing works too as well, because that's a lot of times like I can open up a pr, but I have no idea how to get the test to run um so like knowing where the tests live and sort of like some of the hoops you have to jump through.

A

That's super helpful um we're at pretty close to top of the hour, so I did want to leave some room for questions like do you have a hard stop in the next few minutes.

B

No I'm, uh I don't have uh like anything else after this. Okay should be fine.

A

Cool so yeah, maybe we don't have to rush uh through the questions, but if anybody has any questions about next, um please leave them in there in the chat too, on twitch and we'll address them in a moment. But while we're waiting for those questions to come through, I'm gonna actually actually I'll keep the screen share going uh because I wanted to I mentioned I wanted to do this little exercise.

A

There's a um do with the github.com stars. You can actually see the last star that you've starred as far as repo goes, and uh so these are my stars. uh You can see I've done 551 stars.

A

I used to start projects for saving for later back in the day, and then it got to the point where I just was starring too much stuff that I could not sort of uh uh figure out what happened or what I started before, and then I discovered github.com and I'm like oh excellent. Now I can see like I'm a big fan of javascript projects. Apparently- and uh I tend to my my pattern- is I actually whatever I'm working on if this solves my problem, so I was working on a chat bot for twitch.

A

um I am uh I'm sticking to get stalker yeah. That's uh the last thing I start, um but yeah I've been trying to work on a chat bot, so I looked at a bunch of twitch apis and sdks, and I've been starring that I've also been following a bunch of uh twitch streamers, so I've started a their chat bot as well, which got me down this. uh This rabbit hole, but I did want to talk really quick about get stalker, uh which is this here.

A

um Git stalker is a little command line tool, um which is uh it's it's a lot of fun and it's uh it could oh yeah. I should definitely look at the uh the ascii art. That's there too, as well, uh but yeah, it's a it's. I think the project's less than like a week old as well. So it's only got six stars, so everybody um who stars projects- please, oh, don't use get stalker on me. um Please uh do that.

A

uh So I actually distaled uh you uh tim and I could see that you have uh well. This is your bio, co-author of next.js and mdx, and probably this actually pop that out in the beginning, and we could uh uh everybody see the intro but um yeah and it's it's cool to see like you have 204 repos. uh It actually tells you the languages that you're, um I guess, you've sort of touched or is yeah.

B

A

And then also we can see uh that you've closed a bunch of issues too as well. So if I want to yeah um sorry what was a command, I'm gonna stalk myself, because I didn't actually do this on myself.

A

So I'm talking myself um yeah. So this is my bio host of mutual fund live yeah. That's come directly from github, oh, I didn't actually see when you joined either but uh 2013 of october. That's when I created my github account. No, I'm not looking for a job yeah. I thought that was really really neat. So if anybody, uh um if anybody is interested in checking that out, I'm curious. Also, um if you have, I guess what was the last project you starred.

B

So I actually had a bunch, but uh I don't start that often so like if, if I'm starting something it's something really good. Oh.

A

In general um man, I hope that one day get a star.

B

For you know um so, like the last thing, I started that wasn't something that we built ourselves um was denno the new javascript runtime typescript runtime. How do you, how do you spell that uh so d-e-n-o do you know.

A

Yeah, you know yeah, we'll see if it pops up.

A

Is it this yeah.

B

A

It okay, very cool.

B

Yeah, so this is basically um something that uh replaces note as the runtime for javascript um as building rest, and it looks it's super interesting um and it's still very much in development but they're working on it pretty heavily. So I'm super curious where it will go and then something else that I had was wallace cli um I'll, probably send it to you in a chat because.

B

Otherwise, it's hard to get that over because it's very long night.

A

Yeah and while you do that I'll figure out how to open up the chat.

A

B

Yeah, so this is a um tool to basically analyze the css on your website. So if you, um basically, if you scroll up, you can go to the website, that's like probably a better way to show it.

B

Sorry say that one more uh time you just cut out okay. So if you scroll up to the the website, that's linked yeah and go into the website, it's probably a better way to show it because you can also keep track of other websites. I think um you should probably go to the homepage of the website. Actually uh is oh okay, gotcha yeah!

B

A

Click a live demo.

A

Live demo that always gives me uh yeah yeah for sure.

B

Yeah, so what this does, is it basically analyzes your css? So if you give it a website, um you can basically see like how many selectors you have properties like all that.

A

B

How many lines of code you.

A

Have where do you add the website.

B

I think you have to log in actually.

A

B

I was, uh or maybe you have to go to the home page and then like say get started, but.

A

B

You I'm not exactly sure.

A

Okay yeah: oh you.

B

Have to create an account I'll, create.

A

Account some other time but uh yeah. I.

B

Definitely want to check.

A

That out, because uh yeah, my css, I use uh style components on my main project that I've my set side, project yeah, um but I'd be curious. How it's it's analyzed, um mainly because I've I've been aggressively deleting my index.css as I move stuff to style components, but also because I know I'm bad at css, and I do a lot.

B

A

Like I do a lot of like not great things in css, so to keep myself good and honest, and I can also have people contribute with me. I try to like try to keep best practices, but I will definitely check out uh project wallace for sure yeah.

B

That one more thing, that is uh something that we built, but someone on my team built it's a git of action to keep track of size increases of javascript uh of next itself. um So if you go to pro request in next js yeah yeah, but it's open source. So, like I sent you the link in the chat already, but.

A

B

If you go to um like, let's first go into the proquest, so like click on pretty much any pro request, you want sorry, I just clicked the link in.

A

B

A

B

Take this one, for example, um even though this doesn't change next itself, but you see those stats from current pr yeah. That's a github action that basically like uh clones, your request and the nexus canary, slash master wrench, and it will basically like try to figure out like what the size difference is in what you like made in changes.

B

So like say, you make a change in the nexus compiler yeah. We actually know if it's going to help in bundle size or will increase bundle size same if you include a like massive library, for example, will know if you're like increasing the module size of the next project in a way that is like too much basically.

B

So it shows you a lot of like other stuff. uh The reason that you see uh jj's handle there is that he uses his own like.

A

B

To send those um which is funny because we have like in the repo we have two bots and they're. Both people from my team that are like they've bought a fight themselves.

A

B

A

Yeah I've seen that happen.

B

And a job um so.

A

You never know if you're talking to your to the real person.

B

Yeah so like, overall, um like these comments are uh basically to help like one thing that we noticed was we had users that broke the tests but couldn't figure out where they broke the test.

B

So, like the first thing that we did was we introduced this stat action to basically show you like: hey you're, increasing the the size of the next chess project, and we don't want that yeah, because we want to consistently like either have the same, consistent size or reduce the size right of like your browser bundles. um So this helps a lot with optimizing, but then we also introduced a separate git of action that publishes the filled test result into your pull request, so anytime a test. Fails. We basically send this message being like hey.

B

You broke this test. uh Can you fix it or well? Not even can you fix it but like this is the test that broke, and here you can see like what broke specifically.

B

So we have a lot of like other stuff to help new contributors um be as productive as they can be because, like otherwise, you have to like go through all these logs like going to get actions that kind of thing which is really hard to get right, basically like if you're, if you've never been inside of this project, you you just don't know where to go. If, like something fails, right.

A

Yeah yeah, it's super helpful and um yeah shout out to github actions, for um it looks like the net stack. uh Sorry, next, stats action, that's a tongue, twister yeah,.

B

A

So excellent, so yeah, um I appreciate going through those projects. um If anybody is curious of those, uh I'm pretty sure somebody will drop them in the chat. If someone didn't get those uh links, if not the the video will be up it should render shortly after we hit stop, but I did want to transition to the questions in the uh the chat as well.

A

um So let me just get uh real quick. I'm gonna fix the window because it's a bit broken.

A

Excellent sorry, I had it all set up and then I I fumbled it.

A

Okay, that should be good all right, yeah. So just looking at the chat, uh I think we had one question come through, um which was uh I'm parapus parapass, I'm parapass, that's who you are and um yeah the one question was like how many issues does uh is made on next js repo uh per day, which is a good question.

B

I don't know it's a lot, I I think that's like I don't know actually yeah at.

A

The moment there's.

B

Pills or something.

A

Yeah at the moment, there's 428, so I I think actually on the insides tab. So if you win the repo and then insights.

B

Yeah I I was just looking at that. um It's like the last week, 33 issues, but the last month 121 and 185 closed. So slowly going down.

A

Yeah yeah: this is actually available to anybody who wants to sort of uh check out and get that answer to that question. um Yeah yeah definitely check out the next repo actually any repo and let's check out the uh up on the insights tab and then you you've got exactly what you're looking for um yeah cool and then uh yeah, I'm just gonna. Look at the chat a little more um yeah thanks for starting the the next js repo too.

A

uh I'm a big fan of people, starring repos um and mainly it's a it- is a vanity metric. But it's also a good signal for for maintainers and contributors to know um if people are using their project and sort of the engagement, um I think a lot of people, uh it's easy for people to get burnt out at open source. So if they don't have that signal or have the sort of interactions, then it could sort of fall off. So I'm curious.

A

My question to you is: how do you sort of not burn out on the uh the hundred prs that you're you need to look at after this call or the 50 50 issues that you get this week like? What's how do you sort of pace yourself, um because I know it's your full-time job, but it also could be overwhelming yeah.

B

A

Maintainer community manager, like I don't know to someone who's, actually managed the community, but you are in the the issues. So you you are wearing this sort of hat of community and project manager and stuff like that.

B

Yeah so um so personally, I just really enjoy brookfield next, uh like work on open source. um It's sometimes like. I just try to focus on like other things like that's.

B

Why I like sometimes I I let the like issues or pull requests or whatever like go up a bit, um because then you can go through them like one by one like in a day or something um like right now with like 90 open view requests you have to like spend multiple days to go through them, um but they also know that, like most of the pro requests are not like pressing as in like oh, they need to be shipped tomorrow. Right, um they're, mostly like updates to examples, updates the documentation.

B

That kind of thing- um and the like downside of that is also that some of these, like changes to the core, for example, have to be discussed like very extensively also. um So it's obviously a lot of work um for me personally.

B

I just try to go through them as fast as possible, but that's really hard to do if you have like a lot of notifications and a lot of requests, so I don't have a good answer to like how do you not burn out um because, like I was also like before I joined for sale, I I was just like contributing to the next, probably like 40 hours per week, next to my 40-hour, like job or whatever, um but I just found it really interesting and I was learning new things all the time, so it was like it wasn't like.

B

Oh, I have to do this. It wasn't a burden to do it right. It was more like. Oh, I find this really interesting. I like doing it, um I'm learning a lot and that's why I'm doing it um and it's not because, like some random person like on the other side of the world, wants me to like fix all these issues or something right um today.

B

It's obviously different because now we're like building the project, the product, slash project uh out um and like tons and tons of tons of more users come by and we try to like help everyone right, sometimes that's possible. Sometimes it's not, um but overall it's just like yeah. I would probably say like try to do the thing that you enjoy doing or something which sounds super cheesy, but.

A

Yeah, that's I mean that's a a good thing to mention too, as well like, if you aren't enjoying it, perhaps find something else that you are enjoying like. I know, frameworks come and go libraries come and go like people moving waves. Like I mean I used to have a different haircut five years ago, so like we, we change.

A

We change our style and like the things that we're interested in and like there's, no reason that, maybe, if you aren't into react today and like you, want to try something new like a felt or a view like there's nothing against doing that, um but there's always opportunity for anybody who wants to sort of contribute so like shout out to stewie who found this uh stream super helpful. uh He mentioned that he's gonna.

A

uh I guess peruse to the examples tomorrow and see if there's any sort of help that he can also give too so you'll. Have uh you have your 101st uh pr this week to look at? Hopefully.

B

But um so uh yeah we're working on a um a ui for examples, also on the website so like that, you can basically like see all the examples instead of that they're like hidden behind this, like one click inside of together, prefer that you don't know about, for example, so that will probably also help.

A

Awesome and then also shout out to everybody shouting out github actions too, as well uh as like a nice little tool um yeah. I appreciate you showing off your your action that you all are using on the on the the project and um yeah. If anybody else doesn't have any questions, I guess my only question is sort of how do people sort of connect with you? um Actually we didn't even cover that um zeit or do they have like a community like secretary's channel.

A

I know we have discussions, uh which is a good place to get questions answered yeah, but as far as like meeting the rest of the community is there another uh channel for people to figure that out.

B

So currently we we only use discussions like mostly for this type of stuff, um so we have a bunch of discussions. It's still like very much work in progress, um but we're getting there. uh We used to use spectrum, but we moved to get a good discussions for this um and yeah. If you want to reach out I'm on twitter um quite heavily, so you can always like reach out there.

B

uh That's what you did also to reach out for uh this talk that we just had um yeah it's um it's generally, where, where I can be fine, uh can be found like for dms or whatever.

A

Yeah and stewie's actually mentioned that he um so I'm just looking at the twitch chat for anybody who needs contacts, but he's mentioning that he um used an xjs uh hashtag on twitter uh and got an answer yeah to a question as well. So it seems like at least you're following that: hashtag.

B

Yeah yeah, I I have custom filters for that.

A

Yeah, are you a tweetdeck fan.

B

Yeah, so I use tweetdeck for uh yeah for the extensive twitter, uh like uh looking into all the twitter streams, but um I also just have a like search inside of the twitter app on my iphone um and it works pretty well too, like it works in the same way as sweet deck only on your phone um and yeah. What else do I use? I?

B

I mostly use tweetdeck for, like just scrolling through all the tweets for, like certain uh topics.

A

Awesome well, um I think we're good on questions. uh If anybody else doesn't have any. um I really appreciate everybody came on. Watch us live. um We will be doing more of these in the future. uh Just definitely follow github on twitter follow the. If you haven't hit the follow button for the github twitch also hit that as well, um because uh we will try to get a good stream of announcements.

A

This was not so much a test like I sort of knew what we were going to do um and like we knew we had a plan for this but sort of trying to figure out um sort of streaming here. um So I'm super happy that a bunch of you showed up. I also want to give a shout out too, as well.

A

um For those who aren't aware, uh github satellite is going to be next week, so, which is also why, uh potentially, I have a stream book, but uh I'm not confident that we actually will do that because satellite's going to be a super busy week, uh but get up satellite is going to be at online 100 online conference. Normally it's hosted or would have been hosted in paris, but norm was hosted somewhere in europe.

A

So if you want to hear all the new things that we'll be shipping, including github discussions, which got a lot of mentions today- uh definitely check out github satellite, it's gonna be 100, free and online. uh We're gonna have like a a couple different tracks as well. uh I think they're calling the play track uh so we'll have some live djs um uh uh playing, actually yeah. I think I think that's actually posted.

A

I don't want to give away any more secrets to as well, um because I'm not sure what's on the site and what's not and what I just heard internally uh but yeah, we'll.

B

Have some some.

A

Coder djs, I guess I don't know what you call them today, but they write code and make music, so that's gonna be fun. uh I am also giving a talk. This is gonna, be the very last talk at the end of the day or the beginning of the morning, depending your time zone, uh but it'll be the last one to schedule and I'll be giving tips on uh how to leverage github as an open source maintainer. So talk about some features we ship, but also talk about some projects that are doing things like.

A

What's uh what uh versel and nexjs are doing uh so yeah. I think I have a lot of information. I don't know if it's gonna make the slides, because I was supposed to have my slides done yesterday, um but I'll be working on slice today. So who knows? I might you might get another mention from uh from the github stage, um but yeah again tim. Thank you so much for coming on the stream and agreeing to be my test subject as we sort of figure out the uh the transitioning.

A

Also everybody who's been here live. Also apologies for the internet too, as well. um You know and then bandwidth it's hard to come by, um so we appreciate everybody. Who's uh who's uh listened with us, the recording itself. We have a local recording, so hopefully the local recording will have over audio and um yeah check it out. So with that being said, I'm gonna switch to the goodbye screen and uh actually I don't have a goodbye screen, but uh I will just go black all right thanks again.

A