 Great to see all of you here. I'm very happy to welcome you to the first Osmocom conference. It's been basically nine years of work on Osmocom projects, but we never had a public conference like this before. And well, as you can see, quite a number of people have turned up. So I'm very happy that, at least in terms of attendance, it is a success. Now we only need to deliver on our promise of telling you a lot about Osmocom. So I would like to go a little bit about the audience first, who is basically here, who is attending. Then there's a couple of organizational things I'd like to say in the beginning and have a very quick overview about what Osmocom is, where does it come from, because maybe not everyone is on the same page here. So what do we have here in this room? We have Osmocom developers, people who actually write the code and contribute to it. Maybe if those who have contributed to the Osmocom, any of the Osmocom projects could raise their hand for a moment. So we have some insight into that, so you can see a significant portion of people here attending. We have some people who operate commercial cellular networks. I think it's very few people, if maybe they could raise their hand. Well, actually, quite a number of people as well. We have some community wireless network operators here. Maybe they could raise their hands. Great. We have some people who do IT security research and use Osmocom stuff as tools for their work. Maybe those people could also raise their hand. Thank you. We have academia research present. Also, three people, all in one corner. We have vendors of BTS hardware or physical layers also present. Yeah, that's some few people, three at least. Well, okay, not so bad. And we have people who are doing device testing. I'm not sure how many there are here, but that's typically also in our user base. So people who use Osmocom or let's say the NITB to test phones or machine to machine devices or something like that. Yeah, well, okay. So that's basically, well, probably there's some people from other backgrounds as well, but that's sort of just to give you an idea about who is here and to give you some background basically on where. I'd also like to say some thanks to Hike for organization back office and registration desk work over there. To Micah for ticket sales and registration. To our hosts here at Eugen Gästehaus, which probably nobody who doesn't speak German can pronounce. So JGH to our speakers, to the anonymous sponsor for the travel grants and to the C3 VOC, the CCC video operation center for doing the video recordings and even live streamings today. So anyone who cannot be here can watch the talks and see the recordings afterwards. That's, I thought, very nice of them to be here and to help us out with that. Thank you. While I'm saying that we are sharing the internet uplink for the Wi-Fi with the video stream. So if all of you are doing, I don't know, Debian upgrades or something like that over the Wi-Fi link here, then the stream might have some issues. So please consider that. Yeah. Okay. Also, of course, thanks to everyone who contributed code. Otherwise, we wouldn't be here. So schedule, the RAS schedule, the detailed schedule you have on paper. It's also online. So we have some talks, a morning break, a lunch break, an afternoon break. We have the social event at the evening or in the evening. If you don't know where the social event is, there is a paper leaflet at the registration desk that tells you the address and how to get there. Yeah. So you can inform yourself. Of course, it's also on the website. Yeah. And in between all those breaks on the schedule, we have the actual schedule. So social event again here. Yeah. So where do we come from? In 2008, Dieter and I started with some old Siemens space station hardware that was available on eBay. That's basically where we're coming from. So there were some old Siemens BTSs available with E1 interface. We had to connect them using ISDN cards. There's no IP or Ethernet in those space stations. And we implemented whatever was needed beyond this BTS hardware to have a self-contained small telephony network. And this initially was called, I think, BS11 ABIS because well, it was an ABIS implementation to talk to the BS11. And then we called it OpenBSC, which is not really a good name because it's not just a BSC. It has many other things besides the BSC. And we have the first commit basically there in December 2008. So it's been quite some time. And we initially had this as a proof of concept just to demonstrate IMSI catchers, false space station attacks and so on. And we added support for more hardware over time. Already in 2009, we added support for IPXS nano BTSs, which means that we have created more or less unknowingly at the time the first base station controller that can operate with BTSs from multiple vendors, which normally is not the case. So BSCs and BTSs have always been sourced from the same supplier and from the same company. In 2010, we started Osmo-com BB, which is where Osmo appears the first time. So the etymology of Osmo. And we used the name for the phone side GSM stack. So we implemented the GSM stack for the telephone side as part of the Osmo-com BB project. And then this also created what we call the Osmo-com umbrella project, which is by now a large project with many sub-projects. Initially, it was basically just the Osmo-com BB and the OpenBSC as the only two projects, but then SIMtrace and many other projects came along. So what brings us together is we are all people who are enthusiastic about doing free software in the area of cellular communications or mobile communications. We did some work on Tetra, on Turaya, on Deqt, on OP25, on various SDR projects. SIMtrace, many others. I did the account two days ago. We had 59 projects in Redmine and 112 Git repositories. And I think what most people know about is mostly the RTLSDR, the OpenBSC and the Osmo-com BB. But there's lots of other interesting stuff, so feel free to check that out and have a look. And basically what I want to emphasize is that Osmo-com is more than what we're talking about today. So today we're talking about the cellular infrastructure project, specifically. So we're talking about GSMG, PRS Edge and 3G running networks of these technologies using Osmo-com. But there's many other projects beyond these topics, but this is at the core of the interest of a lot of people. So we thought we focused the event there. Also one thing, since not everyone shares the history or the background in free software, free software is not primarily about somebody getting some software for free, but it's really about doing collaborative development. And everyone brings something into the project and in the end everyone gets all the results. Some people have characterized this as the cooking pot economy. So basically you're cooking something and everyone brings some ingredients and in the end everyone can eat from that pot. The difference is though that in software and in non-tangible goods, everyone can have the whole pot and you can copy it as many times as you want. So it's sort of a bad analogy, but this is really what this is about and it's not about a one-way consumer-producer relationship because in the end people who write software somehow they have to earn a living as well and it only works if it's a complexity and the wide scope of the projects that we are running today only works if everyone who uses it and who builds commercial products and so on contributes to the code. Also one word or one slide about SysmoCom. It's a company that Holger and I founded in 2011. It exists to support the development of SysmoCom so we do some products which we use and the revenue we use to finance to cross-subsidize the SysmoCom development by the paid developers on our payroll. SysmoCom does not claim or want any ownership of SysmoCom. That's very clear. We always try to keep a very strict separation there. We organize this event as a legal entity but that doesn't mean that we as we don't claim ownership or anything like that. This is fairly separate. Also the trademarks, the domains and so on are not with the company. Unfortunately I have to say today SysmoCom is doing more than 80% of the commits on those cellular infrastructure projects which I say unfortunately because we don't want to be a single point of failure. We don't want to be the how can I say if SysmoCom dies tomorrow OsmoCom should still live. That's basically the goal. It has to be sustainable and it should not have this kind of single dependency on any single entity. Just in time at quarter past I'm very happy. End of file.