 Thanks everyone for joining in. We are about to kick off Code Beam Lite. I think I just quickly wanted to introduce the man himself, Francisco, as you know him. He is the creator and the CTO of Erlang Solutions, but more importantly, he's been behind the Erlang ecosystem, you know, the conferences that you see all the Erlang and Alexia conferences. Someone who I highly look up to as someone who's bringing the function programming and Erlang and Alexia community forward. So without too much of a delay, I think I want to hand it over to you, Francisco, take it away. Well, Naraj, thank you so much for having me. So, you know, today, I think unlike my last talk at Code Beam India and functional conf, I'm here not to share knowledge, and then instead here, I'm actually here to rally you and all of your friends, you know, to come forward and start sharing your knowledge and help us build the Erlang ecosystem. What I will be doing is introducing the Erlang ecosystem foundation. You're mentioning who we are, what we've been up to and finally, you know, how you can actually go in and start getting involved. Now, who are we? The Erlang ecosystem foundation got founded the last decade, probably two, three years ago in 2018. It was a group of companies and individuals who are really passionate about the Erlang ecosystem, but felt that it was time to go in and get together, you know, rally community and start leveraging our network to get together people who could then cooperate and work together. You know, we'd been lucky enough to see a single programming language, Erlang, turn into an ecosystem of languages. And, you know, we also, you know, and often these ecosystem of languages came from a variety of communities. So we wanted to go in and really start getting, start getting these communities to start working and cooperating together in a wide variety of work groups, which we'll get into right now. But, you know, who we are, we're a nonprofit, you know, we're individuals from the Erlang and Elixir community and not only Erlang and Elixir community, what we're doing is we're volunteering our time, you know, to grow the ecosystem. The goal has always been, you know, to grow and support a diverse community around Erlang and Elixir and the ecosystem as a whole and encourage, you know, the continuing development of technologies and open source projects, you know, based on and around the Erlang runtime. It's, and it's not about Erlang or Elixir, it's actually about all of the languages running on the Erlang VM, which we today know as the beam. But it may not even be about the beam, you know, in the future, you know, new VMs will certainly come up. And, you know, and if the community founds it important, you know, to develop and promote them, the foundation will focus on them too. And, you know, it is, and that is the important bit. The important bit is that the community is one that guides the foundation. It is the members which tell the foundation what direction to do. And it's foundation from the community to the community. And when I talk about the community, you know, that means you, I don't know how many of you are aware of it, but, you know, there are, you know, last time I counted, there were over 35 languages running on the beam, 35. You know, these are some of the most well-known or popular ones. You know, we've got Erlang, Elixir, this flavored Erlang, Luerl, and we're seeing a foray into statically typed languages. So caramel, gleam, we've got, you know, Sofia. I don't know how many of you have heard of Sofia, but it's, it was developed by Eternity and it's a domain specific language for smart contracts. But yeah, like I have all the others, it also runs on the beam. So, you know, we're seeing a lot of language inventors which have implemented language on the beam, actually being very interactive within the various work groups of the foundation. To give you some numbers, you know, the foundation in numbers, you know, there are currently 26 sponsors, two of them, I'll introduce them soon, you joined last month. Sponsors are companies which donate money and allow us, you know, to go in and pay stipends, pay overhead costs and, you know, support activities. Among others, you know, they're supporting this conference and have helped, you know, sponsored by the few students who joined. We've got 140 annual supporting members. They pay a membership fee, which allows them to vote. And alongside that, members who wish to, who are actually contributing and, you know, by contributing, you know, they're active in the work groups and, you know, contribute, I believe a minimum around 20 hours per month of their time in developing libraries, helping you build community, get also, you know, what we call a, either a managing or a contributing membership. And that gives them also the right to vote for the board. There are 17 lifetime supporting members, you know, to become a lifetime supporting member, you pay your $999 and then you basically are eligible to vote for the rest of your natural life. We have voted in two fellows, actually three fellows, Joe, Michael, Robert. So fellows are, you know, members of the community who have done outstanding work. And, you know, what we did is in 2019, you know, soon after the foundation had been created, Joe Armstrong passed away before we were able to vote him in as a fellow. And the bylaws, you know, clearly state that your fellows have to be alive. So we couldn't posthumously go in and vote Joe in. So we created a new title, the fellows emeritus. And, but the bylaws didn't state that you were not allowed to vote in someone who had passed away. So Joe Armstrong, Mike Williams and Robert Verding all became, you know, got voted in as fellows. And then Joe got automatically disqualified, but we made him a fellow emeritus. And then so we kind of, yeah, we got creative and found a solution to the problem. So, you know, we have two fellows in a fellow emeritus and we've got 917 basic members when we last counted yesterday. And, you know, basic memberships is free. Anyone is allowed to join. And what you do is you get access to the Slack channel and you're able to go in and interact with any of the 12 work groups. So I really recommend you, you know, go into the early yes.org website now and sign up for a free membership. It would be great to see you all do it. And, you know, you'll get a few, the odd newsletter, but more important than that, you know, you'll be able to get access to the Slack channel and I'll be getting back to that very soon. Now, this is the board. The board is voted in by the board is voted in once a year by the community and, you know, by the members. And just to give a quick update, you know, we had Jose who was one of the founding members. He decided to step down a year ago to focus on a machine learning work group. And just last week, Ben Marks got elected in. He's a new member of the board. He replaced Richard Carson, who'd been also founding member, as well as Maxine Fedorov and Kenneth Lundin, who both went in and got re-elected. And, you know, who's the born? You're a peer street singer. You might know from the grist boards. You know, Miriam Pena has been part of the ecosystem for, you know, well over a decade. She was voted one of the 12 inspiring women to watch in tech in 2018. Maxine Fedorov is a senior engineer at WhatsApp. So it's a really great connection to have. You know, Alistair Woodman, well, he's been around the community for ages. He's an entrepreneur and angel investor, Exisco. You know, Sebastian Strowlow was a colleague of mine at the computer science laboratory where they invented our language as an intern there. You know, Kenneth Lundin is the manager of the OTP team. And then, yeah, we've got Brian Paxton who, you know, initially got involved in the foundation very early on. And then got involved very early on with helping out with the infrastructure. And then, you know, got voted to the board. There's me, you know, there's Fred Herbert who you'll know from all of his books. You know, Erlang in Anger, Learn You from Erlang, you know, Adopting, Erlang in Property-Based Testing, you know, with Erlang and Alex here. You know, Sophie. Sophie's been working with Alex here also forever. She initiated at the Flat Iron School and then she's currently at GitHub. And she's also a co-author of, you know, Phoenix Programming with LiveView and Ben Marks. He got involved with Alex here at Bleacher Report to help to migrate from Ruby to Alex here. And it's currently the VP of Engineering at Subspace. He also co-authored Adopting Alex here. So it's an amazing lineup. And they're all here to actually serve, you know, we are all here to actually serve you. And, you know, how can you get involved? The best way for you to get involved is, you know, through the workgroups. Go in, you know, join the Slack channels, lurk, join the calls which various workgroups have, and reach out to the workgroup chairs, you know, look at their issue trackers on GitHub. And I'm gonna go in into what a few of these workgroups have been working on just to give you a taste over, you know, over what has been achieved so far, which is, you know, pretty impressive, but also, you know, where your help is needed. First and foremost, you know, we've got the build and packaging group on, you know, the top left, you can see a build and packaging, you know, that's the Slack channel and the early F Slack channel. The aim of this workgroup is to go in and evolve, you know, the tools in the ecosystem related to building, documenting and deploying code with a strong focus on interoperability between the beam languages. So it's, let's not go in and reinvent the wheel across languages. Let's create a solid foundation which the ecosystem can use. And I think they, you know, the build and packaging group have been one of the most active ones, you know, they've done a lot of rebar mix repairs and updates. So, you know, there are discussions about supporting prebuilt artifacts in mix, rebar free already supports them. And you know, and it's also, you know, they've also had discussions on how to ease the life of all of the Gleam users, Gleam being another, you know, a strategy type beam language. There was the documentation workgroup which was merged into the build and packaging workgroup. They achieved, you know, X stocks, which they shipped and they created the documentation Erlang extension proposal, which, you know, got accepted and then now allows you to basically go in and they've created a standard for documentation in all of the languages within the ecosystem. There are, you know, currently kind of ongoing discussions about supporting offline bills and then during dependencies, rebar three, rebar free hex version seven was released with two factor authentication. Mini repos of rebar free caught up, you know, and that's, you know, looking at hex four right here. And there are also, you know, quite a few talks, you know, taking a long time but there's a lot of brainstorming innovation happening over finding ways to integrate rebar free into OTP. You know, hex folks are currently going and doing a round of license normalization in all of the packaging and all of the build tools. And, you know, where do they need help? You know, I think there's a lot happening right here. So if tooling and your building packages of interest to you go in and look at the, you know, issue tracker on GitHub, go in and start following the Slack channel. I think one of the most interesting projects they're currently working on is, you know, the infrastructure project is an infrastructure project which aims to create a new continuous integration system that is integrated with all of the OTP repos and they want to go in and create this continuous integration system which actually tests all of the bills and push requests and pull requests and, you know, with an intent to hand it over, you know, to the build and packaging group as we go along. So how do you get involved? You know, this applies to all of the work groups. So not just the package and build work group but you go in into the early F.org website and in there you see there's a work group link up there. You click on it. You go in and you see all of the work groups. You click on the work group which interests you and you get a description of the work group. You get the list of users who's sharing it but on the top right, it also tells you how to get in touch. Some workers have email addresses. Others, you can reach on the Slack channel and prefer Slack to email. Others, you know, have a GitHub repo with issue trackers where you can actually go in and see issues which have been raised, which is also a very clear indication how you can get involved and help. And last but not least, there's also a calendar. All of these work groups have regular calls if anyone is welcome to join these calls. And you can find about the joining details through the calendar and you can actually subscribe to the calendar and embed it in your own. So this is it for the building packaging. Another work group which has been very active is the observability work group. So, you know, hashtag observability on Slack and their goal is to evolve the tools in the ecosystem related to observability such as metrics, distributed tracing and logging with, you know, is made possible. And all of this with a strong focus on interoperability between beam languages. Solve the problem from one language, make sure they work on all the other beam languages. They've had a lot of achievements. They've previously gone in and integrated airline's logger. You know, they've structured the logging release in Alexia 1.11. They've worked on the telemetry library. And a lot of the work now is, you know, telemetry has been around for a while, but a lot of the work which is happening is, you know, working on patterns of best practices and implementing them across all of the libraries and applications within the ecosystem. Open telemetry. So, you know, looking at distributed tracing, they're keeping up with the specs right now, which are evolving. And the main project, you know, that they're currently focusing on right now is instrumentation of functions, you know, for open telemetry and somewhat confusingly named telemetry library. And they've reached version 1.0 alongside many other, you know, very well respected languages, mainstream languages. So, you know, this is a blog post, you know, that they posted, which you can just Google and, you know, go in and read more about. They are on the lookout for volunteers. So a call-out for the volunteers is needed around all of the open telemetry instrumentation libraries. There are a lot of projects, you know, still in need of instrumentation and also there's a need to provide an easy setup to distribute, you know, the tracing of airline and elixir in the whole ecosystem. So, you know, this is, you know, that is the place just to start for anyone looking to contribute. And you can actually go in into the kind of open telemetry Github repo and just search on open telemetry airline contrib and in there, you know, you'll find, you know, the issue tracker and another gateway apart from Slack channel, obviously it's also to look at the calendar and join the car calls. Education, training and adoption, yeah, I think they're probably one of the most active groups reaching out to, reaching out to, you know, to the wider community. And that's where I think, you know, we would need a lot of help in India to go in and help, you know, help with the meetup, help with trainings, you know, start providing, you know, lists of guest lectures and lecturers for local universities. And they're currently working on, you know, publishing, you know, training material in Spanish, but, you know, why not do it in Hindi? You know, what's stopping you? So what they've done in the past is they're the ones who've gone in and defined a stipend program which has now been adopted by the whole foundation. And they're also sponsoring, you know, diversity conference and tutorial tickets, you know, for minorities and underrepresented groups in tech. You know, they're focusing on a guest lecture program. So it's a program which helps connect universities and companies to spread the word of, you know, of Ireland and Alex here to students. And universities and companies can register, you know, for public lectures. And they're also able, university is able to then go in and search for other universities, but also, you know, members who are willing to give guest lectures and tutorials, you know, close to them. And right before the pandemic, they were working on meetup trainings, you know, defining a train-to-trainer program which would then be able to go out and start training others. So now that the pandemic is easing and we're coming back and meeting face-to-face, you know, I think, you know, this is something which again, they need a lot of volunteers for which, you know, they've dusted off. Now embedded systems workgroups. So you'll find it in the Slack channel under, you know, the hashtag embedded. Their goal is to evolve tools in the ecosystem related to observability. So, yeah. So the goal is, you know, to go in and evolve, sorry, the whole ecosystem, not for observability, but looking at embedded and bringing the bean languages to the embedded space. I think there's been that Ireland was invented as a language to run embedded telecom applications. And now, you know, with hardware getting more powerful, yeah, I think more and more compute is moving into embedded devices. And I'll be speaking a little bit more about in a second. But, you know, what are the biggest achievements? You know, the JIT assembly compiler for ARM64 and ARM32. So this was, you know, Ericsson have worked on the JIT compiler, but they're not supporting all of the architectures. The foundation, you know, funded stipends to bring the JIT compiler, you know, to ARM64 and ARM32 architectures, which Ericsson have now integrated into the main release. There's a lot of collaborations around nerves, grips and meta airline. And last, but not least, the ROSI project, which is an implementation of the robot operating system in pure airline. And Latalia will be speaking right after me about the ROSI project. It was funded by the foundation and is a corporation across companies and academia. You know, as part of the better work, they've also started an engagement with academics. So they have a lot of developers who have ideas, but they have no time to really think in through and code them. So what they do is they post these ideas to academics so that if academics have interests and you know, students or postdocs, they can develop them with support from the airline ecosystem foundation. And that's how the ROSI project started off. It's a, you know, cooperation with the University of Milan. So, you know, and Latalia will tell us more about it right after. Now, even more exciting, you know, well, not even more excited, but as exciting and very tightly connected to embedded is the machine learning work group. So the machine learning work group founded by Jose. And the goal is to develop the ecosystem on all aspects in the context of machine learning from native compilation to high level abstractions and auxiliary programs. So it's a very wide scope. And it's a new area which has been explored for LXR and ultimately the beam. So in the first instance, the machine learning work group has gone in and actually gathered experts in machine learning in AI space who are not necessarily beam experts. I'm sure you've heard of NX. So, you know, what they've done is, you know, they've gone in and created a subset of NXR which runs in the GPU. And this foundation has become the foundation for neural networks and other machine learning algorithms. They started with an NX, EXLA, which is an XLA compiler for NX and Torchex, which is LibTorch backend for NX. Now, to foster adoption and expand the community and bring in collaborative interactive notebooks to LXR and hoping that providing a high level tool, you know, to work in LXR will help expand the community and bring machine learning and possessed to the ecosystem. So keep in mind, it's not always about having the best library. You need to get people to use them. And I think, yeah, Jose excels at this. On top of that, they also have Explorer, which is an abstraction database, which allows you to abstract data sets to NXR. And Explorer is there for your people working with very large data sets, distribution and concurrent processes. So, you know, I think it all goes hand in hand. Now, together with Axon, which is, you know, the machine learning framework, Ashwin Variety is working on, there's a very, very long road back. And what you need to do is join the Slack channel and you look at the issue tracker, yeah, and join the work groups and start contributing. But, you know, if you're a bit intimidated about starting to contribute, just as important, go in, start using the libraries and start giving the work group feedback on your use and your experiences of them. Is that, it's what's going to allow you to go in and it's what's going to allow you to go in and help foster the adoption. Now, I spoke about embedded, I spoke about machine learning. What makes me excited about both? Well, the two go hand in hand, believe it or not. Because, you know, this is a quote from Gartner where from 2017, so from five years ago. And it says that around 10% of enterprise generated, of enterprise generated data is created and processed outside of a traditional data central cloud. So this was five years ago. They predicted by 2025, this figure will reach 75%. And this is what excited me about what's going on with Ericsson combined with work around machine learning and embedded. Traditionally, we always moved the data to the compute. You know, we weren't amassing large amounts of data, you know, but that is changing year and year. Every year we collect more data than all of the previous years put together. So it's increasing exponentially and it's becoming really expensive to move this data around. So instead of moving the data to the compute as we used to do in 2017, we're moving the compute to the data. So close to the source. And, you know, this is where Edge networks and IoT devices, you know, to the Edge networks and IoT devices themselves. So instead of transmitting data, we will be making decisions locally and just transmitting the results of the compute. And so, you know, put together the amazing work of Lucas Large and the OTP team, you know, we've got the JIT compiler, you know, pair it up with Shomo Arte and Jose Baleen's effort of bringing machine learning to the beam and, you know, Frank Hundler's efforts on NURBS alongside much more powerful processes than embedded devices. I think we'll soon have a platform for machine learning and AI which we can use on all of the devices, you know, all running on the beam. So this is really what, you know, makes me really excited about what's going on and probably why you should be getting involved and start listening and looking up over what's happening. And obviously, as soon as you deal with data, as soon as you deal with IoT and embedded devices, security becomes critical, in a wide variety of areas spaces, but right here. And there's a security working group on Slack here, it's the hashtag security, it's the Slack channel. And the most visible achievement has been secure coding and development guidelines. You know, they've also worked with OpenID Connect, online certificates, the online certificate revocation protocol and are planning a security testing guide. You know, if anyone is interested in any of these, or if you're just interested in the topic around security and the beam, you'll join the security channel and participate in their calls. So their next call is at April 6th at 3 p.m. GMT, which I believe is at around 8.30 p.m. India time, you're depending on what time zone you're in. So go in, join them, meet them, get to know them and again, start contributing. And then finally, last but not least, the unsung heroes, you know, and you can become an unsung hero yourself, join the infrastructure working group. They are the foundation of the foundation and the mission is to provide tools and services that enable members to communicate efficiently, share ideas and updates. So if you're into DevOps, if you wanna help improve the website, it's all open source in Alex here on GitHub, join the Slack channel. We're also looking for volunteers to reach out to me for that, to help build a jobs board where we plan on putting together companies and people looking for work. Now, just wrapping up, all of this wouldn't be possible without the generous contribution of all of our sponsors. To become a sponsor, these companies have donated between $2,000 and $10,000 per year and just a shout out to the latest editions, Feedbaps and EM2X who joined this month. And I would really rally you to go in and tell your employees to become sponsors in the Erling Ecosystem Foundation. It's for them, it's not that much money, but it allows us to actually go in and fund a lot of these projects. Well, you'll argue with your employees, why would your companies join? Well, a variety of reasons, but you know, there's exposure to their services, recruitment, if they're recruiting, it helps increase their visibility. I mean, we show all of the logos in all of our presentations. And in some cases, just to say thank you, Ericsson, thank you, Jose, and thank you, Community of Large, you know, and this is a wonderful quote from Valentin Michek. He is the founder of Ferris of AntGuard, he's a company in South Africa. And Erling and the Beam have basically allowed him to have a huge impact on the whole telecom infrastructure in Africa. And he felt that the foundation was helping build the foundation which would allow others like him to create a similar impact in the respective countries. So he's gone in and he's actually donated and become a member. And you can ask him just to email sponsorship at theearlyf.org. The goal is to achieve $200,000 in sponsorship donations per year. And yeah, depending on the turnover, of your employers, there are various costs associated to it. But yeah, you can also give very small donations, but obviously larger donations are needed and welcome. So just in conclusion, as I'm running out of time, how can you get involved? Lerking the Slack channel is very welcome. Go in, join a work group channel, ask questions, or just read their issue tracker, attend their meetings and listen in and get an idea of what's going on before you even make a commitment. If you've got new ideas, you're welcome to go in and propose a new work group. Processes on how to propose work groups are on the website. stipends, you can request a stipend to get some work paid for if you've got a particular project. And it then gets assigned to a work group and you get someone who will ship review it through it. You can become a member. So please go in, earlyf.org and register today. And more importantly than not, just as important as your company is to become a sponsor and help fund what we're doing. This is where you can follow us on social media and Twitter. So join the foundation and start becoming loud and participate in the community. So big thank you for me. Great, thanks, Francisco. I think there's a lot of useful information that you packed into this 30 minute presentation. I think we've got some of this information tweeted out as well as you were presenting, hopefully other folks who not joining in would still be able to benefit. So just wanted to thank Francisco again for the great talk.