Welcome, this is the September 1st edition of European Docs Office Hours for Jenkins. Today on our agenda, we have some action items, update on Google Summer of Code, some info about the Jenkins 2.361.1 release, and I think it comes along with that. We have some recently added blog posts about DevOps World 2022 in the Jenkins blog, which I wanted to point out. And then a couple of other topics from previous sessions, the search improvements on Jenkins.io and the commercial support page that's been proposed by Gavin. So just to start us off, Mark, would you like to give us an update on the action items? Yeah, so the archive, the docs mailing list, no progress, the blog posts, you can delete the Sheikot Africa Contributon, that one really is complete. Okay, great. That's it. Okay. Thank you so much. Next up, beyond, would you like to share what's been going on with Google Summer of Code? Mark mentioned you were talking about the Docs Generator and was able to add that. So yeah, just wanted to see what you had to share. Yes, so I was able to get the request for the pipeline search documentation generated on and we merged it a couple of days back, but it was breaking the site, it had some errors. And basically I fixed that by writing the code to generate the parameter folder. And even that was merged like a half an hour back. And Mark also created a pull request to test it on Jenkins.io, which I think has failed again because of that particular reason. So not able to debug what the error is, but it's not able to find that particular parameter file that I've created. So we'd have to debug it more, but I can show you the result on my local machine, like what it looks like and maybe we can look into it together if that's fine. Sure. Yeah, let me go ahead and stop sharing my screen behind and you can take over. Is it visible? Yeah. So I'll just run it locally first. And so basically the error, I think this is the builder that is facing and is seeing those as file directory, which basically should exist according to the local file that I have. And we'll be able to see that in a moment when the site runs. So I'm not sure whether this is happening because we've created a new folder inside the file structure of Jenkins.io, but you can maybe test it. Something else. So it is running. And if we go ahead and look into monitor branch, basically the loading time for this, this page required around 20 seconds before it becomes stable of the JavaScript going on. And the browser often requires only a couple of seconds now to get there. And for example, with the configuration I've added, many of these have been abstracted to the new pages. One of them is from SCM. And if you click on that, we'll see another list of all the SCM providers. And we can basically go ahead and check out some more configurations that we've done and in this something like this. So all these are connected within themselves. And if you want to, basically, it has given the error of the first ask it off that we had created. And if you can check the config, which was present that separated it, we can maybe find out the location and see if it is working correctly on the local machine. So. The clock will request, right? So let's see here. Yeah, so this is common for, OK, I think I can find it now. So, yeah, this one. So this is separated correctly as far as my knowledge. Yeah, this is working fine on my local machine. Not sure what is going wrong with the with the side generation. But any any thoughts on this one? I'm wondering if maybe it's not in the all ASCII that was just generated. Let's let's take a quick look at that. All right. So once that the the copy that I'm showing you right now is these entire docs are taken from the all ASCII or zip and unzipped over here. So these and that's the one that you downloaded from the most recent build. Right, right. From the request to one one. OK, so backlog. We can walk through the procedure again, I guess to double check. So but but what file were you expecting it to be in? Because I don't see a file in the copy of all ASCII dot zip that I downloaded called back low back. Anything more than just backlog dot a doc. Um, so when we unzip it, it will have a folder which is known as bad amps in it. And after that, so basically that for particular folder will consist of this file. Over here. Yeah, so backlog pull request SCM source dot a doc does exist in the copy that I see and it's and it's got some content. It's a K-byte. So yeah, OK, but you say that should be in params. Yeah, it is. OK, OK. So then so so what that means beyond is something something else is causing it not to be found. Is it not in the correct location or. OK, so it says no such file or directory content slash doc slash pipeline steps params backlog pull request SCM source. So is it possible that that is not being unpacked in that location? Um, basically earlier when the fetch external resource, as far as I can recall, it's it calls the OK, so it unzips it in the steps directory itself. And when we do that, the params will come within it. And if it's not able to find it, then I'm wondering how it is able to name this file correctly in the first place. So from where is this name coming? It's not able to find it in the first place because I've not linked it. It's not that the link is coming out to be like this. And basically, this is happening at compile time. So it won't even know if it exists or not. Is that particular link exists or not? That's been linked. That makes sense, I guess. So I'm not sure how it knows if this like the name of this particular ask it off in the first place if it's not able to locate it. So is the is the unzip that's being used, honoring directories? I'm not sure what script is used to. I use the standard Linux command on my machine, which basically gets the folder out as well. And like I can demonstrate that by moving to. Hmm. Yeah. And and it looks like so I can basically remove all the ask it off. So to be happy, I have these approach and it's sitting in this director, sir, and also remove the patterns folder. And if we do, OK, so this or ask it or ship is a new one. And when I do an insert, I should basically have a parent school sitting here. OK, so I'm exactly sure what's going on with the ask it off. Is it happening because we are creating a new folder, which indeed also requires a new URL location on the site? But is it flexible in that sense? I didn't think that that was the back to the message that it's it's displaying. Let's read that. It was saying no bundler, no fetch, external resources, no such file or directory. OK, so so it's that's external resources. OK, so the thing it's downloading is C I dot Jenkins that I owe job in for a job pipeline steps, doc generator job, master, last successful build artifact. I'll ask you that. And I download that same thing. Not sure what the other things are. Not sure what he's also starting from, but in the end, go ahead. The main or the folder that we want is the first answer. Not sure what the second or in the fourth line of the line. What what they are touching, basically. Yeah, and I think if we read that script, we should be able to see what it's what it's doing with resources, right? So tells Fetcher dot new process with recent resources and it looks like the the four arguments are the origin, the destination, the front matter and the zip destination. So origin, that URL destination, so it copies it into content underscore temp front matter, none required. And then zip destination, content doc pipeline steps that seems all quite reasonable. So let's see if I run it. Um, do you think that it is appending the name patterns over here? So not sure this has happened to me once as well, but basically giving so it's not able to find the end point of this. Maybe putting it like this, I don't think it would make a difference, though. But it's not able to find that particular ASCII doc and the URL mentioned over here is the correct one, the one we expect. Not sure why it is not finding it after mentioning the correct URL. Yeah, so it's now it does look like it's using Ruby to perform the unzip, right? And so if there's if the Ruby zip package does not honor directories, that could be a problem. But it seems like we would see that if we ran scripts slash external fetch external ourselves. OK, I'm running it now just to see. OK, and it says needs to load the package named Faraday. It's been a while since I did anything with Ruby. OK, Ruby, Jim package. I have same same error for me as well. Right, so it's I think what we want. What is Ruby gems? So we say gem space install install Faraday. Had a look a search within GitHub.com on this repo to see if it was called elsewhere. But unfortunately, there is just one occurrence in the make file and another one into Docker file. But that's all because I was wondering if you have the error if you have maybe somebody else should have it for other resources. But that's the only place where it is called. So false positive. All right, great, great. So now is there a way to install a gem as an individual user? I'll do the dangerous thing. And maybe it's stupid, but could it be just a transient and temporary FMR or whatever error if we relaunch the build? Would it fail the very same way? I would expect it to fail the same way just. But but it's it's cheap to try it. Let's do it because it can be running in parallel while we're investigating other things. So I've launched it PR5404 on Jenkins.io is the one that's evaluating it. And the same failure will be visible on the on the master branch. I could start that as well because then we've got two different places to check it. Yeah, good idea. So what command does it use to unzip Ruby? The one you mentioned right now that Ask your question again, behind. Yes, Ruby zip is the thing that's performing the unzip. I assume it would honor directories. I would be surprised if it did not. Now, is there a way we could check that? Actually, there is. I can probably go. Can I go to that pull request and look inside its workspace? I don't know if I can because it's a pipeline job. Workspaces, OK, so it's pending another. Well, let me try it locally on my computer. So behind the technique that you used locally that did work successfully for you was you did you modified something to allow make all to not download the file externally? Could it come again? How did you run? What steps did you take to run it locally? You downloaded all ASCII dot zip. And then what did you do? Then I commented on the fetch external resources part for this particular report. And I shifted all ASCII zip dot dot zip on the pipeline steps folder. And then I run unzip all ASCII dot zip. OK, so so the technique was comment out the all ASCII. Line 45 through 40 in fetch external resources. Got it. And then. Download. All ASCII dot zip and unpack it. Did you unpack it all the way into the content doc pipeline steps? Yes, that was OK. All right, so hang on just a minute while I do that then. Well, OK, I shall stop famous screen in case you want to. OK, great. OK. And the location where you unpacked it was content. Docs. Pipe doc pipeline steps. And I don't have a params file there right now. So if I say unzip, OK, now I have the params folder. And then you can run the make runs script for. Oh, you use make run. OK, I think that may be the magic I need you need. I believe you need to use make all. Yes, I tried that. So make all visit, but it doesn't run it. And then after make all, when it basically purchase everything and get something done, then I don't make run. So to test it, but basically make all was also running successfully because in this case, we've, anyways, committed out the fetch external resources part, right? So that couldn't be caught even if you use this method. And if we don't do not comment that out, we will get the older ones. But I think now if we since the latest in the repository is updated now, so last simple points towards the new documentation, we can try out the fetch external resources script itself. Right, we could could we could update fetch external resources to pull from the from the pull request or from the classes as well. Yes, well, and in fact, it's already doing that, isn't it? Oh, yes, it should. So maybe we can try commenting that out and removing all the ASCII doc that is sitting from that answer thing. So I try not to take much time. Make make all take some time because it's fetching a lot of resources through that time. Yeah, so so but because I'm sitting at. So if I if I take the if I do a make all from anywhere, it will fetch the external resources now. OK, so let's get that added. Yes, the same error as the pull request. OK, good, so go ahead, Veehan, excuse me. Right, exactly the same error line that you are seeing in the pull request. OK, as well, good. So you've got you've got at least enough information to do investigation. That you can check locally. Yes, basically, the fetch external resources itself is not working. So when the Ruby is fetching that and unzipping it locally, that is where the problem is. So we need to we need to investigate the Ruby part. The way it is. So while you're doing that, I'm going to go ahead and revert the the change to the pipeline steps doc generator so that we don't break the build of Jenkins.io site. Are you OK with that so you can do your investigation on a branch? I'm sure so I can do that. And I believe those changes would be needed in Jenkins.io and not pipeline steps of generators. So whenever we make those changes first in Jenkins.io, then we can re recreate that pull request from BSTG. I see. OK, so you're thinking is that the likely fix is no longer in pipeline steps doc generator. It will actually be on the Jenkins.io build process. Great. Great. Anything else to add behind Mark? Or is that does that take care of the Google Summer of Code update for the time? Oh, go ahead, behind. Nothing has to my say. Is it all right that if we move on in the agenda? So next thing that is on our agenda today is the Jenkins September LTS, which will be 2.361.1 along with the release, Faith has asked for a blog post about Jenkins for the Continuous Delivery Foundation blog. I'm working on that currently and have been able to get a lot of feedback and suggestions from the Jenkins team, developers, community at large. So I've been able to revamp and add a lot more information there. And I'll be sharing it as a pull request. And once I've actually submitted the pull request, I have to double check on what kind of formatting and file type they use. Since it does seem to be different from the regular Jenkins ASCII docs. So once that's been submitted, I will share it here and with the community as a whole. It's a high level blog post. It's not necessarily a technical document for the ins and outs of the Java 11 requirement, but more just to see milestones and a historical perspective of where Jenkins started and where it is to where it is now and where it's going. That is also going to include some information that I've been able to source from Basel's previous blog post about requiring Java 11. And with the amount of content that's going to be in the change log and upgrade guide, there should be more than enough information to go over and check out with the new LTS. The September LTS is going to require Java 11, as we mentioned. It's also going to bring support for Java 17 to it. So that's moving from preview to general access. So that will be another fun new update for users to try out. And the change log and upgrade guide itself is open for review at this point, we've got the backports and a lot of the other pieces added to it. We're just waiting on one or two other potential items. But for the most part, that's going to be ready to send out when the release is ready. One other thing I wanted to point out on Jenkins.io is the fact that with DevOps World 2022 approaching so soon, we have some contributors and other posts on the Jenkins community blog talking about their various topics and ideas that they're going to be bringing up at DevOps World. It's really exciting. This is back to in person for DevOps World, which is a nice return. And with everything that I'm aware of that's going to be happening, I wish I was going that much more now. But my team is going to be there. And I am so excited to see what everyone brings to the table and shares. The search improvements for Jenkins.io is essentially the search results right now are not as good as they could be. Some keywords don't show the results you would expect. But this is in part due to the fact that the Algolia search is older. Right now, we're using the legacy scraper. It needs to be updated to be more modern. And this will take some time to develop and figure out and configure. It looks to be something that's specific to the credentials that right now, Mark and Gavin Mogan are the two that have those credentials. So thankfully, Mark's already created a GitHub issue for tracking. But this will take some time to get going and get this straightened out. On the last topic that I have on the agenda is the commercial support page proposal, which was shared by Gavin in July. It's been a little bit since there's been any updates or discussion on it. So I just want to make sure that that's still visible. This is something that would greatly benefit not only Jenkins as a whole, but the user base and the community at large. The idea of having an updated support page would lend itself to getting that direct communication, be getting that easier support and even expanding the options of what support means, stuff like training, certifications, other commercial opportunities are all possible. And we want to make sure that this has the best set of information and support that we can provide for anyone that might be looking to use it. So if you have any ideas or want to get in on the discussion, that link is in the agenda and available on the community.jankins.io site. Was there any other topics that anyone wanted to add or go over here that we didn't mention or any other items they'd like to share? Yes, so basically one thing that I could think to rectify the error was in case we were not able to see why the unzipped thing is not working. What we can do is instead of keeping that params folder wasn't all ASCII.zip, we create another zip for it, maybe known as params.zip, and then we unzip it. And since that is a folder, it won't have any issues that we are facing now. And yeah, it should work. So that should be the green path maybe and figuring out why the folder is not getting extracted is the priority now. So maybe work on that. OK, thank you very much, Pihan. And I just wanted to say thank you for all of the continued work you're doing on the documentation. As a docs person myself, I really appreciate the fact of trying to simplify and, you know, could condense the bloat on these pages a lot. So I love it. Keep it up. This is amazing. So thank you so much for the continued innovation and contributing. And so OK then. OK, and with that mark, I think we can stop the recording. It will be available in 24 to 48 hours. Thank you. Was there anything else that you wanted to know? Yeah, so I was just listening on this. Pipeline generation. And I guess this problem with the subfolder is really just that we need to create the subfolders recursively. So there's like one line of ruby code missing because we're trying to write into a sub directory that wasn't created yet. So that should be fairly easy fix for. For the Jenkins I also behind, if you want to submit it, I've posted it in the chat, but the change that needs to be done. But yeah. Yes. And with the hope that there is only one folder missing because if you do that and it corrects the first error, then maybe you will have another subfolder which will have to be created and so on. I don't know. Yeah, so the code is already going recursively through all the files, but it's not. It's assuming that they're all in one directory. And so so it's been like the the perplexity for me is where would that change be applied in the fetch external resources? Yeah, exactly. So there's there's already this loop that goes through all the files. And I guess we just need to do this one and maybe add some imports. I'm not sure about that. Yeah. OK, maybe we would find the magic parameter set which would allow Ruby to unzip while creating necessary directories. Yeah, it's possible that there's some Ruby library that's like on a higher level than this simple zip API. Oh, oh, OK, all right. Yeah, so I think I'm understanding I hadn't looked at the code. It says if downloading a zip file extracted unzipping to and it does a maker of the zip destination, but then iterates exactly as you said over each file. Yes, exactly. And then online hundred twenty seven and just extracts into possibly non-existing directory. So we need this equivalent of the make their minus P to to create the folder safely. So we do want to create a request with this fixer. Should I take care of it? Um, it would be great if you can guess. OK, cool. It's possible. Mark, have you reported the full request already? Uh, I've I've submitted the pull request to revert it. So the pull request is being evaluated now. But it hasn't finished evaluation. So what we can what we can also do is for testing, just say that we want to download it not from the last master build, but from like fixed. So build number 800 or whatever was was the number where the pull request was applied and we can test it independently on the build of Jenkins IO because we probably don't want to block building the website. By by this. OK, so sorry to interrupt, so could you do another pull request maybe with your proposed fixed? And yes, my suggestion is to create a pull request that would pull a fixed version of the ASCIDOC, an old one, and it would contain this fix so that we can verify that it actually works. Yes. And then we have to rebuild the base. We revert the part that fixes the ASCIDOC, point it back to the last build of master and then we can independently merge the ASCIDOC generator pull request because this will only make the Jenkins IO part more robust. So it's not necessary to merge the Hans changes first. Yep, got it. I think even more that if you can submit your pull request relatively quickly, it will evaluate with exactly what's out on the system right now. And whereas the master branch is failing, your pull request, if successful, will then be able to fix the master branch when we merge it. So I'd say, Spinnock, let's have you do your first choices. Let's have you submit your pull request. Let's see if it fixes the master branch. If it does, then I can throw away my proposed revert of Vihans changes on Pipeline Steps doc generator, and we've got the solution then. OK, so that one's not the revert is not merged yet. It is not. That's correct. Then I will just do my proposed change and see if that helps. OK, cool. Right, and the folder part that we want to create, I'll just paste in the chat in case. So the one we have to pass the parameter and learn the name. And this is the file part that we want to create. Yeah, exactly. So if we add this Ruby code to make the unzipping recursive, then this folder should be created automatically. And it should also be future proof in case you add more subfolders in the future, then it should be no problem. Great. So the way I'm interpreting that, Spineck, if you're OK with it, let's give it, say, one or two hours. And if in the course of the next two hours, you successfully submit a pull request, we'll watch for it and merge it. If after two hours we haven't seen it, I'm going to assume that something got in your way. And then we'll revert the Pipeline Steps doc generator, and we can try again on another day. Would that be OK with you, Spineck? Yep, definitely. Great. It's not that the two hours is some magical deadline. I'm not trying to put pressure on you. It's rather that I want to be sure we have an expiration time so I don't leave the Jenkins.io build process broken for an extended period. OK. Great. Thank you. Thanks very much. Thanks for joining very much. And unless anyone has anything else they'd like to talk about, share or discuss, we think we might be able to stop the recording. And this time it will actually stop. It will be available.


The top three features of Apple Vision Pro you should know. Number one is eye tracking feature. The goggle is able to track exactly where you look at on the screen and the apps you look at, it can highlight and then once you use the finger to click, it's gonna blow up the app. This is so revolutionary.  Number three is a FaceTime experience. You're able to see people in real time through FaceTime and then as we'll see you as if they can see the 3D avatar of you which reflecting your entire facial expression and also hand movement as well. Like and subscribe, watch the next tech news right here.


Episode 6 here with Lovecraft at the Long Beach Public Library. Let's enjoy Music Out Main, number 6 with Lovecraft. Thank you for coming. I have questions as an audience too, if anyone has any questions. So the first off, we'll always ask, how'd you get your name Lovecraft? I read this book by the author Lovecraft, and I never actually read it. But I read the summaries about what it's about, and all the stuff you wrote about was really cool. But also just the idea of crafting love, making something. But I also wanted to be a memory artist, but everyone else wants to be Lovecraft.  Because we do have a cane. Do anyone else want to make a comment? Next question, I would like to know how did you all meet and what are your names? Javier Garcia, Garcia's family over here representing. We both met each other pretty much in high school, although I've known Chris a little bit longer. This as well. Well, yeah, first grade. But yeah, we all pretty much came together in high school. That's when we really started getting serious about making music. Anyone want to answer? Yeah, I know Javi since first grade. We used to go on swings together. And we'd run. Just play on the playground. My name is Dennis. This is Savannah Noel. We've all known each other for quite some time. I don't want to. I'll just speak with my voice. We've all known each other for a long time. It's kind of nice that we're all still together. You've been about four or five years after high school. You usually split apart, but we still manage to make time for each other. Yeah, we've all known each other for at least five. Sometimes I've been on the walls. We live on the same block. Neighbors, I know of Dennis since kindergarten. We all go back to school. What schools did you go to? World. Eric actually used to do the morning announcements. And he was like the president of ASB. And he's really popular. And I don't know how. We trapped him in the famous morning announcements. He'd go, yep, Eric, do it. And tell us about your visuals a little bit about your unique original visuals. Yeah, I actually made the visuals here at the studio on Long Beach. Thank you for having the studio. It's a cool place where they have 3D printers, all the Adobe products, people who don't have computers and stuff and resources. And I basically came here not knowing anything about Adobe After Effects and my friend Gabriel who works here taught me how to use, like, push me in the right direction. Yeah, they look just like geometric visuals. I'm like really into geometric patterns and stuff.  And then I put two of them and they're rotating in opposite directions. And then the next visual is actually just water. It's just the ocean, like, coming in and out. And I just added colors, all the stuff. In fact, so we're all here at the Long Beach Public Library, but you also have worked for the Long Beach Parks and Rec. Oh, yeah. What are the products of Long Beach here? Yeah, Long Beach, I love Long Beach. But I work, yeah, I work at Parks and Recreation. I work with a bunch of children, they're crazy. And I love working for Long Beach. It's a great city. It's because Snoop Dogg's from Long Beach. Yeah. And then I'll make my last question about the other name I know you by, Memory Palace. How did you come up with that? I was watching that show. It's like, okay, it's not on the left. It's like, no, yeah, I think it's any way you should know it's not on the left. Hannibal Lecture. There's a show about Hannibal. And then he uses the word Memory Palace. But then I kind of took it into a different way.  It's always like, to me, it's almost like meditation. You could reach your Memory Palace when you just focus and concentrate and stuff. To me, Memory Palace just represents being at peace with yourself. All right. Long Beach Library for having us. Shout out to Books. Thank you guys for coming out and watching us.


Thank you very much, and it's a real pleasure to be with you here at Slush today. This is my fourth Slush actually, so I'm very happy to be able to be back here in person. And I'm excited to share with you today some of our learnings that relate to international expansion. And when we're talking about international expansion, I'll be referring to both expansion across countries in Europe, but also referring to expansion from Europe to the US. I'll just start off by introducing index briefly. So index, we're a venture capital firm that was founded in Europe 25 years ago, and today we are duly headquartered between London and San Francisco, so half the team is based in the US and half the team is based here in Europe. And we're investing across three funds, from seed, venture to growth. So essentially partnering with founders anywhere from first check into the company all the way up until pre-IPO. And we've been really fortunate to be investors in many Nordic companies, including, for example, Supercell coming here out of Finland. At index, we have also been fortunate to work with many companies that have expanded across Europe and more than 40 companies that have expanded successfully from Europe to the US, and nine of which have since gone on to become publicly listed companies. And by partnering with companies and really following their journey from the planning of expansion to then the launching and ultimately the scale-up phase of the expansion, we've come to realize some of the opportunities that expansion presents, but also become mindful of some of the potential pitfalls that exist when thinking through structuring your expansion. And so I'm excited to chat through some of this with you here today. As I mentioned, index, we are duly headquartered between London and San Francisco. And as a reflection of this, roughly half of our investments are also between Europe and the US. And so just a snapshot of some of our existing portfolio and some of our previous portfolio that is split roughly 50-50. And many of the learnings that I'll talk to you about today have really come from our experiences with working with some of these companies, among many others. So let's dive in. As you start thinking about international expansion, what are the key factors that ultimately are shaping your decisions when it comes to international expansion? So there are six factors that we have identified as critical before actually launching. The first one is market size. How big is the opportunity in dollar terms? And and this will be important and we'll touch on this later as it will also help feed into a lot of the decision-making around at what point should we go to that new market? Or which member of the team should be first on the ground in that new market as we're opening it up? Should it be the CEO, the founder? Should it be a local GM that we hire? These are all critical considerations early on. The second one is localization. So by that, I mean, do you need extensive product or go-to-market localization, for example? We'll touch on this. Does it require particular regulatory requirements on the product side? Or will go-to-market require inside or field sales? And how do we structure it accordingly? The third factor is competitors. How strong is the competitive dynamic in the new market that you're going into? And depending on what the competitive environment looks like, that might have different repercussions for how to think about product differentiation, bigger budgets, how to think about whether there are any lab-grab decisions to be made, for example. So these are all things to have top of mind before going. The fourth one is familiarity. How well do you actually know the market? Do we already have early inbound leads in the market? Do we already have customers there? Fifth one is regulation. And it's particularly important for some sectors, such as healthcare, for example. And it differs quite a lot by countries. Do you require certain licenses to operate there? How difficult would it be to acquire those? And how does that impact the timing of the expansion? Lastly, as an initial factor to consider is capital. Do you have sufficient human capital, but also financial capital to be able to pursue the expansion? And what does it actually take to be able to tackle all the requirements as you're expanding? At Index, when companies are thinking about expansion, we often get asked, you know, what are some of the common challenges that companies have come across as they're thinking about expansion? Because expansion can be presenting a wealth of opportunities and there's new market to go after, but there are also some challenges that we think it could be helpful to just be mindful of beforehand. And so I'll walk through some of this and we'll touch on this a bit more in the presentation, too. The first one is hiring. When you're not familiar with the new market, it can be difficult to figure out which are the right talent pools to tap into. How should we think about hiring local leadership for this new market? The second one is culture. And this one is interesting, I think, because it really spans across any sector and is relevant to any organization. How do we keep culture aligned between offices, particularly when maybe there are key time zone differences between the different offices? How do we keep that aligned and also alive between the two? The third one is brand. And this is interesting because you can have a really powerful brand or a brand name in your home market. But then you have to also think through how does this brand resonate in another market? Will we have the same cut through effect in a new market with this brand? Will we potentially have to have a different name in another market? How do we think about that? It's important to consider because in some instances you might want to have the look and feel of a local product. Acquisitions. This can be interesting and sometimes when expansions happen through acquisitions, is there a cultural misfit through the acquisition? Things to be mindful of. Timing. It's a key one and we'll chat about this quite a bit. At what point does it make sense to do so in the scale-up phase of a company? Is it happening too slowly or too quickly? And what's the impact on the organization as a whole? Lastly, as a common challenge, I want to touch on the matrix organization. And by matrix organization I mean what should be a central versus a local factor to consider? Should marketing budget come from the central or should it come from the local office? What should actually be central? What should be local? And who do those that are working in local offices ultimately report to? Do they report locally? Do they report centrally? These are all matrix questions that come up and it's important to be mindful of as a potential challenge but certainly one that is overcomable. Touching a little bit about timing. So I guess we can simplify it into four different sequences of international expansion and number two and number three is what we see most often and I'll spend more time on these two. The first one is global from day one. And this is usually applicable to companies that have a lot of self-serve distribution or distributions through the app store like gaming companies, for example. The second one is companies that start off with European expansion and then might go on after that to also do say US expansion or a rest of world expansion. And a few companies in our portfolio as examples of that are Deliveroo or Livy who have started off by doing European expansion and focused on that and then some afterwards have also gone on to do other expansion such as Revolute going to the US. As a third there's US expansion that happens quite immediately from the get go and we'll talk soon about why that is because it comes down to this market opportunity that we touched on as an early consideration. And then the first focus is US expansion and then sequentially might come back to do more European wide rollout. The last one is around expansion to China or to Asia and it's something that we don't see as frequently particularly not in the early stages of scale up for a lot of European tech companies. So I'll focus a bit more on number two and number three here. So when thinking about European expansion, the main thing that comes up that we chat to companies about and often get asked about is just what are the factors that are central versus local that we should consider? And on the right here just identified the difference between some companies that are in the index portfolio of just how differently it can be structured even though they've all done European expansion of some sort. Some that are highly localized models like Livy or Allen. They're operating in the insurance or in the healthcare spaces where there's a lot of different local regulation requiring just local teams to be present on the ground. A lot of local decision making needs to be made. But then on the other hand, you also have companies that are perhaps more centralized in their structure and are able to be set up in that way just by the nature of the business model or the product that they're selling. And so these can really be structured differently. And when we're thinking about factors to consider on the product side, this can be a marketplace model. What are the supply or demand side considerations for this particular product? Are there any operational constraints in this market that we're going into? And so as a result might need to be much more of a local decision making. On the go-to-market localization, a lot of questions can be what kind of sales structure should we have? Inside sales, field sales, what are the target segments that we need to be focused on? Is the sales cycle or the process different in this market just by the nature of how things work here? What does marketing or growth need to look like given the competitive environment that we're seeing in this local market versus where our home market is? And how do we need to think about customer support in that context? I also want to touch a bit on just cultural fit and accessibility. As we're thinking about which countries to go into, how should we think about the travel time to the target country and just the simple accessibility? And also just something like cultural similarities and differences between the target country and the home country. And how does that, if at all impact hiring decisions? How does it impact just how operations are run more broadly? So these are questions that we often chat with founders about when thinking about sequencing European expansion and making decisions around how to structure those decisions and those organizations throughout that journey. I want to spend a bit of time on expanding to the U.S. So in September of last year, we released a handbook which is based on research of over 300 companies that have successfully expanded from Europe to the U.S. And this included surveys, a lot of deep dive interviews and case studies with companies. And we really compiled a handbook which is available freely on our web page for companies to really help think through how based on the type of company that I am running as a founder should I best think about setting up my organization in the U.S. And at what time in my journey should I be doing so? And I'll be touching a little bit about this. And I think the reason why it's now more important than ever is because Europe is creating more and more U.S. winners. And it's not short of successful examples of companies that have expanded from Europe to the U.S. And if anything I think this slide is just so telling of the momentum that Europe has now in that thinking about the pre-2010s, there were really just a handful of European tech companies that have been successful with expansion to the U.S. But when we're thinking about the last few years, there's been quite a meaningful increase in the number of companies that have gone on to also be successful in the U.S. such as Spotify, Unity, both Nordic companies or ADIEN, Supercell of course and among many others. And of course there are several that haven't even exited yet and so they're still on their journey. So now there's never arguably been a better time to be a European founder because there's such an opportunity to not only scale in Europe but then also to go on and scale in the U.S. And what our research has led us to be able to identify is that companies can really be archetyped into four different categories and four different organizational templates if you will. And I'll walk through what each of these means and it can be a helpful guideline for how to think about how should we expand to the U.S. and when should we do so. And the four archetypes that we've identified are telescope, compass, pendulum and anchor. So what does this mean when you're discovering your archetype? By telescope we've defined this as companies that have a focus on the U.S. and this is a global lens in Europe. So these are usually companies that I mentioned earlier that might have self-serve distribution channels or are available on the App Store for global distribution from the get-go such as gaming companies like King but also other companies that are self-serve like type form pipe drive. These would categorize as telescope. The second one is compass. What we mean by compass is in Europe, but they're sold in the US. And so going back to that initial consideration that I mentioned early on about factoring in market size early on, in the instance of Compass, it's usually that the US market represents north of 50% of the total addressable market. And so organization and leadership will quite early on pivot to the US. That's where the majority of the opportunity is. In Europe, that have been classified as Compasses might be Calibra or UiPath or Algolia, for example. The third one is pendulum. And what we mean by that is companies that are distributed and they have distributed customers, distributed organization. The US market is roughly 30 to 50% of the overall opportunity. And organization ultimately becomes quite distributed between the two. And an example of that might be Spotify. The last one is Anchor. And it's really tethered like an anchor in Europe. So the center of gravity remains in Europe. And the organization and the leadership team remains in Europe. But there might be local leadership teams that are in the US. And the US TAM is roughly, say, 15 to 30% of the overall opportunity. And examples of that might be Wise or Farfetch. And what's interesting is the typical timing for US expansion will usually differ depending on archetype. And it really comes down to, again, a lot of the market opportunity that each of these might have. If you're thinking about a Compass where the majority, nor the 50% of the market opportunity in the US, it makes sense to go there quite early. So companies that we've classified as Compasses will go there, perhaps already at Series A. Companies like Telescope or Pendulum, it might be more at the Series B stage. And then lastly, in Anchor, what we've tended to see as the majority of the opportunity is anchored in Europe. And there's a 15 to 30% opportunity in the US. It might be closer to Series C. I'll just switch back here. And before diving into where in the US we should think about, I also just want to highlight a little bit which member of the team might be part of the early expansion journey to the US. And what we've typically seen is that, for example, for a Compass where it happens early on, usually the founder moves over to the US, or at least somebody from the early leadership team in the whole market will move over to really help set up first feet on the ground in the new market and be a leader there, set up the culture and make sure that organization also becomes equally set up in the US. But what we've seen with some of the other models is that it might not be as obvious that also the founder will move early on. And what I'd recommend you all to do, as I mentioned, this resource is available for free on our webpage. You can go in and look through and figure out, based on your business model, customer segments, and the structure of your current organization, figure out which archetype would we fit into. And so how should I, in light of that, think about setting up the US organization? So please do go in and use that resource, and it's available for free with an app as well. What's interesting is that when setting up in the US, there's been some change recently about where to set up. So if we're thinking about 2008 to 2014, roughly, it was split pretty equally between New York and the Bay Area, roughly 37% each across the two, and then slightly smaller in Boston. But actually, recently, what we're seeing is that more and more companies are starting operations in New York versus the Bay Area. And of course, there are different considerations to weigh up, customer locations, the sector, the time zone difference, talent accessibility, talent pools, personal networks. All this will feed into the decision making. But it's an interesting trend we've noticed where actually it's not the default to set up in the Bay Area, but actually we're noticing more and more companies do so in New York. Again, as we chatted about, founders don't always have to move to the US. While it's essential for Compass, for some of the other archetypes, it doesn't have to be. And some it's not even necessary, whether anchor or telescope. That said, there might be other types of leaders that should be present as you're setting up your operations in the US. So if we're thinking about a pendulum, while it might not be the founder or CEO, but could be, it could also be a local GM or a president, for example. For an anchor, similarly, can be a local GM or a president. And lastly, for telescope, it's usually more functional leads. So for example, might have customer support or might have business development rather than the actual founding team or the CEO. I want to just double click a little bit about some of the common challenges that we touched on earlier, that are top of mind sometimes for founders as thinking about expansion to the US. And usually what can happen is that it can be difficult to assess and hire US candidates. And that might be for a different reason. So for example, just compensation. And this is, it's an interesting one because it's changing a lot. And we've seen a lot of change in the last few years, but even just a few years ago, compensation tended to be very different between Europe and the US in that US talent is far more focused on equity. You need to pay to play and they will do a lot of due diligence, which is getting much better in Europe and it's catching up with the US, but hasn't been on par with the US historically. And also US talent tends to be much more aware of compensation benchmarks and just the vocabulary around stock options more broadly. So these are all things to think about when thinking about compensating talent in the US. There's also just a question of perception. So I'll touch on this. I think it's an interesting quote, which as a European company going to the US, it may be that candidates are naturally a little neutral or even slightly say suspicious of your European companies. They might not have been to the city that the company has been founded in. They're less aware of it. They're perhaps less aware of their investor base. And so these are all things to just think about as you're navigating, transitioning to a completely different continent and a different market. Culture tends to be the second biggest challenge for European founders that are following your US expansion. And of course, operating across two continents makes everything harder. Time zone differences, cultural differences, different expectations from teams. And you'll need to really think through the people strategy. How do we make all hands available? How do we think about staffing? What kind of documentation do we need in order to be able to make this seamless? How do we think about engagement and onboarding? How do we set up our video conferencing just to make that transition as smooth as possible? And there's some interesting quotes here that I'll let you guys look through. But one in particular, I think is really interesting, which is just pay careful attention to how your meeting room is set up. Everything from the positioning of cameras to microphone screens and furniture and how people are sitting. All that can really impact how how closely you almost feel like you're being there in person and small sort of tactical things to think about as you're trying to make that cultural familiarity as close as possible. One thing I do want to mention is that even though for each of these archetypes, there may be different members of the team that go to the US and sometimes the founder or founders will and sometimes they won't. What has tended to be a pattern is that R&D had count remains predominantly in Europe and actually only 18 percent of startups that have expanded to the US have any developers in the US. And as you'll see, it tends to be much later on in the journey that perhaps the R&D scales up in the US. And what I think this shows is just really what an exciting time it is to be starting companies in Europe. There's such strong engineering and tech talent here. And as we've seen from having done the synthesis of over 300 companies, so many of the tech talent tends to stay in Europe. And so it's really such an exciting opportunity to be starting companies in Europe at the moment. As I mentioned, this guide on expanding to the US destination USA is available for free on our web page. It's a digital handbook. We also have our expansion plan app, which is available. And lastly, there's an online quick guide just to help you figure out which archetype does your company fit into. And as a result, at what time should we think about expansion? How should we think about the organizational setup for US expansion? And also, who of the team should be part of that initial journey? So I do encourage you all to go in and take a look and please use this freely. So with that, what I do hope that you take with you today is that Europe is such an exciting time to be a founder. We're seeing more and more European companies be successful with their US expansion or even just more broadly with their expansions across Europe and more and more strong tech talent that's really coming out of Europe. And so there's a wealth of opportunity out there to expand. And hopefully some of these learnings have just made you a little bit mindful about some of the considerations or just challenges to be on top of before you start your expansion journey to help set you up for success when doing so. Thank you.


Craft presents the Great Gilder Sleeve. Cheese company will also bring you Bing Crosby every Thursday night. Present each week at this time Harold Perry as the Great Gilder Sleeve, written by John Whedon and Sam Moore. Here from the Great Gilder Sleeve in just a moment. What's the grandest, most appetizing aroma that ever wafted its way out of a kitchen? Well, for me it's always been the tempting smell of flaky, crusty brown breader rolls fresh from the oven. And say, did you ever spread breader rolls when they're fresh and piping hot with delicious parquet margarine? Now there's a way to really enjoy all of your baking favorites, to spread them with parquet margarine. For parquet's own fine flavor makes other foods taste better. Of course that's to be expected, for parquet is the quality spread for bread made by craft. So naturally being made by craft, you'd expect parquet to have a delicate appetizing flavor that really satisfies. And since parquet requires only four ration points a pound, your whole family can enjoy it at every meal. Parquet's a grand source of food energy too, and every pound contains 9,000 units of important vitamin A. So serve parquet for its own flavorful goodness, and for the extra flavor it gives to other foods. Ask your dealer tomorrow for parquet, P-A-R-K-A-Y, parquet margarine made by craft. Now let's see what's happening to the Great Gilder Slee. While tonight our hero has taken another step forward in his public career in Summerfield, he's been elected to fill a vacancy on the school board. And having attended his first meeting, he and Judge Hooker are escorting Miss Goodwin, the grammar school principal, to her home. Well it's been so nice of you gentlemen to see me home. The pleasure Miss Goodwin was all ours. You're sure I couldn't persuade you to come in for a moment. Well, the judge has to be getting home, I'm afraid. Busy day tomorrow, eh, Judge? Well, I don't know if you... Yes, the law is a stern mistress, a stern mistress. All those briefs to read, decisions to hand down, bills to collect, not much time for play, is there, Judge? No, the law's demands are pretty heavy, but as it happens... So if you don't mind Miss Goodwin, I think perhaps we'd better say goodnight. Perhaps another time? Well now, wait a minute. I don't know about you, Gilder, but personally I should be delighted to... Another time perhaps, Judge. All right, I can take a hint. I was beginning to wonder. Miss Goodwin, this has been most pleasant.  You must tell me more sometime. Yeah. Well, one has many amusing experiences in the law. I remember one particular case involving litigation over a dog. Another time, Judge. Oh, quite so, quite so. Good night, Miss Goodwin. Good night, Judge Hooker. Good night, Judge. Good night. Oh, Gildy. What is it, Judge? Did I tell you that Leela Ransom is arriving tomorrow? Yes, you did several times now. Good night. Good night. I'm sorry you haven't time to come in, Mr. Gildersleeve. Won't you at least sit down here on the porch for a moment? Oh, thank you, just for a moment.  Me? Why would anybody envy me? I envy you, your career. If I were a man, I can't think of anything that would be more exciting and more rewarding than a career of public service. Well, mine isn't much of a career, just water commissioner. Oh, but... Of course, the department did operate at a profit last year for the first time. Yes, and that's only the beginning. It's only a stepping stone. Oh, you think so? I'm sure of it. Well, I just think already you're a member of the school board. That's quite an honor, you know. Yeah, gonna have to be some changes there, too. Last year, the water department. This year, the school board. Next year? Who knows? With the right guidance and encouragement, there's no telling how far you might go. Uh, Miss Goodwin. Yes, Mr. Gildersleeve.  You've been around. Do you've had experience? Let's just say that I'm a woman. I'd like to ask your advice. Do you feel that marriage helps a man's career or hinders it? Oh, I think it's a great help to it, definitely. After all, nearly every great man in history has had a woman behind him. Well, I was asking his advice on behalf of a friend. Oh, this is a friend? Yes, a friend. Well, I've known him for quite a long time, too, he said. Well, he happens to be in public office, too. Only in another town. I see. Not married. No, that's the point. He happens to be about my age and he lives alone with his niece and nephew. He was wondering whether he ought to get married. You mean he's met someone? Oh, yes. He's taken quite a fancy to a certain young lady who moved to this town. He lives in. Oh, well, tell me, what is she like? Well, she's, uh... Is she attractive? Uh-huh. You know, she interests me, this friend of your friends. Uh, tell me more about her. Well, she's young and not too young, but just about right. Yes, go on. The only thing is, she happens to be a widow. Oh. Yes, they were very close there for a while, as I understand it. But then she left town. Now she's coming back and the question is, well, should he or shouldn't he? Mr. Gilda, see, I wonder if your friend has ever read a book called A Human Bondage. Well, he's a pretty busy fellow. I don't think he gets time to do much reading. You recall it yourself, though, of course. Oh, yes, yes, fine book. And so true to life. I must read it again. But about my friend... You remember it was the story of a man, a really splendid man, who fell in love with a girl who was beneath him and how she dragged him down and ruined his career. Say, didn't they make a movie of it? Betty Davis. Come to think of it, my friend saw it. Then you might just remind him of it. I'll do that. What he should ask himself is, can this woman really give him the things he wants in a wife? Is she fitted intellectually to be a suitable partner to him as he goes on to higher things? Well, I don't know that she's so much on intellect, but then my friend is very broad-minded. Nevertheless, I think he might be wise to keep their relationship on a platonic basis for a while. Platonic? Yes, he hasn't tried that. Yes, at least until he's sure. Of course, I'm speaking only as a woman, but you asked my opinion and there it is. Miss Goodwin, I'll do that. I'll tell my friend they ought to be more platonic. That might solve a lot of things. Yes. And now, if you'll excuse me, I have a rather early day tomorrow. Yeah, I know. I've kept you too late. I know how to thank you. And my friend doesn't know how to thank you either. Not at all, Mr. Gildesley. Miss Goodwin, before I go. Yes? I'll tell you a secret, if you won't tell anybody. A secret? Yes. I haven't any friend. The friend is me. Why, Mr. Gildesley. Yeah, good night. Your usual self, I see. Marjorie, have you got a kiss for your old uncle this fine and glorious morning? Of course I have. Mm. Mm.  Marjorie, I've spoken to you about that. Oh, but uncle, darling, all the kids use lipstick. I know, I don't expect to be obeyed, but I do think you might ration yourself a little. That's nothing. You ought to see Wally Hoff after they've been to the movies together. It looks like he's got scarlet fever. Leroy, that's not true. Oh, yeah, look at her blush. You made that up. No, Leroy. He just made that up to be funny. Now, children, let's not start the day with any arguments. It's a fine morning, and besides, I have some good news for you. On the way, I wouldn't kiss Wally Hoff if he was a last man on Earth. Oh, yeah? What are you always hanging around with him for? If you two would listen to him. Because I happen to like the way he plays piano. Is there anything wrong with that? A likely story. Can a man and woman just be friends, we're going to say? Of course they can. Leroy eats your prunes. I ate them. Then eat something else.  She says her friendship with Wally is platonic. I, for one, am prepared to take her word for it. Thank you, Uncle Lord. Platonic? What's that? Platonic? Well, it comes from the Greek word... Well, there was this old Greek named Plato. A historian, wasn't he Marjorie? Philosopher. Well, a philosopher too. Anyway, he was a great authority on Greek. So, that's where we get the word platonic. Oh, yeah. Eh? Well, it means when a man and a woman are friends. Yes, it means... What would you say it means, Marjorie? Well, it means... It means no monkey business.  Good morning, Mr. Gillespie. Good morning, Bertie. You can take this dish if you want. I'm through. Yes, sir. Here's a bill, Mr. Gillespie. Bill? What's this? The cleaner.  What pants? The one you spilled a tomato surprise on the lap of. Oh, that's about time. By the way, Bertie, no more paper plates. No, sir.  I ain't bought a one, Mr. Gillespie. Not since the tomato surprise. Good. Not me. Not anymore. Not after you told me. No, sir. Good. Picnic or no picnic, I ain't buy no paper plates. That's fine. Bertie, another thing. Tell the cleaner to submit his bills monthly, hereafter. Monthly? Yes. Tell him I expect to be a very busy man from now on. I don't want to be pestered with a lot of odds and ends of bills. Just send me one, one a month. Yeah.  Yes, sir. But, Mr. Gillespie... Yes, Bertie? The man's waiting out that boy's money. I had three weeks for my pants. Why do you expect to be so busy, Uncle Moe?  You were? Leroy, did you hear that? Uncle Moe's been elected to the school board. Isn't that wonderful? How much does it pay? Leroy, it doesn't pay anything. The position is purely honorary. You mean you don't do anything? Of course we do things. We do a great deal. What? Well, we meet from time to time. How often? As often as necessary. What do you do? Well, we... How do I know? We pass on things. We make suggestions. As a matter of fact, I believe we even hire the teachers. Can you fire them, too? Leroy, I know what you're thinking, and it won't work. Anything, Uncle? There'll be no special favors for you. You'll work just as hard as anybody, young man, and even harder. Have you done your homework for today? Yes.  Bertie was dusting the piano. Well, go practice. Okay. From now on, we're going to have things done on the dot around here. I'm not going to have time for any more nonsense. Have I have to listen to much more of that? Let Bertie go. You stick to your lessons. See if you can improve a little. I'm doing all right.  Just put it on the table, Bertie. My goodness. The post marks from Savannah, Georgia. Oh. Savannah, Georgia. I wonder... Mr. Gillsley, didn't Miss Vanson come from Savannah, Georgia? That I couldn't say. Bertie, just leave it there, will you? Yes, sir. If it's from her, I won't read it. Did you open it and find out? No. Because it's from her, I'm just not interested. That's all. I made up my mind that now on, everything between us is going to be strictly platonic. Strictly. I think you're right. Maybe the best thing to do is burn it. Yeah. Now, hold on, my dear. I might not be from her, either. Time to think of it. I believe there was a classmate of mine in college. You used to come from Savannah? Yes. Smith, his name was, or something like that. Yeah. Smith. George Smith. Butch, we used to call it. Might be from Butch. Give it here, my dear. Just as I thought, Butch. Let's see what he says. My darling Throckmorton. Just a line to say that I'm coming back to Summerfield. I may even get there before this does. What does he say? He says he may be coming to town one of these days. Oh, really? Yeah. Let's see. He goes on here. I don't suppose you can ever really forgive poor Leela for what she has done to you. I don't ask that. All I ask is that if we should chance to meet anywhere, you'll give me your hand and believe that I am as ever your friend, Leela. Good old Butch by George. I'll be glad to see him again. The great Governor's leave will be with us again in a few seconds. Here's a $64 question that many families have been asking lately. What's Parquet Marjoram made of to make it taste so good? Well, that's a natural question. Because Parquet is winning new friends everywhere as a flavorful, nutritious spread for America's bread. So here's the answer to those questions. Parquet Marjoram is made by Kraft. It's made to the same high standards of quality as our all-craft products. Parquet is made from top quality ingredients, including highly refined vegetable oil and other products of American farms. It's made in modern plants as spic and span as a model kitchen. Parquet is delicious and appetizing. It's one of the best energy foods you can serve, an important aid to good family nutrition. And Parquet contains important vitamin A. Yes, there's 9,000 units of vitamin A in every single pound. Parquet is a quality marjoram that bears the seal of acceptance of the Council on Foods and Nutrition of the American Medical Association. So serve your family this delicious quality spread for bread at every meal. Ask for Parquet, P-A-R-K-A-Y. Parquet Marjoram made by Kraft. Now let's get back to the great Gildersleeve. He hasn't been able to get his mind on his work today for some reason, possibly because of a sleepless night spent tossing from pillow to pillow and post to post. Determined not to lie away again tonight, he drops in at Peavey's drugstore in mid-afternoon. Well, hello, Mr. Gildersleeve. Why don't you put a stopper on that door, Peavey, so it won't bang? You must be a little on edge, you never noticed it before. How long has it been that way? Every summer for 23 years. Yes, sir, 1920 was the year I bought that screen door. Never mind, Peavey. Before that, I just had flat paper. Let it go. Have you got a good reliable sleeping powder? Insomnia? No, I want it for a hangnail. Well, no, I had one customer who used to take sleeping powders because he liked the taste, but he overdid it. Did it kill him? No, but he became quite as unambiguous. So let's not rush into this.  Well, I wouldn't say that. I've done some pretty hasty things in my time. Oh, you have. Yes, to mention only one, that's Mrs. Peavey. The minute I laid eyes on her, at that time, she was Miss Horsefall. The minute I laid eyes on her, I said to myself, there's the girl I'm going to marry. You did? Of course, I didn't ask her till five years later. Peavey. About the sleeping powders, Mr. Gillers-Leave. Maybe a simple home remedy would be just as effective. Have you tried hot milk? I want something stronger. I can't stand another night like last night. Oh, have you had a number of them, or was this the first? This was the first, but I wanted to be the last. The reason I ask is that a lot of insomnia is in the mind, Mr. Gillers-Leave. Anything been worrying you? No. You're not nervous about anything? No. You haven't had any bad news lately? No. Peavey, I came here for a sedative.  No, France, you see, sometimes... Wait a minute, Peavey. Quiet. Didn't I hear a train? Oh, the 419, I guess. Yeah, right on time. 419. Oh, I've got to go. Expecting someone on it? No, that is not exactly. I just like trains. What do you do? Go down to the station and wave at them? I'm not going to the station. Peavey, I'm going home. Well, you won't find a train there. Oh, I know. Is there no other room in this house where you can practice? Well, you want me to practice, don't you? I suppose so. Nothing at all. You watching for somebody? You just watch your little music. Walking up and down? That piece would make anybody nervous. Why don't you learn to play something good? Something by Bach or Beethoven. Who wrote that, anyway? Bach. Must have been... Must have been one of his bad days. I'll conclude your piano lesson for today, young man. All right! Leave me alone, will you? I'm going to try to get a little nap here on the couch before dinner. Okay, uncle. Sweet dreams, punk. What goes on next door does not concern me in the least, Leroy. Besides, I've told you time and again it's distinctly bad manners to pry into other people's business. What do you see? You mean it's Judge Hooker. Is there anybody with him? Leroy, I asked you a question. It's her, uncle. It's Mrs. Ransom. Oh, that's so. Mrs. Ransom, huh? How does she look? Judge's arm. Leroy, how does she look? How? What do you think I am? A peeping tom? Anyway, it's nothing to me. You better hurry, they're going inside. Where? Oh, your mister. Why didn't you get out of the way? Well, gosh, you don't have to knock me down. All right, if you can't keep your eyes open, make room for somebody who can. I can't stand this. What the devil is Hooker doing over there so long? Did you say something, Mr. Gillsleeve? Just talking to myself, Bertie. I'm going out for a minute. Well, Mr. Gillsleeve, supper's almost ready. Don't worry, I'll be back for supper. It'll be ready in five minutes. No less than that. Uh-huh. I will, too. I'll just come to a quick understanding with Leroy. Get the things settled once and for all. And maybe I can get a night's sleep. Get everything straight right at the start. Well, hello, Gillsleeve. What's the idea of hanging around here, Hooker? Don't you know when to go home? I think I do. I've seen no evidence that Mrs. Ransom is bored with my company. Where is she? She's going upstairs to get some papers for me. Well, you might as well come in. Don't worry, I'm coming in all right. What have you been up to all this time, anyway? Well, we had a lot of things to talk about. What, for instance? What do you care? I don't. All I want is an understanding with Leela. Now on, she and I are going to be on a strictly platonic basis. I want to make that plane to her. No. How is she, Horace? As beautiful as ever. Uh-huh. What's she going to do? What are her plans? She's going to stay here, live here. Booker, did she say anything about me? Not that I remember. She must have said something. No. Oh, yes. She asked if you'd been lonesome during the summer. What did you say? Did you say anything about Miss...what's her name? Miss Goodwood. What would you care if you and Leela are going to be so platonic? Oh. Wouldn't want to make her feel bad, you old goat. If you... Oh. Here she comes. Morton, it's so nice to see you again. Yeah. Nice to see you. Leela? Can't we harsh it down? Yeah. Why not? I thought you were going, Judd, as soon as you got the papers. No hurry. No hurry. Yeah. Like a whole whole week, huh, Leela? Yes, Horace. Here are the papers. Thank you. You're looking well, Leela. Oh, not really. But y'all looking well, Throckmorton? Uh, feel pretty well. Rocking chair still squeaks, doesn't it? Yes, it does. Well, yes, I'd better be running along. Must you, Horace? Must you, Horace? Well... Yes, I'm afraid he must. Goodbye, Judd. Goodbye. I'll call you tomorrow, Leela. Oh, thank you. You've been a good friend to me in my time of trouble, Horace. You can count on me. Bye, Gildy. Goodbye. Good night, Horace. Good night, gracious lady.  Good morning. Go home, Hunter. Well... Well, here we are. Everything's so changed, isn't it? You look different, Leela. Do I? Well, I guess it's the black dress. I'm in mourning, Throckmorton. It's true, then. Beauregard is... Yes. Positively? I buried him, Throckmorton. He was a fine man. I'm sure he was. Leela, I wanted to say something about our... Well, Throckmorton, you have no idea how Beauregard had changed. He was a different man. I declare he was. Well, how do you mean? He came back because he needed me. He never needed me before. Oh. And all these last few months before he... Yes, yes. He was so sweet and sympathetic and thoughtful. He was wonderful. Yes. Well, about us, Leela, I just wanted to say... I always told you Beauregard was a gentleman, Throckmorton. Yes, Leela, you always did. And where did you live all summer? On my family's place down south. It's just a plantation. Was Beauregard practicing law down there? Oh, mercy, no. He wasn't doing anything. Nothing but just be sweet to me. Did he have any money? Oh, no. Beauregard never had a penny, the poor lion. But he was such a handsome man. Didn't you think he was handsome, Throckmorton? What? I thought he looked like a jiggaloo. What? And I was right, living off your family. Throckmorton, I will not have you talk that way about Beauregard. But, Leela... No one ever understood poor Beauregard but me. No one. No, Leela, I didn't mean to. I knew the real man. He must have been a fine man, or you wouldn't have married him, Leela. Oh, he... Here, take my hand, could you? Oh, thank you, darling. Oh. You're the only man in the world as thoughtful as Beauregard was. Oh, I'm not thoughtful. Oh, yes you are. You're sweet. Leela, I want to get things settled between us. Oh, please, Throckmorton, if you knew what I've been through.  What are you talking about, Leela? Why, if he ever saw anyone mistreating a dog or a horse or a cat, he was furious. That's what made it so sad. What, Leela? Beauregard's passing. How did he go, Leela?  Well, we never know where it's going to come from, do we? Weeks ago today.  There, there, have a good cry on Throckmorton's shoulder. Oh, you're so sweet. So are you. What was it you've been trying to tell me, Throckmorton? Tell you? Well, what I was going to say, Leela, was that, well, I think maybe you and I should have a more platonic relationship. What, Throckmorton? A platonic relationship. Oh, Throckmorton, five weeks is too soon for us to be thinking about things like that. Good night, Throckmorton. My position to bully your friends. Well, I'm not bullying him. What? Something he borrowed. What did he borrow, Leroy? Your electric drill. My electric drill? You tell him to get it back here in five minutes, or I'll have him expelled. Good night, everybody. Good night, everybody. This year, thousands of women all over the country are discovering what a special help with wartime meals is the product called Kraft Dinner. A box of Kraft Dinner gives them a lot of delicious macaroni and cheese for four people and only a few cents of serving. They get two boxes of Kraft Dinner for only one single ration point. And with Kraft Dinner, they cook that delicious main dish in just seven minutes. In every Kraft Dinner box, there's a special macaroni that cooks fluffy tender and boiling water and an envelope of Kraft grated. With this handicraft grated, you whisk cheese goodness through and through the fluffy macaroni in a jiffy. A very smart trick is to shape the hot Kraft Dinner in a ring mold for a minute or two, unmold on a platter, and serve with cream vegetables or fish or a little meat. But just as is, Kraft Dinner gives you a mighty fine main dish. Try this seven-minute macaroni and cheese soon. At your food store, be on the alert for point-saving Kraft Dinner.