 Well, thanks everybody for showing up for those of you who don't know who I am. My name is Wayne Stamball. I'm the KeyCAD project leader and I'm going to give you a little talk. It's going to be fairly short today because I want to spend some more time in Q&A than the past. We've had a lot of questions that have to go in unanswered and I have to spend two hours outside, talking to people. So I'm trying to give us a little bit better Q&A today. So I just want to give you a heads up on what's going on with the KeyCAD project. In the last year, since my talk last year, we've had a lot of really good things happening. And I don't know how much people follow the project or not, but it's been really, things have really are starting to make a pretty solid trajectory upwards. So we released version 5 in July, finally. That was pretty painful. I was hoping to have it out last year by FOSDA, but we weren't even close. But you know how that goes. So as part of that, we had opened up, CERN had opened up a campaign to start funding the next version, version 6. We were originally hoping, I think what was the original target? 30K. 30K. And we ended up getting 70,000 Swiss francs in less than 60 days. So if any of those donors are in here, thank you. I mean, it was just unbelievable. Yeah, give yourselves a hand. From being in this project for over 10 years now, it's pretty humbling to see that kind of generosity. So that's fantastic. So some of the work packages of all to people are wondering, OK, well, now that you got that money, what's happening now? Well, some of the work packages have actually been drafted. So the way we work it is through CERN is we create a work package, then the developer usually we don't have a, we really don't bid in the classical sense that, yeah, here you go do it because there's only a handful of developers that can really really get it, yes, actually dig around in the key cat code base because it's rather large and rather complex. So there's a handful of people that can fulfill those packages and some of them have already been assigned and metered out. So talk a little bit more about that later. But on the donation front, there's been a lot of interesting developments. Our friends at Eisler have, yep, there they are, they're here, the gentleman who did the last presentation, he's also part of Eisler. They're donating, every board order they get that has, that's with a key cat file with a known key, like you send them your PCB new file. They make a donation for every order that you order for them with key cat and it goes directly to CERN and that's set up and it's all automatic and they've also added an extra link on their website. So when you place your order and if you want to donate at the same time as you place your board order, that also goes directly to CERN for the key cat foundation. So thank you Eisler for that. I don't know how familiar Europe is with the System76 people but System76 is a U.S. Linux, they're a big Ubuntu computer maker and they do laptops and desktops and they basically always bought pre-made hardware for their, like a lot of resellers do. Last year they decided they were going to do a new desktop called Thelios and I don't know if you've seen them yet but they're very cool, they're very neat. If you get a chance go to their website and look them up and they gave us a percentage of, they decided to donate to four open source software projects that they use in house to do their, to run their business and last year between, I think it was like November to the end of January this year, their total sales and I haven't heard what that amount is yet but they're going to take a part of that and donate to key cat as well. So that's really good news, they gave, and they created this quirky little promotional video, I don't know if anybody's seen it but there's a link to it there that has key cat in it. And on another person who wrote, there's a gentleman who wrote a book called key cat like a pro with a company called Tech Explorations. He's also going to donate for every sale of the book, he's also going to donate a percentage of the proceeds to the key cat through CERN. That's in the final, because it takes a bit to get the routing done and whatnot, that's almost in the process of being approved so that should be done soon. And of course there's the never ending like improvements in our symbol and footprint in model 3D, or 3D model libraries, I don't know how many of you use key cat directly but if you look back, if you go back and look at our libraries at four and you go look at them now. I mean, think what is our library up to, like five gigabytes, six gigabytes, a download? I think six and a half. Yeah, it's really, and they're really high quality. We have some people that are really, really, really, in fact there's more contributors to the library, I think the library, well the library group, the actual source developers, so it's really phenomenal what's going on there. This year, about two years ago we had a couple of new developers that joined the project and they got up to speed really fast and did a lot of contributions. So for the first time in a long time, I've actually given three developers commit acts that commit privileges to the main source repo in key cat. And that's really helped move development along really quickly in the last year. It's been pretty phenomenal. We also have new developers, we have a lot more people like at the fringes, you know, I see patches from people that I don't recognize, so that's really encouraging, the interest to help contribute to key cat keeps growing. For those of you in the U.S., and if you haven't heard this, in the U.S. in April 27th, or 26th and 27th in Chicago, there's going to be the first ever key con. There's going to be a conference and it's going to be user-focused. It's not going to be, I'm not going to be talking, I don't think I'm going to be talking to developers. So if you're interested to get a chance to go to that, I think it's going to be really good. The people that are helping to run it, Chris Gamble and some of the other folks that live up in the Chicago, in the Great Lakes area, they really, it looks like they're going to have a nice thing. And so far we've got Digikey as one of our primary sponsors. We've got the folks, I don't know if you're familiar with Snap EDA. They're like a library. They provide library tools for our friends at Isler. Yes, our friends at Isler also. I saw you up there. So, yeah, we're all looking forward to that. It should be interesting. And that'll be like two days of personal experience. People who use KeyCAD on a regular basis. I think some of the, I want to say some of the Maker Faire people are going to be there to do some of the talks. Their experience, how they use KeyCAD and things they do with KeyCAD. So that's really, really interesting. And so if you get a chance, I highly recommend that you show up and make it to that. I think that's going to be a lot of fun. And of course, I get to do the keynote on that one. So, yeah, that'll be the first ever KeyCAD conference anywhere in the world. So that's exciting. OK. So you're probably going, well, where's version six? Because you know everybody, you get one version out and everybody's going to, the first question out of everybody's mouth is, when's version six coming out? Well, hasn't started yet. And there's a reason for that. On Linux, we ran into a problem. There's been a transition with WX Widgets, which is our primary tool set, which is our UI tool set. They've been migrating over from GTK2 to GTK3, right? Well, we ran into a problem. Because WX Python, which is our glue Python interface, still is built with GTK2 because it can't be built with GTK3 and Python 2. It has to be built with Python 2. So you can't run a GTK2 instance and a GTK3 instance in the same application, boom. So we had to make a decision. It wasn't what I wanted to make, but we're going to have to fix it. So that's why we're getting a version 5.1. And that's going to be, that's what drove that. So the other problem with that was GTK3, their standard canvas is completely broken. It doesn't work at all. So we were completely screwed. So if you use the legacy canvas, if you're familiar with Keycat and use the legacy canvas, like in the board editor, the schematic editor, the graphics are complete junk. And so we were like, ah. So we had to port the graphics, the high end graphics library from the board editor to the schematic editor. That's already done. It's been done for a while. So we had to disable the legacy canvas because it would be useful. We'd get bug reports. When that first transition first took place, the bug tracker was just flooded with the same bug report, basically. We had to modify the Python scripting to support 2 and 3 before we only supported 2 because we only had to. WX Python only supported Python 2. But the new Phoenix project, which is the next evolution of WX Python, only supports 3. So now we have to be able to build with 2 and 3 and all the different combinations of WX Python, WX widgets, and GTK2 and GTK3. It's a mess. So we updated the, there's been a lot of UI interface changes, which is, you'll notice that the footprint editor now looks like the symbol library editor, where you have the pane on the left and all your footprints show up. And you can edit it, it's very similar in design. Because we had the five transition. We had the left over. We had the new design and the schematic symbol editor, the old design and the footprint editor. And that's been fixed. We switched to Cairo for printing. We get a little bit better quality printing for, so that was a big change. The usability, I can't overstate the UI changes. One of our new developers is a retired Adobe employee. And he's a UI guy. And he just bangs out code like, yeah, he makes the rest of us look bad. And he's really good. So the UI, if nothing else, 5.1 will be compelling just for the UI changes and fixes. It's really significant. I mean, even though there's no new functionality in there, it's just the whole feel of, you know, he's basically the whole suite of your dialogues and how they behave. And so it's a lot more coherent than it's ever been. Which if you use KeyCad, you know that's not always been the case. Well, I mean, it's got 20 different people over 20-some-odd years doing. It's just how it works. And we're not the only open source project that suffers from that problem. So and we had improved clipboard support. So now it's more like your normal copy paste instead of the old way we did it. It still don't do a lot of copy and paste between the different editors because that's a tricky proposition because some things you can't paste from a footprint editor from the board into the footprint editor because some of those things don't mean anything to the footprint. So we're going to work on that in version 6. So we did the feature freeze in December. And we were tantalizingly close to getting RC1 out. I was really wanted to have another bullet here that said, RC1's been tagged in release. But it didn't happen because there's one bug left. And yeah, he's sitting up there that nobody can figure. And he's got the only computer. He's got the only computer. And I wouldn't have believed it if I wouldn't have seen it with my own eyes. But I spent some time this morning and it didn't fix it. So we get that one. That's the last showstopper that's holding up the 5.1 RC1. And after RC1's released, I'll give the translators and our librarian guys a chance to get their last minute changes in and get everything ready. So hopefully, hopefully, if nothing too egregious goes wrong, we should be late. At the end of February, beginning of March, 5.1 should be rolling out. So that's kind of exciting. And then once we branch 5.1, then the main repo will be open for version 6 development. Because I know there's quite a few people that have some significant changes and features that are actually ready to merge. It's just I don't want, if I open the merge window up, everybody will forget about getting this done. And we'll go work on 6. And then we really need to get this out and get it done. Just because I don't want our Linux users to be, we could give them half a key card. And I didn't think that was a good option. So I made the decision to postpone v6 development. So that's all my shoulders. But I think it was a good decision, at least the way I see it. I'm not going to talk too much about version 6. I've talked about that before. You can always go to the key card website and see the roadmap, the v6 roadmap. Some of that stuff's already been pulled into the graphics layer. That was actually pulled in to fix the problem. So some of that, it's a little out of date. But most of everything else that's going to happen in version 6 is already defined. So and just I want to say thank you again. I'd like to thank everybody who contributed to key card, whether it's libraries, translations, source code. There's a lot of people that actually work on key card that make it work. It's a really big project. I don't think people realize how much there is involved in all the packaging, the guys who maintain our build servers, all that stuff. A lot of work goes on behind the scenes. And I might be out in front of everybody here, but there's a lot of people that make that happen. Once again, thanks to everybody that donated. I mean, like I said, that 70k Swiss francs was huge. I mean, I can't overstate that enough. Thank you for your interest and support. We keep growing the number of reports. I get a lot of reports from people, board vendors, that tell me that the number of orders they get now from key card is really like Osh Park in the United States. I know some of their guys. And they tell me the number of orders, board orders they get that are direct key card order. Because you don't have to convert everything to Gerber. You just send them your board file. And they produced your boards right from the key card. And the number just keeps growing and growing. So we're definitely making inroads. And that's the goal. The goal is to keep moving key card. I'm an engineer. So people don't know that I'm a double E, right? And the reason I work on key card is I actually use key card in my day job. So it is capable. And if you don't believe that, go look around some of the really complex projects that people are doing, I mean, really complex stuff. We have a guy that wants us to go above 30. He has a 32-layer board. And he wants us to, right now that's our limit. We have 32 copper layers. Let me clarify that a little bit. He wants to do more than 32 copper layers. So I mean, it's serious. It's serious. I mean, so yes, are we on par with the big players? No. But every version that comes out, every new version, six will close a lot of the feature gaps. So we're just marching along. We're going to get there eventually. But it's definitely something that you can really make use to, if you're an engineer and you need a board layout, especially if cost isn't, because I work for small companies. So cost is a factor. And almost all the big players in that game now are very, very, it's expensive. It's really, really expensive to buy board development suites. If anybody works in a commercial world, they know what I'm talking about. I also like to thank CERN and Javier for setting all this up. This wouldn't happen without them. So thank you to them for setting it up. So all right. Any questions? Yep. Firstly, simple one, how about in other comments, what is 70k Swiss francs? Oh, the question is, what is 70? What's that? Oh, thanks. Because I saw your voice. Yeah. The question is, what is 70,000 Swiss francs? It's almost 1.5. It's just slightly more than a US dollar. So it's almost one to one. And you could almost, I think in the. 1,300 euros dollars. There you go. And one. And what? And your second question. Go ahead. So yes, second question is, I've been using Eagle for some time. I think there's still some problems with the Eagle import. Is there any plans to fix? Which the question was, there are some still issues with the Eagle import. And so my next question is going to be, which we know there's some things. Because there's some functionality in KeyCAD that does it. The biggest thing I can think of is constraints, like the geometry constraints. The geometry constraints in Eagle don't map one to one to what KeyCAD does. Now, some of that, that's one of the version six fixes. We're going to have a full-featured constraint manager. So at some point, we should be able to get pretty damn. I don't know if we'll ever get 100%, because they use a kind of funky matrix thing, right? It's a little different than what. So we may never get pure 100% import in, but everything else. So the issues I'm having, I like the oblongs, which are much smaller pads. Oh, OK. All right, I think I understand. I actually put two public boards in this. So the question is, and I'm assuming Eagle can do this on a fly, because it's I haven't used Eagle's in a decade, so it's not really. I don't even remember that far back hardly anymore. So the question was about being able to change pad shapes on a fly when you import it. And that's probably going to be problematic, because we use hard, basically hard-coded pad geometry. So if you have a footprint, right? Now, you can update a footprint. Like, say you change your existing footprint. We have a way to update automatically, but we don't have a way to change them on the fly. Like, say, instead, I don't want all my pads to be oblong instead of round. Yeah, we don't have a way to do that. It'd be nice if just when you import and actually read those design rules and say, actually, no, I need at the import stage, because otherwise, then you get a board that is just doesn't pass proper checks. OK, we'll have to look at the top. So we'll have to look at that. Yeah, I don't know. I haven't looked at that, so I don't know what the answer to that is. There's a few bug reports, so the key problem is that Yeah, well, I have to talk. Yeah, I don't do much work with the Eagle Importer. So that's not my exact strong point. So yeah, it's and we know that we know that from other and we know that from other board. Yeah, we know we know that from other board packages, too. That when you pull a constraint in what it means and that board package means doesn't necessarily map to the same constraints that we have in keycats. It's not an easy problem to solve. Yeah, the question that somebody, people know me in here, so they're going to know what the answer to that question. The question was, the question was, could we simplify the key cad user interface so that it's easier to use and it'd be more like fritzing? I'm going to, you know what, if when we have all the other problems solved, we can talk about that. I mean, yeah, we get and don't get me wrong. I'd love to support everybody's project every way they wanted it, but that's just not reality. I mean, one of the problems I get is every once in a while somebody gets mad because our UI doesn't work well on a 800 by 600 resolution monitor. Like, I'm sorry. Who lays out boards on an 800 by 600 monitor? Who does that? My eyes aren't good enough to do that. They don't make monitors big enough to lay out boards. And so when I hear people say that, I'm like, come on. So yeah, I mean, I get it, I get it. If there was some way it was easy to make, you know, make all those like different configurations work. But it's, yeah, we got, to me, that's like one, okay, when we got all these features done and we're on par with the big guys, okay, we can go back and revisit that. But I think we got a lot of work to do before we get to that point. So yeah, go ahead. Okay, the question was, the question was moving from right now the source, the question was moving from Launchpad to GitLab, right? Yeah. Okay, there's, I didn't talk about it and I probably should have. There's currently, we are in the process of migrating the key CAD servers. I think the web server's done. Correct me if I'm wrong. Awesome. Yeah, yeah. So we're migrating to CERN servers, okay? So the website's done, are the downloads, are the package downloads done too? Okay. And part of that discussion was at some point in the future. Because one of the problems right now, if you don't know key CAD, the source is still in Launchpad with that. I mean, we use Git, but it's Launchpad's supported Git isn't necessarily the best. So we're there with, that's where our source is and of course, like the libraries are all in GitHub. And so for me as a project manager, because I got to interface with all those different, just separate groups, it's actually makes more work for me. So the end goal is to get all that in a GitLab instance somewhere. And so that's just gonna take time, but yes, that has been talked about and it probably will happen at some point when we just one step at a time, we just gotta, I don't wanna try to, I don't wanna create a lot of work for, because that's something I don't do. So that means it's work somebody else does and I really don't wanna bury somebody and just on a whim say, we're just gonna totally migrate to GitLab tomorrow. And that's not very realistic, but I think it'll happen, yeah. Yeah. Is there some list where people can have local support or so get a head start? I designed PCPs for 15 years with Eagle, but to switch on, I would like to have a head start, some go to somebody with some problem and talk together and see how he works. Okay, the question is, is there a list you can go to for, I'm assuming you mean user support or help? Yes, there is, there's the key cat info. There's a forum and it's pretty heavily, it's pretty big. I mean, it's run by Chris Gamble in the United States. He set it up, it's really, a lot of times some of the developers show up there for like the really tough stuff or the regular, even the advanced users don't necessarily do the answer to the question, but it's actually a pretty good, it's actually a pretty good resource for a new user. It's very good and there's a lot, there's usually somebody that can answer your question. Yeah, don't post user questions on the dev mailing list. It'll take a while for you to get an answer, but yeah, key cat info, if you go to our website and go under, is it resources? There's a dropdown, you'll see the blogs, it's under there, use a direct link to it. You can go to it from there, yeah. I actually have great questions, if you don't mind. First one about schematic editor, in schematic editor, we need to really think when we place components before we only have rubber band connection, right? So if we try to drag components when we already connected them, it's basically need to remove all connections and do it. Rubber band, yeah. So do you have any plans to implement like right angle connections when you drag components? Yes, the question is, are we gonna get rubber banding support? I think that's in six, isn't it? Yeah, it's in the roadmap, the six roadmap. So we have plans to have somebody work on that. When that happens, and I don't know, you just use the stable version, so you're using 5.0.2? Okay, so if one of the goals of key cat, if you're not aware, is I make a really strict point about making the nightly builds as stable as possible. We don't like, let's just dump everything into the repo and let's go and nothing works. We don't do that. And I never let that happen and I don't know that I ever will. So, because if you want people to really help you test, you have to have a reasonably usable nightly build. And so a lot of people, in fact, at work, I use, I always keep a stable install in case something goes wrong, but I pretty much use nightly builds every, every, when I, at my job. So in question six, or second question? Okay, you're free router. Okay, the question was what happened to the free router button? The reason the free router button went away is because basically that interface that we used for free router went away. You can still use it, but you have to, it's a manual operation right now. The old interface, you have to actually, you used to be able to, there was actually a website link that when you clicked on it, it would actually take you to the free router, the one on the one through your browser. And, you know, it would do the, it would export the spectra DSN file and then upload it and then you could, it was automatic, that interface is gone now. So we, you have to do it manually. You just have to go export the spectra directly and then you can just open up, you can run, you get the JVM and you can just run free router locally instead of through the web interface. It's, that's why that, that's why that went away. Okay, sorry guys, we need to move on with the program. What's that? Somebody, there you go, somebody wrote a Python script and that's why we have a scripting language, so. Okay, let's thank Wayne again. Thank you.