Strong Nix
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 28 | |
| Autor | ||
| Lizenz | CC-Namensnennung 3.0 Unported: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen. | |
| Identifikatoren | 10.5446/61029 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
|
NixCon 202210 / 28
10
12
20
21
22
24
25
26
27
00:00
Digital Object IdentifierMeta-TagSoftwareentwicklerProdukt <Mathematik>MaschinenschreibenPunktSoftwareentwicklerCoxeter-GruppeFacebookGemeinsamer SpeicherReelle ZahlSoftwareComputeranimation
01:24
Leistung <Physik>WhiteboardMereologieWendepunktComputeranimation
01:55
Coxeter-GruppeOffene MengeBereichsschätzungOrdnung <Mathematik>Open SourceDokumentenserverSchlüsselverwaltungMultiplikationsoperatorDifferenteSoftware
04:10
Normierter RaumCachingSoftware EngineeringViewerSichtenkonzeptBitMaschinenschreibenZweiGrundraumPerspektiveMatrizenrechnungWendepunktSondierungOrdnung <Mathematik>SoftwareTermFlächeninhaltDifferenteMAPAnalogieschlussMenütechnikRückkopplungGanze FunktionZahlenbereich
10:08
WhiteboardQuellcodeDesintegration <Mathematik>Kollaboration <Informatik>Formale GrammatikPartielle DifferentiationIntegralFunktionalMechanismus-Design-TheorieSoftwaretestSoftware EngineeringMereologieProdukt <Mathematik>WhiteboardMenütechnikOpen SourceMetrisches SystemProjektive EbeneJensen-MaßMultiplikationsoperatorWendepunktOffene MengeDifferenteMaschinenschreibenTermUmsetzung <Informatik>Kollaboration <Informatik>HilfesystemAutomatische HandlungsplanungKontextbezogenes SystemMaskierung <Informatik>Patch <Software>SpeicherabzugLeistung <Physik>Computeranimation
17:52
Formale GrammatikSoftwaretestElement <Gruppentheorie>RückkopplungFlächentheoriePunktBefehl <Informatik>ATMWhiteboardEndliche ModelltheorieMechanismus-Design-TheorieBitMulti-Tier-ArchitekturTermFormale GrammatikUnordnungMultiplikationsoperatorVollständiger VerbandDifferenzengleichungOrdnung <Mathematik>Quick-SortDatenstrukturService providerFlächeninhaltFigurierte ZahlLoopKanalkapazitätLeistung <Physik>Hinterlegungsverfahren <Kryptologie>Exogene VariableMAPRichtungWechselsprungBus <Informatik>Automatische HandlungsplanungTemplateHydrostatikMereologiePhasenumwandlungWissensbasisTeilbarkeitTrajektorie <Kinematik>Computeranimation
25:36
PunktWeg <Topologie>AggregatzustandObjekt <Kategorie>Jensen-MaßGamecontrollerUnrundheitWendepunktUmsetzung <Informatik>StrömungsrichtungDistributionenraumRechter WinkelNichtlinearer OperatorDoS-AttackeGemeinsamer SpeicherBitVerknüpfungsgliedMAPBesprechung/Interview
31:26
Computeranimation
Transkript: Englisch(automatisch erzeugt)
00:00
Again, thank you guys very much for coming. I'm going to kind of touch a point that's near and dear to me. I'm bad with naming, so I called it Strong Nix because it's supposed to make Nix stronger. Very straightforward. All right, I think I introduced myself yesterday, but real quick run through.
00:23
Software engineer, IDF, startups, developer products, or Facebook. Big on nonprofits, so I love things like this. I love organizing it. I love seeing people. I love this, you know, helping out. And flocks now. Share a little of my Nix backstory.
00:42
I do have to thank my wife for letting me do Nix. About a day after I proposed, I took her to Nix Paris. That's actually intro, but this is Nix Paris. And she's still with me. So that's also a picture of Ryan before the haircut.
01:02
Other than that, I've been quite busy, so excuse if my deck or presentation is... We good? Okay. Excuse if the deck or presentation is a bit chaotic, but yeah, this is a picture of me working on it five minutes ago.
01:22
But let's get into why I'm here and what I'm talking about. I hope this is good. Okay. So a few key topics I want to discuss. Strong Nix, why, what it means, the key areas, and the inflection point.
01:43
Learning from our neighbors, it's another effort that we did as part of the board. And then empowering teams and community power. As I said, I'm really great with Nix. So excuse him. Why? Why Strong Nix? What does it even mean?
02:00
So Nix over a decade ago, and since then have solved many, many different problems for a lot of different engineers, for all of you sitting in this room, it's just technical masterpiece thanks to Ilico and a lot of contributors and members. We've grown as you've seen in the presentations that we've had in the past few days.
02:21
We have thousands of contributors and we have one of the more active open source repositories in the world today. But as our friend who I think did one of the best presentations I've ever seen at Nix yesterday said, we want to give him more friends, right?
02:41
We want Nix to grow. And we are growing. Just in the last survey, as you've seen also yesterday in some of our presentations, 30% of the community today is comprised of people that joined just in the past year. And in order to keep that growth, we need to create clarity and confidence
03:02
across Nix, the community. And I think one example I would like to give on the why here is as we grow, the community is going to change, right? It's going to kind of start bringing in the less Nix experts, right?
03:20
The more new to Nix or completely unfamiliar with the concept where we talked yesterday about the principles of Nix, folks that are software engineers, but just have not been exposed to this at all. And while Nix is free, it's open source, it isn't. Every one of you here is paying for it. And everyone that's going to be joining is paying for it.
03:41
They're paying for it with the risk that they need to kind of take in order to switch their infra, switch their OS or rely on a new technology. And they're also paying for it with time, right? Obviously onboarding has been documentation is a key topic and there's going to be a good talk about it today. So it's not free. And therefore the why,
04:02
we need to either reduce that risk and time or just make it much more compelling so that they can understand why they're taking that risk. Wait, lost my mouse.
04:22
So first, what does this mean, right? What are the key areas that we think we should kind of look into and see how we can strengthen that inflection point which I'll get to in a second. Number one is increasing our general resilience, right? So when someone's looking at Nix or looking at the community, they're, like I said, taking a risk.
04:41
And because we're a very kind of lower on the stack level we're an infra technology, that risk has upstream impact on almost everything they do. So when they look at us, they need to kind of feel confident, not just in the tech itself, but also in the general community
05:02
and making sure it's a community that's supportive and helpful. So some of the areas that we've been thinking about in terms of general resilience has been the fact that the growth will start putting more strain. We'll have more contributors, we'll have more users, we'll have more people asking questions.
05:20
And some of the areas that we've been looking into has been, I think things that have been called out, right? RFC, collaboration, general support. Another area of resilience is that imagine you're an external user, you have no clue what Nix is, you come to nixos.org, you might visit our discourse or matrix. And we wanna see how we can provide that clarity, right?
05:42
We wanna see how we provide both clarity and clear governance. So people know what's going on, they can kind of like understand and have it seem straightforward. So I think this has two facets. Internally to us, it's exposing what the community
06:01
and the user needs are. We talked about it in terms of like the surveys and the feedback and just making sure that we're doing the right things and prioritizing them. And from them, they're of course prioritizing it correctly. And really showing an external viewer how things are done in Nix.
06:21
Because when someone comes in, they haven't been to Nixcon, they haven't spoken to Ilco privately, they haven't interacted with Nixers potentially, and just helping them understand that very clearly is gonna be a focus for us. Externally, it's again, the things that I mentioned earlier, right? It's helping them jump into Nix,
06:42
but also reducing the concept and of the risk involved with taking on Nix. Advocating, pretty straightforward. I won't add too much on that. I think it's just making sure that we are all advocates of Nix in the external realm. I think there was a ton of great talks
07:00
on how we can be better at that. But positioning, I think, we talked a bit about the marketing team. Where is Nix positioned? I'll click through a few pictures later, but when I come today to a, let's say, I mean, we're in France, right? We come to like a French restaurant,
07:20
or let's say we go to a crepe place, right? We're going there to get a crepe. They're not advertising the fact that they have like Coke in the fridge. They might have it. Once you get there to get the crepe and you want a Coke, cool, they have it, that's an added value. And I'll touch on that in a second.
07:41
General ecosystem, I'll talk about that as well. Community is going to change. It's gonna grow with people that are outside of this room and they have different perspectives to software engineering, different enthusiasm to software engineering and we need to see how we can kind of bring them in and embrace them with a warm Nix hug, not a too hot one. And that kind of ties into setting up
08:01
the newcomers to success. So in terms of positioning, I just found this graphic. Nice. This is the DevOps ecosystem. Be curious to say, where are we? No, you need to choose one.
08:22
Where are we? There's planning and coding, there's building, testing, integrations, there's CI CD, there's release and deploy, there's operating and monitoring. Nixinator is pretty on point, right? I mean, we're all of it.
08:47
Now, there's a few analogies I can use. But yesterday we went to a French restaurant and one of the Flox team members really likes trying new things. So we saw in the dessert menu
09:01
something called the Big Baba Plug. We can't force an entire cake down people's throats. People have a view of what they do. They have a view of how they use it. They're used to doing it. They were taught about it in college and the university.
09:20
Their friends explained it to them once and forever they don't wanna leave it. There's politics in software engineering. For us, maybe less because we're very open source. But once we step outside to the engineers that are working from nine to five and all they care about is being a software engineer in order to come bring a paycheck and then do other things,
09:42
they have different considerations, right? And this doesn't work. We need to be able to tell them, maybe it's all of it, but we need to be able to tell who's coming to us and then why they should come to us in order for them to come in and then go and see,
10:02
oh, shit, it is all of it. Now I can grow into the rest. This is what I did about five minutes ago. I'm great at drawing. I have lots of skills, guys. You asked about board composition. I'm the artist.
10:20
The inflection point. So you've seen this yesterday. We talked about it. Excuse me. We're growing five X in like two years. That's great. But really this is what's showing us just the beginning of where we're at and kind of where we wanna go, right? We want some pitas on the non-keying petabytes
10:44
on the menu for us here. And the real question is there's two. What does it look like at the top so we can build, we can work backwards to make sure that we set that up for success. And then along the way, how do we maintain it as a community, right?
11:02
So again, this has been seen across like Nick's awareness, the fact that 30% are newcomers. And then some of the metrics that we shared in the opening keynote yesterday that you've all seen. Now, as I've stated earlier, right? A lot of this growth is gonna go beyond this room
11:23
into people that just have different concepts of software engineering than we do and use it and utilize it for different ways and are more risky or less risky. I would assume off the bat that they're gonna be less risky in terms of the risk that they're willing to take. They're gonna be engineers that have less time to dig in, right?
11:41
They wanna take a piece of Nick's. They want to go into Nick's, but we need to kind of help them do it. And on the other side, the things that we're thinking about and I would love community support and ideation on how we can do it is how can we introduce more entries and escape patches into Nick's, right?
12:02
Allow people to that beautiful graphic that I had before, come in somewhere, but leave before they have to finish everything. So for instance, more sandbox learning, that's something that's very kind of starting to be common in the general industry. I come in, I can play around, I can feel the power
12:20
and then I can understand why I wanna use it. More practice projects, partial integrations of Nick's, like I said, and really mechanisms to help us, help them test Nick's out, right? Take it for a test drive. So this is the generality of strong Nick's. I think this is a lot of,
12:41
you guys ask questions about the board and what we're trying to do. This is a big part of what we're trying to do. And this is the reason I'm talking about it is because we're not gonna be able to do all of this without all of you, right? So I wanna kind of start building up and collaborating on things in that area.
13:03
Now, some of the other things that we've been doing is we've been, oop, clicked the wrong place. There are successful open source projects that we can learn from. Some more, some less, but again, we're not the first open source. So we've started talking to a few
13:23
and we wanted to share kind of some of the key takeaways that were shared from it. So we talked to Plone, Linux, Rust, Haskell, presidents, PMs, chairwoman's, chairs of the board, and really just kind of started asking them, what worked, what didn't, what would you,
13:41
I think the main question that I really appreciated was if you could do it all over again, what would you change, right? What would set you up for more success or given you less pain or potentially skipped a failing point? And I think the things that most stood out,
14:02
at least to me from those conversations or to us, were these six things. So I'm gonna kind of just run through them. And by the way, I do at some point, once we have time, just plan to release all the notes from the interviews. I think one of the key things that came in
14:21
and we've been discussing it is that the foundation serves the project and community, and the community is served by the project, right? So the concept here, and I know it's a ambiguous one, it's very macro, but the concept here is that the foundation, that's the core principle of it.
14:41
And again, why am I emphasizing this for probably the 10th time across the two days? We can't do this without you helping us understand what this means, right? Now, make sure that the Nix community stays a greenfield. By the way, I replaced Nix, I think, with Rust here, just to make it more sense,
15:00
stays a greenfield than anyone that wants to join. I don't know how many folks kind of understand the depth of this statement. Greenfield means that at any time for decades to come, anyone coming into Nix will be able to easily bootstrap from the ground, whatever they wanna do with it. Make it always accessible, always welcoming,
15:20
and keep it that way. Integrate intentional priorities and plans, make it explicit. So I think one of the other concept that came up was that a lot of these communities benefited from starting to think about where are we going and how can we be intentional about it? How can we collect that feedback, right? I think in other terms,
15:40
it might be called kind of like the product cycle, but looking at our open source and if it was a product that we're trying to offer to these people that haven't been blessed with Nix. Invest into empowering collaboration across the community. So teams, so I'll touch on that in a second, and we also touched on it yesterday, but the whole concept of team empowerment
16:00
was really also strengthened by, I think, talking to both Rust and Plone, and I'll touch on it again soon. Drive, I like this one, drive the right awareness to the world. Nix principles. We don't have to force you to use Nix tomorrow, but I think another big gap that we have today
16:21
in getting that inflection point even further along the road is the principles of Nix, right? Reproducibility and the things that we mentioned yesterday, do other people understand it? Do they know why it's impactful and why they need it? And I think we do this insanely well, but keep it up in terms of prioritizing
16:41
like the strong community ethos and the culture of Nix itself. Jumping into empowering teams alpha. I know some of you probably haven't seen it. We posted a little post about it this week out of all the Nix craziness.
17:04
Really the goal that we kind of came into with empowering, with the whole team empowerment concept, and I think everyone touched on it, came from the surveys, came from people talking about it for probably years and just came from the general need within the community.
17:20
So the idea here is that we want to improve the functioning and the impact of all of you by giving you the tools you need and setting you up for success and also giving you direct actionable support from the board and the foundation. Of course.
17:42
So what we hope this will achieve for us is that we hope that it will create a scenario where the community and the teams in it have clear mandates and responsibilities, but also have clear ownership. I personally believe that in a lot of instances, that is the path to being empowered and being able to do what needs to be done.
18:01
Having that ownership or whatever that mechanism is, but just you knowing that, you know what, marketing team, I think this is a very easy one. They own the website, right? So they have an idea, they want to test it out, they can roll it out and do it, but we need to spread that out to a lot of other areas and a lot of other places
18:21
so individuals can just come in and not be stuck in a loop of approvals all the time. We can make mistakes, but it's better to make a mistake than to be kind of like held back in some sort of status quo waiting for something. Reducing overlap. So ideally through creating transparency and better communications,
18:40
people will be able to contribute, but also people will be able to know what's being worked on and what they shouldn't. Not shouldn't, but don't have to. Like I said, direct board support and funding. And I think one of the main concepts that we also talked about is removing bus factor, right? So if we want to look at it in a positive light and not in the bus factor light, there's a few people here, some of them in the room,
19:01
that if they win the lottery and decide to completely disappear from the surface of the earth, we'll have a few sleepless nights to figure out what the hell we're doing. So going into the empowering teams, we came up with a tiered model. Sorry, actually Rust and Plone and a few other communities came up with a tiered model. We added a third tier.
19:22
Their model had community and critical. Our model has community, formal and critical. The whole concept of why the hell do we even have tiers is because in order to give, we have to create some sort of structure. Otherwise we'll be in a loop of, okay, we're, you know, this one's asking,
19:41
this one's asking, do we go there? Has to have some sort of prioritization. So starting off with the community, very point blank. This is the community today with just a bit more support. It means everyone and anyone can open the team, a collaboration, do whatever you need to do. But now we want to make sure
20:01
that you guys also have access to the website, right? Some sort of like team creation template that will maybe help you out. Just get your thoughts in, excuse me, in a structured way. And beyond that, we also plan to introduce just in general, start collating like a Nyx team knowledge base
20:22
where we have so many teams and so many people doing incredible work. I think Valentine's gonna talk about documentation very soon but he's been creating templates and has been creating like these things for the team itself. The Nyx team with Tiofan, there's a lot of things that if we just ported them out into a template, when I want to come in and create a team, it'll be much easier.
20:43
So that's generally the community. I think some of the examples we had of these teams were like Emacs, static builds, Mac OS, right? But really it's anything and everything. Formal, so formal is the middle tier that we introduced.
21:00
Most of the communities we spoke with had community and critical. Critical, I'll jump into that in a second, but critical is like, if that team disappears, they win the lottery and go, we're in deep shit. Formal is the middle tier. Formal is, we don't wanna have such a huge gap between, oh, these are the critical teams that we think are critical and we support
21:21
and everyone else, Greenfield's great. We wanted to have an opportunity for folks to move into like a middle tier where it's still very impactful, but if the days appear, we're not gonna be not sleeping for two weeks and still giving them the support that they need. Some examples of formal teams is like, for instance, the Nix team or the doc team
21:41
or teams that are directly impacting the trajectory of Nix itself, but we won't need to kind of chaos firefighting mode if something happens or something is delayed. A little bit more about what this means in terms of the support that we plan to give. So we plan to release a Nix Foundation funding mechanism
22:04
to all of these formal teams and beyond. So formal and critical. If you need funding, if you need to do meetups, hackathons, you need resources for your teams, that's something that we want to introduce. Non-monetary support. Thank you.
22:21
Non-monetary support. So going beyond that, we talked, you saw the board yesterday, there's people that are actively involved. We have board observers, we hope to have more as well. We want to be able to, like the board is going to be actively taking time from their plates. And if formal teams or critical teams need us
22:42
or just need general support, we'll be the first to raise our hands and kind of provide that SLA to all of these teams that will be there if needed. And of course, just like some smaller things like added visibility across channels. So like the formality, right? The website, the social medias, the discourses, and really kind of working together
23:02
on that advocation piece. So that's what we're providing. And in order to do what we said in terms of empowering the teams and making sure that the teams get stronger, we're also starting to alpha test. By the way, this is all alpha, it's big there. We're testing this out, so we'd love the feedback,
23:21
but we want to also kind of provide guidelines to responsibilities and accountabilities that we think teams should have in order to be at a higher level. So some of the things we've been thinking about is like tracking membership and having a point of contact, clear ownership statements. So why does this team exist? So others can understand and kind of provide that transparency.
23:42
Long-term vision, public issue tracker, and then just general ops, like have all your meetings on the next calendar so others can join, know about it, know its recurrence and who's there. Moving over to the last, critical teams. So again, like I said earlier, those are teams that if they disappear tomorrow morning,
24:03
we need to figure things out. The idea there is to both have all the formal capacities of the previous ones, but then introduce a few more. One is direct commitment of the board to be involved, either as a contributor to that team
24:21
or as someone that is like at a, like a army 12 hour response time, like something happens, the board is involved. And also as an escalation path. So all critical teams, like a question I can ask is like, if you need to escalate something that is blocking Nix, where do you go? Just making sure that that's very well-defined and there is a definitive stopping point
24:43
in terms of if that person has an answer and that person doesn't answer, here's my phone number, here's like someone that is from the board that is gonna jump into this no matter the time, the hour, where they're at. Quarterly plans and retros, roadmaps, and really these are parts that we wanna help with. Some of the teams that we've been kind of looking at
25:01
to alpha test this with is like infra. And we also imagine the RFC team potentially being in that mix. And really that's it. So the whole concept of empowering teams right now, it's in an alpha phase. We release an initial concept and idea in a post. We want you guys to give us that feedback.
25:20
And I think I've already started seeing people comment, apologies for not responding, it's been Nixcom. Get involved, if you care about it, if you have ideas, and that's how we kind of go from there. And last, Nix community power. So I can't state this enough.
25:42
The only way that this works is if we have, if we're able to reach like an aligned friend where we're all plowing through these things. So really how we do this, we're trying, I think I'm going back to that graphic. We're trying to do quite a bit
26:01
and we all want to see Nix grow. And I think that I am super bullish on the fact that Nix can take over the world. We can do quite a few things that are gonna be, if I told this today to a non-Nix developer, they would probably laugh at my face. Why do you need containers? I think we had a lot of container talks. But to do so, there's a cliche kind of point
26:21
of like it takes a village. It probably takes like an entire citadel of like 50,000 people, but who's counting? Okay. Again, thank you. And happy to kind of move to questions.
26:42
Thank you, Juan. Thank you, Juan. There we go. Are there any questions? Ron, I like what you're doing. It's great. You're studying, you're talking to Rust,
27:02
you're talking to Haskell. Have you talked to Red Hat? Have you talked to SUSE? Have you talked to these people about growing an operating system? Yes, so I mean, I've personally talked to Red Hat and SUSE Linux, but I think that's a good point that we can kind of explore more of how they took,
27:21
I think they took it at a different approach or at a commercial approach, but I think that there's probably a lot of learnings that we can get from them. Well, to me, it was commercial takeover, yeah? So basically, these were independent companies and then big money came in. And then these companies changed. And Nix is kind of my little baby passion.
27:41
I mean, it ain't my first rodeo. I've been in it, I'm the oldest Nixer in the room by a long, long way, right? And I just don't want the repeating of history. So talk to them and see where the- What would you ask them? What would you ask them? Why did you sell out? Why didn't you just keep going?
28:02
Red Hat? Yeah. What do you count them as selling? But I'm confused. Well, we'll talk offline. Okay. I don't want to bore you. No, no, I'm- Good question.
28:20
Okay. When I first came to Nixcom, I was a newbie. And I don't, it's only newbies in the room that never used Nix before. So I'm reading the newbie track called officially upstairs and it's 14 flights up the stairs. And if you want to learn about what reproducibility is and Elko's amazing work, then I'll be up there all day
28:42
because I've got to work. So come and drop in. So I have actually an objection on the criticality of teams. So I think that the marketing team should absolutely not be critical. And also the RFC team is not critical because simply, I think as a community,
29:01
we are not ready yet to take the influx of new users that we would produce if we had successful marketing. What do you think about that? Two things. This is why we've been butchering this topic like hell for the last few days.
29:21
And this is why I put alpha in big bold letters earlier. I completely agree with that statement. I think we aren't ready, right? And if we want to be blunt about it, I think a conversation over beers is more fitting than a recorded talk. But I have some very kind of like strong opinions on our current status and,
29:42
oh, Dave wants a good dinner. So I don't, so again, like very bluntly, we aren't ready. I think making the marketing team a critical team doesn't necessarily mean that we're gonna open the flood gates to 10 million people tomorrow morning. It's gonna be a, yeah, sorry, Brian. Brian is like, yeah, Brian's a hype guy, so.
30:00
It's gonna take us month, if not years to reach a point where these teams are like, look at Linux, look at these other distributions and repositories, right? To get to the stage where we're ready for it. So it's something that has to happen. I mean, we have to start structuring them now, right? Because the inflection point,
30:20
and we also don't control the inflection point. It's happening with or without us wanting it. We're seeing it. We didn't do, I mean, we did kind of do some things, but we didn't do like something grandiose and things have five X, right? And people, like I said, the people that are coming in externally, some of them have an appetite for a one-time thing.
30:41
They come in, they get scared, they get shell-shocked, and it's gonna be really tough to convince them to come back. So I think that's my point, but you're right. Yeah, I agree. I think we should first fix the basics, the substance that already is well-explored and only then let people come and get a taste of that.
31:00
But if you have more concrete thoughts, please share it with us. Right now, why not? Yeah, no, I think I just shared it. I ended up sharing it. Like my thoughts on how the inflection point is not something that we decide on, it happens. And it's something that is gonna be kind of tough for us to walk back from if we're not able to structure it correctly.
31:21
Thank you, Ron. Thank you. A round of applause again for Ron. Good to ask the lightning speakers.