Hello, and welcome to this presentation of the STM32 Interconnect Matrix. It covers the main features of this matrix, which is widely used to connect various internal peripherals between each other. The Interconnect Matrix integrated inside STM32 products provides direct connections between peripherals. Applications benefit from these interconnections to ensure time-predictable operations, to decrease power consumption by avoiding complex management of peripheral communications through reading or writing registers using CPU instructions, and, in some cases, to reduce the need to loop the signal from a source to a destination through a dedicated GPIO. The Interconnect Matrix offers two main features. First, it ensures direct and autonomous connections between peripherals, allowing to remove latency in regards to software handling, thus saving GPIO and CPU resources. Second, the interconnection between certain peripherals can even operate during low power modes. This slide indicates the list of source and destination peripherals. Source peripherals are the EXTI, the timers, analog IPs, clocks, RTC, and system error. Destination peripherals are the timers, infrared interface, and analog IPs. The Interconnect Matrix is further described in the STM32G4 reference manual. This slide and the next two ones describe the various possible uses for the Interconnect Matrix. Synchronizing or chaining timers, for example, allowing a master timer to reset or trigger a second slave timer. Triggering the transition to burst mode and also configuration update of the HR-TIM through a general-purpose timer. Triggering an ADC through a timer or EXTI event. Triggering a timer through an ADC watchdog signal when a predefined threshold value is crossed by an analog input. Triggering a DAC through a timer or EXTI event. Calibrating HSI-16 and LSI clocks, for example, measuring the external oscillator LSE frequency by a timer clock by the calibrated internal oscillator. Other use cases. Starting low power timers from an RTC alarm, a tamper event, or comparator event. Implementing blanking windows in comp modules. Connecting internal analog channels to ADC comp and op amp units. Using the comp outputs as timer external triggers or break inputs. Other use cases. Protecting timer-driven power switches through the direct connection of system error signals through the timer break input. Infrared pulse modulation signal waveform generation using two timers. This slide shows a simple example of timer synchronization. The timer 3 is used as the master timer and can reset, start, stop, or clock the timer 2 configured in slave mode. In this example, timer 3 is clocking the timer 2 so that it acts as a pre-scaler for timer 2. Peripherals can be interconnected using the interconnect matrix even when the circuit is in a low power mode. This table indicates in which low power modes the interconnection between peripherals remains active. The low power modes that can be used are run, sleep, and low power sleep modes for all interconnections. The connections from the real-time clock or comparators to low power timers can also be used in stop 0 and stop 1 modes. For more details about the interconnect matrix, refer to the reference manual for STM32G4 microcontrollers. Refer also to these trainings for more information if needed. Timers. Low power timers. Analog to digital converter. Digital to analog converter. Comparators. Operational amplifiers. Extended interrupts and event controller. Infrared interface. Reset and clock control. Real-time clock.


I think we can get started. Yeah. Hello, folks. My name is Neil Gompi. I was here on the stage just a little bit ago, but I have a new companion this time, David Duncan. Come on, introduce yourself. Hey, everybody, I'm David Duncan. I'm a, well, in the Fedora team, I work on the Cloud Edition and I've spent a lot of time working on that in my professional life. I'm a partner solutions architect and I work on cloud images and cloud solutions for Amazon. Yeah, and I actually also wind up occasionally working with him professionally too because I work at Red Hat as a senior black belt on managed OpenShift solutions and that means that I get to interact with him when working on Red Hat OpenShift service on AWS or Rosa as everyone loves to call it. So we're here to talk about, with you, all of you, this is a participatory panel thing about cloud images and getting people to be able to make their own what kind of process type stuff and what we hope to achieve and what you would like to see from Fedora Cloud to help make your lives better running Fedora in the Cloud. I think one of the things too that we're curious about is where in your workflow might you have a good space for something like a bespoke image. We spend a lot of time looking at what we can do to create images that are small, minimalized and provide a generic base, but that's just the tip of the iceberg when it comes to how the Cloud experience works. You want to be able to generate, manifest and create application space that is specific to your workloads. There are many things that we do in our daily experience that we don't want to do twice effectively. Just to give you a great example, the CoreOS images that are created for building out the OpenShift services for all of the public Cloud providers is in fact not just CoreOS. It is CoreOS and a series of tools and technologies that are necessary for deployment so that we can get that deployment model down or decrease the amount of time to a ready state. With things like Red Hat OpenShift service on AWS or if you're running maybe as we were talking about yesterday in our talk about Fedora Cloud KDE, these are scaffolds of workloads that we build to provide something useful and differentiated on the Cloud that you will be enriched with. We want to help you be successful in the Cloud doing these kinds of things and doing cool stuff with it, and we want to know what you guys are doing in the Cloud. Would this stuff to help us or to help them? Yeah, just as important is what documentation do you think is significant to make the next generation of your experience with the Cloud Edition better, right? It obviously doesn't have to run on a public Cloud or it doesn't have to run on some managed Cloud. It can run on your desktop and we expect that the experience to be just as important, just as critical for others, and with some of the things that you can do now with Cloud in it and in Vert install and... Yeah, there's a lot of ways to... Like some of the things that you might not be aware that the Fedora Cloud Working Group actually maintains is the vagrant images are ours, right? Like we take care of the vagrant work stuff. I think we recently started doing what cube vert images or something like that, and we're also doing things around adding it to additional Cloud providers. We just added Azure recently and we're looking at Oracle Cloud and a couple of other providers just to kind of round out the table of things. And we've always had the network of the common VPSes like your Linodes and DigitalOceans and things like that that we've also been having our offering on for many years. So anyone got something? Anyone? Yeah, looks like that guy. Hey, how are you doing? My name is Brian and I work quite a bit with upstream cube vert. So I actually came here today to ask you about if the Cloudsic would have an interest in publishing images for cube vert VMs basically. Yeah, I think we have the definitions for making them, but we don't know where to put them. Yeah, so I think at the moment we're building our own kind of container disk images which are basically just kind of wrapping. We say Fedora Cloud, CentOS Cloud images. So they rely on Cloud in it and then we store them in Quay as container images. Sure, sure. So yeah, it's great to hear that you're interested in actually developing some of these images because that's fantastic. Like our goal here is to provide all the deliverables that are needed for people to have an end-to-end positive experience using Fedora technologies in the Cloud development and production process. So whether that's on your computer or actually in your infrastructure or somewhere in between, like we want to make that experience good and help you succeed in that front. Yeah, so one of the things that made us excited to talk about this today was that we wanted to talk about what tools are available, right? And so a couple of the things that are available right now is just being able to create the build definitions inside of Koji and then build those in Koji. And we were worried that there are a lot of people who don't know, or in our community, right? Who don't know that they in fact have that ability. Yeah, just today, right? To generate those images in a way that is consistent with their expectations. I know Adam knows about it because... Because he does it. Yeah. A lot. We appreciate you, Adam. Yeah. And well, but he was also very vocal about learning and learning how to do it and there's probably, if you were to just wander back in the infra lists, you'd probably find some great conversation around that process from him. But we wanted to make sure that everyone knows that the tools are there. There are some other, there are tools for uploading to cloud providers and whatnot that are there. And while we don't expect that we'll be doing that for everyone individually, we expect that if there's an image that we need to have in a place that makes it available for specific cloud providers that that's something that we would manage and maintain for you. And then, obviously OSBuild is out there to help you do that in your own independent, like in your own individual accounts or whatnot.  All the things that OSBuild is the back end of. You have some way of producing these things in your own environment. We also, I mean the tools that we're using in Fedora Cloud Day, we're in the middle of a transition moving away from some of our legacy tools that are kind of specific, that can only kind of run effectively in Fedora infrastructure to stuff that people can run anywhere. So whether it's OSBuild or in some images we'll be, we're looking at using Kiwi for. And the idea is that we wanna move to a model where everything that we're making is something you can make too. Because we know that as much as we wanna serve and offer all these wide variety of things, the key power of the cloud is being able to build for yourself, tailoring it to your experience. And we want to make that a core tenant of what we are doing, we want everything that we're making to be something you can take and make your own. Yeah, there's a lot of times where we get feedback from the cloud providers about security or some sort of vulnerability that they don't wanna see in the machine image. As such, they wanna see it, they wanna see a new image deployed and then that image has, the governance around that is really complicated because we really wanna just put out one image and then put out an updates associated with it. But their process doesn't fit that. Fast forward to the customer experience, right? Then you start, they start to have a deeper impact on their own customers. Their own customers think that, oh, okay, well now we know that our process is to update our machine images and then, or just images, depending on who it is. And then the updates themselves are there for us to be able to make something that is more consistent. But then to make it like once every two weeks or so. So we know that people who are working on cloud solutions are also being, have a high amount of pressure to issue new images instead of just creating a patch management model for the instances that they create from those, right? Yeah, because if you're in the more ephemeral world and you have the ability to subscribe to a feed to get the latest image every time you provision, then you probably wanna take advantage of that. But on the flip side, if you're one that's starting from this and you have a machine environment that's sticking around for some time and you're gonna keep it and life cycle it, then you would favor being able to do patch management and things like that. So being able to handle both types of workflows is something that we try very hard to also do. And that kinda comes back to, we're trying to make our tools easier and simpler and more flexible to be able to handle these divergent use models because they're both valid. And we wanna make sure that people are happy using these things in the cloud locally, wherever. Yeah, the Kiwi decision was one that came about because we were looking at how to create composable image definitions and it was just a fantastic way to do it. We could create any, basically any kind of image we wanted from the WSL all the way out. And so we were, we've been pushing in that direction. On the other hand, the uploads and configuration and like post config, we started off trying to determine how we could build our own tools but then it looked like Ansible actually does most of what we needed to do. So we turned our, we turned the cloud team has kinda turned towards maintaining those, the software development kits in Fedora so that we can have full support for the, for the Ansible collections that support them. And ideally, like these are things people can take and use in their own environments. One of the, you know, I spent eight years as a DevOps and doing DevOps type stuff. And, you know, one of the things that made my job challenging was that I saw all these interesting things and ways that people were doing stuff. And things that I could have loved to use in my own environment but they didn't make it successful or available for me to be able to easily take it, adapt it and extend it for my own use cases. Well, it's still not easy to like integrate with the infrastructure. Yeah, I know, but I'm speaking aspirationally. Yeah, aspirationally. So like this is something that we, like David and I have been like working really hard on trying to like make that a guiding point for us when we're making our new decisions about how things are supposed to work and what we're producing. But it also allows us to put limits on what we are going to do. And for example, we're probably not gonna make a cloud variant of literally everything that exists in Fedora. We don't need to, that's... But we definitely do wanna make a, you know, cloud variants that are gonna do things that we think are gonna segue into more of a Fedora experience. So there are lots of people who come to, one of the things that I talked about yesterday actually in the cloud discussion was how we looked at the, like cloud nine, right? Cloud nine and inside of Amazon doesn't have a Fedora based image, but it could. And so, you know, it's for us, that's something that we want, we are looking at how we can produce. It's, I mean, obviously backlogged on other things, like getting rid of Python 2.7. But we're, you know, it's a, the, you know, our goal is to see how those things can fit into the process that, you know, processes that users are already dealing with and say, hey, I couldn't use Fedora as a foundation for this instead of just using, you know, some other distribution. Yeah, and like kind of riffing off of that, a lot of this was, well, you know, CIS admins that are like in an emergency scenario, they're away from their main computer station, you know, being able to spin up, like say a cloud KD desktop that's got like, you know, their open shift and Rosa command line utilities, their cube definitions, their access to their version control systems, all that push button provision so that they can do emergency work in the environment that they can actually be comfortable with.  Typing into a terminal and having to like do things from your, from a crappy phone console that's in Android or iOS, compared to like being able to access like a remote desktop from a web browser, is yeah, I would take the remote desktop in a web browser because then I'd have access to all the tools that I actually need to function. And that's the kind of stuff that, you know, we're looking at to like enable cloud experiences, but also we want to have a framework where like, let's say for example, you know, the Python classroom, the Python state who maintains the Python classroom lab for Fedora, wants to also have a cloud variant. They are perfectly capable of reusing our framework to be able to provide that on their own as part of their lab. We don't have to do it for them. No. We would give them the tools and the capability to just do it and make it part of their own deliverables. We want to be able to provide that kind of flexibility to people in the same way so that they can actually have their own tools for success. Yeah, but I mean, I think we think other, a lot of other groups are feeling that they see that segue and we want to help them in that way. Oh, sorry. Yeah, we want to hear, you know, we want, we think that there are other members of other teams that are looking at things that they want to be able to stand up quickly. They want to verify, you know, they may be working on windbind or they may be working on, you know, key cloak. But there's a lot of things out there that you want to just be able to bring up, look at and drop and that process of building those machine images and making sure that you have the updates and that you have sort of a, you know, basically a step, you know, kind of a step function style approach to ensuring that you have what you need. We want to help make that a reality for lots of other groups. Maybe you want to work on open QA on a virtual machine. Right? Perhaps you want to be able to make your own just environment to do all this stuff just with pushing a button in the cloud. Any other questions? Yeah, just keep it going. Sorry, so you mentioned that members can build their own images. Is there a good starting point for that? Is there a Clouds Hick Docks page or is there a good starting point for that? I don't think we're quite there yet. We're trying to, I mean, that's what we're doing. That's part of our goals with the rework of our image build stuff. In fact, that was a little bit of what I was hoping to get a springboard for today is to see where the interest is and how we want to frame that documentation. Yeah, so like part of the reason we did the CloudKD talk yesterday and why we're doing this panel today is we wanted to have some interest and learn from y'all, like what kind of stuff would you be, that you would find compelling and interesting to do with Fedora Cloud stuff? And because we have some ideas of what we want to do and I think we're on a good path, but we also want to hear from y'all to see like what are you interested in? What are you looking for? What kind of questions do you have about like doing stuff in with Fedora in the Cloud and that sort of thing? Yeah, I mean, I'll be honest, the Kuvert thing is super exciting to me because there's two aspects of that. So one, just generally Kuvert is a great way to create a great modernization strategy. And two, it segues into some of the work around lightweight virtual machine environments that we have not gotten an opportunity to work on just yet, but porting to Firecracker and things like that is a big deal. Also, congratulations, Kuvert, for reaching 1.0.  Yeah, we finally got there, yeah. You also mentioned Rosa on the site, I was just wondering, is container native virtualization included in Rosa? I don't think so. Can we, I don't, yeah, I don't think it's a thing. Yeah, we, so there's a couple. It's a him question for whether we'll ever do it though. So whether or not it'll be supported, that's kind of a question, that's questionable, but like, there are flags in the metal instances where we're still working on the metal. Yeah, like most of the reason why we can't do it is because the instance types we support literally don't let us. And also it just, to some level, it feels weird, right? I mean, I think there are reasons where I think it would make sense, but like, you could also just EC2, and so like, but I also can get the idea of like, you wanna have the abstraction and the same API everywhere to be able to do all the things, but.   Part of the issue that makes Fedora cloud images currently today so kind of painful is because the tools currently require us to boot up into a virtual machine to produce the cloud images, which, and the cloud and the virtual machine boot up process is kind of special, and that makes it difficult for people to be able to replicate our processes on their own. And I wanna move away from processes that are so complicated that like someone who's like just getting started fresh into the stuff and is excited, doesn't get so discouraged that they wanna flame right out of the whole thing. I mean, you can flatten a kickstart now and just figure out what's in the process, but that's like, that's just one way to make a virtual machine. I mean, you could literally make it in the same way that you make an open VZ, or made an open VZ image. I hope you're not making open VZ in the winners today. Hey. Yeah. In the same way that we did a gazillion years ago and that's not unusual. I know the Amazon Linux team, when they build an image, it's basically just, you know, it's a tar file. Right, when you're finished. And I don't think that, you know, this is also one of those places where there's more than one way to skin this cat. And I think that that's an important part of what I think is interesting for us is that we don't necessarily have to do this in a way that is consistent with the expectations of the one tool. You know, if we decide or determine that there's something that we wanna do here that's different, we can be versatile. And... As long as it's maintainable. Because what we don't wanna wind up as in a situation where we have a litany of things where we don't actually know how we can keep them going. Oh, agreed. But you know, if we're helping somebody Sure. in the process, I don't want it to be constrained to like, oh, well, they're using Kiwi, so. No, that's not what I mean, right? Like, if a tool is kind of central to building the thing that they want or need and we need to, and as long as it's straightforward enough to integrate and support, I don't have a problem with it. Yeah. Yeah, so there's a lot of ways, there's a lot of different directions you can go with how you make your, you know, how you create your, or how your process, whether or not that process is consistent with the one that we have. And I think, I don't think that that should be something that would concern, you know, concern you. The most, I mean, to me, the most helpful thing is knowing that you can pull this, you can pull together this configuration, you can push that into the utility, the tools that we have already in place, you can get your build alerts in the same way that you would get them with any other Fedora projects.  Or Adam might just do it anyway and then tell you he did it. That's right. Any other questions? Any other? Comments? Comments, yeah. There we go. This is more looking farther into the future, but one of the things that I'd like to do eventually is more, or working with like GPU instances in Fedora. And that's predicated on getting all of the stuff packaged in Fedora so that it works. But is that something, assuming we can get everything to work, is that something you think would be reasonable? Yes, actually. So like, we briefly mentioned this yesterday during our Cloud KDE talk, like GPU accelerated instances and being able to support them properly in Fedora Cloud is absolutely on our roadmap of requirements. Most of the public cloud providers also have the ability to distribute the NVIDIA controller drivers so we can, we can, we can cheat. Piggyback off of that, yeah. I guess the, I don't know, one of the problems I'm seeing is where we're starting is with AMD, not with NVIDIA. That's fine too. And I know of one cloud provider who has one instance that has an AMD GPU in it. And it's not current. It's a couple of generations old. Better than nothing, but, like I was just saying, all the cloud providers do have NVIDIA. There's, Amazon has one instance that has an AMD GPU in it and I have not been able to find a single other cloud provider that has an AMD GPU. Well then, props to AWS for having AMD Radeon GPUs. It's pretty good. Yeah, newer ones would be awesome. Yeah, more new ones would be awesome. Because it's not technically supported by RockM. There's questions. I mean, it's not on AMD's official list. Whether it works or not is a different question. It's just it's not on their current official. These are the GPUs we support and then the one that's in AWS is different. Well, I suspect, you know, I'm not gonna speak for David, but at least from the Fedora Cloud perspective, I think if we start having those toolkits in place and being able to have instances, have images with that stuff preloaded, that instances, when they're provisioned on those instances, that they can just take advantage of them. I think they're gonna see a different dynamic and start building up for it. But what do you wanna talk about with the Amazon side? Well, yeah, I mean, so from the Amazon side, we have our own crafted drivers for those. The way that works from the Amazon perspective is the drivers are produced by AMD for the AWS environment and then they're maintained in an S3 location for the instances. But they're available and they're easy for us to distribute and there is a rail workstation that was created for specifically that reason to have two things incorporated into the instance. One was the GPU drivers for both standard GPU workloads and general purpose GPU workloads. And then to have on top of that the nice DCV VDI solution in place so the server's already there, you just connect to it with the client and it's basically like running it where you are. And the reason we wanted to do the KDE workstation is because we don't have an upstream kind of experience for people to have that same experience to iterate on for some of the same reasons. So we're really super interested in making sure that customers have that or users have that available to them because the user experience around machine learning on Fedora is a story that we very much need to tell. Yeah, that was part of one of my talks yesterday. It was what it is and hopefully how we're going to fix it. I am for my perspective, I am super excited about seeing the ability to use GPU compute in Fedora out of the game. I'm seeing the Rockham stack get integrated in and being able to start doing that kind of thing. I hope that what it will do is encourage more GPU compute workloads, whether it's AIML or something else. I mean, render farms are another example of GPU compute workloads that will use AMD GPUs with open drivers and an open software stack that everyone gets to exercise the flexibility and freedom that they need to be able to do what they want and not what somebody else prescribes of them. And just like you're doing, our goal is to build this narrative so that people don't forget or don't think that just because there is another narrative, right, that this one is absent, we want to make sure that this one is very clear and in their space. So for me, the machine learning, I mean, if you'll let me soapbox for just a minute. The machine learning conversation is one that I think is really hard because first off, most of the applications that make this space or work in this space are impossible to package, right? I mean, we've had that conversation several times. And then the way that others have approached this has been to take all of that stuff that they can't really figure out how to package, just throw it into slash opt, create an image and then just make that available. And that's- How kind of you? It's a scary, you know, to me, that's not, it's not a helpful model, right? Like there's no way to do updates. There's no, there's a consistency there that maybe I might like as a scientist, but the real, but this goes back to our like the whole idea of developing images for yourself. We wanna have those images in, you know, like in my project, in my account, right? I wanna have those images. But that doesn't necessarily mean that I wanna find them out there in the world, you know, in an incredibly vulnerable state for, you know, for super long or I wanna, you know, I wanna find out that they disappear at some amazingly fast rate and makes it impossible for me to have a steady workflow. So, I mean, I would love for us to try and figure out how we can do that, you know, Akash Deep and his work on the Neuro Fedora, I have thought was a great entryway into this space. And, but it's not, you know, I mean, Open Data Hub, right, was a really important part of that process around the OpenShift experience and, you know, we have, I mean, I have built out machine sets, you know, that were GPU enabled for doing machine learning workloads and in the OpenShift space. But really a lot of that work can be done on a single machine in a very, you know, sort of a limited space.  And helping people to understand how to do that means giving them the tools that they need to do the work. Just, I want to follow up quickly on something that you had said a while back to make sure I understood. So it is not a requirement for Amazon to have the driver supplied by AMD, it's just something that was enabled. So if we had something in Fedora that was completely upstream and didn't have AMD's binaries, that is an option for... Yeah, that's totally an option. Just wanted to make sure I understood correctly. Yeah, you can use the open driver stack in there if it's pre-loaded. Amazon just happens to have a bundle that you can just source it and install if you don't have anything. Okay. Yeah, without getting into trouble. No, that's an important part. Anybody else? Then I'll just ask, I'll ask Isaac's question. No, we don't have the RISC-5 images. Just yet. Oh, you know, I have expected someone gonna ask it. Like, I know it's so prepared. He's leading the witness here, so I'm gonna ask two questions. You just asked one of the questions, but the real question is, when will Amazon support RISC-5 in their public cloud? I'll defer to people who are, you know, more capable of answering that question. Because that's the chicken and egg. So when Amazon declare that they're gonna do that, then we can say, okay, so when are we gonna have Fedora images to sit on the RISC-5 boxes? I mean, why would we have to wait for Amazon to that? Because Fedora Cloud does way more than that.   There is, but he's Mr. Amazon, you're Mr. Fedora, right? So, that was a blunt question for Amazon. And from a Fedora perspective, then you still have the hardware enablement conundrum, right? Yeah, well. So, yes, we could do all the things you said, but we have to have the hardware enable to begin with. It's customer driven. And for us, it's somebody's gotta give us the stuff to be able to start doing it, because... We're gonna help triangulate the giving of the stuff to help you do it, and we're also going to politely encourage all the cloud vendors, not just Amazon, to support. I mean, you can, it's on public record, Alibaba actually have a T-head, where they're developing RISC-5 servers already, and their hook, line, and sync bought into this equation. I would love to see Amazon do the same. I have nothing to say to that. I mean, you can't rule it out, but you can say the roadmap is definitely driven by, based on what we're being asked to do. And all I'll say is that RISC-5 is an interesting architecture, and I hope that the machines bring up, go better than previous machine bring ups have. Probably a small question, but do customers not want RISC-5 on Amazon? I mean, you're asking the wrong guy, but yeah. I mean, there's some other people who are more deeply aligned with the, Peter DeSantis would be the one to ask that question, not David Duncan. And if we're speaking of people in the third person, Neil Gampa is just like, well, I would like to have, as many architectures supported in Fedora, and offered in platforms, and be usable in all the different ways, but I suspect that really, it's just most people don't know that they exist, right? Like, you don't ask for something you don't know exists, and once you know it exists, and you find a reason to want it, then things, the dynamics start changing. And that's true even in the Fedora open source case, like, we started having this interest and development into all these architectures, because people come in, and they're like, we really want this, and they start talking about it, and other people get excited about it. It's that flywheel of success. So I'd just like to add to that that, yeah, it's a bit premature and early yet for enterprise servers that are risk-based, but they are coming. And if anyone's familiar with the guru, or the demigodder from Mount Olympus called David Patterson, David Patterson maintains that risk-life is actually gonna supplant all CPU architectures over the next 10 years. And he's a, you know, he's a former X86 guru, et cetera, and he's ridden the wave with arm, and risk-5 is something that's, it just gives so much choice, flexibility to the HPs of the world, the startup chip vendors of the world, customers, countries, like India, China, et cetera, that it's an inevitable equation, but we're not quite there yet. So at some point, yes, the Goldman Sachs and the Bloombergs are gonna start consuming this, and Amazon is gonna bring a surprise on us, and hopefully we'll evolve on the groundwork to enable all the hardware on donations, then we can be off to the races. I mean, that's very lofty. My comment on that is that I remember when James Hamilton said that he thought that ARM was the future, and then it was like three years before, yeah. Yeah, but three years for him to make it work, and it was very interesting to see from the perspective of an engineer, because the questions that happened as a result of that were like more economic than they were anything else, so it's very interesting, and then of course, like a series of really amazing engineers started to solve really big problems really fast, and it's just like that, seeing the way that hardware can evolve in such a very short amount of time always makes me, it always surprises me, and I feel fortunate to have worked with a lot of these people. I will kind of add to this a little bit. You know, your comment about how it'll be everywhere and surpass all the other architectures and whatever, the concern I have right now is that when you look at how risk five is evolving, and how development is going, and manufacturer interest is growing, and how CPUs and all this other stuff, I find some degree of credibility that there'll be more chips risk five than anything else by the end of the decade. I don't know if I could put a pin and say that it means that risk five will be the dominant computing architecture because of the fragmentation between the risk five variants and instruction sets and stuff. We don't know how that's gonna settle out yet, because it's still changing even to this day. But before we get onto that question, let me just say that one of my favorite places to watch what's going on that's gonna be relevant to the way that cloud images are being built is the work that's being done in the VRT team that Karen runs and a lot of the things that start to come back to, like what's being added to the QEMU KBM code bases makes a huge difference in terms of what we can support. I mean, my goal would be to make sure, to ensure that that KBM QEMU support is there and it's there in a way that we can all take advantage of. And importantly, as I was saying with the fragmentation of the instruction sets, whatever gets implemented in QEMU and that the distributions and all of us rely on, the hardware vendors have to do. It can't really be the other way around. If the hardware vendors start stratifying the eight, because risk five ties ABI to instruction combinations. So if your instruction combination isn't correct, you cannot run the application. And so we can't have a situation where something calls itself 64-bit risk five and you can't run it because you don't know, like when it tries to come up, it's like, oh, all the instructions are missing. So we can't run. Like there has to be a guaranteed baseline that everybody's going to support for that. And like even today now with Fedora risk five being bootstrapped, there are two other separate efforts going on right now that are doing the same bootstrap for different instruction combinations. And that's the part that scares me because if we wind up being in a situation where we have to deal with the different instruction subsets that are not compatible, risk five is going to fail. Because people can't figure out how to work with it. I want to make sure that we all know we're on a tangent. Yes, I am aware. We are, we definitely have right hold. But let me go back and say the tenure comment was a Patterson quote. Yeah. So put that in context. Yeah. And also that new architectures require a lot of work under the hood from all the distro vendors, upstream, kernel enablement. And that in itself is what actually causes a standardization and helps prevent some of the potential fragmentation. So that's the beauty of open source. When you're working things and it's open hardware definition and because it's in the open, that means that the definitions will evolve with a little bit of common sense from the community sprinkled all over it. So I'm not really too afraid of it going off on potentially on 50 different tangents, which it could. It could for all the edge devices, but rel is never going to run on those devices. Sure. And Amazon's never going to have to worry about supporting them. So for the enterprise server side of the equation, I feel really competent, confident that things will consolidate and come into focus because of the community effort. I mean, it's everyone here and everyone beyond here that helps create risk five and helps create Linux. And that's the beauty of open source. So to tie it back to Fedora cloud as we're talking about for this, to bring this tangent back to the nose. I don't care just about the enterprise servers or in just the cloud, but I have to care about the whole cloud experience down to the person's computer. And so, whether it's risk five or whether it's ARM or whether it's running a desktop or if it's doing Kubernetes or whatever. Or S390. Or as mainframes are special. I'm gonna, that one's getting put aside. But like when we're talking about a Fedora cloud experience for that, I don't talk about just Amazon. I talk about, I also talk about like the desktop that someone's working on to develop the cloud workload. And I talk about the experience of going between the two and all of those other things. So there has to be an underlying level of consistency at all those levels. You can't have an experience that only works in the server side. It has to work locally too. And that's the piece that with ARM, it took a really, really, really long time. It took twice as long as it did to get the server parts. The server parts were easy. Getting everything else was harder. And I am very happy and willing and optimistic about supporting RISC-5 for Fedora cloud. But we have to have all those pieces in place to make it work. And again, it'll be because we have all those component parts in the KVM, Quinnu code base, and we'll be looking for that. That's what we work on. And that means dealing with a lot of special problems like how do you get, I mean, on cloud instances, one of the things that we worry about is like, how do you get a dump? Right, I mean, how do you get a memory dump? What happens to the program crashes? Yeah, where do you get your, yeah, where do you get your debug? Those are- And that's actually a surprisingly difficult problem. It is. But we wanna be there to help you and anyone who wants to build specifically cloud images, or cloud-like images, the opportunity to have our help and to be a part of our experience and part of our, really part of our team. We're open. Come join us if you're interested in this stuff. Actually, we need you to come and join us. Anything else? I think we can call it. Yeah, I guess so. Thanks for being here.


Hello and welcome to NewsClick. We are back again on our favorite topic with Rajat Nag, former ADB. I'm going to make it short this time. Trump has been our favorite subject when it comes to the global economy. Now, the trade war is really fully on from what it appears. America has imposed sanctions or at least increased tariffs on a whole bunch of countries, a number of products and some of the countries have now started retaliating, including India. Now, how do you read this? Do you think that we are going further down this path or do you think there is any chance of pulling back from the brink? From America's talks it doesn't appear or Mr. Trump's talk doesn't appear that he has any intention of pulling back what he has done. You recall when we spoke about this a few weeks back that I was hoping that the springmanship will be only that and then people would pull back and better sense would prevail and I remember saying that cooler heads will prevail. I have to confess that I'm very worried now about the trade war which seems to be on. Now, one never knows but it's very unlikely as you said. I just want to interrupt you for the moment. This is not really a trade war. It's an aggression started by the United States against the global economic order. It could be. Even if we just use the word trade wars as a telegraphic symbol for what you are saying. I think what has happened is Mr. Trump has unleashed his words and tirades against many countries. Some of which I have to if the one is rational about it are reasonable points. If expressed reasonably. For example, issues with China about intellectual property rights, about theft of intellectual property, cyber security. I think those are relevant issues which needs to be discussed but cannot be discussed the way it is being done now and my own conversations in Beijing where I was there recently. There are many people there who realize that China also has gained the system for a while and therefore they do run a huge trade surplus with the world at large and then they have to sort of, you know, now start trimming those back. What I feel has happened by Mr. Trump doing what he has done that all those rational people in US, in China, in India and others who want the global trading system to work are now finding that they're totally off the table. Therefore, India has now announced a list of 29 items. Canada has done the same. China has said and rightly so that if you impose this tariffs will do the same and Mr. Trump has said if you impose tariffs in response to what I have said then I'll put more etc etc and that is going to continue and I think as I was talking to you just before coming on the set that I'm very worried about what's going to happen to the global economy because I think a trade war is on. It'll take effect in the next few days and it's very unlikely that anything will change between now and July 6th when the first rounds are supposed to kick off. You know, I don't want to digress too much from this topic but just as an aside when you talk about intellectual property rights theft and so on I would argue well that the whole trips agreement which was put in place was the biggest theft of shall be say knowledge of the world into certain companies. So I don't want to enter into that. My point is just hold on Roger and the second part of it when you come to the cyber security issues the student documents make clear that US has hacked the entire world. So let's also agree that they are actually relatively extraneous issues. The real issue is that there is a trade surplus that a lot of countries have United States and the argument is United States has is able to have a huge deficit because it prints a dollar. My point is that on trips or intellectual property rights or on access or limited access non-tariff barriers the world is far from perfect on the trading issue. That's why the Doha round never sort of materializes. Exactly. But the world at large through the global trading system through the WTO we did come to what I'd say a second or a third best and of course one tries to improve and many of the issues I mean one can have discussions on the trips on the intellectual property rights US's role China's role etc but those cannot be done with a gun at your head. Exactly. And that is why what we are so very different. Yeah. This is those discussions which I think were very important and many in China would agree with that that if you really want to move ahead you need to bring all of those to the table. Those discussions are not possible now. A and B because of what Mr. Trump has done and is doing now many countries are willing to cut their nose to spite their face. And I think it is true that US has the ability to withstand it much better than other countries because its economy is doing very well economy strong. Canada for example. Canada depends so much on the US that in any trade war between these two countries Canada will suffer. But talking to my Canadian friends almost to a person they're saying we are prepared to take that pain. And this means people are moving away from economic rationality to basically something more fundamental pride sense of sort of you know being humiliated by Mr. Trump. And I think you're going to see trade war getting worse before it gets better. And I don't think it's going to get better any time soon. You know I would agree with one proposition that you're making that war is perhaps the last thing we need to settle differences of any kind between countries or economies. So yes taking a hatchet shall be say to even a bad global global trading system is actually worse than trying to settle those differences and move towards a different direction. The important thing for Trump and the United States today and I really have to accept is the United States today because the president that it seems to be arguing that global trading system as long as suited us we gained out of it was rule based. Now it doesn't suit us. So forget the rules that you might we might have agreed to or we might have actually helped to build. Now the rule is simply whatever I say is the rule. Now is that a viable global system at all. It is not and it's unacceptable because you're not dealing with sovereign states and sovereign states come together to negotiate but with some fundamental assumptions the sovereignty has to be respected. Take NAFTA for example three sovereign states came together and actually U.S. contrary to what Mr. Trump says actually benefited significantly from NAFTA and so did Canada so did Mexico and that's the whole point of global trade that it can be a win-win proposition not equally. That's the whole point that you know global trade actually caused prosperity global trade benefited globally but there were losers within the countries and between countries. Mr. Trump seems to look at it as a zero sum game. Absolutely. And in the process he's actually moving the sort of you know levels much lower in which my own feeling is and it's not just my personal feeling I think even the IMF recently has come out and said it that even the U.S. will lose. Now U.S. can bear the burden better A because it's a larger economy B it is a stronger economy at the moment but the countries say China or Canada or India they are very smart they are actually picking those products which hurt Mr. Trump's water base say in agriculture or say in some manufactured products etc. So I don't think even the U.S. is going to come out of it unscathed. For a while Mr. Trump will probably be able to say to his base that I stood up to all of these people who took advantage of us but ultimately quite frankly I don't see any winners in this actually going to be losers on all sides. You know Rajat we have to also think about the rationality of the irrational people as well assuming that there is some rationality what is the rationality here A the story of victimhood if we are not doing well it's only because others are taking advantage of us. So essentially the fact that America is losing its economic dominance over the world the hegemony if you will of the world which was the quote unquote unipolar system after the 1990s of all of the Soviet Union and so on that is actually weakening this hegemony is weakening and manifests itself politically as well as economically. I think in the 60s various gaming exercises modeling exercises were done and Americans realized by 2040 or 2050 China would be the world's biggest economy which is what we are seeing slowly happen. Do you think that the irrationality of what appears to be rational of Trump's action really is stemmed from the fact they want to reverse this by some method or the other? I'm not sure that Mr. Trump has thought it through in a sort of global way in a rational way but he certainly looks at it from the prism of his base and his base I think if one looks at things rationally and fairly have lost in the so-called war of globalization they are the ones who lost the jobs they are the ones who sort of you know suffered because of the steel prices collapsing etc. What I think Mr. Trump and his base missed that it is not because of global trade that it happened that was a part of it but because of robotics because of the manufacturing sort of in a productivity automation automation etc. But it is true that globalization has its discontents globalization has its victims how the system within the country manages the redistribution is a challenge which say people in the rust belt in the US feel was not done equitably and for them the enemy therefore is the world out there and Mr. Trump has I think brilliantly exploited that feeling but if I look at it from Asia's point of view the point that you were alluding to about USA losing it sort of in a global dominance I've said before that the 21st century could if not the Asian century it will certainly be a multipolar century in which Asia will be much more dominant than it was Mr. Trump has just hastened that process so in that sense Asia should feel actually good that the withdrawal or if not withdrawal certainly the backing off of USA that we were talking about has probably been hastened and that space will be taken by China for sure and India so you probably see the center of gravity of the world economy moving eastwards even more rapidly than sort of we had thought a few years back what you're saying is that instead of retarding this tendency of shall we say the unipolar world giving away this is actually going to accelerate it but at the same time it's going to have pains for everybody yes and if Mr. Trump thinks that he will inflict more pain on others and therefore gain because he inflicts less pain on the United States economy that's not good to happen that's right I think he probably thinks there'll be no pain on the US economy what I think he is probably right in thinking there will be pain elsewhere but they'll also be pain and I think increasing pain on the US as well including and maybe particularly his own base last question do you think that impacts the dollar as a national currency because one of the ways US has been able to dominate a global shall we say economic rules is the fact that it can print essentially the reserve currency of the world do you think this is going to now break up not in the near future and that is not because US's domination will sort of in a continue to increase as a matter of fact it'll decrease but because the euro and the n haven't been able to become as strong as one would have thought possible particularly now with the Brexit the Chinese remnant be certainly is now a currency in the SDR basket and will increasing importance but I don't see global settlements really happening in any currency other than the dollar in the near future but I do see over time again a multipolar basket in which the dollar will remain dominant I think for the foreseeable future next few decades irrespective of what happens to the Chinese economy US dollar will remain dominant but not exclusive I see the Chinese remnant be increasing in importance because China is starting to tell many of its trading partners that they're willing to settle bilaterally so you don't have to go through the US market so I think to answer your question the dollar will remain important but it'll have contenders certainly the Chinese remnant be in the decades to come you know completely as an aside the fact that you impose sanctions in Iran impose sanctions and Venezuela you also are forcing the other part of the global currency scenario the energy market which is again picked to the dollar to move away from the dollar because if Iran is under sanctions Venezuela and the sanctions they will have to find alternative ways to settle the market as you know India at the moment can't buy is thinking of not being able to buy from Iran because of the sanctions and of course they don't want to go to the remin by route but that seems to be the only one left for others and and I think you will probably see the Europeans being a partner to this process because the Europeans who certainly were very much against you know Mr. Trump withdrawing from the Iran Accord felt that their companies will also suffer through the secondary process of sanctions so they themselves are actually seeing or looking for ways in which the financial global financial system which is so dominated by the dollar can find alternatives so and I think what you will see in the next few decades is also the evolution of a global financial architecture which doesn't depend exclusively on the US at the moment all roads lead to New York I think you will probably see a bit of a dilution of that thank you very much Roger this is all the time we have today for discussing this issue I don't think Mr. Trump is going to go away or Mr. Trump's policy of breaking the global order is going to go away soon so hope that we can continue this discussion further as these issues develop thank you for watching news click and do keep watching our YouTube channel and our website


Thank you. Better. Okay. Hello. Yeah, I have to do this. Okay Stage career pending Okay, so we talk a lot about openness innovation and opportunity on the web in Missila and and we do care a lot about this And as you guys know work with us for years It has to be like a key part of everything we do. We can't do anything alone We're simply not big or strong enough But the realities of day-to-day life is that when the teams are shipping code and things need to be fixed Sometimes this aspect of openness can seem like it gets more tedious than it gets effective But we can't stop there that can't stop us in creating open code and it can't stop us in working in open ways And so we really wanted to understand how we create a better experience And that's a better experience of people who want to contribute to Missila's mission and the stuff that we do But it's also a better experience for the people who are working at Missila and who want to work in an open way And one of the ways we do this in design in UX world is that we start off by understanding people's needs So there are motivations. Why do they do something because when we understand that we can design better experiences for them So that was the ground kind of idea of this project It's really how do we create a better experience for contributors who want to help with Missila's mission around the world a Really good way of starting to understand people's motivation is to ask them. So we had a lot of interviews 26 in in total that were Between an hour and an hour and a half Across the world some people in this room that we talked to as well We talked to people in person and San Fran in London under an OSFAS But we also talked to a lot of people remotely over Skype and video calls So the people we talked to ranged from a lot of different open source networks We didn't focus just on Missila open source contributors because we wanted to understand how other open source communities doing this What are people getting out of being part of those other open source communities and what can we maybe do better? So we talked to primarily technical Contributors from different projects range of different ages the projects ranged from open source hardware projects such as the V-Volvo project platform, which does bionic arms and robotic arms for people who Anything and then but we also talked to people who were part of like open source hacker spaces across different areas So there was a lot of breath in the in the group of people And I want to say before we go further is that it's not like it was me and Brian and a few others doing this on our own And we worked a lot with the community as we went for it and through conversations and small kind of group intercessions But also through some really big co-creation sessions One in London where we had about 40 participants But also one in Shanghai where we actually had over 70 persistent and the way we did this was we Basically presented the findings and the things that we saw and then we asked the teams and the groups there like what does this mean? What are the things that come out of this and that was a huge part of like building the recommendations that I'm gonna talk to you about today? So what did we find we found a lot about what motivates contributors funnily enough The way that we did these interviews is that we focused on their stories So it was a lot about getting them to tell us stories so that we could understand How they first got involved What was the things that kind of motivated them to get involved? But also telling us stories about when things have been really good like what were the things that were happening when this was really good What were the things that were happening when this is really bad? From a kind of social science perspective, we do that because once we get people to story tell we can normally better hear the tacit motivations as well as the known motivations that they have So the stories ranged From a lot like obviously we got a lot of information out of this But one of the stories that I thought was was really interesting was an 18 year old student who was volunteering for the Xperia Android fork and he had Started at a very very young age But he'd found himself totally immersed in this project and he was now one of the kind of not leads But one of the second in commands in the project and it was a huge part of his status and how he moved forward in his career there's also stories such as a An office assistant who felt that making sure that everyone had access to the internet and understood What was on the internet had kind of driven her to start a local community in her own little local village and Are still driving a huge part of the localization forward from a seller today So very different people very different areas. I'm going to talk a little bit about Some of the motivations that we saw Learning being one of them. I'm going to talk about these on a high level The report is public and I'll see other link afterwards and you can go into detail But each high-level motivation area has kind of forked into these under Kind of lower level of motivations that we saw which are a bit more specific But for today, I'm just going to kind of quickly brush through them. So learning I think is pretty obvious Everyone who's participated in open source knows that the learning curve especially when you start is pretty steep And it continues as you go through the the project and this was definitely the main motivation for a lot of people to To join one of the things that we heard from one of our interviews was it's like having a constant update of what matters Like I know when new things hit. I just know it comes up on our see through chat through other things It's like having this kind of push metaphor. We thought about it internally as like a kind of news feed That was created for you Community it was another one a lot of people were attracted to the community for the unity and for being part of something and A big part of it was taking part in something that was bigger than themselves and also just belonging to a social group That was important for them and there was a real belief in obviously the power of these communities So we heard things like the community is the engine like we can't work without the engine But also how community helps us keep going so this idea that it's your personal blackmail When I say that I'm gonna do something I've promised that to my friends and so I will do it because otherwise You know, I will let them down And it was interesting that even for those who work with a comfort entity within the open source project such as Mozilla or Android or Cyanogen mod This is still a huge factor for them The other one was calls and calls as I put here can be a lot of different things It can be and the cause of doing something better moving something forward changing the life for others But for most people it was this pure concept of just open source the way of working that we do an open source and the way We share knowledge that hopefully we all believe first is innovation in some form and having that as as a key reason for Continuing working on these things were also important fourth and second last is recognition and So a key part of why people really stay is the ongoing recognition that happens and again, this can be Very different as we've talked about here For starters when you're just starting out like something like a sticker or swag can be immensely Important to just show your relationship But once you get a longer term contributors and longer term Relationships it really is about the kind of tacit recognition that happens within the group and within the community as well And a story I thought was interesting here as well is was one of the guys who talked about who was an expert on a really specific fork Of an open source project said that it was quite nice You know when you go to conferences and they introduce you as that guy when you go on stage You know there's something about having that feeling of really being an expert on something That's that's a huge part of this as well and the last one that I once quickly cover is tangible goals So most people are also there because they want to see impacts So whether that is for the junior developer who wants to be able to see their code actually ship in a larger project Or whether it's for the more experienced developer who just want to be able to kind of drive where technology is going Where development and focus is going and also work on new technology and interesting projects So This is not brain science, right? I think if I had talked to any of you guys you could have told me those five things were pretty important for every contributors But what we do in design and what we do when we when we do X is that we really focus on the need and designing those experiences for that need and One of the ways we do that is that today we can't design for every single individual yet I may change that and I may be out of a job But so far that is not where we are and so the way we make sure that we Look at these different motivations is that we cluster them We pull them together in things that look alike and this is complex, right? Like it's not like one person is just inspired by learning and the other person is just inspired by recognition so the way that we try to kind of minimize the complexity in this which is a In social science what we call a little bit of a finger-in-air exercise, but tends to work Is that we took each of the individuals we talked to and on each of the scales of these five motivations We gave them a score from one to ten So what is most important what is least important for them and that helped us build like a profile that we could then actually cluster on Which we did and luckily the clustering exercise led to four distinct Kind of groupings coming out. So these are the four design personas that I want to talk about today I want to talk a little bit also about before going to them what we use design personas for So as I said, we really focus on needs and the motivations when we design these experiences because that's just how things move best for us and Personas are key in this because it allows us to put a face and a person behind things that sometimes are a little bit tangible Now if I just say learning to you and like 10% recognition and 50% something else That's really hard to build for but if I present you with a person that has specific needs and a story It's much easier for us to design experiences for them and that's why we use design personas a lot I'm sure most of you who have seen these from your UX partners in the fields Well, so I'm gonna quickly go through each of these again. They are they are online if you want them and The first cluster we saw was a cluster. We've called the independence the pictures here are fake By the way, because we really want to keep people who pad took in this study Kind of anonymous. So this is just a flicker picture that was on creative comments license So the one thing you saw in this cluster of people we'd interviewed was that they were all quite young They had the obviously common characteristic of being high in recognition and tangible goal as many motivations But they were all very young in their career and they're often focused on a really specific output, right? This is the tangible outcome for them. They're there because Things we heard was like my teacher had said you need to be part of deaf communities and this young female had no idea What that meant and so she googled that communities and open source came up and hence she got involved and has now been like a contributor for five years So sometimes it's it's fairly random kind of ways that they get into it but mainly it's so that they can build up their skills their networking and Get things that they can put on their CV and show and move their careers forward with however, they stay in open source because they get Enticed by the community and they get enticed by that recognition and status that they can get when they actually successfully ship something and get it put into code The second group we saw was we called the leaders The reason we called them the leaders is that they all had the same characteristic that they had been contributors for a longer period of time So it's not exactly a fancy name for them But they obviously were quite on the other end of motivation spectrum So they scored fairly high in recognition fairly high in calls, but really what matters to these people is the community That's what's keeping them there. That's what's keeping them really engaged This is also where we heard the the community is my personal black male comment And heard things like you know for one of the Mozilla contributors we talked to They said that there's you know this great feeling about being able to say I am the expert of Mozilla in my country that is like me as the go-to person The third and second last group that I want to talk about is we called the fixers We called them the fixers because there was this great quote from from one of the guys I was in this that said that you know, I have a fixer mentality I just want to fix things if they're broken. I can't leave them broken and they are Scoring really high on kind of tangible outcomes, which is obvious from this quote But also learning and so they are really there because they have a specific problem They often join because they have an own project they're working on or they want to work on a project That's relevant to one of their own things and open source is a way for them to get that done quicker with more people or collaborate on that problem But they stay because this is really an ongoing source of learning for them They feel like they can keep like up in the pulse is that I don't know how you say that But they can keep up to date and they can learn new things and this is like their continuous learning development program for them So lastly is the citizens and we actually call them the activists to start with I don't know quite why we changed the citizens But but we did sounded better. Maybe They are really high in cause and communities Again, they span ages. We can't say anything specific about age groups They were most of them all professional and they are really there because they care about the cause And this is like whether it's open source or a literacy or whatever it can be that they're working on some of the people We talked to from the revolver community really cared about, you know Enabling people with disabilities to move to work to engage and hence they spend a lot of their free times building and open source Bionic arms But most of what we heard from these people is that it's not about getting paid or necessarily Just being able to do this full-time. It's the satisfaction I get from contributing my time and my knowledge and seeing this area move forward All right, so in the last five minutes I want to talk a little bit about what this means because Having designed personas is great But like how do we move from there to the actual experience that we want to build and this is an ongoing journey for us at Missile We're by no means done and this project is still happening But one of the first things we did is that we sat down with the community and we sat down with the internal people Some of the internal people we're not done with this process either Who work with volunteers and we talked about what does this mean for you? Like what are the things that you do different knowing this that we can do different knowing this internally in Missile So this is very Missile-focused so apologize for this, but I think that there are some general trends that pretty much every open source Community can can utilize So one of the recommendations that came out was this idea of showcasing the value exchange I'm used a very businessy word in you value proposition But the reason that we've used that is because it's super important One of the key things that we saw when we talked to people is that in the beginning of their engagement with Any of the open source communities? They didn't really understand the benefits to the full extent that they do when they're involved So when they start they maybe think okay, this is great I can do some code I can learn some code and once they've been involved longer the benefits are so much more than that It's the community. It's the network It's all of these more tacit benefits that you can't really put your your finger on It's ensuring that we're better at communicating those up front when people start We also help them overcome some of that hurdle of getting involved first time Which we all know can be can be hard if you don't necessarily know anyone in the community Reinforcing infrequent communication on how to get involved. This is the big hurdle of how to get involved Now this workshop was done with some of the people from our open design community as well And so there's a lot around like how can we also visualize this like can we use visualization as an aid for this? So this is some of the things that we're working on now to try and figure out how we do So we wanted to communicate and visualize an onboarding process that gives them a sense of where they are in the process This is obviously a really hard problem, but one that we're really committed to working on We also want to visualize Missila and what we're about that's everything from like the projects We're working on and to the things we're doing some of the projects that are tapping into this It's like the pulse project if you haven't heard it. You should check it out. I'm still a pulse school search We'll probably get you there Where some of our foundation people have built the site that basically pulls out all the small projects that are happening across Missila and gives people a better an idea of what can I like contribute to what can I work on? the last thing we thought about doing which is Work in progress was creating a content and contact map of Missila So this is kind of the idea of creating a heat map across to see where people are that you can get in contact with from the different projects Third recommendation show how you can make a different for the mission And this is basically focused a lot obviously on the kind of citizen group that we talked about But this idea of highlighting that Missila is obviously about the open web But we do a lot of other things like web literacy Like to work on them projects to connect with women In India and all these other things that are kind of happening with our community and around our community We also wanted to do a we have the Kind of get started bug list We wanted to do something similar for people who are more interested in the cause right? So what are the easy things that people can get involved with and kind of start off straight away? We also talked about building a culture of positive recognition I think this is pretty obvious for anyone who's an open source So I'll kind of let you read it, but this idea that recognition is really important for us We also think that connecting to the communities early is really important now at Missila This is a something that the community themselves manages And if you don't get through the right place or you're not contacted through the 100% right person This can be a little bit of a thing where people fold through the cracks But we know that once you have that personal connection once you have feel like you're part of that community That's really what makes you stay and that's really what makes you feel like this is a worthwhile use of your time Lastly and this is for the more kind of experienced contributors We wanted to foster co-ownership and what we mean by co-ownership is that Things go bad and things go well and obviously as Brian said, you know This has been a turbulent year from Missila, but it's important not to be like this is all good and we're all happy It's important to own this both good and bad days together and giving people that co-ownership and Pulling them into both the hard times and the good times is really what makes us a joint community And hence we also need to be more transparent in the way that we're working And that's ongoing work both from the leadership side, but also from us working with volunteers on the ground So you can kind of look at these recommendations There are many more in the document that's online, but I've tried to kind of look at how we're looking at these as we think About how people engage with us across their experience with Missila and where we're focusing in so as I said It's online. It's it's open-source If you want to go have a look how we clustered how we did this you can do this here. It's 250 pages. Good luck But you know if you really interested so next steps that this work continues so this is a Project we started last year as I said, but we've actually partnered now with Howard University Who's really interested in understanding more about open source as well and therefore like looking further into this So we're still looking for people to interview we're looking for existing contributors for all open source communities We're looking for people who've left we're looking for people who maybe have thought about it But aren't really convinced. We're also doing a survey. You'll see some posters around here And again, this is run by Howard, but we would love if you could take part of it And we also just want your feedback anything that you have questions input. We'd love to hear Malika is from Howard and I'm our Jensen if you have any questions or comments That is where to go sorry She is not she has a newborn baby and so she's stuck, but she's hearing You take some questions Okay, so really probably the best be the best timekeeper of all the speakers all day So we have loads of time for questions. Let's take five minutes. So I will ask two things We only got one working Mike unfortunately, so ask your question really loud I mean, I would ask you to repeat the question on the mic. Please. Thank you So this is not a quaint project. This is what we call a qualitative project. So having us that decision look at 26 Sorry repeat the question Jesus it's right now He asked have we had a statistician look at this both from the point of view of the methodology and from how we recruited the Participants and so this is not a quaint project It's a core project. And so it's a different way of gathering information What we're trying to do with Howard is to add that quantitative part into it And that's part of what we're trying to do with the survey And so the way that we look at this in social science is that these are ways for you to gather information You can't quite can help you understand how and what but it will never help you understand why So we're using this to understand the why and then we're using the quants to go back and look at the how and can this actually be Replicated on large scale. Can we see this back in a survey? And that's how we're doing that. Yes So the survey and everything that we've sorry Thank you Jesus He asked if we had tools that other people can use in other open source Projects to kind of replicate and these surveys and using their own projects. So everything's online If you email Malika, she can tell you where it is. It's on Howard website tomorrow that I actually can't remember on my Kind of feet right now, but if you go there, she will talk to you about the if you email I shall talk to you about the methods she's using She can talk a little bit more about how she's looking into this from a statistician point of view as well And she will give you the survey and and the background everything to use in your own projects as well So the question was if this was a particular Missilla project or general open source communities So the first round of interviews that we did was definitely Hierated on Missilla because it was a Missilla question. The partnership that we've started now with Howard is general open source So that's why Malika is still looking for interviews and it's gonna do more of these as well Yeah So the question was if we've looked into the negative blog posts around add-ons to understand more about how the community is Feeling right now and the answer to that is that Malika is also running some Like basic content scraping to understand sentiment analysis online. So we'll probably appear in that But again, I would reach out to her to understand more about how she's doing that. I couldn't Let me see if I got that right It reminded you of a project that I didn't know about and did you ask what inspired us to get involved or So we did in the beginning of this speech out to quite a few different open source communities because we wanted to talk to people from different areas The feedback we got from the ones we talked to was that they weren't doing anything But I should also say we haven't reached out by any means to all of them And that is probably something that we should consider but we haven't done that The slide with the The URL


I am Ganesh Biyagalave working as an assistant professor in Department of Mechanical Engineering Valchen Institute of Technology, Singapore. In this session of heat transfer, we will see the unit conduction in that general heat conduction equation in Cartesian coordinate system. Learning outcome, at the end of this session, students will be able to derive general heat conduction equation in Cartesian coordinate system. Consider this as an element of the system, of the system. Small part may be rectangular or square is taken of a big system, which is exposed to the heat transfer. Now, here the surface A, B, C, D through this face, Qx amount of heat is flowing in the x direction and the thickness in the x direction from the origin x is a dx. The face A dash, B dash, C dash, D dash is losing the Qx plus dx amount of heat that is in the x direction. Now, remaining two surfaces are also exposed to the heat transfer. So, in the y direction, Qy amount of heat enters through the bottom surface and the thickness in the y direction is dy. It flows, it conducts throughout this element and from the top surface it is losing Qy plus dy. Remember, this surface is exposed to the heat transfer in the conductive mode. Can you think for the z direction also? Yes, Qz amount of heat is entering from the back side and its thickness in the z direction is dz. Then this front surface will lose Qz plus dz amount of heat. So, this was the Cartesian coordinate system in which we have shown the small element of the big system. Now, we will try to see the different equations respectively x direction, y direction and in the z direction. Here we will be using the energy balance equation because what is going to happen? Whenever there is a heat transfer, the temperature gradient must be present that is low temperature and high temperature, heat always flows from high temperature to low temperature. Because of that, there may be some possibility of internal heat generation which will be denoted by small Qg and at the same time there might be internal rise in the temperature of the element. Now, we will go through the next step. So, here see here the Qx heat is entering into this surface which has the equation that is Fourier's law of heat conduction we can apply. So, Qx is equal to minus k dou t by dou x dy dz. Here we are going to consider all the three dimensions and for this equation we have considered only conductive heat in x axis. So, this was for the surface a, b, c, d. Now, from the opposite surface a dash, b dash, c dash, d dash the equation becomes dQx plus dx is equal to dQx plus dou by dou x of dQx dx this is the Taylor's expansion. Now, this can be simplified we can substitute dQx as minus k over here minus is taken common dou t by dou x plus dou by dou x as it is we are written here then what is the dQx it is k minus is taken common. So, k dou t by dou x into dx and remaining two axis will be dy dz here dx dy dz is nothing but the volume of the element. So, this equation these three equations we have seen along the x axis now we will consider the y axis through the y axis dQy amount of heat is entering and this top surface is leaving Qy plus dy amount of heat. So, similarly I can write for the y axis also dQy is equal to minus k dou t by dou y dx dz and through the top surface which is losing the heat is dQy plus dy is equal to minus is taken common. So, what is Qy it is minus k dou t by dou y plus dou by dou y as it is written here in the bracket k dou t by dou y bracket complete dy bracket complete dx dz this was y axis. Now, in the z axis similarly dQz is equal to minus k dou t by dou z dx dy and Taylor's expansion is used for dQz plus dz as minus k dou t by dou z plus dou by dou z k dou t by dou z bracket complete dz dx dy. So, this is regarding three equations we can we can write these three equations for three different axis in the Cartesian coordinate system this assume it as a first one then the equation can be simplified for the net amount of heat conducted net amount of heat conducted means dQz minus dQ sorry dQx minus dQx plus dx plus dQy minus dQy plus dy plus dQz minus dQz plus dz. So, that step is omitted over here and directly we have written dQx plus dQy plus dQz minus in another bracket dQx plus dx plus dQy plus dy plus dQz plus dz and we can get now see here we can get here dou by dou x in the bracket k dou t by dou x. Now, what is going to happen here we can write it also k dou square t by dou x square plus k dou square t by dou y square plus k dou square t by dou z square. So, all the three dimensions we have considered three axis we have consider over here and this is the volume dx dy dz. Now, this was regarding net amount of heat conducted ok now here we will consider the second part that is the possibility of internal heat generation inside the element. So, the internal heat generation will be equal to q dx q bar dx dy dz and the rate of change of internal energy is will be equal to m c p delta t m c p delta t. Now, rho is equal to mass per unit volume. So, m could be replaced by rho into v. So, what is v here dx dy dz. So, this equation becomes rho c p dou t by dou t this is the change in temperature over time dx dy dz. So, if we apply the energy balance equation that is net heat conducted plus internal heat generation is equal to change in internal energy of the system. The equation can be written as dou by dou x of k dou t by dou x plus dou by dou y k dou t by dou y y axis plus dou by dou z k dou t by dou z z axis plus internal heat generation is equal to rho c p dou t by dou t. This is known as generalize heat conduction equation in Cartesian coordinate system. Now, if the case is that there is no internal heat generation you can omit this and for steady state condition change in temperature over the change in temperature over the time will be 0. So, in that case for three dimensional heat flow without heat generation for steady state condition the equation will become equal to 0. In that case q will be 0 and this change in temperature will be 0 because it is a steady state condition we will try to see it. Now, for a homogeneous material homogeneous material in this here will be assuming the conductivity in x direction y direction and z direction is same that is k x is equal to k y is equal to k z is equal to k then k I can take common k in the bracket dou square t by dou x square plus dou square t by dou y square plus dou square t by dou z square plus q is equal to rho c p d t by d t. Now, here del operator we will consider. So, this is nothing but del square t plus q by k this will be dividing both sides by k. So, del square t plus q by k is equal to 1 by alpha dou t by dou t where del square is equal to this one. Now, here alpha alpha is nothing but thermal diffusivity which is a ratio of k by rho c p for highly conductive material the thermal diffusivity will be higher and for lower thermal conductive material like insulators the thermal diffusivity will be small. So, the unit of the thermal diffusivity is meter square per second. Now, just now we have written del square t is equal to 1 by alpha dou t by dou t this is for steady state condition. We can write this equation for steady state condition that is del square t is equal to 0 this will be general heat conduction equations Laplace star for transform without heat generation and for steady state condition. In this fashion you can use for a single dimension two dimensions etcetera etcetera the general heat conduction equation. For further study you can refer fundamentals of heat and mass transfer by in Cropera David. Thank you.