Hi everyone, my name is Brian Barrett and I'm a Software Engineering Manager at Facebook. I support the team at Facebook Connectivity that contributes to the MAGMA project in the MAGMA Core Foundation. So we've just heard an excellent overview from Ammar who talked about MAGMA, why it's different, how it's architected, what it's used for, and how it's designed to dramatically reduce the total cost of ownership of networks. We at Facebook Connectivity see this important bringing more people online and also to enabling the open source telco movement and catalyzing open source 5G. MAGMA is a hyperscalable and distributed core. One of the things that's different about MAGMA is designed to run at the far edge on far edge appliances to support local breakout to IP all the way at the cell site. It's open source and license free. It's cloud native containerized and features control plane, user plane separation. It's modern, vendor and transport agnostic and supports integration with existing mobile network operator cores using the optional Federation Gateway shown on the diagram as Ammar explained. And it supports all access conversions. So it's designed for LTE, for Wi-Fi, for private LTE use cases with CVRS spectrum, and also 5G use cases. But I'd like to talk a bit first about MAGMA's history, how it started, where it's gone and how it's really accelerating lately as it's really found accelerated growth in the community. So if you look two years ago when MAGMA first showed up on GitHub, it was being built by a small group of software engineers at Facebook. Around 20 or 30 people built MAGMA. The team grew until in July of 2020, MAGMA was announced as an open source project with release 1.0 backed and supported by the Open Infrastructure Foundation, the Telecom Infra project as one of possibly several open core networks, and the open air interface software alliance. And since July 2020, the community has grown rapidly. So across these three sets here of advocates, contributors and participants, these are the sets of people that participate in writing code for MAGMA as advocates, people that participate in code reviews and technical discussions as contributors, and people who engage in the community on Slack and Q&A and participate in GitHub discussions. And it's really grown dramatically. And in February 2021, we announced our next move for the community, which is to become a neutral foundation called the MAGMA Core Foundation hosted under the Linux Foundation with neutral governance. And that occurred in February 2021, which we announced at our MAGMA developers conference. We've noticed even more rapid growth since then. So as of April 2021, we had over 400 people actively engaging and contributing in the design and engineering of MAGMA. The community is actually even larger than that. If you look at the last tier in the orbit model of people who are observers of the project that are starring our repo or pulling a branch on GitHub, it's actually even larger. So we clock in over 1500 members of the community at this point that are either members of our Slack community or are starring our repo and are pulling a branch on Git. So when the MAGMA Core Foundation was founded in 2021, we're really trying to position MAGMA as the de facto open source network core. And we think we're there with the launch of the MAGMA Core Foundation. So you'll find familiar governance from the Linux Foundation with the technical steering committee and a governing board. The technical steering committee is elected, group of contributors, and the governing board is comprised of members that join to help steer the project's strategy. So we retain our affiliation with the telecom in for project as one of possibly several open core networks. Facebook community still provides a backstop of software engineering contribution to the community. We also provide a backstop of technical support to systems integrators and value-added resellers that want to deploy MAGMA who can be assured that they can receive Level 4 support from the Facebook software engineering team for any operational issues that could emerge. We have ecosystem partners at the Open Infrastructure Foundation and the Open Air Interface Software Alliance and a number of both large existing well-known companies and new startups that are participating in the MAGMA Core Foundation. So it's our belief that MAGMA will be the one open core implementation that's open source, that's converged, and that supports multiple types of access technologies and is access-agnostic, that's cloud-native across both the central cloud and the edge cloud and is multi-tenant, allowing a single instance to manage potentially multiple networks at a time. So here's how we're building the ecosystem. If you look across, we have industry groups that we partner with to help scale our developer community and help drive adoption amongst developers and operators. Developers and operators help define current use cases but also motivate future use cases and we partner with research projects as MAGMA with the academic community to help investigate some of those super future use cases. So examples are there are features that are showing up in 5G releases 16 and 17 like integrated access and backhaul networks like non-terrestrial connectivity and 5G release 17. Also work in ONF and open-air interface software alliance and ORAN alliance on software-defined radio access network and radio intelligence controller work because we've seen people building on top of MAGMA to integrate through with non-real-time radio intelligence controllers. The academic community really helps spur innovation that we see flowing into startups that want to use MAGMA to build novel solutions that they build on top of and then startups help drive adoption in industry groups. So startups often will partner and use MAGMA technology to build end-to-end solutions, new innovative solutions and take things to market as value-added resellers of the stack. We really like to invite anyone listening to consider joining and building your connectivity software as a surface or enterprise solution or end consumer solution on top of MAGMA to build your business faster and ride the 5G wave with us. So here's what's in it for you. If you're looking at yourself as a possible distro vendor of MAGMA, you're going to build your own distro around it and take it to market. So your development teams can focus on development and integration as a key part of your strategy. You can use MAGMA's production grade commercial ready building blocks to build your end-to-end solutions and lean on the MAGMA community to help kind of jumpstart your project.  If you have an expert community you can lean on and you can explore adjacent opportunities in emerging use cases around the core problem you're trying to solve. So really it's just going to help you accelerate as a project. So you can see here some of the quotes from Boris the founder and CEO of FreedomFi and also Patrick the founder and CEO of Connect 5G who know how MAGMA helped them in their project go to market faster, deploy faster, and really act as an engine powering wireless innovation. So I know that MAGMA is partnering with academic and public domain projects. So if you think about some bleeding edge research projects that are trying to do experimentation on some of the latest things in 3GPP or other projects, it's not very practical to start from scratch recreating parts of a 4G or 5G stack only to add your new use case or differentiation or research project on top of it. And it's difficult to do that with any existing commercial solutions because you don't have access to the source code. So what we're witnessing is that a lot of the bleeding edge features are showing up first in open source. So an example there is non-terrestrial connectivity with the Satisfy project or the ESA-ALIX project by the European Space Agency to adapt cellular protocols and waveforms to be used for non-terrestrial high altitude platforms and satellite connectivity projects. We already see contributions from those projects with significant amounts of public sector funding showing up an open air interface and open core projects. Another example is public sector opportunities with DARPA and the U.S. Department of Defense. There's a lot of interest in that community on shifting security left and having more secure open source solutions deployed because you have actually access to all of the lines of code. And when there is a security vulnerability, you can very quickly patch it rapidly and spin a new build. And so that helps mitigate supply chain threats that can be of concern using vendor equipment. And so there's projects going on with DARPA and the open programmable and secure 5G opportunity where they're looking at the advantageous nature of magma and other open-ran projects for their ability to support that shift left security model and quickly have a more secure solution that has quicker turnaround time under vulnerabilities. So we support several universities as well shown here who are using magma and are contributing back to the community. So just to highlight a couple really interesting building blocks and solutions that we see happening in the community that were featured in our magma developers conference that I thought were particularly exciting. So we featured in February of this year that we now have support for Amazon's far-edge appliances to deploy the magma access gateway component. So now if you're deploying magma on AWS, you can take advantage of work that we've done together with Amazon to let you in a single click provision your magma orchestrator in the cloud, but then deploy your magma access gateway component with no upfront cost on one of Amazon's far-edge appliances that have electronic ink shipping labels right on them. You just tell Amazon where you want them shipped and one of these boxes ships out pre-provisioned with the AMI for the magma access gateway and set up for zero touch provisioning where it'll connect back to your AWS hosted orchestrator in an AWS region or on primal and outpost and set up your network for you and you're ready to go. You just connect your 4G or 5G radio to it, which I think is pretty exciting. So these are ruggedized boxes that are low-cost, you pay Amazon a monthly subscription fee to use them and Amazon replaces them if they ever go bad. Another really exciting solution that we've seen built on top of magma is from the Helium project. So Helium is a cryptocurrency that instead of burning electricity to mine their coins, you actually mine coins by connecting the unconnected and until now the Helium network's mostly been a LoraWan network for IoT where you deploy Helium hotspots to extend a community LoraWan network that anyone can use for their IoT applications. But FreedomFi together with Helium just announced at our developers conference a new solution where using CBRS spectrum, you can deploy 4G and 5G hotspots to connect the unconnected in a people's network using Citizen Broadband spectrum that's unlicensed and free for anyone to use for 4G and 5G and use that to mine coins, which is really exciting use case that I think is really going to we're going to see a lot of fast growth and adoption from. So thanks for listening. I think now it's best to turn this over to Arpit who is going to take you through some end-to-end solutions built on magma and their use cases. Thank you, Brian. That was a great overview and a great set of use cases that kind of covered the magma ecosystem from a big picture perspective. I'm excited to be here on the magma day and what I'm going to do is basically give you a quick overview on how magma fits into the end-to-end solutions across multiple open source projects and how end-to-end use cases are being developed by the community at the Linux Foundation. Joining me is Tina Sue from ARM who is the TSC chair for Acreno, a critical project under LFNCH. So before I get into the details of the roadmap as well as the end-to-end solutions and Tina will walk through the one specific example of how Acreno and magma are integrated into what's called a blueprint. Let's take a step back and look at the big picture of how vertical market adoption is happening of an end-to-end open source software. So you can see that there are lots of open source projects. Some of these are very critical, very important. It's not a comprehensive list by any means. But as these projects come together, whether through APIs, through integrations, through onboarding, lifecycle management, through use cases, through demos, you know, many different ways. One of the fundamental things that we have been doing here at the Linux Foundation is trying to get them to evolve these markets. So in the middle, you kind of see a big segmentation. You know, there's the enterprise networking users and then there's the service providers. Service providers obviously include cloud service providers, telecom carriers, etc. And then in the enterprise, you have the different verticals that each have a different need from an IoT and an edge perspective that will use magma as well as other projects slightly differently. So if you look at the specific use cases that are very important in 2021 and maybe a couple of years since then, specifically for enterprise networking, you can see we have private LTE, how workloads run across clouds, how do you get network visibility for an enterprise in these multi-cloud deployments. But then when it comes to service providers, the telecom and cloud service providers are collaborating significantly under the Linux Foundation Networking, under the Linux Foundation Edge, under CNCF, to bring, you know, an end-to-end 5G-based deployment, to train people on 5G, to develop global connectivity. Huge initiatives going on. And then as you get into some of the very important users that are taking advantage of this open-source stack, you know, government across the globe is at the forefront of building on these end-to-end open-source projects. One specific project I want to, or initiative I want to point out is the 5G Blueprints or Super Blueprints as we call it, under the Linux Foundation Networking. So this is what's happening. And when you take a project-centric view, you can see that from an end-to-end perspective, you know, I've presented this at multiple conferences, but it keeps getting better and better and as more innovation comes in. From the left, the various means of access, mobile networks, residential, small, medium, or enterprise, whether they have their own data centers or not. You come in through ORAM, a project under the LFH called Home Edge, Fledge, Eve, all these projects, I'll tell you the use cases on that, brought into an Edge integration project called Acreno and then move into the core part of the stack through a public crowd or through a telecom service provider, moving into the data plane acceleration and the infrastructure part, whether it's FDIO, Kubernetes, DPDK, etc., moving up into sort of the VIMS, which is OpenStack, Control Plane, Network Automation, Project Fallon App, all the way up into the core or network application functions, right? Now these could be VNF, CNFs, and one of the first ones that now we're showing you and talking about today is Magma, which is one of the first open mobile packet core, which is kind of an application sitting on the telco side that can be pulled into the end-to-end stack. So a very important set of projects that can be brought together and then when you can do open compliance and interoperability in an open environment under a neutral governance, that project like an Anuket is getting extreme traction. This will just speed up the deployment. So let's talk through how these projects come together from an open source perspective. As we all know, projects are hosted under neutral governance with the developer community, TSC code gets produced, documentation gets produced, a set of use cases, whatever, right? I mean, it's a set of technology that gets produced, created across the world, brought together by either products and integrators. So these could be vendors, system integrators bringing it all and then put into production where people can make money and then invest back in the community. So that's kind of the circle of project life, if you may. And one of the things that we have seen in the last three years is the need for accelerating what is the lower part of the cycle, products to production. And for that, a couple of things need to happen. The interrupt, the compliance, the verification, the testing, the certification, etc. etc. needs to happen in the open world. It's not open source software, but it is open source governance. And two initiatives that I want to point out, one is Elef Networkings. Anuket, Anuket is a project that kind of combined two existing projects, OPNFV and CNTT, I mean, I'm throwing a lot of acronyms here, but essentially they are responsible for defining architectures, reference architectures, whether it's open stack based or Kubernetes based, into a reference implementation that a solution can get tested against, whether it's an FBI, MANO or VNFs, and get certification and matching for that. So very, very interesting activities there. And then Elef Edge is a set of blueprints that bring hardware and software as an implementation of a particular use case to the community so that it can be reproduced and deployed very quickly. And we'll talk about some of these in a little bit more detail. So if I look at the specific use cases that have come around, let's talk about the projects that are highlighted here. So the first one is Oran. As you know, it's one of the largest communities and the largest alliances to disaggregate and open up the RAN, which is one of the last pieces of the puzzle in the Telco network. Linux Foundation hosts the software community for Oran, which is called Oran SC. And the use cases that are being produced, created, discussed there are RG, end to end slicing, quality of experience, optimization, how do different white boxes come in, etc. Then you move on to Kubernetes open stack, sort of the cloud layer or the virtualization layer, if you may, infrastructure layer. And then you get into Anuket, which I talked about, open compliance verification, standardization, onboarding, reference implementation. On App, I won't talk about the control plane projects. They have been proven and deployed for quite some time now. But then when you get into On App, you get into 5G network slicing, cross cloud VPN, zero touch, closed loop, control loop, lots of these real use cases that are needed for network automation. And then on top, obviously, the Magma, which is a critical piece of the open source core wireless network. So these use cases are being done in each of these projects. And our goal is to bring it all together. You move out into the edge of the network. You have a set of projects that are now trying to unify the edge across the cloud deployments, across IoT, across the enterprise and across Telco. So think of these four markets trying to solve the same problem of plumbing, lifecycle management, onboarding, et cetera, for the edge computing world. And I'll talk about the definition in just a bit. But some of the examples include virtualization on on-prem devices, anomaly detection. You have projects like Fledge that are doing extremely constrained, sensitive, IOT type predictive maintenance and base monitoring, right, turbines, transformers, pumps, et cetera. Or you have EdgeX Foundry, which is one of the large projects under LF Edge that would do IoT frameworks, again, all in the open source for building automation, industrial process control, smart city. And then of course, you have on the edge a Crano, where you're going to build blueprints for testing out these various use cases and deploying it very, very quickly. So you can see that all these use cases from core to Edge to access from telecom to enterprise, they're all solving use cases and similar issues that are important to an end user. So let's take a moment and define the edge. And this is important because you will see very quickly that when Tina comes and talks about an ICN blueprint under a Crano, it uses terminology that fits together beyond what magma defines in the core. So this diagram is one of the most screen-shotted diagram in this new world of the pandemic. I wouldn't say the most widely used, but the most screen-shotted diagram that we have seen on all these virtual presentations. And what it is is under an umbrella called LF Edge, we have taken, the community has taken the liberty to define the definitions in terms of an edge. And this is what the diagram shows. So if you look at the bottom, there's really two types of edges. And before I get into that, think of the terms that you have used in Edge, thin edge, thick edge, far edge, near edge. All these are relative terms and they don't mean the same thing to everybody. So what the community did was they standardized on definition. So we would really appreciate as magma community, as well as CNCF community, starts looking at edge computing to use and utilize these terms because that's what the edge community has done. So there's two types of edges. There's a user edge and then there's service provider edge. User edge is dedicated and operated by the user. Service provider edge is shared and as a service. Now, the last mile separates these typically, but it's not a hard cut. If you go in the user edge, it's not one implementation. And that's part of the challenge we have in the community. But we have been able to standardize across three specific implementation. There is on the extreme left an edge that really has extreme constraints, right? Physical constraints, resourcing constraints, memory, compute, etc. Hardening constraints. And that's called constraint device edge. These could be microcontroller based, this could be embedded compute, etc. Then you get into some more semi secure locations where you may have an IoT gateway sitting around still in the control of an enterprise user or an IoT user. And there you may have something called a smart device. And then if you are a large enterprise or if you have enough of these factories, buildings, homes, etc. where you have service in a semi secure location, then you have something called on-prem data center edge. These are all, again, in the control of a user, as I said. And then if you move on across the last mile, you get into a couple of edges that are very important. One is the access network, which is really the RAM. So if you're putting edge compute below the RAM, and if you're putting it in a smart central office, about say one to six servers, you can get the about 20 milliseconds of latency across the application. And that's very critical, because 5G really narrows down on the transmission latency, as we all know. So once you have that, you can now have edge computing all the way to the smart central office. Anything after that, the latency may be tricky. So I always say an IoT application that dumps sensor data once a week is not an edge application. It may be an IoT application, but it's not an edge application. So with that said, the projects shown here, and I won't go into that because some of them are relevant to Magma's community, some of them are not, some of them are relevant to the CNCF community. But the more important thing here is there is a different types of constraint edges, everything from infrastructure to application. Edgex Foundry and Acreno being the the two largest projects, most mature, if you may, stage three. And we've seen several other projects moving up the pipeline as well. If you want to download the whole LF edge report, we just published it under LF edge state of the edge. And it's huge, the market's huge. And we want to take advantage of that whole edge computing, using CNCF projects, using LF and LF edge, and more importantly, integrating with Magma. So I really wanted to take this couple of minutes to get into explanation of the edge terminology. So with that said, how do we pull this all together? We pull this all together in an end-to-end solution and a project called, or I would say an initiative called end-to-end 5G Super Blueprint. It's hosted by the Linux Foundation Networking, so you can go to www.linuxfoundationnetwork.org slash 5G Super Blueprint. It is a task force. It's a project that is extending an existing governance under the LFN demo that we did, but it's more than the demo. It's now bringing components together from an end-to-end perspective that crosses LF networking, LF edge, Magma, CNCF, Oran, and a lot more. These are just some examples. And what we're doing is we are building this blueprint in real time. So we really encourage everybody to participate in this, join as members if you want to influence this even more under LF networking, but it is an open initiative to everybody. So let me walk you through how Magma is getting integrated into these components. So here's the overall roadmap that the community has created. Lots of details are being worked in real time because these projects themselves have a roadmap. So bringing all these projects back together is obviously going to be a challenge. And the reason we want to show it in an open community is so that it can be done under a neutral governance. And then we'll have vendors, system integrators, end users doing distros, doing multiple things with it. Linux Foundation is not in the business of that. But what we want to do is show a blueprint that can easily pull projects together upstream and downstream solve specific use cases. So here's how these things look. The team is working on this quarter. It's working on getting the 5G core and some version of Mac integrated with a whole set of components that can bring an open source core stack and edge stack together. Obviously 5G fixed wireless access, private 5G, multi-access edge computing, IoT, etc. are primarily the use cases. As we move forward, we get into the end-to-end slicing, which brings not just the core, but it also brings a set of commercial rands and from an open source perspective, end-to-end slicing in play. And then finally, through the Q4 timeframe, this brings not just the end-to-end network for RAM, but it also opens up the RAM with ORAM SC software. And it's a fully disaggregated open source-based 5G stack. So with obviously all the use cases that are required by the end user. So let me walk you through the three steps. The first phase is the following. We're going to use emulators for the RAM. Easy to do. I mean, easy to say hard to do, but those are sitting right there on the left.  What is shown here on the Acreno side is ICN and I'll have Tina talk about this in a lot more detail on how to do it. So I won't go into this, but that's kind of the application control and application layer. And then on the bottom, you see the NFVI in the telco terms, right? Network function, virtualization infrastructure layer, which uses a whole bunch of what is called open source projects from data plane acceleration to control plane to storage, et cetera. So that's kind of the phase one. Phase two is relatively straightforward. But what you're doing is kind of adding two main things here. One is you're adding the support for commercial RAMs. And then the other thing you're doing is adding end to end network slicing, which kind of comes from the Magma roadmap. ONAP already has support for the network slicing. Magma is working on it. And I think it comes together very nicely. And then finally, in phase three, you include the ORAN community. So today, the OVA-NAVAN interfaces from ORAN to ONAP already tested and released. There are other interfaces that need to be worked out both for non-real-time RIC as well as real-time RIC, but more importantly, bringing it in such a way that it is a seamless end-to-end use case across these projects. So very ambitious to participate. It's part of LF Networking's initiative. And there's a large community that is working on it. If you need to look at anything particular or cannot find anything, you know, obviously reach out to me. But that's kind of the ambition we have on doing this end-to-end Blueprints. So with that, I'm going to hand it over to Tina to walk you through some of the specifics of one example of a Crano and Magma coming together under a blueprint called ICN.  So she's going to walk you through that. And again, if there's any questions, we'll come back and kind of do this. So again, I'm going to pass it over to Tina and, you know, she'll do a deep dive on this. Thank you. Thank you, Apit. This is how a Crano R4 Blueprints available now. We announced it in February 24. So from here, you can see the R4 Blueprints, which are new, are indicated in blue. So you can see the industry IoT predictive maintenance blueprint sits on the smart device edge. And it has been integrated in Fletch. So it supports for the industry IoT case, like when the temperature is up, it will give an indication and alarm to the back end, like a GCP. And then you want the AI Edge autonomous vehicle, the iVix, which support integrate the Auto.Ware, AutoWare the Auto, sorry, AutoWare the Auto. And the federated learning, which has been deployed in the financial technologies, has been widely deployed by WeBank. The other one, the ICM Private 5G LTE. I'm going to talk about this a lot in the later slides. The Covey Edge support AI and the ETC and the highway, the electronic collected control. It has been deployed in the cloud and in the edge. The public cloud edge interface here sitting above the public cloud core part and public cloud edge part, which has provided APIs, orchestrations for the tailcoats and hyperscalers to work together via PCS layer. And the other one, we have the KNI Industry Edge, which is new, to support operator in France about their deployment for the industry IoT and also the manufacturing. And the green one, the existing R1, R2, R3 enhance the blueprint. We are still developing and making them more mature and adding more use cases and hardening the code. This is Private LTE 5G ICN. The purpose is to create an EPC 5G in a box to enable enterprises and operates to deploy LTE 5G. We use OSS like Free 5GC and Magma. Magma has been used here and also Free 5GC. You can see the infrastructure orchestration includes Ironic, Mitre 3, and cluster API sync could be. This is quite wide. And also the ONAP has been used as orchestration layer. We covered the network segments all the way from UCPE using Kubernetes on the network edge number one and cross the network core, which runs the Kubernetes SDE1 with EPC 5GC there. And same as the Edge number one. And the other side of the network is the network edge number two. In this case, we can support the many industry, the manufacturing, retail, farming, and mining. So I would like to talk about this Private LTE 5G ICN blueprint. This is our MVP plan. You can see from here. The ONAP openness is orchestration layer and Kubernetes is orchestration for the containers. We have the Kubernetes plus openness with the code in for orchestration. And the Magma sits on top of it. For example, we opened the CNF number one to have a look. So we have the Magma orchestrator on the top and sitting on top of the AGW for 5G. The SMF and AMF and UPF is at the control layer and data plan layer. So it connects with the other CNF number two with the M1 interface to the 5G UE emulator and through the N2 interface to Gnode B emulator. So the N3 is between the Gnode B emulator to the UPF directly. And the UPF interconnected with the data network. So this is runs the VNF number one. And Magma sits for the CNF number one. So the workflow is like this. Number one, we first installed the KubeF number one and two. And then we installed ONAP and ENCO as the orchestrator. After that, we registered the Kube ref number two. Kube ref two with the ONAP and ENCO. And we onboard the CNF one and two. You can see from here. And also VNF number one. In this case, we can create a network service with CNF or VNFs. And we can deploy the network services like what you can think about for the 5G, private LTE, I can find the manufacturing, etc. And then we registered the AWG with the Magma orchestrator. This is important to interact with Magma. And finally manually configured AWG and run the UE Gnode B test. This is the minimum workflow, the minimum data flow for our private LTE 5G integrated Magma. Here we can see the Magma integration plan details. The Magma AWG 5G early implementation available as a VM, like here is a VNF. Also the Magma orchestrator early implementation available as a container, we call it CNF of course. And the private LTE 5G ICM team, which is our blueprint team, part of ICM blueprint family, will orchestrate this too using ONAP. The UEN and Gnode B emulator will also be orchestrated as a CNF. Let's see the previous page as a CNF number two. If available in a containerized form. So this is our detailed plan. So LF Edge and Equinox community are very excited to have Magma to join the LF and collaborate on innovative blueprints to provide this end-to-end solutions. Thank you again for the opportunity to discuss this here at the Magma Day. Thank you. Have a good one.


Okay. Good evening all. So, I think this is the last presentation of authority. Do we have any? I do not. So, this presentation, we are covering by three people. So, I am talking about quickly about globalization. Then Alex will talk about the Zanata. And then John will talk about globalization. This one session, which I am planning from now, at least from 6 months I am planning for this session. And I think this is the opportunity. So, I will generally say that what is happening in this session. So, this is the slide which I always like to say that when it is a globalization, these things come to that. So, it is, I didn't, there is a localization, there is a Zanata, and an FATG. So, FATG stands for Lions Testing Group. So, that group does the testing, the testing, the testing, that kind of stuff. Then, moving to the next slide. So, here I want to say that if you see this image of the federal, you see, all are closely tied. So, unless actually you don't have freedom, you will not have a friendship. You have friends, then you can get together, develop some features. When you start in features, you can have it first. So, it is like, I want to say here is, it is all closely tied together. If one is missing, it will affect other. On the same line, we started globalization, I think last April 2015, we started this activity. The group is the umbrella group. And why we started it? So, every group has some advantages and minuses. And what we thought that by having this umbrella group, we will try to solve those things. So, if you see, AT&T was good at proposing the changes for each release, having the development for the federal development cycle, that was good happening. From AT&T perspective, localization teams. So, localization teams has more contributors and more languages. There are many active people. So, if you see AT&T, it is like 10 people are active. From the localization, it is like 50 plus people active in each release. From testing part of it. Now, I didn't actually do something. So, testing group has testing expertise that created test cases. And again, transition platform. Transition platform here is Zanata. So, they are serving localization with more stats. So, if you remind the mad term sessions regarding the stats. So, Zanata is the place where we get all the statistics that what is happening. Which language is doing how. So, we try to create umbrella group on the top of this and try to make it as a more strategic group from the language perspective. So, if you want to do anything in federal from the language side, what should we do? If you are planning something, then each group should do. Every group is required what thing and how we can create those things. So, that was the plan behind the globalization. And we did good, I will say. So, these are the snaps. I think there are many, but I just quickly found these four. So, this is the one localization screen in Albania as possible. Second, we had a quick winter interview in 2016. Then, that is the third. Third image is from the fact that we had a jama. And the fourth that many small photos is the spring which we did recently. So, things we did under the globalization is that of course the fact was very successful. I will say it was. In limited amount of like couple of days, we did so many things. We worked, we talked, we planned, we had fun. So, we did so many things and it actually went like a mini-conference. You know, because there were so many people in there. And that planning we used till after the desert. So, if we want to do anything, I quickly say yes. Let's go through that list and see what is missing. So, I was planning to finish my talk at this moment, but I think since we are late. So, we did a test days. We got more contributors for test days because we became a single group with more contributors. We had a regular meeting, more active discussions on the mailing list. More exhibition for the team. I think this thing happened definitely. So, if anyone say that, what happens? I will say recognition. When we started globalization, everyone in the Fedora came to us. Globalization is the globalization. I think, of course, we all, I should thank everyone for this because of the real good work. And that is the thing. Then I will move to the next. Now, here I want to explain you the weak link concept. Do you know well about the, this is more from the system thinking. So, your system strength is not more than the strength of your weak link. That is what. So, like say if you have say, in your team, you have said 10 people and one is like, no, rather than the people perspective, the manufacturing process is a good example. So, if you have manufacturing processes and one process is not doing output or machine is not doing good. It will affect the whole thing. Same way, we have faced some problem in globalization. And the problem I will specifically, which I observe is that the localization team, though the group is very big, but there was not an activity in the localization group. That is the first problem which I have faced. So, whenever we were used to have a globalization meeting, we were mostly Pokemon of localization issues. That is what I observe. And most of the time, the globalization meeting was actually localization meeting. Spring, we started, it went well. So, we did a three-spring for the transition. But right now, if you take an example, like the most of the organizers. So, I was the one, Yonah, Alex helped, John of this help and the many people helped. So, right now, they are going to make tasks. So, gradually, we need more leaders for this and it is not happening. And it is like once we have one lead, other people start to come to support them. So, we need this one lead. Again, the second point is to come to the first one. If we have a lead, we can take care of this kind of thing. Unless, actually, we do not give strength to a candidate, it will not make Jiren possible. So, this is the point which I want to make here. That we need some more strength in localization. Once we have a healthy localization group, it will actually help us to achieve the objective which we tried for localization. And this is the point which I wanted to make today. And we can definitely have more discussion about this. So, any question at this moment? Or maybe we can take question at the end of session. So, John of this is going to talk about the localization. So, I think we will end with something. We will have further discussions. So, I think we will stop here and then we will have more discussion. Okay, so, over to Alice. Thank you. So, for Zanada itself, we mainly concentrating on the automations. Get from the database recently for the past six months. So, one of the main problems that we identified in the Zanada platform and the source repository was about the manual process that's involved in the whole workflow. So, in the current process, that's not a manual. What needs to be done by pushing up the source to Zanada and followed by notification to the translators. Get them to translate it in Zanada. Then package it into full translation from Zanada and push it back into the repository. Then it will continue from there. And those kind of processes usually based around batch of self-scripts or any script on prawn jobs and using Zanada CLI because that's the client that we have. Another problem would be the installation of Zanada CLI because on the Fedora community the item client is preferred over the rest of the client whereas Zanada CLI was developed on Java languages. Although we've got a good wrapper around it so that it can be installed in Fedora, it's still a problem. And usually when it happens, package maintainer usually does the push and pull only a couple of months at a time and by the time next time you want to do it they need to update the client itself and they just forget every command in there already so by then, so that's the main problem. And another downside would be there will be requirements of basic model and knowledge in order to use another CLI manual. What the deep was, initially we know the problems. Then we were trying to develop an application to do the automation. The first time we tried was to develop everything from scratch so we developed new applications, web applications that handles all these things but as soon as we wrote out the first version we found out that there's a lot of problems that's already been solved in a couple of the CLIs applications available in the market. That's why we moved to Jenkins because Jenkins is obviously a widely used and recognized CLI in the DevOps space and it has already a couple of plugins that we are trying to solve so it's already integrated well with it repository it's integrated well with what it has a strong feature of the scheduler it has notification plugins that we are trying to solve at the same time repository integration, that's what I talk about and security modules. All those problems that we face on our first option when we developed the application is already solved in Jenkins so that's why we moved up to instead of creating a new application we just created plugins on top of Jenkins and the good thing about that is we can feedback all those features that's already developed and well maintained in the Jenkins community itself. The last five years we used features from Jenkins so there's a lot of features in Jenkins these are the basic stuff that we were trying to target on our first option when we tried to develop the automations obviously there's a lot more in Jenkins that we can use like integration with RLC, integration with a couple of systems that you can think of so everything is there the downside of using plugins instead of our applications is that obviously you require an agenda server to be up and running also we are restricted with the Jenkins plugin development process so if you are aware Jenkins plugin we need to follow certain workflow and certain criteria if you want to develop a plugin that's available for public community Jenkins so that's one of the limitations that we have we need to work around with also the problem will be access permission to produce an RDI repository so if you want to use what with the plugin itself we will need to input the credentials of the source repository as well as credentials from Zanah server into the Jenkins but like I said Jenkins already got to put security modules in there so I don't think it's a big problem and a lot of the big communities is doing that as well and everything is in one place and also the plugin is limited to Jenkins server environment ties up to the first point where yes you require a server to Jenkins server to run up and running so that's the downside of having the problem developing a whole thing based on Jenkins so that's the base diagram that I can put up so on the left side you've got all the stakeholders on the top yes the package maintainer or the writer which is another spot as well push and pull into GitHub which is the source repository then on the Zanah side again on the lower side left low corner it's a translator push or translate in Zanah and those two entities on the left side will communicate to each other by the Jenkins plus the Jenkins plugin so with the Jenkins plugin every time the GitHub or every time the source files has been updated in the GitHub repository it will file a webbook and from the Jenkins you actually listen to the webbook from there you push the updated source into Zanah straight away or depending on how you configure it and likewise whenever a translation has been updated to Zanah and again depending on the webbook that you configure in Zanah you would be able to push or send a signal to Jenkins and the Jenkins plugin would be able to pull the latest translation and push back into the GitHub repository itself so that whole process you don't even need to install Zanah CLI there's no manual process in there you just need to configure it in the first place and everything will just run automatically every time something updated or depending on how you schedule it so yes now CLI has no way to push and pull manually from command line you just depending on the Jenkins itself to listen and push to all process into both of the entities so for demo let me do a quick one there so in here I've got a Docker Jenkins running on my local machine this is the Zanah plugin which is published so basically if you're familiar with Jenkins you're just going to manage Jenkins and install the plugin yourself and from there you just need to create a job so this is the job that I created so what happened right now is this job is configured with this GitHub repository and it's a proper file type where this is Zanah that I run locally configured based on the Jenkins itself based on the plugins so every time you create that you should do a quick test just to show you all the features that's available in the plugins so obviously the source code management all these things are the source repository modules or plugins that you can configure so for kids yes you can do a GitHub which is what I put in here actually it has all the information the URL this is provided by the plugin itself so what you need to do is you need to copy the URL or web URL put it into Zanah projects which is this one so what happens is that when you put in the URL you can configure one type of web book that you want to fire up when anything happens so there's a couple of them that related to translations 100% translated documents as well as whenever a translation is being updated so every individual string also there's a manual event where you just trigger a manually Bible retainer itself if you don't want to be automated you just need the maintainer to go in every weekly or something just to get on the button in Zanah send a signal to Jenkins and start doing each else so this is how it's being configured go down to the bottom obviously there's a credentials in here which is handled by the Jenkins plugin security modules and moving down this is the part where you go in your Zanah credentials so if you're familiar with Zanah you can see by the way this is Zanah 4.0 Zanah 4.3.0 so it's not being deployed to the Dora instance so with the Zanah credentials obviously you need your APIs and your username in here which is included in here then you get the Zanah and you're going to push the Zanah or pull from Zanah and connect to the given repository on the way back the base general configurations that you need to do also obviously the branch that you want to push to so obviously localizations what happened in Red Hat is they always push to a localization branch instead of master branch because obviously they want to keep master as possible and after reviewing the localization branch they will merge it into master branch so right now with the demo I just push it to master and see the date update and everything straight away but yes you can select whatever branch that you want to push it to so in here what I can do is now because I'm running on localhost I won't be able to get I won't be able to get GitHub to talk to my Jenkins but I can do I can get by Zanah to talk to my Jenkins because we're running on the the same instance localhost so what I can do here let me refresh this let me refresh this so right now yes it's 11 days ago and 6 hours ago and 11 days ago so what I can do here so right now the webboot is being configured so that it sends a signal on every translation being updated so if I change one of this hopefully it works in this course there you go you can see it starts running and yes so after that I refresh this 12 seconds ago and if I open this I would have the latest update at level 1 so all this is automated so again from the source point of view I can't demo it right now because I'm running everything on localhost but if there's any commit up to the give repository itself if the webboot is completed properly it should do the same thing send a signal to the Jenkins and the Jenkins would actually push the updated source into the Zanah straight away yes, yes so in the Jenkins in the job itself you can configure it only to do one job so it's it's very configurable, it's very dynamic so you can do whatever or you can mix and match whatever you want to do you can even set it so that it runs based on cron jobs instead of waiting for the webboot from behind itself or from Zanah now those two tick spots push to Zanah pull from Zanah so here you can be configured according to whatever the maintainer wants some of the project probably you don't want the source to be updated to Zanah that often and you just want the latest translation every day then yes, it's Jenkins you can configure whatever you want, it is pretty powerful so that's for the demo let me bring back nice slides so the last one is about the statistics that I managed to pull up it's very interesting to see what's been happening for the past 6 months so yeah this first graph is about it's all the languages so not a particular language so it's all languages that's activities that have been happening in the photographer instance so January, August, February we've got a spike in there March, I believe April was the sprint 2017 then yeah 2017 the transition sprint the previous yeah so it's considered high compared to the rest of it but somehow in February and March we've got a higher number on that I can show you the more detail on the breakdown of what's happening on February and March so this is for which branch sorry which branch which general general all the projects in the photographer instance I think there was branch February 26th from March yes so probably that's why because every time you branch it off you copy the translations over and create a new one that's why there's a spike there so that explains it it makes me very excited that my there is so much transition in February but it's a good right so this is the breakdown of the top 20 languages that's been translated for the past 6 months Japanese got the highest ones again we've got Spanish and followed by FI I'm not sure about language finish finish finish then French yeah all about so this is just the basic stats obviously I've got the detail breakdown if you guys are interested in each of the languages but yet we've got a couple of APIs that's in 4.0 so we'll probably be able to combine those APIs do a different couple of API calls and probably we can get data from there right now all this is done by Metal without exploring because obviously there's some limitation on here but yeah we probably can do it while we can automate it or even before that if I can run it locally then yes I can mix and match those APIs and automate the process of getting those data but yeah that's about that for automations obviously it's more targeted to package maintainer and for translator if you guys want to make use of the Jenkins plugin to automate the process yes I'm more than happy to help out so to set it up and everything I actually talked to the in-front team if we can use the Jenkins instance to host all these things obviously they are more secure and stuff so perhaps yes it's a possibility that we can use the Jenkins to do that yes Brian I apologize for having walked in I just want to apologize if this is to run Jenkins Shouts to Fire Jenkins and other translations are big we should be able to host those with the simple CI structure so we don't necessarily need to talk to to everybody that's why we're shifting a lot of those Shouts over so that between the two projects we'll collaborate on a simple CI instance to make life hold on each one and that's ready to listen to both webbooks and FAT messages all right it's good to know so yeah we might have a solution there so yeah the only concern was there will be a lot of credentials that we're storing in the Jenkins instance that's why we chose not to host it ourselves because we'll require those credentials from the package maintainer and there's another user so it's best to host it somewhere that the in-front team or someone that's more secure environments compared to us but yeah I'll move on over to Alex there was some discussion to have a Zanada client for mobile as well for mobile was there any discussion well initially we were trying to do it in Android but the problem was we figured out there'll be a lot of maintenance happening because once you've got Android then you need to maintain it in the Apple one as well so what we're trying to focus right now is to instead of creating a client enable the browser itself to support client or different resolutions so you can work on tablets or mobile so that's what we've been trying to do in the editor itself so the thing is that Federa contributed a lot into the GSOC kind of stuff Federa contributed to GSOC and how great the program is there so if you prepare a proper proposal for this you can get some contributions as well from apps not Android apps though the website well that one really included in our design so currently we are working on it but yeah if we can get any help then it's more than welcome to start with you yeah that's fine nothing wrong in the my screen here I think it's there it's there on third so let's think about my name is Jean-Baptiste I'm a translator and team coordinator the slides are already online and you can access it if you want so what do we do in localization? we want to improve the user experience the Federa integrated system by translating application and every document that is related and useful to the end user so there is no limit to what we translate which we are translating on this software that is 100% for Federa we translate whatever that can be used on Federa most of the translators that are in our teams are also involved in the office in Mozilla and you know we are a trans project and the only limit is the translator will ban the availability and availability means our time but it also means that we are tooling to translate so are we currently addressing our actual users? the main difficulty with Federa is we have earners and no stacks the only one I could get is from the get-for-the-roll website and what teaches is there is way more connection from India than from the United States and in India there is at least 20 official languages plus maybe 200 languages that are model tongue native languages so we program it most of the languages that people connect to the website so this is that only for the third semester of 2017 it's not accurate it's only using IP address it's only using number of dates there is a one-third of the dates that you can link it to some but it's the only data that we have we have no statistics about what is the language and operating system so if any of you may have an idea about a source to guess about what are the language that our users are speaking we love to know it so to have success we have to measure it and I've been looking for a way to measure what we are doing so the first one is what the users see we have low software using app data as you can see here it's translating in French and we can translate it in every application so on the left you see some the top 15 locale by package translation there are 4 this means I take every locale available in in federal I take the locale that have the most important number of package that has translation and then I make the top 10 and I take what is the average translation level of each package what we learn from 2004 which was one year ago to federal actually we move slightly more so little by little the biggest thing can have hope to improve but if you go deeper in the statistics you will see that most of the teams are tiny teams they have no hope at all to give a user experience in app data for the end user in known software and this is on top this is the different part of translation because we are talking about the translation level the application itself and some of them can be quite flat in terms of quantity to translate and on the bottom line you see the description just the tool lines that are describing the software and if I am French I don't know English I type in French when I search so if the description is not in French there will be no match so if you take the best teams so again there is the solfice the 15 locale that has the most description translated the best team don't reach even 20% of the translation of the single description in the application so the user experience cannot be very good when you don't speak English on a federal but any other line of distribution so all of these data are from upstream they are insulated in a local file that we may translate the question is if we do something downstream in the federal world you have to find a very easy way to push it upstream if not it is something that should be denied by the federal community so if someone wants to go into this and find a way maybe to translate easily here on the aggregated level in federal and find a way to push it upstream or at least send a message with which one this you can reuse it maybe with a little new introduction a few minutes ago I would love to discuss it and go to dive the subject because I think there is really something you can do so can we go deeper because what we have here is any ad data files there is ad data files or some software what we have to look for is the packages itself when you use dnf there is a command line that enables to create files inside the packages so you can do some sort of query to say dnf please tell me all the packages are at least one file in my local repository for the French language and this brings me to 193 packages maybe with this we can try for every languages to know how many packages at least one file there and maybe we can have a trend of other different releases of federal entity does it improve as a bonus we should also be able to take the file and replace the categories and maybe run some queries we should also be able to go and see the ambassadors and tell them oh we want to reach that country or that kind of community how good are we or how bad are we do we support funds, we can answer this because it supports the timing we can answer this we do not we just don't know we have no answer for this so this is another hint maybe that we can follow if someone has some knowledge in dnf I would love to discuss with them so let's think about coordination this is what we have in our so you can try with this car but the problem is the way we are currently following the way we are currently following is this one so this is trans-pagoreal action which is a very very nice road in Romania which I will go someday but yes, that's awesome so this is really something that exists and it's a perfect idea of the open source road the way is different but at the top of the mountain you are very happy because you are not alone to reach that goal and you are all together on this road the problem is with that car we have very good engine nobody will tell you that that is not good for translation that is very good for translation the problem is there is no feedback to the cockpit like user activity project updates are coming but yet at the moment we just don't have it there is no chorus our communication is quite bad if you go to our weekly page I tried to change it last year but it was just too much work I did what I could but we need to do way better we need to improve the good the people who are having some nice initiative and we need to communicate about it and when we do a sprint we should be able to produce an article two weeks after the sprint to say we were 50 people and this is what we done after that we have some way to move around between us the mailing list it falls sometimes it's good sometimes it's top acumen we are an onboarding process which is very difficult we have to introduce ourselves in places you have to require some technical access to some fast route which totally makes sense for an end user it doesn't it's very complicated reaching the federal project and contributing to the state of it it is difficult do we have toolbox in our main language do we have toolbox do we know how to fix it if we miss if we are meeting someone we start with some issue hey, I have a little project I would like to translate my documentation how do I do hey, I'm okay because we have a toolbox to help do we create a new project I think there is 150 projects in Fedora.senata.org and I think there is more than one for them in translate do we know what those projects are and do we have some people that are missing that we want to take we say you are a good project I want to take you Fedora come here and I want to translate you we do that and do we have some room for friends if a project comes and say that we want to join a new project is there a way to reach it as you know camera connection okay and the last question where is the driver there is no driver I go to that before my before I start translation there were more people doing some great job maybe there were some other people before it but since two years we have a bunch of people it was a project a few minutes ago who are just doing their best that it's you know it's best effort it's one third of the little hour we have to contribute a trick or each night or maybe just from 5 to 6 in the morning because we cannot sleep anymore and we really need a driver so this is the present now we can see the future so this is the future it has closed so it means we will try to improve our communication we should be able to see what's happening inside the machine because we have some windows we have plenty of stuff and we should have some cockpit to drive the car maybe we should have some tools, some ability tools we had a president about 3 minutes ago maybe we should be able to communicate and to regroup the people that does good things for the translation when there is a guy from Czech Republic who is doing a book for the newcomers and say this is the way to translate it and please use it in new countries we should have something to say thank you because you are doing a good path and this is something we don't do now maybe we should have more promotions for the mailings I have a statistic about the mailings language but it's so low it's just not interesting maybe we should have more tools to reach the project why do we have to have so many steps is there some things that projectors can do without having so many obstacles in the way shouldn't we control the project in the event of sanada not controlling like when you are not in the democracy controlling that just welcoming communicating we are welcoming a new project and I think the last point is that in the future are we good enough to have an autonomous car or do we still need to drive so these are the my point of view of the organization coordination objective with what happened 3 minutes ago this is the end of my presentation I would like to discuss it with you now we would like to thank you for your point of view on the coordination provided by


In Vietnam, we took care of each other. In combat, you look out for your battle buddy. I'd do anything for my unit. When things get tough, it's great to know somebody's there for you. Every step of the way. Honor America's veterans by participating in the DAV 5K Run, Walk and Motorcycle Ride on Saturday, November 7th at NTC Park at Liberty Station in Point Loma. Register today at DAV5K.org.


Rojon leads the field of green It's a green green The month of May here in Indianapolis Rojon was wasting no time getting off to the throttle And Jack Harvey and that pink car shooting up the inside of Nougat Hey guys, welcome in the car So yeah, that's the steering wheel With a very pinky button for my daughter 86 is battling there with the wild thing Both of these guys raced each other in F1 But we wait But we wait, says Olivier Bousson Some weight jack ahead that you use on the ovals The pit lane limiter The push to pass both sides here And then one of the specificity of IndyCar is That handle And that handle here Which is the front and rear under all bar That we can modify when we are racing And then yeah There's a couple of switches here at the back Just to get the ignition going And then many people are asking about the arrow screen Well, it is, you know You just don't quite realize it's on So yeah, that's my car And Rojon, the NTT P1 winner


In this example problem, we are going to analyze the effect of a 100 kilonewton force acting on the horizontal stabilizer of a commercial jet aircraft. But before we jump into calculations, let's try and understand what the horizontal stabilizer does and what we could possibly expect it to do to the aircraft. If you think about the function of a horizontal stabilizer, it is a control surface that generates forces to provide pitch control and stability. It allows the aircraft to pitch up, like this, or down, like this. And that motion is a rotation about a specific point, its center of gravity to be precise. And notice it is reasonable to expect that the forces on this surface will generate a moment about a center of gravity because a moment is what causes rotation. So what can we say about the moment this force generates about the center of gravity? If we want to analyze what this moment would be, we need to gather some information. First, we need to establish a reference coordinate system. The aircraft body makes a convenient reference line, so let's define this as the x-axis. I will then define the y-axis as positive upwards and center this coordinate system on our point of interest, 0.0. Next, we need to obtain some more information about the orientation and location of the forces on the horizontal stabilizer. For this problem, our force is oriented 60 degrees counterclockwise from the x-axis. The linear distance from 0.0 to the location of the force acting on the stabilizer is 13.2 meters, measured at an angle of 20 degrees. With this information established, we are now ready to answer the question, what is the moment generated at 0.0 by the 100 kilonewton force? There are multiple ways to solve this problem, but we will start with the method of vector decomposition. We can now begin to build our model of the problem. We will start by representing the entire aircraft as a single point, its center of gravity, or 0.0. We can then put our force on the stabilizer in this model, which we will denote as vector F. And from our problem description, we know that F has a magnitude of 100 kilonewtons, and it's oriented at 60 degrees. Next, we can define our position vector from 0.0 to this force as position vector R. From our problem, we also know that this vector has a magnitude of 13.2 meters and is oriented 20 degrees. Now, we want to decompose these vectors into X and Y components. Starting with the position vector, it will decompose into component RX and component Ry. Similarly, vector F will decompose into FX and FY. The reason we decompose the vectors into components is that all of our decomposed distances are either parallel or perpendicular to our decomposed force components. This allows us to determine the moment by scalar multiplication, as the moment of a force about a given point is simply the force multiplied by the perpendicular distance from that point to the force. Knowing this, we can easily see that a moment is generated by our force component FY with its moment arm RX. This component of our moment will tend to cause a counterclockwise rotation as shown here. And in order to see that this counterclockwise rotation is positive, we have to look at our coordinate system. We established X as positive to the right, Y as positive upwards, which would mean that Z is going to be positive out of the screen. If we use the right hand rule and align our right hand with our thumb pointing in the positive Z direction, our fingers will wrap around our palm in a counterclockwise direction. This defines our positive moment direction. Looking at force component FX, we see that FX is perpendicular to Ry, so we will get a moment that is Ry times FX. This will tend to cause a clockwise rotation, which will be thus negative according to our coordinate system and right hand rule. The total moment at point O will just be the summation of these two moment components. So we will get that our moment is equal to RX times FY minus Ry times FX. Now we need to calculate all of the various components. Our X will simply be R times cosine of 20 degrees, which will give us a value of 12.4 meters if we substitute the 13.2 meters into this equation. Similarly, Ry is going to be R, the magnitude of R, which is 13.2 meters times sine of 20 degrees, which will give us 4.51 meters. For our forces we have to use our angle of 60 degrees. So FX will be equal to F cosine 60 degrees and FY will be F sine 60 degrees, giving us 50 kilonewtons and 86.6 kilonewtons respectively. Now we can see, do a little bit of a sanity check to whether these numbers make sense, because it's very easy to make errors with swapping sine and cosine.  But we can always look back at the problem and see if it makes sense. Here for our position vector, we see that we calculated that Rx is significantly larger than Ry. This makes sense for our angle of 20 degrees, because we can see that Rx from this angle should be significantly larger than Ry. So we can be pretty confident that we're correct there. Similarly with our force components, FX is smaller than FY and for that 60 degree and this orientation we expect this component FX to be smaller than FY. We can now substitute all of these values into this equation and get that our moment is equal to 12.4 meters times 86.6 kilonewtons minus 4.51 meters times 50 kilonewtons, giving us a total moment of 848 kilonewtons meters acting in a counterclockwise or positive direction. Earlier I mentioned that there are multiple ways this problem could be solved. So let's take a look at another method using the vector cross product. The moment of a force is defined vectorally as R cross F, which can be shown here with both letters as the vector or with the vector notation over top of the variable. Now it's very important to remember that the order is important for a cross product. So this is R cross F and R cross F does not equal F cross R. You have to be very careful with that. So in order to evaluate this cross product we need to know vector R and vector F in vector notation. Now luckily for us we already calculated the Rx and Ry components in the previous calculation. 12.4 and 4.51 and Rz has to be equal to 0 because our vector R is contained completely in the xy plane. Similarly for our force vector we calculated Fx and Fy already and Fz is 0 because our force is completely contained within the xy plane. Now that we have these vectors we can solve the vector cross product. And I'm going to use the Amsterdam method for solving for this cross product. And if you're unfamiliar with the Amsterdam method there will be a link in the video description to another video describing how to apply this method. But you may have learned another method for doing cross product that's also okay to apply. So in the Amsterdam method what we do is we take our position vector and our force vector because it's R cross F. So we have R and we have F and we stack it on top of a copy of itself. Okay so we have position vector R here as well as a copy of position vector R, force vector F and a copy of force vector F. What we then do is cross out the top and bottom row of this stack. And now what we can do to calculate the components of our moment is actually do a cross multiplication of this array. So what we do is take the diagonal products so we get 4.51 multiplied by 0 and we subtract 0 times 86.6. So in this method if it's a downwards diagonal multiplication it's positive if it's an upwards diagonal multiplication. Like here it's downwards from 4.5 point to 0 and upwards from 0 to 86.6 we get positive and negative. Now these products are all multiplied by 0 so the final result is 0. But now we can move down one row and we get 0 times 50 minus 12.4 times 0 which indeed gives us 0 again. And the final row we get 12.4 times 86.6 minus 4.51 times 50 which will be equal to 848. And this gives us our x, y and z components of our moment so we can write that in vector notation as shown here. These are the two main approaches for obtaining the moment of a force F about 0.0 for the problem. But there are ways to set the problem up in an even smarter way to minimize the number of calculations you need to do, particularly for the vector decomposition approach. Can you figure out a more efficient way to set up this problem?


willing to pay the price. On every bracelet in here that I put on these desk, it says dreams come with the price. How many of you right now haven't got your dream yet? You know why? Because you haven't paid price yet. That's why. Your dream will not come true until you start paying the rent, okay?  Nobody giving you permission. I don't need permission to go get my dream. It's my dream. You didn't come up with an idea. This bracelet says 365 committed.  That means 365 days. That is every day of the year. Christmas, you're still committed. Thanksgiving, you're still committed. Your birthday, it's your birthday every month. Today, the fact that you're alive. Let's be real about it, okay? All right, are you willing to pay the price? Write that down. Just write it down. Before we get into the training, there you go. I want you to ask yourself, are you willing to pay the price? Because if you don't pay the price, you're finished. Guaranteed 100%, you'll never get where you wanna go. It's physically impossible, okay? It says everything great is paid for in blood, sweat, tears, grit, sacrifice, everything. Everything worth having is going to be hard. If you do what's hard, your life will be easy. If you do what's easy, your life will be hard. Some of you in here, you got a hard life. You know why? Because you choose the easy path every single time. I watch you guys do it. I can't ask anybody in here right now any question and I'll show you just as an example, okay? You sell, right? Stand up. Where's a mic? Somebody grab a mic for me. I'm gonna ask him something real quick. I don't care how long you've been selling, okay? Okay? Here we go real quick. What's your name? Easy man. Okay, how long you've been selling for? Five months. Five months. Let me ask you a question. How many days a week do you work? Six days a week, five days a week? Five days a week. Five days a week. So this guy works 22 days a month. 22 days. Okay? How many hours you work a day? 11. He works 11 hours a day. Somebody do the math. What's 11 hours a day times 22? Somebody do it for him. Is that the real math? Cause I'm not good at it. So somebody's gonna give me the real answer. 242. This guy works 242 hours a month. Is that right? How many cars do you sell a month? 15 a month. Okay, how long does it take you to sell a car? Be for real. Three hours max. Three times 15 is 45. 242 minus 45. He's off 198 hours. Listen, I'm gonna tell you this right now. Everybody in here is that same way. The question is, are you gonna change? You know what to do. You just don't do what you know. Or you don't know what to do and I'm gonna teach you today. And today you're gonna pay attention. And I'm gonna explain this to you and I'm gonna make it really easy. You will leave at the end of the day and you will go back to your normal lives. You will either be normal or you will be extraordinary. And the only way to be extraordinary is to decide to truly be different.  Why? Because you're on a different mission.  A few have a good life. Just a couple have a great life. You have to decide, are you going to be in that great life section?  You will never be able to enter that. Why? Because you're not willing to pay the price. Today I'm gonna explain what these prices are to you.  Everything.  They don't care. You know what they care about?  Okay, I'm a leader.  Doesn't lie to you. If you don't get ready for war, you'll die. It's that simple. Don't play, you can sit on the couch and watch something. Get motivated and inspired.  Those are losers.  You're here today for a reason. Number one, you don't like the way that you're operating. You don't like the results that you're getting and the actions that you're taking. Even if they're good, you're not taking enough of them. Massive action is not in the table in this room, okay? I know this for sure. When you leave, there'll be some people in here that will become legends. All of you can. Every single one of you. You're all capable.


Hello, everyone. Thanks for joining me today. My name is Piyush Chandra, and I'm a Principal Product Manager with the Amazon Alexa AI team. Now before we get started, I want to make it clear that I'm not representing Amazon today. The views and opinions expressed in this presentation are my personal views. Today, we're going to be talking about the lesser known key skills to succeed as a product manager. And that begs the question, what are the more known key skills? Now every time I hear about product managers and product management, and when I go online to see what are the skills in job descriptions that people are looking for when they say I need a product manager, a few key things that jump out you have to be analytical, you have to have critical thinking and logical reasoning, and a bunch of similar stuff. You have to be good with numbers. You have to be able to look at the big picture and then funnel it down to something that is more actionable. And I hope that sounds great. But in my opinion, those are the building blocks. Those are the starting points. You have to have those to be a product manager. But simply having all those skills, simply being a critical thinker or very logical, does not guarantee your success as a product manager. Today, I'm going to be talking about a few key skills that have helped me succeed as a product manager but are not so well known or not so well talked about. Before we do that, I want to ask you a question. What do you think product managers do? When I hear that question or when I ask that question to other product managers, I hear a lot of grandiose things that product managers are the CEOs of their product or sometimes that they create the vision for the product. Sometimes I even hear that product managers are the voice of the customer slash end users. Now as a product manager, when I hear all of that, it makes me feel good about myself. But honestly, the day-to-day life of a product manager is quite different. So before we get started about the skills you need, I want to establish a definition of what product managers do. Product managers build a shared understanding of the product vision. They remove roadblocks to ensure smooth development and they define what success looks like for the product and they iterate through this cycle. So that is my own definition of what product managers do on a day-to-day basis. Now product managers do not come up with a vision for the product. It just does not happen. What they do instead is that they socialize a broad concept and refine that concept by taking inputs from the various functions in a product team, engineering, design, sales and marketing, legal and so on. And then they stitch together all these feedbacks and make a coherent vision that is shared by everybody in every team. That is how product managers help create a shared vision. Now to do this, you need facilitation skills because it's clear that PMs are not the decision makers. And even if you were, most of the organizations today are so cross-functional that there is hardly ever one decision maker. One of the key skills of a successful PM is not to make decisions, but to facilitate decision making. The goal of decision making is to help align cross-functional teams, large or small, on a goal that they are all aligned with. This is the concept of shared vision and of course is not limited to just the product vision. In product teams where most decisions impact various teams, there is no centralized decision making. The burden of ensuring that teams reach a common understanding is on the PM. This is key to any successful product because without all hands on deck, the product is doomed to fail. The PM ensures that engineering, design, marketing, sales, legal, and others, everybody are all behind the shared product vision. Now you know that you have to be a good decision facilitator to be a good PM. How do you become a good facilitator? A couple of things that have helped me become a good facilitator are, first of all, cultivate empathy. Empathy for each function and each individual in your team. You have to appreciate and acknowledge that every team and every member has a part to play and you have to see where they are coming from. You have to understand what matters to each of them. While they are all part of the same company and they might be working on the same product, they might not be motivated by the same thing. You need to understand what motivates each team and each individual. The second thing that has helped me is to learn a framework that enables me to facilitate discussions and whiteboarding sessions to help democratize the process of decision making. The one framework that has worked really well for me is the process of design thinking. Now design thinking is a well-researched and well-established method and is something that you can look up online. But this is one thing that is very well-defined and it brings all different parties to a product and enables everybody to share their views openly and builds a process through which teams can come together and define a shared vision. So you need to figure out which framework you're going to use to democratize the process of decision making. And the third thing is, as a PM, you need to be respected. Now, how do you get that respect? One thing that I have figured out and has worked well for me is that every time there's someone who has a quotient about your product, the first person to come to their mind should be you. As the PM, you should be the go-to person for that product. Does not matter what the quotient is about. It could be about the technical architecture of the product, or why did we go with this pricing or that pricing? Or how is it growing? What are the plans for the next year, next five years? Every single quotient, you should be the one people come to get answers for. And I'm not saying that you need to know everything, but you should be the first point of contact. Every product team has multiple functions. And as a PM, what works really well is to know the key things of each function. You need to understand the key things about marketing, key things about engineering of your product, key things about how you're going to sell it, and so on. So what you end up doing is you have a horizontal understanding of different functions in the product team. And what also works really well is if you can develop deep understanding in one of those functions. For me, I'm very passionate about user experience.   So I go deep in that one function. So a PM skill set basically looks like a team. You know a little bit of a lot of different functions and you're deep in one function. And you need to figure out what is that one function you'll go deep in and how you'll gather sufficient working knowledge of all the other functions. This will help you create a shared vision and this will help you become a great facilitator for your team. The other critical thing that PMs do on a day-to-day basis is they remove roadblocks for everybody else in the team so that they can continue with their work. And product management at the heart of product management lies influencing without authority. So you remove roadblocks by influencing people and decision makers without authority. Now, if there is one thing that everybody in a product team will look up to a PM for, it is removing roadblocks. Maybe design needs to be approved before front-end engineers can start coding or a KPI needs to be finalized before the BI team can build a dashboard.  To make sure you can remove roadblocks for others, influence is your weapon. At the heart of product management lies influencing without authority. The good thing is that as a PM you are already tuned to understand what your users want. Treat your stakeholders as your users. Build personal relationships with them. What does John want to do over the weekends? Did his team win or lose? What does Jane do in her free time? It might sound superficial, but it is hard to influence people unless they feel a connection with you and connections are hard to build without having things in common. Find things in common with people you work with. Make it a point to never have lunch alone, for example. Go for a walk with your colleague. Stop by at their desk to say hello. If you work remotely, maybe take the initiative to share personal stories at the start of a team meeting. And these are just some of the ideas. Now, two bonus skills. First one is communication. Now, we all hear that, yes, product managers have to communicate all the time. Either you're writing documents or you're creating user stories, sending an update to your manager, or maybe giving a presentation, writing a press release. So many different times you are communicating. And I think we all believe that we are great communicators, but it also helps to know what are the things that you can do better? So it's good to know your strengths, but also identify areas that you can improve as a communicator. What works for me is that I record my important speeches to see what can I do better? You can also do a drive-on in front of your colleagues or friends and family and get their feedback. You can also ask your colleagues or your manager after a key presentation to see what part of the message you were able to deliver well and where were you lacking? You'll be surprised when you see yourself from the eyes of the others. This is the best way to learn what the audience expects from you as a speaker. One way to regularly practice the art of connecting with the audience is through Toastmasters. There are also online courses and in-person programs offered by multiple institutions you can make use of. Remember, there is no perfect speaker, but there are things you can do to become a great speaker. A day in the life of a PM involves spending up to 75% of the time in meetings. That leaves you with very little time to work on your own deliverables. Good time management will save you when there are 10 things trying to pull you in 10 different directions. A couple of things that helped me are first, I block time on my calendar way in advance and I dedicate that time to work on my own deliverables. I do not relax this rule unless there is an urgent situation. And one thing that helped me really figure out this concept is a book called Deep Work by Kel Newport. If you can get your hands on a copy, please do read it, it's a great book. I also like to keep a running list of things, which I call my own personal backlog. I structure this backlog as things to do today, things to do this week, things to do this month. And when I block my time on my calendar, I make sure that every day there is zero items on my list to do list for today. And I also try to make slight progress towards things that I have to do this week and things that I have to do this month. And that's how I can maintain my sanity. Now to conclude, these are some of the things that have worked for me, but they say that product management is not science, it's an art, and you need to figure out what works for you. And these are some things that work for me. I hope that you found it useful and maybe you can give it a try and see if any of these clicks for you and makes your life as a professional product manager more productive. And if you have any feedback, any questions, please, you can always reach out to me on LinkedIn and I'll be happy to answer. Thank you very much and thanks for your time. Bye.


Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by Ed Mead. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste. I know a trick to make you thrive, which is a quaint device. Your stillborn poem shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these two papers sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sew them to curl for fifty pound, and swear they are your own. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by Great Plains. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poem shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these two papers sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by J. C. Kwan, Montreal, February 2008. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these two papers sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by J. C. Kwan. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these two papers sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by J. C. Kwan. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these to paper sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by Lisa Ash, Folly Beach, South Carolina. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these to paper sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read from Braille for LibriVox.org by Merrill in western New York, March 2008. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these to paper sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by Mike Love. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these to paper sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem. This recording is in the public domain. Advice to the Grub Street verse writers by Jonathan Swift, read for LibriVox.org by Rhonda Fetterman. You poets ragged and forlorn, down from your garret's haste, you rhymers dead as soon as born, not yet consigned to paste.  Your stillborn poems shall revive and scorn to wrap up spice. Get all your verses printed fair, then let them well be dried, and curl must have a special care to leave the margin wide. Lend these to paper sparing pope, and when he sets to write, no letter with an envelope could give him more delight. When pope has filled the margins round, why then recall you alone, sell them to curl for fifty pound, and swear they are your own. End of poem.