Session Date/Time: 18 Jul 2026 08:30
Speaker 1: Oh, again? Yeah? That is so typical of you. I gave someone a hand. I said hello. Sorry. I just had 100% CPU. Yeah. That is is actually, yeah. Yeah, yeah, that is. I'll let you I'll let you do this, so I can do this on Monday. Yeah, yeah, yeah. Yeah, okay. Excellent. So, good morning. Good morning. We will start to kick off in a couple of minutes. So, this is an heads up that I will be talking. In a couple of minutes, but only 10 minutes, I'll try to keep it short. So, we can start the hackathon, and you know the logistics. Thank you. Excellent. All right. Yeah. Yes. There there. Yeah. Excellent. Thank you. Okay, thank you. So, I will only take 5, maybe 10 minutes of your time. So, this is the hackathon kick-off. Uh it's a crowded event. For sure, it's normally crowded, but the room is a little bit smaller than uh we had in the past uh past uh years. But please be kind to each other, uh make room for each other, combine projects with one table. I think we'll manage. I hope. There's some room around the corner. It's just sitting in a corner, and there's electricity and Wi-Fi. But first of all, let's start. So, welcome for the for the ITF hackathon. This Saturday and Sunday. Um this is always what we ask. For whom is this this first ITF hackathon? Because it's a great way to start the week. Excellent. Thank you. Yeah. Make use of this time to connect with other people, to discuss how things are going. Happy to be to have you here. Of course, who is also We are asking this question always. What's the Is this for whom is this the first ITF event? Also, ah great to see you. Yeah. Yeah. So, I hope this is a good start of the week. Uh you find your way. Uh there are some introductions for the newcomers tomorrow morning. Um yeah. Ask people if you want to find your way and if you uh want some information. Good. So, why are we here? I want to keep it brief. Um ITF uh is about standards, but it's about running code. And that's that's the important. This really important to have good standards. Um right. And the ITF started with that idea. So, with to support our standardization work, uh we can also start with working in the group. Uh the weekend before the ITF, and start implementing code, discussing drafts, uh etc, etc. So, besides all the other things we mentioned here, we also want to attract developers. That's super important. And new uh other communities. Um but in the end, uh we we believe in rough consensus and running code. So, this this is why the ITF hackathon is that important, and so successful. So, thanks again for joining us this weekend and in the past years. Um it is an ITF meeting, so you're supposed to be aware of the Note Well. I won't go into the details, uh but there is something that what you discuss here with your colleagues is ITF contribution. Um I'd just go fast-forward. The code contribution, the the code you write, is not an ITF contribution. So, that's your own proprietary, oh, your own IP, your own licenses you can apply on it, etc. So, we make a distinction, things you discuss and you present tomorrow, is ITF production uh contribution, so the ITF Note Well applies. But the code is yours, as the stays yours. So, that's important to remember. Um yeah, there are more details. You can always download the slides, ask me about details about licenses and copyrights, and IPR. But I want to skip this here. Um the projects, so I've ooh, I've looked at the projects on the wiki. There are 40 plus. That is great to see. Um Here we are. Um so, if you haven't done yet, it's really great to have your project on the project wiki. So, this is also our history, uh who has worked on which project, and uh yeah, that's good to see, and that's also good for your own exposure of your project. If you're not sure you want to join, which project you want to join, have a look at it. Have a look at the project pages. Um there are the the the champions. These are the people that the contact persons of the project. You can approach them. Or if you're not sure, you can go to the Hackathon Lost and Found. You can put your name, your expertise on the wiki, uh and people that running a project uh can find a match, and vice versa. People that run a project and looking for people can advertise that they're still looking for expertise. Uh and that's the great thing of the hackathon. It's just meeting people, talking, exchanging ideas, going from one table to another table, and contribute. Good. Uh this is for today. We are now at the Hackathon Kick-off, at 10:30. Uh next is form teams, um if you haven't done so, and there will be around 1:00 will be lunch provided. We ask everyone to be very specific about if they would join lunch or not, because of, well, our planning. We we don't like to waste food, so I hope everybody has truthfully entered uh correct uh uh that they would join for lunch or not. The same for the dinner. Okay, so uh Okie-dokie, so at 7:30 6:30 the uh dinner provided for today, and the room closes at around 8:00. Again, next time, so this is important to remember. So, because of lack of, well, uh this this little bit, this room will be used tomorrow around 4:00. Normally, we end at 4:00. So, we moved the whole Sunday schedule, I'm sorry, 1 hour earlier. So, instead of starting at 9:30, we will start at 8:30. We have an early lunch at 11:30, and we will start our presentations at 1:00, not 2:00, 1:00. And we run until 3:00. So, I will re-remind you to well, later the today and tomorrow morning, 8:30 we will start again here. Um the presentation Oh, the gather. Um yeah, I will skip that. People are using gather. If we have not enough seats, just come by me. Uh Charles is over there, and Barry is in the back of the room. Yeah, there at the right corner from me. Um You can always ask us uh about support, about hackathon, about other things, network requirements you have. Good, I will skip this. So, we have a gather space we can meet. This is important. The presentations, tomorrow, at 1:00. Um so, I guess we will have around 40-ish uh presentations, 2 hours. So, that doesn't give much time. So, we have to really to streamline all the presentations. Uh first of all, submit your presentation before 1:00. That really helps us in organizing and coordinating. And the other thing is keep it brief, around 90 seconds. And that's difficult, I know. Maybe I'm already talking longer than the ex uh promised 5 minutes or 10 minutes. It's really difficult to be stay within time, so be very aware that limit your number of slides, and try to present your project on a high level, so everybody in the room can understand what the contribution is, how relevant, and what's the follow-up steps. I think that's the important. Good. How to do that? Data trackers, we use the same procedure as working group. So, submit your slides via the data tracker. Uh it's integrated with MeetEcho. It's fully streamlined nowadays. We have really great features in MeetEcho to go to next slide without clicking too much buttons, which we did previously. Um yes, we still have GitHub available for PowerPoint templates and HTML templates, people want to use that. So, if you go to the GitHub repo from the ITF hackathon, uh you will find some information, or some templates for for your presentation if you want to use that. This is important. So, if tomorrow, if you start uploading your slides, easiest way is to go to agenda, find the hackathon at 1:00. There's the upload materials, and then you see the pop-up. Make sure you see the slides tab, and then upload slides. And everything goes smooth and automatic, and we will accept the slides. Uh be sure you upload them for the proper time slot, Sunday, 1:00. So, that's the right top. Double check that. Um I think I've said this, 1:00. PDF format, please, and uh if you want to upload the revision after that, please use the exact name. So, data tracker MeetEcho will replace that to a new revision, and don't don't place a copy. Sometimes we have two, three copies of the same presentation, or small changes, but if you use that's the case if people change name in version 1, version 2, version 3. Don't do that, use the same name, and then everything goes well for us. Um and presentations will be made in order if which they are uploaded to the data tracker, so you can follow the the flow of presentations and when you're up, so you can already walk up to the microphone with the presentation, if your presentation's about to start. So, that also helps in time. Good. The hackathon, this is a from two hackathons again uh ago, ITFs ago. This is the the GitHub, instead of the ITF 124 you see now, ITF 126. You can click on that, and there you find the templates if you want to use the PowerPoint or the HTML. Um right, good to know. Um In data tracker, if you have drafts of other work and you want to well, the work you have worked on during the hackathon, put that uh associated with your drafts, you can use additional resources, uh if you're the author. If it's an individual draft, you can do it yourself. If it's a working group document, you have to ask the chair. And then you can have different tags and you can add different resources to your draft. It's a very useful uh feature of data tracker. Thank you, Charles. It was the idea of Charles, and uh it's very useful. Uh Monday is really the last thing I will mention. Monday we have the Hack Demo Happy Hour at 6:30, at uh at the same place where the registration is. Uh it's a great way to present your results to the broader ITF community. So, if you want to present your uh project, you can register uh at the wiki. Uh before 1:00, uh is there an Okay, it's on the hackathon wiki, look for the Hack Demo Happy Hour, and there you find uh a link, and you can fill in your name in the wiki, so we know how many tables we have to make uh room for, how many tables we have to reserve. Good, that's it. That's it. We don't have a uh uh code lounge this time, uh so please use the lobby bar. Probably a great place to meet other people, to hang out, and work on code, and discuss stuff. Good, want to thank ICANN for sponsoring this event, and that's it. Any questions, you can find Charles, myself here in the front, Barry at the very at the very back end, and success. Enjoy, bye.