Now, you know, if I'm going to do a speech to the camera, I might as well just look at the camera. I'm right here. Here, go. All right. So, hi. I'm Chris Norris. I'm the Senior Collections Manager for Verde Rappel Intelligy at the Peabody Museum of Natural History. I'm also the incoming president of the Society for the Preservation of Natural History Collections, or SBNHC. For natural history curators and collection managers, I think probably our biggest challenge is the size of the collections that we work with. We have so many specimens, so many objects to deal with and work with that it's very hard for us to make decisions about conserving those objects on the basis of individual object-based treatments. We have to focus in on preventive conservation. And this, I think, is a very good area where SBNHC can work with the Collections Care Network at AIC to come up with some really creative solutions to our problems. It would be great to see this as a two-way process whereby our membership in Spanish that has a lot of experience working with large collections can tap into the collective expertise of AIC, conservation expertise of AIC, and whereby people in AIC that have maybe had more experience of object-based treatments can begin to learn about and understand some of the challenges that we face in natural history collections, working with units of tens of thousands, hundreds of thousands, or even millions of specimens. So this is a great, great opportunity for our two groups to work together. SBNHC has been a strong supporter of Collections Care Network from the outset and we're really looking forward to working with the group in the future.


You are about to witness an epic Tarot Magnus reaction. What is happening, Magnusite? Back with another Hitler-reacts to Chuck Norris is coming. So, let's get this on. It's time to talk about the information. In the south, there is a house and a support for Stansdorf. The enemy is on the north side between Furnau and Pankow. In the east, the enemy is on the right side of Ragnarok-Mansdorf. With the attack stone, everything will be fine. Chuck Norris is unstoppable. It's left in the room.  It's on the way, baby. What's funny was, I saw that title. I just had a hunch. I didn't think it would be too good. When I was doing the other ones, I was like, I don't know if Chuck Norris would be funny or not. Do not judge a book by its cover, man. It's hilarious, man.  Or I'm sending Chuck Norris to your house. What many subscribers?


Okay, hello everyone. Welcome to the Jenkins infrastructure weekly team meeting. So today that will be overloaded because we cancelled the meeting last week for. I was alone as far as I can tell available for running it. We had production operation that were planned that day so the combination of all of these make it made it harder. Today on the table, we have myself damaged the portal. Marquette, Stefan is off green with off and Kevin is there with us. So announcements from the two past week. The Jenkins version 2.413 and 2.414 are available. Last week. This week so I haven't had time to finish a comment but I started an issue about the release process. So the goal is to track somewhere because I thought we already had an help desk issue, which we didn't. We already have an help desk issue for infrastructure about moving all the application process to release CI, which is something that is discussed. But today, we want to automate the manual task where we create an annotated tag and we publish the draft release. That is something that changed compared to six months ago, for instance, and it's a manual step documented on the release process. So I've opened an issue because these steps could be automated at least for the weekly release. I saw the discussion you had with Tim Jacob about, yeah, maybe we can or cannot automate it for the LTS core release, which should be doable. But that was the exchange for security release that will need to update, that will need to an exchange with the GenSec team. Another fun thing, Marquette, we discovered with Irvine realized I was a bit enthusiastic to create the tag. And I created the tag before the packaging builds was finished. And I realized it was not available on get.genkins.io. Exactly. I need to add a comment that one of the release parts and the release process must be done. That's the part that push it, at least on the archive Genkins.io mirror. So get Genkins.io as at least one example. I didn't realize this one, so we need to track it and I need to add a comment on the issue I created earlier. Well, and my apologies that that race condition is there. I thought it was valuable enough to do the poll from get from get.genkins.io even with the race condition because I was aware of the race condition when I proposed it and accepted the race but obviously if we lost the race once we need to implement a fix. Yep. So last week release went well. This week, we had two issues. So the one we just mentioned. And another one, since we have graded Kubernetes last week, I run a replay of the package thing because I wanted to check that the agent were properly created on the corresponding not pool to avoid a bad surprise today. And packaging failed due to a replay build. Because when you replay a build that clean up the parameters. And as we already have an issue on Genkins in France leads. We still have a no old issue that say, hey, if there isn't a previous build. Then we are stuck. Where is that one? Oh, it's on packaging. We, I think that's that one. So the initial build on a given branch for the package process at least and I'm sure the release has the same issue. The first build is failing and need to be retry a second time each time we create a new LTS the dot one of LTS has that problem and the replay on the master branch that I did. Cleaned up the previous versions. So today's packaging weekly bill failed due to the same reason. He didn't have the default value. So it failed because it was empty and the shell script failed if it's empty. So we have good safe words, but we need to solve at the pipeline level to provide the default value that could at least allow us to replay. Because I don't know for the LTS initialization, but for the weekly release, it shouldn't happen. So replay the build and that's okay. I need to open an issue or at least update the existing issue. Let me add this to open issue or comment on existing track this race condition need to wait until war is available on get the Jenkins IO. That's all for me for the weekly releases is there. There's something else to add. So I've confirmed that the container image downloads and build successfully so so that part was successful even after the race condition got exercise so the rebuild must have worked. That's great. Thanks. The change log has been merged. Thanks to Kevin for proposing changes to the change log. There was an oddity in the change log that sometimes happens where the automated change like generates unexpected things. And I didn't do the investigation to figure out why I just fixed it. Just to note about the change logs. I'm impressed because since one year. We have the weekly release and the change log done the same day every week. That's really impressive. It sounds normal now today. But trust me one year and a half ago. That wasn't easy to have this kind of timeline so congratulations to everyone involved in the process that's really efficient. Well and thanks to Tim Jacob for his automation of Jenkins change logs it really is a much better experience thanks to his automation. Yeah. That's all for me in the weekly releases from both weeks. Anything to add or questions or things to play for cool. Regarding the announcements. Next week I will be off. So I need you folks either to run the meeting or to cancel it. I'm available to run the the the zoom part of it. If every is willing to run the the actual meeting agenda part of it. Is Stefan back next week. No, that's why I am asking Stefan and Bruno will be off so that will be only the three of you. So maybe we just intentionally cancel. What do you think? Are they you will. Will you be off in two weeks. No, I won't be off in July. Okay, so that means that we move to the 20 25 of July. Is that correct? Right. Let's cancel. Next week. Meeting and run the 25. Sounds good. Yes. I can I ask you to update the milestone and created just before the meeting to update it from 18 to 25. Okay. That's all for me on announcement. Do you have other announcement folks. Okay. Then let's continue with the upcoming calendar. So next weekly won't be delayed like the meeting. So next week. We will have the 2.415 version. I've already forgot the next. Not yet. So 2.401.3 will release. So let's see. So baseline or release candidate today. So releasing in two weeks on the 26th of July. Today, tomorrow, the new baseline will be selected. And the new baseline is likely 2.414. Because 2.413 looked very good. And I don't expect any surprises from 2.414. Okay. And 26. Okay. So I guess we will check the next baseline in two weeks during the week. Correct. Yeah, there's there's no crisis for us. Whatever baseline is selected doesn't doesn't have significant impact on infrastructure. Perfect. There is an advisory announced earlier today publicly for tomorrow. I haven't checked the content. Nothing announced. Nothing has been. Plugin Sony. Plugin Sony. I don't know what has been announced publicly just so then. He announced it in about three hours ago. Yeah, I saw the title of the mail, but I haven't looked at the body. Let's look it together. It's public. Yes, it is public and let's look at it. So for Jenkins plugins, not Jenkins core. Absolutely. So sorry, I cut you a. Okay. So plugins only. So that, that means that they, the GenSec team might need to access here. I was late on come on pinging them on that element. Thanks a lot for catching that really because otherwise they would have been. Slow down on that process. They will use the new CI Jenkins. So if any of the current plugin version are. Yeah. Are concerned then they would have to update it. Otherwise they only need trusted CI Jenkins to be up so they can publish Jenkins website when needed. Yeah.  Yeah, I mean, okay, we don't know. They haven't told us which plugins are involved in public disclose which plugins, but it feels safe to just say. We're going to restart CI Jenkins that I would tomorrow. And then if we don't. Okay. We smile and say we didn't. Yep. Absolutely. Yeah. I mean, is there a volunteer to open the status here? I can do that. If that's helpful. I have done that before and I'm comfortable with it. Okay. Thanks. So I saw you were a bit slower to answer than Mark or maybe the electron from Paris or slower. That means you are dizzy. You are volunteer to review and approve Mark's pull request and status. So, and, and I assume we set it for a time tomorrow. Okay. So you might have a timeline. So we'll deal with that privately until we, we know when they start. Usually. They always start at. So it's a 1 p.m. for me. So that will be. 11 AM. Yeah. I'll, I'll just, I'll make up a time. Put it on the status and then we'll correct the time because they can restart it. Anytime they want, right? I mean, it's, it's whatever pace works for them, but we just alert that we expect to restart there because it may. Okay. I will take care of upgrading all the plugin from trusted CI and CI Jenkins later today. So deep when they will update plugin will be as tiny as possible. Thank you. Thank you. That's very considerate. I see one plugin update pending right now. I saw seven and trusted as well. So get a check. Great. Okay. Next major event. I don't have any. Okay. Then. And we can start. With the huge list of things that has been done. I will try to be as, as fast as possible. I promise. Thanks. Survey for the work on integrating CI Jenkins. Say, Observability in data. Using the data. Plug in. So now we're going to go to the next slide. Okay. Okay. Next major event. I don't have any. Okay. And we can start with the huge list of things that has been done. I will try to be as fast as possible. I will try to be as fast as possible. Okay. So now we have data. Plug in running on the instance that sends metrics logs and traces. To the virtual machine data. Agent which. Buffer bufferize all of that data and send them to that. And now on that. There is a nice section. See I observability that provide dashboards and pipeline execution. And we can see. A lot of traces and telemetry. So now we have a full observability integrated in. Data dog and we can start doing things such as monitoring bills. For instance, monitoring the bills in infra acceptance tests. That could alert us when an agent cannot be spawned or when the package is not able to be installed or. A lot of things. So these jobs will be really helpful to warn us in case of issues. That will be helpful to study what is the. Why are the bomb builds taking so much time for simple steps. With the telemetry, we can prove that with the traces. And a lot of other use cases. So thanks for that work. That's really useful. And that will open a lot of. Improve management here. While we are on Seattle, it runs on a new virtual machine since last week. In a new network in a new resource group with a new hardware, which is way more powerful and cheaper. And it runs on a network. Which does not have any overlap and potential to. To have IPv6. So see, I can say, you is not reachable for IPv6, but it could be in the future. Then the former resources have been cleaned up. We did a lot of clean. Thanks for the help on there. And if you use to access see, I can say you're with SSH, you need to look at the new runbook. Like the GenSec team has to do today. Because there is a new, a new configuration. It's just us name change. And you need to use the new VPN. The private one. Because we change a network. Any question on that part? Okay. So let's go ahead. So, let's go ahead. Let's go ahead. Let's go ahead. Let's go ahead. Any question on that part? Okay. So let's continue. There's been an issue when releasing the JellyDoc Maven plugin. Thanks, Basil, for fixing the issue inside the plugin. That was due to the GDK version. And the trend and the set of transitive problems due to that. Now it's fully working with GDK 11. Even 17. But I'm not sure, but I know it's not GDK 8 anymore. Fixing the issue. Thanks Basil for that. Erwe, can you give us a word about Windows Server 2022 agents on trusted CI? Why did we do that? And what problem did we solve? So about two weeks ago, I started to work on creating a 2022 version of the GDK agent image to be able to provide the GDK agent 2022. The CI design that IO has already in those 2022 agents configured, but trusted didn't. So we added them to trusted. So the GDK agent, Windows Server 2022 and GDK agents, Windows Server Core 2022 image could be published on GDK. Thanks. So nice work. I haven't checked the result if the images were published, but I think you did, Erwe? Yeah, yeah. They are published and I've used them to test the 2022 version on the Core in Windows agent. Oh, nice. It's already building everything. I just have to finish a refactoring of the build process in the Core in Windows agent with you. The request is ready. And then creating the 2022 agent, the GDK agent will be as simple as adding a agent type in the trunk inside. Cool. So there is a part that now should move to the SIG regular meeting because we did what we needed to prove that the infrastructure did their work. Anyway, we still need Windows Server 2022 for the infrastructure because we have the release package that build the Windows official MSI during the Core releases. It's running using 2019 line images, not even LTS. So we will need to build inbound agent or to use inbound agent 2022 so we can upgrade the node pool, the Kubernetes node pool used behind the hood. And also we have the ACI Windows agent and CI agent in SIO that are used to run Maven builds on different Java versions inside the Windows environment. This should also be a target to use the brand new 2022 agent. We are building custom images today with Docker on Windows that inherits from these images that are published. So we will have them to update our own builds. In the future, that would allow us to switch every systems to Windows Server 2022 LTS. We will need to keep the 2019 builds, but these can be built from a 2022 Server Docker with Docker now. It will use virtual machine. It's a bit slower, but different isolation level. It's not virtual machine. But yeah. So that means we can move everything as recommended by Azure. That doesn't do everywhere. Is there any question about that target and usage? No. Okay. Mark, can you give us just a head up on the Jenkins board repository? So we've adopted the board. We're using the repository that was created. We've got agreement between me and Alex Brandes that will continue using it. And it's, it's got content. I'm sure we'll do more with it as time goes on right now. It's just a content archive, but it could certainly be posted to someplace like governance. Jenkins.io or, or see this archive. Jenkins.io or, you know, et cetera. That's, it's, it's initial purposes met. And I am pleased to announce that one action item that was on my list for probably two years is gone. Yeah. Thanks Mark. Any question? Yeah. Alex mentioned it in one of the issue of poor request. This also means you are already using. Or you will use. No, because Alex and I haven't settled yet. And I'm the note taker for the governance meeting right now. My strong preference is still Google docs. I appreciate that everybody likes HackMD, but editing, editing. Markdown live in a meeting is more difficult for me. So for me, I'm still prone to keep using Google docs. I've got to talk with that on support. What's that? You have Markdown support on Google docs. I don't know. And in fact, that's what we do is I run a Markdown converter from Google docs to output it to Markdown. It's very simple. It works great. And so, but for me, the editing experience in Google docs is faster. It's just easier for me if I, if I'm live in a meeting and Google docs. I was asking it because I saw the current export of the archive from 2020 to 2023 is one unique Markdown file. And I was about to propose to, to split it in daily or month year or like the other archive. And with that, I don't know. You might have to adapt your process for archiving. No, no problem. It's trivial. If we want to split it to a file per, per meeting, that's easy to, easy to do. And I fully support that if that's easier or that I have no problem with writing an individual file. That's what I did with most recent notes is I had to update them. I extracted the current. Ran it and it was easy. So happy to do that. No problem. I'm great if we split it to individual meeting profile. If that's easier for people, I am happy with that. Okay. Okay. Let's continue. We had an issue build money to plug in failing with 401 unauthorized. So that one was due to air pay. Repository permission of data build failures on trusted. I don't recall if the timeline was due to the outage. I caused the last Friday or something else, but that was the cause. And as soon as the build run again properly, then problem was fixed for basically update GitHub user to authorize as committers. So thanks. I think it's, I guess it's Alex. So someone added for permissions. So thanks for this one. Test history page and see agent can say for COVID is inaccessible. I don't remember what was that issue. It was after your side switch. Yeah. Okay. So that, that issue was due to other. Yeah, the S3, the S3. So there were too much builds. So the page mentioned by Alex, that was in error. It's the proxy time out on Apache because it took two to three to four minutes to load at the beginning. Due to another issue we'll see later we were able to rotate the builds. So back to an effective limit of 50 builds in the history of the master branch of Jenkins core. And now the time is 30 to 40 seconds, which is below the minutes. So no more time outs. So yeah, thanks for reporting. Thanks for the, because really pointed an issue on the G unit plugin that could have been related to that. So yeah. Now it's working. So no more problem. There were requests to add users so they can access to gen, to a Jenkins CI team. Releasing to incremental yields. So yeah, that was a five or three that was two weeks ago. So the incremental publisher was failing because someone here bumped the Node.js core version to trying to clean up the image. And of course that person named Damien DuPortal, which is me, didn't tested powerfully. So it started to fail. It has been fixed. But also we had a secondary issue that was initially using its authenticating, authenticating on CI Jenkins, API to retrieve information to get the build artifacts. That authentication is not mandatory, but could be used for API rate limiting. I'm still having mixed feelings about that. And I don't know how and why, but with CI Jenkins, your migration to new virtual machine, the token of the technical user we use disappeared. So of course the presented token, since it was, there were no token defined for that user on CI Jenkins. So CI tried to pass that token as an LDAP password to our DAP, which of course said, no, that's not the right password to use. Effectively it failed. So yeah, we created a new token on CI Jenkins. I'm sure I added the instruction and it was pushed on our secret store. And once redeployed, that's okay. Sorry, Mark, go ahead. So I think you missed one, one part of that story, which was incremental's publisher was not running dependabot at all. Right. So it was way behind and you found that problem, fixed that problem. And of course that meant there was a flurry of updates. And I blindly approved many of those flurry of updates. And so there was this terrifying period of blind approval because CI passed, but CI was doing almost no verification. So yeah, thank you. Thank you to all involved in fixing that. I guess I've got a question is, is there a way we should safety check our dependabot pages to be sure that if dependabot is enabled, it's not showing an error because I know plugins I maintain have that were on occasion, I'll make a mistake. And if dependabot, and of course it stops submitting, submitting pull requests because I broke it. But it's separate topic. Another time that's hard. I will say. I don't know if we can catch if dependabot is broken, but checking for the last image update, which was two years ago for incremental publisher, or one year and a half and checking for the presence of. Eventually the last. No, it's not with, I'm not sure if there is something on the GitHub API for updates. Yeah, you could look at the last builds, but yeah, I don't know. So we might be able to go ahead. We might be able to check the, to, to, to pull the check status and put the, the, the galerton needs something like that, maybe. You're, you're also sophisticated. I'd read the webpage for the dependency graph that says, I don't know if you can use the function and use that. I know that Olivia is working on a dashboard for dates, for that specific usage because the problem is that you need an, eggs today, whatever solution we choose, you need an exhaustive lists of the project, of the repositories that we need to check. And the more repository we'll create the more we need to update that list. That can be. Okay. But yeah, there is that, that's a complicated topic. And I don't know how it's dependent about answering to that. I would say with a Chrome running every repository and check user is a new dependent about config to add it to the repository to check that. But then how to exclude repository that I don't need dependent about for a lot of good reasons. Config, you can create a pull request with a new one and add an exception list to be reviewed by humans. Yeah, but that will mean a lot of process and things. But that's that's a good idea. Best if I just submit a ticket. If that's the ideas go go into tickets very nicely. Let me take it there. And the main cause of the second problem was the tests inside the application were on testing. Yeah, I don't understand that. Yeah, I don't know how to build and test. Well, and we have similar say cases and other things. We've got a back end extension index or bug report right now that has is highlighting that it's tests are not testing anything useful.  So, so that's a common pattern. There are there are a number of places where we would benefit by more tests. Our apps where tests are not. The tests are necessary but they're not sufficient right they're really not. Yeah. Okay. But now it's working well so thanks everyone involved because at least six person were involved in fixing that issue. Thanks. Brunch strategy and see a Jenkins IO diverge from prior configuration consequence of the migration as well. VM migration since we had we had to recreate a Jenkins home copied from the former one we weren't able to reuse the former one. We applied a lot and a lot of cleanup. And also we had issue with the S3 buckets that are archiving artifacts seen that later. So we applied thoroughly any elements. That means we need to think about using job DSL for defining the jobs in CI Jenkins iOS code. So this kind of elements will be easier to update and we could plan it easier because each time you try to scan it, you eat the API rep limit on GitHub. Effectively that break all the bills and say a Jenkins IO. Or no, that makes all the bill waiting on two with no information saying they are waiting unless you are an admin which is all full for the end users. Switch to job DSL for defining. Okay. Thanks everybody for the IPv6 support. Jenkins IO is properly set up everywhere. And all of the services running on on public on the new cluster are all available for IPv6. Except the service. Good points. It's working on on its own load balancer service. So we could add an IPv6 for the help service, but we can see the need right now. Yep, because we are the only consumer of held up and we don't need IPv6 for the connection to the TCP connection to LDAP. Accepted up our IPv6. Compatible. Compatible. Thanks. S390X. So I've closed that old issue because since we upgraded to 22 weeks ago, the machine. We don't need to replace it. And by the way, the agent was offline. I don't remember exactly, but there was a quick fix. I think we had to restart the agent in SAO. And it was upgraded at that moment. So I don't have anything else to add on this one. And we have an open issue for managing it as code in the future. Plug-in continuous delivery failed without factory permission denied. I don't remember this one, but I guess it was one of the outages. Oh, no, yep. That was one of the outages. In order to migrate to agent in SAO, we had to switch the agent configuration from SSH launcher to inbound. And there was an issue in the code. So the init script is run. That's a funny one. When you use inbound agent with our setup, it uses SH. While it uses bash, when the SSH launcher is running, it uses the init script. And if you use that form, the pipe and the end, that is bash only. So that's why we had to change to the usual form redirect yesterday and then pipe. That was a nasty one. Next one. Javak vanished from the high meme. So we had the issue on the template that has been fixed. So we had the agent configuration and their content. So thanks, Alex, for that. IPv6 again, that has been validated with the new cluster, as we mentioned. And during the changes, we did some misconfiguration. So we had people who are using RFC compliant DNS resolver in the organization. During one day, they weren't able to reach the IPv6 connection. So we had to remove the record. We fixed the IPv6 and had it back to record and the user confirmed that it was fixed for them. So thanks for the job here. That wasn't an easy one. We had to learn how to do it. We had to learn how to do it. So thanks for the job here. That wasn't an easy one. We had to learn that part. I can announce that public cluster has been fully migrated to the new network on the new cluster and we removed every leftovers except a network that is soon to be removed. Which means we don't have any more overlap issues and everything is running on a clean and clean network. So I think it's been a multiple weeks effort by airway sustained by the rest of the team. So great job. Now we have a proper cluster to work with. The first consequence of this one is that now we pay $500 each month less than before. Just due to the fix ups and the new cluster. Of course we had an LTS that has been released to all of our controller using the LTS line. I don't think there is something to add on this one. That's usual. We had a few close as not planned. Since we migrated all the cluster we don't need to back up that cluster. We had issue during the outage of Friday we had an issue about someone saying I want to install it doesn't download. That's all the information we had. I closed it with no information. That could have been an issue with the mirror. That made sense to move it to LDS. Close does not plan. We only have one agent and there is no need for us to have an agent. An agent that we don't control is risky for the trusted CI ports. Since the initial need was to provide Docker images for that CPU architecture and we are using KMU to provide these images in at least one year. There is no need for that. The native machine running on CI is perfectly fine and would allow native tests. If we have plugins or an artifact that needs to be installed, that can happen. In that case, it will be the way to go. Finally, I closed an old issue about importing and managing AWS resources because now we already managed the Kubernetes cluster and we are getting away from AWS. We have free virtual machine left and then we won't need it. That's why I closed the issue because no need to spend our time on this one. One of the machine which hosts the update center cannot be managed properly through the EC2 API because it's running on, let's say, AWS maintain manual hypervisor and it cannot implement half of the features of EC2. So trying to manage it with Terraform is risky and I don't want to take that risk because that could end on stopping the machine and making it unrecoverable and we don't want that. Better to migrate it properly and then we'll be okay. Any question until now? Things that we closed and I forgot? Oh, okay. Work in progress, we had a new issue about the Jira upgrades. I saw there has been a setup on Jira, a default setup that has been changed. I'm not really sure. I'm Jira admin so in theory I could do it but they have no idea what the feature is. I don't know if we can do it. So it's, and Daniel Beck is a Jira admin. So if there's anybody who knows how to do it, it's Daniel Beck and so it may just be as simple as us saying plus one to set the behavior, Daniel, can you do it? Okay. Because like you Damian, I am a Jira administrator but I'm scared as can be to make administrative level changes because I don't have the expertise that Daniel does. Okay. So then that case if it's okay for everyone, I will add a comment saying that to Daniel after the meeting, remove the triage but also remove it from any milestone because it's not something we should expect unless Daniel say I can't, I need you to do it and then you on high will have to take that issue and then we learn enough about Jira admin to do it safely by doing it together. Ask Daniel or Jean and remove from milestones. Not an infrasque but need to be tracked in L-Disk. Okay. Is that okay for all of you? Yes. AWS decrease AWS cost. So short-term, I didn't have time but I need to do it later today. I need to report on the June billing what is the status of our spendings. I guess we will, it stay almost the same since the past three weeks. I haven't seen anything, we have put alerts and we saw the alerts two months ago. So a peak of increase would have been mentioned to us. So I need to report and give a status here. Then the other task for that issue in order to decrease. So I propose that we should be able to close it and create a new one just to focus on the new item. The new step will be remove the free virtual machines that are currently running and consuming half of the credits monthly. One is update Jenkins CI with the packaging machine and then we have two other tiny machines and Susan usage. I think it's usage. Is that okay for you if I report and close this one on the upcoming issue and create a new one so we can narrow the scope and avoid being it to verbose? Yes. Okay. Got a close in favor of new one is title scope. Need to report for soon before. Okay. Almost closeable but not closed yet. Kubernetes 1.25. So we did the heavy lifting including a big general outage of the cluster that we had to recreate from scratch. So first good work survey because you work allowed us to recreate a brand new production cluster in less than half a day. So thanks a lot for the support and the work here. I still have a post mortem mark. I was thinking about writing the post mortem on the Jenkins IU block post because it was the impact was clearly outside our team. So I would prefer doing it afterwards. Is that okay for you? That will be great. I think that'd be great if you don't mind describing what we learned and I think that would be a great place to put it. Absolutely. So that's we need to finish the post mortem. That was an issue with an accumulation of configuration change directly related to IPv6 and the way it works with Kubernetes. But we also learn and propose some let's say improvements. So for instance, the public IP that were deleted is changing effectively all the external DNS resolution of everyone trying to download. That should not happen in the future. So we were able to find thanks to our researches locks. So we have the concept of we can lock resources so they cannot be deleted. What will happen next time if we delete the Kubernetes cluster and the public IP are part of one of the automatically managed resource groups. One of the resource group will fail at the ends because the public IP has locked that they do not delete. So we have added that as a security and it's managed as code. That's a minimum improvement. And as Tim said, so I don't know if you saw this one. Yeah, I saw that. So we don't need the lock protection for IP because we can't create them outside of the cluster and not pull the source code. We can avoid that transitive implicit deletion in the future. So I propose that we can keep it. We can add this directly on the commands of the load balancer even if it's the default value. So we can add a command pointing here saying you can add them on the resource group if you have to recreate it next time. Next. Yeah. Yes, exactly. What is the next Kubernetes upgrade? At least we know that we are able to most of it is stateless. At least we don't have any more pets cluster running for three years and we are confident in its recollection. Absolutely. And the backup LDAP system that Olivier built and that you checked and refreshed during the migration shows that we don't lose data. Because I have to admit that during at least 20 minutes I was more sure that we lost the world LDAP data. It wasn't the best moment of my life. Another improvement is that we have a technical administrative user used to administrate the cluster from our application system. That technical user is a service account and the only way to create it is a script inside my machine which is absolutely not sustainable. So I've got to add the require element on Terraform since now we have managed as code all the cluster that will create that user for us and generate the Kube config as a sensitive output and only copy and pass the output if we have admin access to Terraform. That should be quite the improvement. He could also add the script output to the notes displayed at the end of Terraform too. No other output. We can discuss that later. And finally I need to open the issue for the next Kubernetes upgrade that we have. I propose that we try to do before September ideally just to be sure that we are good enough. The issue will start with what are the depreciation line of 1.25 so that will help us scheduling a timeline that should have the same element that we have. So once these tasks are done we can close the issue but the rest of the issue for this one. Right on Jenkins.io. After lists. Subtasks done. Upgrade the Ubuntu 22.04 upgrade campaign. So one no two last candidates. Update Jenkins.io is still running next one. This is part of the AWS costs. That's a good program. We say that one will allow us to do the upgrade or avoid doing the upgrade that would be even better. A word about Poupet Jenkins.io. Still on Bionic. So we don't have to rush removing it. We have two years. We don't have the same operating system as the others. That one will need to switch to Poupet 7 not Enterprise. Because as for today the problem is the following. Enterprise version of Poupet doesn't support yet Jami. There is a huge ticket with a lot of people asking for that. We are not able to use it for free for the first 10 or 12 machine as an open source project. But it doesn't give us any feature that we have used during the past two years. We used to work with the web UI which is Enterprise but we haven't done it. By default that means we should migrate from Poupet 6 Enterprise to Poupet 7 and then we will have the Poupet server support for Jami. The agent is working on Jami. We mentioned a few meetings earlier about using Ansible instead that would have allowed us to change the paradigm and not needing that virtual machine anymore. However with the recent let's say heated discussion on the Red Hat area and the operating system around the Red Hat ecosystem but Ansible which could be suddenly less open source I'm now having Segon talked about moving away from Poupet. There are other solutions that could fit but yeah so that's why I propose that we focus on during the summer upgrading to Poupet 7 that will allow us to also keep that in mind. Is that okay for everyone? Yes, especially given the noise in communities around Red Hat sponsored software. I think that's very wise. I propose we keep that issue on the upcoming milestone because as we'll see a bit later in two bullet points, we will have to work on updates on CIG and Kinsayo fails to delete stashed artifact with access denied so that one was preventing the build discorder to work effectively on CIG and Kinsayo and that was a chain of problem then. This problem has been fixed. So Erwey do you want to explain just a bit what we did? What is left to be done? The default configuration which is not deleting anything from S3 storage from Jenkins as it's security risk as underlined by JC. That's also why these options are specified via GVM option which is cumbersome but it's not for this reason it's for discouraging people to use this option. I think we can close this issue since the projection problem is fixed and we have to open a new one to put in place a service to discard old artifact and stash on S3 as well. We can close this issue via AWS life cycle policies. Can I let you do this part? Erwey? Yes. Open a new issue about the artifact. Just a note right now during the past two months we went from $1 to $0.60 per day. It increased the cost but we are still below $1 per day. The cost is not a risk on short term. That's why we can close this. Thanks, Erwey. The next one would be split between Erwey and Hai. The goal is to migrate the virtual machine to AWS. The backend that uses to serve and distribute to remote through CDN network package files. That one is running on an old machine on AWS that is locked to Ubuntu 18 right now. That creates a lot of weird issues and maintenance challenges. There are multiple solutions. Right now, Erwey is studying if we can use Cloudflare for the update center. The challenge here is can we replace an Apache web server that we run from ages which is not highly available and subject to issues to something else where we have a CDN network that could be used to distribute. That's the challenge. We have multiple issues and elements to discuss. I propose that we don't go on details here but Erwey is working on that area. Two concerns that we need to mention. The first one is we still serve HTTP content without enforcing HTTP in this redirection. We force the redirection with the mirror downloads but not on the update center because it was written on an old GP that Erwey studied that we had old instances that weren't able to run TLS. As we discussed a bit that sounds like an old constraint that shouldn't exist anymore because these instances don't include plugins and plugins have HTTPS enforced. First of all, independently enforcing HTTP to HTTPS redirection for update center with the blog post that is required like we did last year with the mirrors. I think that should be a good start that could whatever solution we find could be useful. That one is still important.  Yes, absolutely. Last year for Ketchen Kinsaio and Erwey also that the current publication process generates HT access file for the update center that creates a bunch of redirection depending on specific update center chairs or something. So update center is highly compared to Apache. We cannot get away and replace it by an engineering server somewhere building our own distribution system or using the public services. Do you have any other questions? I have three buckets from any others. Is my understanding correct? Erwey, it seems so, but there are a lot of HT access redirection generated by this center. I need to see how it works. All the stuff are on the update center. And one of the compensation that we talked about because the goal for us is to find a way to decrease the outbound bound wave represented by the JSON update center file that are served to the end users. That part costs a lot. So it's not the amount of requests that can be solved. That's what we are paying for. Additionally, high availability is needed. One of the elements that could be studied and Mark might have the answer is that could we think about having an HTTP redirection when going to updates if there is a redirection, will it be honored by the Jenkins core instances? And that would require research across multiple Jenkins instances at least for a year's worth of Jenkins. That's a very much a Daniel Beck question to ask. He will have forgotten more about that than I will ever know. Okay. Update center index. Because if we have this, that means we can always have our own Apache system. We can use that to build our own cluster. Highly available because built and integrated someone one of our clusters. And the redirection when it ends on instead of serving the file that will redirect to the Cloudflare R2 for instance. So we will control the entry points. We would not have to point the domain name to the database. The thing is that what we call mirror is something we control because the reason of not putting update center on mirror bits as far as I can remember. But maybe that can be changed is that if we want to invalidate an update center cache, we can use a specific installation process which we cannot with sponsor based mirrors that are pulling the data from us. However, we could think about using mirror bits with a specific installation only for that and the only mirror will be ours will be Cloudflare. That could allow us to project on China or have a fallback or think about that kind of scenarios. We need knowledge sharing from Daniel. Did I capture everything we exchanged? Did I forget elements or things are unclear? No, seems good. No, seems good. Okay. And on my side, I've started working on PKG Origin Genkin Sayo, which is a second service run on that machine. It's trying to move that service to Azure on our public and private infrastructure. We'll move this to Azure. Because fastly is in front, so no traffic or bandwidth to pay for that would add HA. And also the core release process would not need to be run through an SSH command. That means instead if we have all the data during the packaging process that will run directly on the pod that is releasing and packaging everything that will have access to the real data generate the Debian and CentOS package inside the bucket and that bucket will be immediately available through the public cluster. We could control finally the environment on a Docker image that would not constrain the Apache version because we would have separated elements and the data. So that one will help a lot to getting away from that machine as well. So that's why we speed the job per service. Is that clear? Does it make sense? No? Okay. So that one will be our big next task for the upcoming weeks. Outside the artifact report. Any question or can I switch to the next one? Almost there, folks. No question. You can switch. So Matt, I propose we keep it on the next milestone. We need to work on the topic. Thanks, Kevin, but we will lead you to all the operation during the past two weeks. So I hope that we should be able to start working on this one again soon. Next milestone looks okay for me. So I propose we keep that one on the desk. I've looked at Kevin said that his repo was way more updated than the one in Jenkins and FRA, but I didn't know any difference. Yeah, that's a implementation detail in the sense that we have to spend time on that. But yeah, thanks for the head up. That is that says we can work on that and Kevin already did some work and we need to help him on that area. Proposal for application to migrate to ERAM 64 got a delay until Stephen is back. We had a discussion and now everything is clear. It took notes. So we should be able to resume and it will be back in early days when I will be back as well. So the goal is to have ERAM 64 for all the static services on public gates now that everything has been done, upgraded, migrated. That will be Stephen main priority because it will help to decrease cost on different area. Artifactoid bandwidth reduction option Mark, I think both of us are a bit late on that topic. Right. So that's it will get some focus today and tomorrow for me. I've got I've got to propose well propose changes to the root palm for both Jenkins core and plugins. And then we've got to start evaluating what does that mean, etc. and dealing with the bumps and bruises of it. Thanks. So I'm keeping it. And finally, artifact caching proxy and I was late, but the goal is to open a pull request on ATH based on former basil walk. The goal is to start using ATH on every part, ACP on every part of the acceptance test on this build, not only the initial generation. So got to start a draft pull request and see if it break the ACP on Azure or if it's working now with the new network. I think that's all for the current element. We have new issues. So improve data dog in gestion. Thanks. I think that's to keep track of what we could do with data dog in the future. That one will we treated it. I've opened backup infrastructure data. I was sure we had an issue that you wrote an issue but I wasn't able to find it. So maybe that's a duplicate. But I try to put as much information as possible here to point the different elements we could have that was triggered by the CIG and can say you former resource group deletion. Right now we have snapshot of the two former disks on the new resource group and the goal will be to see the to study the Azure backup that create a vault of the data that can be migrated to another cloud if needed. So that one will be our encrypted vaults for storing data and recovering case of a big problem. There was an issue on the developer extension back in crawler. Mark, I believe you took care of at least answering to this one. Well, I wish I could say I've taken care of it. I've got to do the research to find out what broke. I am reasonably confident I'm the one who broke it and therefore it's perfectly justified that I should be the one who fixes it. But I suspect I merged the dependable change and the dependable change passed all the tests which hints that there are more tests needed. So there will be some research and the outcome of that will eventually be tests that check that particular attribute and then only allow pull requests if that test passes. Okay. Should we follow your recommendation and move the tissue directly to the back end extension? Yes. I think it doesn't belong in our help desk. I don't think I have permission to make that decision. But if someone else does, I would love to have it in back end extension indexer because there's another issue somewhat like that from Daniel Beck already that's been moved to back end extension indexer. Okay. I will take care of this one. I will finish the notes with what we said with the new issues. I will give details on what we said. Do we have new issues though? I'm missing some metadata two weeks ago. Missed this one. Oh, yeah. Okay. So we have users from China that have low performances when trying to reach either a data center and or the download mirrors. Even though we have mirrors in China, we have way more than we knew. That could be interesting. So as we say to that person, they cannot use archives or PKG. There is a lot of elements. So one of the proposal we had, the error to Cloudflare has ability to project copies inside China. So that could be a way to help our China users. As we told to that person, we need a sponsor inside China because there are a lot of unknown knowledge. There are a lot of things that we don't know about how it is to live there. So we have to use some friends there and now not anymore. So I've tried to ask the person gave us good details. So, yeah, that I propose that we delay that to after the work that they're doing, once we'll have migrated update center. Does it make sense for you? Yes. And finally, we already treated this one. So I don't see new issues here. Do you have new other topics to, do you want to mention? So I raised an issue that may be interesting to infrastructure. I'd like an opinion. I'm sorry that I didn't solicit your opinion already, but pkg.jankins.io and mirrors.jankins.io both have installation instructions in their Debian and in their Red Hat subdirectories. But the installation instructions are, so if you pick Debian or Red Hat, either Debian stable or Debian, you see a nice page that gives you some installation instructions and they're generally helpful. However, they are not the full installation instructions because the authoritative installation instructions are in the Jenkins user handbook. And the problem with these installation instructions is they are nice and simple, but they only tell you about Java 11 and we want you to use Java 17, but Java 17 isn't available on some Debian machines. And on and on, there's an awful lot. So the temptation I've had is to offer the pkg.jankins.io should redirect for that page to this page and stop trying to present those simplified instructions because simplified instructions are inevitably the wrong instructions for some set of users. So I'm open to your opinions there and we could do it separately. It doesn't have to be today. It's just I've realized this page worked really well when there was only one Debian released to support. We now have 10, 11 and 12 with very different Java versions on them. And there was only one Red Hat version, the Red Hat page worked, but we now have eight and nine and we have other variants like Rocky and Alma and Oracle.  Honestly, I think that's a brilliant and really useful ideas because in the worst case, it's adding redirections on Apache and XHTML can also serve a body that redirects. If you have a web browser. So yeah, combination of both. Yeah, that makes sense for me. I mean, the other benefit there is it will stop the enumeration of directory contents that happens on some of those pages. And I just don't think there's enough value to people listing directory contents. I don't remember. It's mirrors or PKG that actually will list the directory contents. But I just, I'm not persuaded that that's valuable. So just, it's a conversation topic. I'll bring the conversation topic separately on an issue. We don't have to resolve it here. Makes sense. I think that's worth opening an issue to start the discussion here. Right. Don't forget about it because I mean, that makes sense that will help us, especially we had a confusing moments or very high about finding which index HTML is generated from where. If you remember the GPG rotation, the Jenkins design, I forgot the name, things, header and footer. So yeah, that will help definitively. Yeah, it, it, I don't think there's compelling value to having those exact web pages on the PKG site. If instead we could redirect to documentation that really describes the situation for the user. Thanks for raising that topic, Mark. Do you have other major points here? None for me. Okay. So tomorrow. Okay. I'm crossing the issue and stay here. Just need a quick sync with the two of you and see you in two weeks for the other watching this recording. Bye-bye.


on today but first Saturday morning live cast. We round up all the news of the week and obviously the holidays were recent so we have some special stuff going on. So I'm gonna just hand it over to Greg. Hey Greg. Hey elf Greg. What's that? Hello elf Greg. Hello how are you? Fine and you. That's good. And how's elf Betsy doing? Excellent, excellent. Happy New Year everyone. Happy New Year yes. And I have my special elves and crime as I just called them in a discord chat last week or yesterday. Kathy and Christine have joined us. Good morning. Because we're going to start off with the the big reveals right from the Secret Santa? That sounds good. Does that sound like a plan? Okay that sounds very good. Sounds very good. Okay well let me just get my self-organized. I want to say I was the first one here this morning just just while you're getting it. Yeah that's right. We don't have to say who got here but Brian's here. Lisa's here. Let's see and they were talking a lot. Hillary. Hey Hillary. Maria Hedberg is here. Chris Berriello is here. Christine Miller. Ray Womsie. Kevin Guy Campbell. Kevin I'm going to be talking about you in just a few minutes. Well not about you per se, but kind of you. Mary Slippie's here. Let's see who. Judy Spetz is here. Diane Spencer. Carr is here. Let's see. You know who hasn't been here in a while is June Butka. June where are you? Is she there? No she's much better. She's doing great. She's doing much better. I could say that. Janine is here. Let's see. Fran Pickett. Sorry. There's so many people here. Caroline Vernon. Did you guys say that you were doing the Secret Santa today? Yeah we did. Jinx is here. Wow. Take it away Greg. Take it away. Okay so my good elf friend Christine put together a Google slideshow so that I would stay on track which you know if you've watched any of these livecasts you know is an issue with me so let me share my screen. Hey Geary. There we go. Okay so I got to say that we did the G2G post and we've had amazing results. We had over 150 wishes came in and people did just wonderful but before we even began we had the first wish came in. Whoopsie. I gotta put it to the right. There we go. The first wish came in and but it didn't come in on the G2G post. It came in by voicemail. Wow. Yes to the elf central hotline. Elf central hotline. That's 1-800-555-1-2-1-2. Something like that. And so let me just read the transcription of the voicemail message. Dear Ricky Tree. I'm a big fan. I love how you keep track of so many of my dear friends that I get to see once a year. I'm wondering if I should set up a nice category and a naughty category but maybe that is a bit much. I have one wish for you this Christmas. Could you get Sarah to return to the Saturday live cast? Love, Santa. Yes, what? Wish granted. Where she is. Where we're here. Well, it's just just Meg's really big. Now it's Meg. Yay, Sarah. Oh, Santa will be so happy, Sarah. I made Santa's wish come true. You did. Oh, that's great. Look at that. People are screaming. Yay. Well, I was literally laughing to myself so hard, Greg's voice of being Santa. Was that Santa or an elf? I don't know. Anyways, there we go. So let's, should we continue on? We're very happy to have you back, Sarah. This is great. So I thought we'd start off with just sort of a montage of all the GGG messages because part of the fun was just watching the GGG messages come in and how people phrase things and requested things and the words that they used. So I put a little montage together. So when you're watching this, think of, you know, those lovely montages you see in films where there's people narrating over top and we're going to do our best. Live cast hosts are going to do our best to do that. So it's going to start, Meg's going to read the first one that appears on this screen and then Betsy's going to jump in and read the next one as it just sort of appeared. It could be a total mess, but it could be fun. We have to do it in a voice like you did it. Oh, you can do whatever voice. You don't have to do a Santa voice. These voices from one reading to the next.  I'm going to do the profiles of Santa, by the way. Okay. Santa's genealogy, I think that's technically forbidden. Yeah, that's right. I was going to leave that as part of the lead. Okay, Megs, you're ready?  Dear Santa, bonjour, Pierre Nioro, and women's stars. Dear Secret Santa Elf. Santa, it's Debbie. Dear Woman Symbol. Dear Weakie Tree Elf. I would like. I'm looking for. If you could find. I need help proving. Can someone help me? I've been good this year. I hope this counts as I wish. Help me, I've fallen and I can't get up. The gravel falls are terrible. Thank you so much. Merci. Milk and cookies. I made some blueberry pie and sherry. Mirrors for Rudolph. A wee dram. I spiced rum. Yeah, there was lots of offers of that. It was very yuletide. Yeah, there we go. Well, so that was sort of, you can sort of see people were all over the map. Some were super serious and some were tempting, trying to get people to answer their wishes and whatnot. So that was great. At the last count, I believe we had 33 wishes that were solved. And of the 150, most of the majority of them were brick walls, and they were hard brick walls, like really difficult because you think about it. These were put together by Weakie Treeers. So, you know, genealogists who have done their best and they've hit a brick wall. And so some of these were really, really difficult. But along with the 33 that were solved, there was an additional 82, I believe, correct me if I'm wrong there, Christine, with the most accurate number of additional wishes where research notes were added. And so that's really important because that gives the profile writers and the people who make them the wishes more clues to go on. So if there's a way to get through those additional notes will be helpful. And sadly, there were some wishes where we just couldn't make any headway. And we did our best and we apologize for that. But let's celebrate the ones that did get solved. So we're just going through them in chronological order of the ones that got solved. So here's the first wish. And it was from Lisa, who's in the chat with us. And she wants, she wanted to help sorting out parents of her second great-grandfather. She's got DNA results and she doesn't know how to analyze the data and she would like somehow. Well, the ELF team has come through and we have a solution for you. We have arranged a free lunch time or virtual consultation with the world-renowned DNA expert, the amazing Mags the Marvelous Gaulden for a free consultation. Mags the Marvelous? That's a little illiterate. Mags the Magnificent. Oh, Mag the Magnificent. Well, she's Magnificent as well as Marvelous. So, Lisa, you and I need to talk and we can set up a virtual talk. We can talk on the phone. We can meet for coffee and I'll buy you a coffee. We can do anything you like. We can do lunch. So after the talk, we'll get together and figure out how to do this and we can talk about your DNA project. So there you go. Excellent. Super. Next, we have, so some of these, we're gonna, some of these I'm going to go by quickly and others we're gonna spend a little more time on just to highlight because we don't want to take up the whole time. But there's one where the request was for a, to find someone in the census and there it was with the details that were given. This one was solved. This was a wish by Maria was asking for help with, again, it was DNA help and she actually granted me access to her DNA matches. So we, I didn't, we haven't got the solution exactly to the specific problem of Peterson and Odleburg. But what I was able to do is look, starting, this is what her family tree looked like when we started off and she has a few DNA confirmations, but I was able to find a bunch more. And so we have DNA confirmations for a good chunk of her ancestors. And we're also, there's also some leads for some of the ones that are further out. So thank you very much Maria for trusting me with that and I hope you enjoy this. And I have some leads for some of the other ones. Many of these ones were done with third cousins or second cousins once removed. And so those you can do with a simple DNA confirmation. The ones that are further out, we need to use triangulation. And this actually was, is a misconception that some of the wishers had and elves that just when you look at a profile and you see down the side, you see this person has a percentage that could be a DNA match. Those are only percentages and probabilities. Those aren't guaranteed matches. So just because someone could be related by DNA listed on the side, that just means that they took a DNA test and according to WikiTree, they are in the pattern where they could have inherited DNA. But when you get as far back as third, fourth grandfathers, grandparents, because DNA is random, at that point, there's no guarantee. So what you need to do to do a full, a true DNA confirmation at that point is to compare and triangulate with other descendants from the same person and match chromosome segments. But that's really technical, but I just wanted to mention it because it was a misconception that came up during the challenge. And I thought I would just see it now and we can revisit another time. But anyways, moving on. Next year, it's going to be all DNA confirmation. Oh, no. I can tell you, Kathy, do you want to talk about this one? Okay. Yeah, this one is looking for a birth record for San Pedro Meda. And I have some experience with this because this is one where the person, a WikiTree, or needs to actually be the Family History Center or the actual library in order to be able to access the collection and go image by image. I personally was hoping to try and get this done in the past couple of days, but I just wasn't able to get it done. So, Greg, do you want to kind of show why it is solved? Well, it is solved because there is a WikiTreeer who has agreed, an Italian in law, a WikiTree volunteer has agreed to spend at least one hour in his local library that he just happened to get to become a Family History affiliate. So, help is on the way, Chris. He's like, wait, what? Yeah. So, I will be spending time looking through all the 1810s to find the record. Here's one where we were missing a marriage and a death record has been found. So, that's kind of cool. Love how the death records have so much cool information like myocarditis and all that. Yeah, there was a story on that one, a family story that Joseph had died working for Westinghouse, I think it was. So, somebody found this one. It's the closest thing that they could find, so we sort of presumed that it's him. They lost him after 1923. Right. I had an uncle that I lost, and WikiTree helped me find him. We had a couple of lost and missing family wishes. That's cool. That is cool. Yeah. Yeah. That is cool. So, here's one where, again, this is one of the ones looking for DNA confirmation, and the ELF did find a whole bunch of information in the biography. So, that would be helpful for putting that case forward. Nice. Here's an example of one where new members were added. So, to highlight that, I show you the ones that were added, and then there was even more, that six other children, which, of course, don't show up on that initial page. There are some who went nuts in adding additional family members, and we'll come to one of those really shortly. Went nuts. Take it easy on the cookies, Santa. You have to get nuts on the bottom of their stocking. Nuts and oranges. Yeah, walnuts. Yeah. In the shell, and why didn't they also give us a nutcracker in the, yeah. That's right, yeah. I love taking snippets from the original documents to highlight some of the ones here. So, fellow ELFs, feel free to jump in. Yeah, I liked this wish 60. ELF Linda found Margaret mentioned on the probate record of her maternal grandfather, John Finney, and she noted that in that record, it said that all of Elizabeth's full siblings were mentioned. So, John Finney and his deceased wife, Elizabeth Betsy Cannon, are definitely Margaret's grandparents. That was good. I'm gonna get my noise makers. Okay. Here's where the ELF Pilla found a baptism record. Ramon. That one. Pilla was her own elf. Oh, great. She solved it. She solved it. She posted her wish and then solved it on her own. Oh, man. That's right. These other ELFs are not working fast enough. You have to do something. You do it yourself. You can make sure you solve it before we start it. That's funny. Good work, Pilla. Okay. And this is one where, oh, Elf Hillary did this one. She found the birth registration on, is this Find My Past? Or, well, in the GRO, the General Records Office, and ordered it and, what did she order? No, she ordered a will and has sent that up to, so that's above and beyond Call of Duty. Way to go, Hillary. Oh, this one, I'm not sure. Okay. So, we left that note on here. I'm supposed to take that off because I looked at this this morning and the question was, this person couldn't access browsers and didn't have access to sites. So, two ELFs, Elf Goodula and Elf Mindy helped out by expanding and adding sources to many of this Steve's ancestors. So, that was very well appreciated, I'm sure. Okay. Do one of you two want to talk about this one? Or, shall I? Oh, this was the Australian one. Yes. Oh my goodness. There were so many hours spent on this, so much conversation, so much back and forth, so many records. So much collaboration, I believe. So much collaboration. Yeah. Yes. It was really well done. So, kudos to those ELFs. Elf Celia and Elf Judy. Yeah. So, they did prove that Amy Shakespeare was in fact born Amy Alice and then they corrected her LNAB. And they added extensive research notes. Yes. Extensive with a capital X. They went on and on, added additional questions, additional resources. I mean, at one point I thought the Discord chat was being renamed to the Celia and Judy chat. They were just collaborating like it was incredible. So, yeah. Like it was New Year's Day. Yes, that's right. Yeah. And they were talking about Shakespeare and I, but it was not this Shakespeare, not that Shakespeare. No, it was Shakespeare. No, that's not true. Oh man. It seemed like, yeah, and it seemed like every time I went to go check Discord, that's all I was seeing in there was Shakespeare. It's like. The literature course here, what? Yeah. Yeah. So, that was very impressive. Okay. Stubbornness brick walls. Well, Elf Kat Ryan found the parents. This one here. Elf Junya Nehouse found two wives and mother, added some more people. You can see I've circled the ones that were added. Yeah. I think there was some conflation on that one. So, the wives had to be found. And then, I think the profile manager had three children, but then they found the Elf had more children after that. So, added profiles for everybody. Very well done. Yeah. Here's another one where the Elf Jinx, who I think is in the chat. Oh, there she is. She solved this using Scotland's people. And there's the details for the death certificate. Can I just say to Jinx, Jinx, you're allowed to go to bed now. I was on Discord. There was Jinx working on another profile. I just honestly, I'm so grateful. Thank you so much. Okay. Who wants to talk about this one? Because this one needs huge... I think Betsy should talk about this one. Well, I think, well, first of all, let us just preamble this with Betsy is a rock star and is amazing. Thank you. It's a very sad little wish come in for one of our careers who was, got the idea to maybe work on her uncle's family tree, her uncle's in hospice, and they don't know how long that he's going to be around for, which was very sad. But she wants to see if she can find any sort of living family. Now, we know we don't work on living family, so I put it out there to see what we could do. And Elf Betsy just took the ball and ran away with it. So, thank you so much, Elf Betsy, and we're getting in contact with this wishy and she will be pleasantly surprised before. Wishy? Yes. It was a really, really interesting set of families. Yeah. So, Betsy created not one, not two, but 28 different profiles, I believe. Right? That's right.  I had to, I ran out. I had to go down the trunk and into the ground to get the 28. That's how much work Betsy did. And then she created a free space page, but of course it's private because it talks about living profiles. So, that's all I can show you of this free space page is the title. That's some virtual hugs. Yes, virtual hugs from Elf Betsy. Merry Christmas. Yeah. Kathy, you want to talk about this one? Yeah, this one, I know I've kind of seen that it has been a brick wall for a very long time and thanks to our wonderful Elves, I don't remember which one worked on this, especially when it involves family folklore, especially in a different country. And it can be hard to find records and stuff. And so this one was definitely has been a hard one for Sandy and her husband. And thanks to our wonderful Elves, it was... Elf Margaret Johnson is what you thought was in my notes. Yeah, it was solved. And I know that there was... I was sent a message thanking the Elves that they wanted to make sure that the Elves that worked on it are very, very thankful for solving this wish. And there are the addition. Nice work. Yeah. So at least five from the nuclear family there, and then more in the extended. Yeah. Nice. Very impressive. Yeah. Neat. Now, this is a neat one. This is a new member to WikiTree and wanted help with the Russian roots. So Elf Judith created a profile for his mother and several siblings. So that's a nice start for a new WikiTree member getting a leg up on the Russian records, which are always hard to find and edit sources and bios. Wonderful. Thank you Elf Judith. Okay. Elf Maria Lentholm worked very hard on this wish. I love the first line. Oh, what's that? I love the first line. Oh, I haven't written to you on donkey. Oh, I've been very good this year. Yeah. I was really impressed with this one because looking for somebody with a similarly named first name and surname. Yes. It was, I was really impressed with the work on this one. And it's her person. Her person. Yes. Her person. Wow. And a kind of person per person. And apparently there was a lot of per's and persons and per persons. So I think my eyes would have been crossed after about five minutes. Like Smith and the Americas or England. Yeah. I was looking for John Johnson. Oh, yeah. Really? Well, I can tell you from that just brief dive into Maria's DNA matches and then looking at her family tree. Oh, I have so much respect for people who live in countries where you're following the patronymics and it goes from a large daughter to Sven Svenson and to like it just, it just dives and deeps. And how do you keep track of anyone? And oh my goodness. Incredible. Great work. And then, and then again, additional research notes too. Okay. So this is one of mine. So this was a cool one. This was a cool one because so what they know is that Joseph Nelson Lafave was born in Canada, probably Santa Antoine Quebec, though the notes actually spelled it Saint Antoine Antoine, but they figured that probably was close to Santa Antoine, which they were right. And all they knew was the mother's maiden name was Muir, they thought. But they couldn't find any record of him. And not only was his origin sort of cloudy where he where he when he had eventually died, they haven't actually nailed down the desert if you either. So it was a quite a big mystery. But luckily with my with my new new found experience with Quebecois records in French, I figured that Lafave is probably an Americanization of the French last name Lafay, which is spelled L E F B V R E.  Or in this case, and if you leave out the B, which sometimes people do, then it would sound close to Lafave. So I did a bunch of research on the phase. And luckily there was only one combination of a Lafay marrying a Muir that was in the right timeframe. They had a Joseph who was born just a couple years before the their estimated birth. So I nailed down the parents. And from having no parents, no family at all, I now have been able to go extend the back to basically the founding of Quebec and to the original Lafay that came from France. That's amazing, great. That is amazing. Well, now I can't take all the credit. I can take the credit for the parents and grandparents that I had with the parents I added. And the grandparents here. And I think from the great, greats on were already there. So I just had to play connect the dot. And you do that pretty well. I understand. I can connect that really well. And then there's a couple places here where again, there's some more connecting of the dots to do. But I had to at one point, I had to say, okay, you know, I'll just make notes. And I'll let the profile, the profile person play the other connects. But I gave specific details of who to connect and how to connect.  And her father William was a Miller, and worked on one of the senaries in Quebec, just outside of Montreal, I believe. So he was probably Scottish, I think, and came over to work and was hired to come over to work with the senaries. But I have his marriage contract. And he actually it was interesting. He the marriage contract was done by a French lawyer and was all in French. And then later that day, there's an English marriage record from a Presbyterian church in Montreal, where he actually got married. So I guess they covered the best of both worlds, just to make sure they were well and truly married in both official languages. So let's see. Nope, I didn't mean to do that. I hit there. My cursor is on the wrong thing. And just because I love when I do that, I know, I know. I had a little map of the first yellow, if you zoomed in, or if you could look on the profile of the parents where I've added these these extra notes is where Joseph Nelson Lefebvre was born. He Nelson was not his middle name. He didn't have a middle name when he's getting it was just Joseph Lefebvre. And the family progressively move farther and farther south. And you can see the last place they lived in Canada was where his 21 year old older brother passed away in Santa Antoine de la Bay. And then it's a short hop, skip, and a jump to cross the border into New York state where he eventually got married and spent the rest of his life. So that was a very cool one. So thank you for giving me that challenge. Okay, I liked this one. Okay. I was truly hard on this one. I don't know how he did it. But he had to follow this guy who was in the military, as he just bounced around the world, being posted different places, because he was from England. So he was abroad. And then they would have children everywhere that they went. Look at all those children. And then they had children in England, and I learned, and then they had children in, they had a son in Toronto in 1863. And I just like, that was one of the more impressive ones. I thought that was, wow, it was really cool. Sorry, Louise Nicholson has a question about how you created the map on the map on the previous ones. You might want to check with her later. Okay, sure. Sorry, go ahead. No. And so yeah, this wish was definitely solved. And there was a ton of work. And again, my thanks go out to everybody on the English team who did just an amazing job. Hillary and Francesca and Roy and everybody. So much hard work. And thank you. Our thanks go out to these great elves who did all this wonderful work. I love that the live cast is responsible for getting this kicked off a couple of years ago. And I love that Kathy and Christine kind of took it over and Greg and you guys have run with it. Thank you so much. Yes. You're welcome. So this one, so this one, Elf Kathy Evans may not have found, may not have solved the wish and found out who the parents were, but she did flesh out some of the children and added a very fulsome biography to the wish. So that's fulsome. Yes. So that was well done. Marta didn't deem find the birth record, but interestingly, it wasn't listed under Augustus. It was listed just under justice, I believe. And that's a little fuzzy. I can't read that now. So I don't know if it was, I don't know how it happened, but I mean, we come across that all the time where you get baptized as one thing and then your name gets changed a little bit later. That's right. He was known all along as Augustus, but he was baptized as justice. So Elf Celia Marsh found some records and added some research notes, toddied up the profile. I like the start of this one. This is really a long shot. Yeah.  So yeah. Yeah. So carrot for Rudolph in the kitchen. I know that is cool. So this one did find a record of Thomas being mentioned in the will as an Aaron's father's will. And there's, so there's a marriage record and then there's the will is the, in the big gray on the one at the top. And she found a sibling as well. And then it looks like the mother passed away while the children were really little. So I don't know that we'll ever find her name. That's sad. I'm amazed at how neat this handwriting is in these two documents. Right? Yeah. Like, that's nothing like a lot of the priest writing I'm used to seeing. 44. Yeah, script. Yeah. A lot of the script back then was just gorgeous. Yeah. Yeah. So Elf Mindy was able to help find a baptism for this person. And his parents were named on the record. Elf Mindy did a lot of work on this one. Oh, huge kudos. Yeah. I can't believe where she found time. I was just thinking that she's, you know, she has to organize the current wiki tree challenge, which is going on right now, which is Ontario ancestors. I know we've all abandoned the Elves. She stole some of her Elves. Those last couple of days, we didn't have as many Elves working as we, but anyways, and I, but she's done so much. She's gone through so many of these wishes, adding research notes and stuff. So Mindy, huge thanks to you. Yeah, Mindy, here, wait. You get a double chicken. Okay. So this is wish number 136 and it's blank. Uh-oh. It's not really blank though because it's a wish. It's my wish. It's my wish. And what do we find? We found a person and we found details. Yay. Exciting. Yes. And it names Father and Mother. There you go. Very nice. Very cool. I couldn't find the actual original record for this one. It was just, this is one of those ones that was, had the index to transcript. I didn't do this wish. I was just, when I was creating the image for the thing. So yeah, and I have kept my promise. I haven't looked at anybody in my family tree for two weeks. Oh, good. So after this, I'm definitely literally, you haven't, you haven't, do you live with your family and you still haven't looked with them? Look at them. I know you looked at your dog. That's a whole different couple of fish. That's great, yeah. Oh, this is a neat one. So this one we're looking for a death record and Elf Marta did find the death record in an index, but what was also really helpful is she, in the research note, she gave specific instructions on how to get a copy of that. Now, unfortunately, there's a fee involved, but she got details there. So that's useful, helpful. Because I think there's a lot like this on Ancestry where there's an index, but to get to the, the more, the meat you have to actually cough up the fee and I guess that's common in with the GRO in England. I tried looking in some of the New York papers, I couldn't find any reference to him at all. So good job on that one. Yeah. And I like when research notes give that additional information about, you know, how to go that next step sort of thing. So that's pretty helpful. Okay. Elf Francesca took this wish and ran with it. I mean, really ran because she took from one person and this is someone who is new to English sources. So she needed help with Rebecca. And went back to not only her parents, but her paternal grandparents, and then six, six children as well. So that really built out that family tree. So that's very nice. Thanks, Elf Francesca. And there was also an Aunt Mary, which I couldn't get on this display and four other siblings. So there's other siblings there too. And I think Francesca is new to the English project as well. And she was working with Charlie and Roy, I think. And yeah, again, anybody who works at English stuff just amazes me because I've looked, I've given up. Oh, look who's wish this is. This is mine. Oh, no, it's mine. Yes. So Elf Kelly found a link to several pictures and some details on where to find them. And I've got a note here. Due to copyright, I can't show them on. But you've got a link to where to get them from. Look surprised. Oh, I make static about this because being adopted, I can't use DNA at all to go through your adoptive of those lines. And my grandfather died when I was like a year and a half old. So I never knew him and never had any information. And it just kind of that my Erbach line was just never talked about. So everything that I have is stuff that I've been finding. Nice. Very cool. Very cool. So I'm very grateful for this. Yeah. Thank you for that. Elf Susan set up a free space page to work out the parentage of Anne Monty. Um, so this was obviously one where it took a lot of research. So not just a little section of research notes on a profile, but a whole page and listed a whole pile of possibilities there. So a lot of work there. Thank you. This was one where as the mom was divorced from her, from the father of Anne, and then remarried. So in the first census record that she shows up in, she has her stepfather's last name. So that really confuses the issue, doesn't it? Yeah. Okay. And there, look, is there more possible, more census information, more information? Like it just goes on. She did an amazing job. So we just have one last wish to show you. There's another one after this, but go ahead. There's another one after this? Yeah. Okay. Okay. So this one is from James. Dear Santa, on one hand, I've been very good. So can I have the results of my possibly paternal sister's DNA results? Uh, I can't really do that for you, James. Sorry. But on the other hand, for the bad hand, the weather here in North Wales is subarctic and we are expecting power outages. So for the bad hand, can I get a stocking full of coal for the fireplace? Yeah. I leave it to your discretion, but there'll be a wee dram, a 20-year-old single malt Scotch whisk in the table, James. I think James was talking, because Pip was talking about a wee dram earlier. Yes. Yes. I have a glen libret 12 here. Well, we can't do anything about the DNA results, but we can give you a lump of coal. So we have a wish voucher that's sending your way. We will mail a free lump of coal delivered to your doorstep. All you need to do is contact me with your mailing address. And $500 for shipping and handling. It may be a lump of coal in the form of a bag of briquettes, but it'll be a lump of coal. One way or the other. There you go. Look at Hillary's comment. What's Hillary's comment? Not so cold here now. Not so cold here now warm for the time of year. So I had a wish. You had a wish. And my wish was that WikiTree would get a brand new humongous DNA group project added. And guess what? We did. You did. Yeah. So the Campbell DNA group project came over this week. And Kevin, who is one of the people working on the Campbell DNA group project, who wrote FTDNA, actually worked on this page and got it all set up with the everything, all the information, showing the goals, the types of DNA tests who can test gives lots of great information. But it also talks about some of the time scales and all the results and gives links off to the charts of information for the project, of which if I scroll down here to group number 30, and I go down here to Enos Campbell. Let me see how far down I can go here. Enos Leander Campbell is one of my ancestors. So the Campbell DNA group project has been added to WikiTree. And I am so excited. It is a humongous project with lots of people. And so that was my wish. And I got it. So thanks. Excellent. That's great. Fantastic. Wow. So I just wanted to thank all of the elves who did an amazing job. And in the slides, we just went through the ones that were solved. But again, there's three times that many where research was done. And they may not have broken through the brick walls, but they chipped away at it or whatever. And they spent hours and hours and hours working on it. It's just so impressive. And thank you for all. And I'd also like to thank everybody who ordered certificates, death certificates, ordered wills, went out of the way to get records for the wishes. Thank you, guys. Thank you to Hillary. Thank you, Betsy. Thank you, everybody. Yeah. Excellent. Thank you. Thank you. And thank you all for leading us. Oh, well, it was fun. I couldn't have done it without these two helping me out. I could have done it without Mr. Concatenate over there. Yes. She learned new spreadsheet terminology. Concatenation. Yes. It was fun. That's so exciting. So next year, we'll do it again with you guys. Well, we've got the spreadsheets. We've got the Google slides. We've got the free space pages. If someone else wants to do it, that's fine. But, you know, we've got the structure. No, we'll leave it in your hands, Elf Greg. Santa, Santa Greg. Getting lots of nice comments in the thank yous. Let's see. GiftedMe. Janine says that somebody gifted her court records for the Calvin Logston trial. A project I've been working on that is really cool. That's nice. Yeah. Well done, everybody. So what you want to do for the next few minutes? We might have to cut some segments for the rest of this. Sorry. What do we want? What do we want to do next? Well, look, the already dreaming of WIC. We really sidetracked this, haven't we? Sorry. Kogan looking for ancestors says Secret Santa Challenge was a lot of fun. Great work, Elf. Yeah. I at least want to make a comment because right before the live cast, we were talking about the photo challenge, that the 52 photo challenge has been kind of pushed to the side, but we thought nothing else had been started yet. But as, you know, people were talking about the Elf thing, they actually create a new project called the 12 month photo project. And there actually is a free space page. And this month's challenge is grandparents. Let's do it. Let's do it. We can, we can do it at the end of the month, the photos, or we can look at them every week or something, see what's been updated. But there is a new challenge monthly. So just let me know. Let's look at it. It's 48 tills. I mean, it's 48 paths. So there is, is there a tag that people should follow so that they can, So I, I might, we might want to tell Deere to also tag photos because when I was looking just at photos tag, it wasn't there. It's under 12 photos though and challenges that tag. So it's called 12 photos. That's how I found it. You want to throw it up there? Yeah, I can't throw it up there. So let me share my screen real quick. Hold on. Oh, this is, this is new. Okay, so streaming or change how, hold on, streaming or change how they were doing. Okay. So this is Deeders post at the end of the year about stopping the 52 photos challenge and asking people for suggestions on, you know, I think I want to do a 12 month photo and people were giving him suggestions and all of that. So, and then I found this, the first month.  Oh, we can zoom in a little bit. There you go. Yeah, good. Okay. And then here is the free space page. And we have five photos so far and the theme is grandparents. So I won't go through all of them so we can talk about other stuff, but we can at least look at these first. Are you checking to see if there are any animals? If there are some animals, but no, it does not look like it. Not so far yet. Somebody put, you have, you have three weeks to upload. So, yep, that's that. And we can, it's kind of exciting because it gets people more time to flesh out that, I think that flesh out that free space page, add more photos in that theme. So that is a new photo theme for this year. All right. I was wishing that, and it means so much have, have a firmly connected family to the ancestor. That's cool. And Lisa, yes, go ahead and add that photo. The other thing that we had going on was we do have profiles of the week, which were the cheers people. Yes, I can share my screen again show that we all think we have time to go through all of them, but we can at least look at who they were, who they are. Oh man. So we have some of the main cast characters, and then some people who made one appearance, and then the, the one who did the composing of the, the songs, and stuff, first cheers. So I didn't realize Ted Danson was on cheers. Like, I mean, like I didn't like like, I know Ted Danson from stuff more of now that he does. And I was like, oh, he was in cheers. Like I didn't make that connection in my head at first. So, and then we also, cheers was chosen because Christy Alley was passed away last month. So that's why I think she was 71, I think, from what I remember. So that's why the cheers theme was chosen this week, unfortunately. Yes, yes, they were. And Frazier. And then Dr. Simon Finch. And, um, yeah. So cheers. Cheers. Cheers. Woody Harrelson. Some of these people I don't know, like Craig Sefa on the score composer. Yeah, he's, he composed some other stuff. I actually looked that up too. He composed a whole bunch of, I mean, it's a really, it's a really catchy tune that he, he did. Like it was so recognizable. Yeah. He, he did the score for the Last Star Fighter Nightmare on Elm Street 4. Wow. Legend of Billy Mane. He did the score for that. Time stalkers. I'm trying to see if I, Corvette Summer, Mission of the Shark, I don't know, Twilds the Knight. So I guess some smaller things. Yeah. But he did, he did quite a few, but I guess cheers was his best known one, I can imagine. I bet you that would got most bucks from that one problem. So if you are connected to the cheers people, I kind of, I pulled up everybody's connections. My closest would be Kirstie Alley or Kristie, yeah, Kirstie Alley and Woody Harrelson, of course. Sarah is closest to Kirstie Alley and Woody Harrelson because she and I are related somewhere close. Greg Clark's closest of those is, let's see, Kirstie Alley, wait, no, Tiff O'Neill. I don't know, and Markey Ross, wait, oh, okay. And then Betsy Koh, I didn't have time to grab our guest hosts this morning. Let's see, Kirstie Gray and Shelly Long, are you close? Wait, Markey Ross, there you go. We have a question from Mary Sleppy wanting to know how many group projects, how many DNA group projects have been moved to WikiTree? The problem isn't that they are being moved somewhere is when the GDPR came about, the website World Families got shut down because they didn't have the way of updating it. So it just disappeared. So there isn't really a place for group projects unless the group project managers go out and purchase web space and server time and create a website or their own. So WikiTree is a great way to do that. And I'm just looking through the categories list, Mary and Sleppy, and there are over 20 group projects that have realized that WikiTree is a great place to put their group projects. So there's the answer to that question for you. Let's see, there's a couple of people who are posting. So Brian says that he's 17 from Kelsey Grammar. Hillary Gadsby's closest was 21. So we got five more minutes left. I can tell you that the majority of the question of the week answers are Christian answers. I can pop that up here. There was an interesting couple like the Swink Felters. Don't forget to up both these when you go check out the question of the week. The question of the week was, what religions do you have in your ancestry? And so Catholics, Quakers, Mennonite, Evangelical, Christians, Muslims, we had Hindus, we had Mormons, we had Shrink Felters. Shrink Felters. Yeah, Shrink Felters. And Betsy pointed out a non-conformist, Presbyterians, you know, Christian, lots of Christian stuff, had somebody comment that based on how many answers were Christian that we really need to work on opening up WikiTree to more people worldwide. So we have more people who have other religions. We get that. And Betsy mentioned to me this morning that was, oh look, Brian Nash, Roman Catholic, there we go, we know all about, is this it? No. No, someone posted in the G2G that I put up about today's live cast instead of responding to. Oh, gotcha, gotcha, gotcha. I won't post that. But they were talking about the fact that they didn't realize that they were involved, that their family was involved in the AME church, the American Methodist Episcopal Church, or the African Methodist Episcopal Church in the United States, which was a huge movement from former slaves and people who were enslaved. So that was an interesting commentary. So there's lots of great information about all sorts of different religions, not just Christian religions, but there aren't a lot of others than Christian religions, which does absolutely point to the fact that Wiki Tree is growing. We're getting even more worldwide, we're already worldwide, as people mentioned Hindu, people mentioned Muslim, people mentioned other religions other than Christianity. So keep those questions and answers coming for the question of the week each week. And there is the, what religions did your ancestors practice? I did. Check this out. Okay. I know that I have a lot of Irish going on. So I checked to see what my earliest known Irish ancestor, who was supposedly Nile of the Nine Hostages, might have practiced. Now this looks like a very Christian representation of him, though he lived contemporaneously with St. Patrick. He probably didn't become a Christian, but I don't know about that. But as an Irish man, he would have been practicing, where did I find it? Ah, let's go back. Let's go back. Oh, I lost it. Oh, no. To the Irish practiced, here we go. The angel, Celtic polytheism, which meant that they were pagan, they looked at a lot of different gods as their gods. And it's, if there's an Irish word for it to a something something, and I lost that page, but that's okay. English, nobody wrote Druid. No Druids? No Druids. Druids. So there we go. So we're coming down to the last few seconds. I can tell you that we have lots of great things in coming up in the next week. The Wikitrude Challenge 2 is for the Society of Australian Genealogists. That's coming up. The first challenge this week is started to help Ontario ancestors, which is near and dear to several of our hearts. Catherine Lake Hogan, I think, has been facilitating that. Thank you, Catherine Lake Hogan. There is a question from Chris Whitten wanting to know if anybody has been working on creating new profiles using the new system. Have you heard of Wikitrude Academy? Steve Harris has got that. Check that out. And of course, the Connectathon is next weekend. When was the cutoff date for registering for that? Was that Wednesday? It's probably this Wednesday coming up. I almost missed it. Registration Wednesday, January 11th, yeah. So obviously a lot of people have already registered. Let's see. 603 answers. Wow. So at least 603. So far, look at the first one on the list here, Kathy Nava. Pretty keen. Thank you. Thank you very much. Now I'm not going to say your name. Oh my God. Fearville. Fearville. Come on. I'm just going to say Fearville O. The last name intimidates me. Oh, go ahead. Go ahead, Sarah. No. Yeah, come on. Thank you very much. I can't even, I don't even know Hayden Nucket Knight. And you know that in Irish it probably is just, no, I'm just kidding. That was very rude. Very sorry. Get yourself started on the Connectathon. And that is the end of our live cast. Unless anybody else has something to say. I'll just, I'll just add that we have a wiki tree basic zoom tomorrow at 11 a.m. Eastern time. You can get the zoom link. I'm going to put it in the, there's the G2G post where you can get the zoom link. And we won't be here next week. Right. Because we will be doing the Connectathon all weekend. So yay. Thank you so much for all you great elves, Greg and Christine and Kathy, you guys and everybody else, Minnie and everybody else that worked. That was so great. It was so great to have a Secret Santa live cast. We will see you in two weeks. See ya. Bye.