So, okay So we're starting now with The title you can read and I can't XEP open stack devian and the cloud This will be the river ride Thomas good on Please Hola, thanks for attending my time my talk. I hope she will be able to cope with my silly French accent So what am I going to talk today? so it's mainly on the topic of What's new in wheezy? I want to let you know about My past work during this year to package cloud computing stacks in Debian So I let you know What we have done together so together with Citrix and with other people working on open stack Briefly, I'm 36 years old and the CEO of GPL host which is a company doing server hosting We have an internal software to do hosting. I'm French. I live in Shanghai. I Normally don't do Self promotion here, but since I'm not in the permanent sponsor list. I wanted to highlight that GPL host is hosting seven relays for the video of that comp It's like all of them, but Sydney and Malaysia so I hear many times that cloud computing is a buzzword that We shouldn't don't talk about it because like it's just marketing and it's boring. In fact, it's not that's one of the things you have to Really put in your mind is that it's not just the marketing That's really software behind that and not just a few like there's many solutions available and All of them are quite large and represent a lot of code There's many types of cloud computing there's infrastructure as a service platform as a service and software as a service Here in this talk I'm going to talk only about infrastructure as a service meaning providing visual machines to the final users This means for having a cloud computing service it needs to have all these four points So it has to be on demand. It has to be self-served Scalable and measurable. I mean like the hosting service Service provider must know how much you've used and together this is awesome Thanks to Dave who gave me that so Why is it important to have cloud computing service software? Indibian so we've been we've seen a trend like everybody's moving to Cloud computing as a service for software like people are moving to Google Doc to WordPress They use their mail on big platforms and Indibian we've made a statement Zack Made an announcement together with Citrix and the OpenStack community that Debian cares a lot that we have Cloud computing software available in Debian because we think it's a safeguard for our freedom We want to be able to use infrastructure as a service directly in Debian. So When we use cloud computing services, we need a hypervisor hypervisor is the thing that runs your virtual machine It's a bit like a PC emulator. So like You have like the illusion that you have a full computer when in fact you only have a Virtualized server, okay So cloud computing Stacks do not implement Hypervisor they all use hypervisors. So there are there are customers of it There's a lot of hypervisors currently available in Debian. So Zen KVM virtual box QMU VMware and you can access These three through packages in Debian. So Amazon EC2 there's UK tools that you can use to access But of course you cannot install EC2 on your own hardware Briefly there's also containers with LXC that is available in in Debian It's it's great to have LXC because now it's it's in mainline kernel So we have very good hopes that we'll be able to provide cloud computing on top of LXC So to do cloud computing as I said, we need a hypervisor So I took these slides from Jeremy at Citrix So I showed them first a bit fast. So you see there's many types of of Hypervisors and different model Basically with ESXi you have a Machine here that is kind of opaque. It's like you Don't have access to it. You just have a black box So as a system administrator, I don't really like this model because if there's any problem there I won't even know with KVM you start real machines as processes of the host operating system and then is different because you have the hypervisor running here and the DOM0 is at the same level as the DOM use like The DOM0 provides the management and it's considered by the hypervisor just as a visual machine with more privileges so on the paper it's better, but KVM is Easier to manage inside the kernel because visual machines are just a process And on the container side, we used to have OpenVisi And v-server available in squeeze and that is gone away The reason is that nobody stood up to say I'm going to maintain that so currently we have only LXC and We can use it in the cloud computing environment Using OpenStack, which is I believe the only stack that can manage LXC So a brief history of Zen that as well I took it from slides from Citrix So Basically, we had the Gen project started there around here We had the first usable Zen hypervisor so like with version 2 it started to be really good Then Amazon started to use it and provide the cloud computing service then Rackspace Then Citrix started to work on Xcp which was Okay, so then after there was Zen server that was sold for about 500 bucks a year that was a cloud computing stack and I'd say that around 2010 or 2011 we started to see open source stacks for cloud computing So basically for us lovers of free free software Nothing between before 2010 available and now it starts to be available widely so In Citrix, they first started to sell Zen server as Appropriatory software Then they wanted to open source it so they took this ISO image Which is sent OS based and provided it as a sent OS appliance of as free software But still not package means that you take the as we made you install it on your server and that's about it. There's no Stand alone. There was no stand alone opinion packages that you could use you had the source and you could do it yourself But that's not the way it was released and shipped and since about a year We have Citrix that worked on a packaged solution for Xcp that was called project chronos and So all of these three implements then API, which is a restful API that you can use to create manage and start-stop real machines, so that's what I've been working on with the guys from Citrix was Packaging that and making it making it available in Debian So this this started about a year ago. So there was discussions in the open stack mailing list saying that Okay, we have open stack. This is a Ubuntu project. So Debian based and we have Xcp which is a CentOS appliance so it didn't really make sense for administrators to have both CentOS and Ubuntu or Debian Together on the same cloud environment As well it made sense on the maintaining sites because like if you have packages it it might be easier to maintain the software So Mike and John started that project like last in April 11 And we've been working on that until December when it was first uploaded in in Debian So Mike and John has been extremely helpful and not only that they've been also very friendly So I'm happy to announce that we have that for Weezy and it's basically you do APT gate install Xcp X API and You have a server which is ready to use with Xcp Still some RC bugs. No, there's no RC bugs anymore There's like two normal bugs and we'd be happy to have more testing and and more Reports and of course more fixes so contributions are of course of course welcome So a few differences we have between the CentOS CD and the packages in Debian Sorry so Because it's a CentOS appliance they have to maintain all the packages themselves So the hypervisor version that you have in current Xcp is a bit lagging behind The DOM 0 that we have in Xcp in Debian or Ubuntu is what is available as the operating system So only 32 bits for the Xen appliance The it's very fortunate that both Ubuntu The last Ubuntu LCS and Debian uses the same kernel version Okay, next slide so what This is the difference between using just Xen and Xcp The main difference is that instead of having one hardware that you maintain with Xm or XL on The command line is that you have Xe and it manages a pool of servers many hardware So you have a master node That you control With the command line or with the REST API So the REST API the Xe tool Sorry the Xe tool on the command line is just a client for the REST API that you could use by yourself using JSON and things like that So you have a pool of hardware not only for computes, but as well for storage So every machine that runs Xen API Can be used for storage as well There's multiple storage type. So Xt is like Xt3 or Storage type. You can as well use directly LVM giving partitions to your little machines or I use Xe, NFS, Semba, whatever so and there's yeah, there's Semba stuff to store your ISO images and provide them to your clients when they want to install Virtual machines There's a very cool feature that Citrix is currently working on which is storage motion meaning that currently you can Move one machine from one server from one physical server to another. It's called live migration But the storage will stay on the hardware where your current virtual machine is running with storage motion as its name As you might have guessed by this name means that you can Move the physical the virtual machines compute workload, but as well as storage. So it will move live when the Virtual machine is running. I really hope that will have that for with E plus one So a bit of demonstration here. So how does it works in in real life? So that's a script that I'm going to Explain in details. So what you have in blue there, there, there, okay, it's things that you can replace In this typical script the red things are the Xe commands So basically every commons sends that you send will return you You you ID so that's if I can find my mouse. Yeah, it's there So what's cool? I mean Chinese So what's cool is that you have? Bash of the complete so you can see all the commons for Xe quite a lot right for more than 400 so you can do Xe VM list and currently you see that there is only my Dom zero machine and here you have the same script as I showed on on the slides. So Find the template create the machine. I did the visual network interface Set few parameters and then finally start so the start is commented So If I do Xe VM list, so you see there's no machines and I do new VM and very quickly VM list Very quickly. You see that there is a new machine called Managua 2012 that I can start if I want Xe VM so ST tab and she completes The M equal and then there I can either give the UUID that you see here or the name. So I'm going to give the name that's cooler Managua 2012 So starting is as fast as you do with normal then That's Managua 2012 and There you go, and you see a nice net boot. You fool So I won't go of course in the process of setting enough that would be boring Just do an Xe VM list to show you that it's running If I want I can shut it down a few few commons so that you can you have Vlan create so everything's there. So that's it about the very quick overview this as well then Open Zen manager. So if you have used the Tool delivered by VMware stats comparable so that here you have a list of the templates Maybe I should show that because that's that's nice When you create the machine, that's what you do. Okay, so you have all the list of templates So if I add the D then it will show only the Debian ones Okay so Now go back to my slides So here you will see all the templates the same way you would see on the common line So basically this is just like Xe so that's a client for the rest API, but In a graphical way So when you use So Xe P you have one of the possibilities to use normal Zen bridging Or you have the possibility to use open v-switch So I won't talk in details about open v-switch because I believe Guido is going to talk about it in the presentation just after mine But basically What does open v-switch is that If you have many servers and many switches and then complicated network What is going to do is that aggregate all these and make it controllable from one unique central point So it's going to maintain villains across your networks Your switch has to support labeling and then it will create villains The goal is that one customer has like many virtual machines You want these virtual machines to be connected to each other, but you don't want your customer to see the traffic of other virtual machines As well what it does is Monitoring with the v-flow protocol so that you will know how much Benweeds Virtual machines are using you can do QoS and things like that So Xcp is nice. It's very easy to use on the shell. You can create and Stop virtual machines, but it's not easy to compatible And there's many services that it provides that are lacking for putting that in production and provided to your customers So one way to use Xcp is to use it together with OpenStack So Xcp will do the compute load mainly So OpenStack will bring you the EC2 API and the STRE API and do storage for you so you will have your Images that will be stored using Glance Over Swift if you use that setup there's many ways to set up OpenStack. I will come to that later You Might have heard that about the first like Citrix is focusing on CloudStack That was an announcement that I think now Citrix is regretting In fact, they are still working on OpenStack and providing support for OpenStack One of the reason is that Zen is a very cool hypervisor And that's the only way you have to use to the only way you can use Zen is through Zen API If you use OpenStack and not through LibVerts the LibVerts think compatibility for Zen in OpenStack is Not tested. So don't even try because you'll be the first person to do it the setup is a little bit more complex than using just KVM meaning that The net the networking part is really complicated You have to set up three networks, three VLANs one for management one for private one for internal connections between your VMs So that now I'll talk a bit more about OpenStack itself So there's many many components in OpenStack Just Nova creates about 10 binary packages and Nova is only one of the project of OpenStack So OpenStack uses database whichever You want because it's used SQL alchemy So you can use SQLite, SQL or Postgres. It doesn't really matter and the RabbitMQ server so RabbitMQ server is a Something to communicate between the components. So it's it's a messaging queue Meaning that you have made on one side You have many components that might send some messages and they want it maybe broadcast to many other components So that's what it does Then you have the core project of OpenStack. So NovaVolume NovaGlance and NovaSwift together providing storage And then the compute part is made out of Nova and as I just said XCP if you want to use them So in Nova, in your compute nodes, you will need Nova network, Nova scheduler and maybe quantum for Managing your network That slide is a kind of a joke to tell you oh look that's easy There's only a few components and of course I have to explain a bit how it works So this is the RabbitMQ messaging thing So all of the components of OpenStack can send messages to the queue and then after the queue dispatches the messages to all the components So basically you have Nova API that will listen to a restful Request from the outside or through Nova dashboard. So dashboard is the horizon project and That's a web GUI. So you connect to it create machines through a web interface I like to highlight that if you use cloud computing It's a bit silly to use a web GUI cloud is all about automation and scaling and script scripting So it's not the way to come as a customer to use the cloud But it's still nice to have a web interface and see an overview of what's going on So the customers took to Nova API and then Nova API Sends to the queue to compute to create start and stop virtual machines Nova network is the thing that will route all the traffic of your virtual machines. So Your VMs will run in this like many hardware and Then absolutely all of their network will go through Nova network. So there's two ways to set it up First one way is that you have one Nova network and then all the VMs are routed through that Or another way is to set up Nova network in each compute nodes that you have so doing that is like You have more things to maintain but the nice point is that you have more redundancy like if one Nova network Several dies then you still have networks for the others So Nova volume is a kind of It uses LVM. So that's the elastic block storage of Nova meaning that you create a partition and then just say assign that to this machine The Nova scheduler you won't have to deal with it too much. It just decides where the machines are going to be started Yeah, and here when you want to create new virtual machines, you have Glance. So Glance just stores your virtual machines images like AMI if you if you use the AWS So here it will store your images and then you have multiple back ends You can use Swift so Swift is the equivalent of S3 so Swift is not File system storage its Objects so you can have literally billions of of objects stored there an image A picture of idol. It's not meant to be fast But it's meant to store a lot of objects and it's highly redundant typically you will Have at least three Swift machines That have at least three copies and then after you can add more and more hardware And it does the copies using our sync in repetitive Chrome jobs So once you have all the complicated setup you have here then you can plug XP on it if you like to use them So what happens is that you have one open stack controller system and Then he connects to let's say what one XP server and that one can have multiple XP servers to get connected to each other so one master many slaves and If you have multiple availability zones, then you can have these three So that's one cool feature about open stack as well is that you can have Availability availability zones. It's like let's say multiple ones in your data centers or Across the world if you have multiple data centers so I like Open stack is maintained by many these four guys including myself and XP's main maintained by by citric guys with me together so clearly the packaging is Quite complicated. It's not easy to set up. It's not something you say, okay I just set up a seed and then five meters five minutes later. It's done So we we tried to have Google summer of code students to do what we call an open-stack packaging use case so what we were hoping through that was that We'd had meet meta packages so that You could say okay. Here's a compute node. I just do APT get install open stack compute node And then magically would you would come up? So that hasn't been done And we would be very happy if we could provide that to dbm and reduce the size of the how-to's so Our final goal will be to have no documentation Because it would be so easy to set up and I think we are far away from that We we've added already few depth conf configuration screens and we hope to add some more later So we targeted in open stack it's Maintained through the same release cycles as you find in you want to so that it every six months does a new release so we had Boston Diablo cactus Boston cactus Diablo and sx Currently we are at sx that has been released through together with you want to 1204 and We're quite happy of this release cycle because it means that the guys working on open stack will maintain that for five years and That's what we are going to maintain in wheezy. So for us. It's really fortunate Like the the two previous versions of open stack like cactus and Diablo were Usable but not as much as sx which we are very happy because it's more stable It has all the features when we need So we're quite on a comfortable situation here But there's a lot of work that is going on open stack is a very young project. It's only two years old, okay? So there's always more and more things to be added There's Indibians in slaini this ganetti Which was the first opens the first cloud stack? That was available in dbn But there's more to be packaged Personally I'd be very happy if we had open nebula or cloud stack or eucalyptus totally package in dbn Currently we have ganetti Leni and then we have Xcp open stack and that's it nothing more available. So especially eucalyptus it would be interesting because Okay, that that is already available in in Ubuntu. They've been using it for years already The very good point of that is that it's fully compatible with easy to Open stack team decided that yes, they will try to be easy to compatible But that's not one of their main goal. What they would like to do is more having a Nice API and if they have to diverge a bit from EC2 then be it doesn't matter because open stack is aiming more at Being the standard of cloud computing by itself So all of these are very interesting and would love to see them in dbn So if you would like to contribute You're of course welcome and these are the references you should take this stuff So once again, I'd like to thank John and Mike from Citrix for being great of streams So on the open stack packaging there's been Louis and Julian from Inovance, which is a French company Inovance has spent like a lot of money By hiring Julian form like many months doing full-time work on open stack packaging It's really really a lot of packaging. It's complicated. So We really needed them to work to do that for the community So big big up to them I Recently George he will recognize himself Did a lot of bug submission on on the dbn BTS. This was very helpful. So thanks to him as well And we are now we have now have 10 minutes. So I'm happy to have Question and answers Please go ahead Was the microphone yeah over there there's a question. I just want Touch on eucalyptus a bit. I work for eucalyptus Sorry, I just want to touch on eucalyptus what you were talking about before I work for eucalyptus as a there Debbie and release engineer We recently uploaded eucalyptus to Debbie and we just didn't quite make the freeze So we're trying to work with the release team to let us in And also I just want to clarify. We're not just open core anymore. We're we're completely open source the only two components that are not are Pieces of VMware technology that we license and so we're not allowed to release that code. You're talking about eucalyptus Yes, sir. Yes, so it's not open core anymore. That's completely open source okay, I Think that Even if eucalyptus is changing the way to release it, I think the arm that has been done like two years ago Is already past. Okay, and I think it you have lost a big Opportunity here very very much That's why they hired me actually they receive quite a black eye on the community. We've been working really diligently with We've got three Debbie and guys on our team now. We've got Charles Plessy out in Japan We've got Rudy. Good boy down in Argentina. I believe it is and Stefan Molar out of Germany have joined the package eucalyptus team So we're trying to correct rectify that situation. So we'll Eucalyptus being with you plus one Definitely we see plus one and we're still working with release team to try to get in Weezy But that's maybe not gonna be 5050. That'd be really a great if we had eucalyptus like I Believe that together with OpenStack and XP. That's the thing that we really want the more the merrier Yeah Is there any other questions? I don't think there is any All right Yes, go ahead So this is all new to me. So that was marvelous But there were an awful lot of acronyms and diagrams and stuff and I didn't really understand about half of that However, it looks really interesting. So if you stick that online, I can read it again and try and work out. All right What's what so for those of us who've never done any of this. It's all quite confusing, but it does look good No, that was after let me find it out This one, right? All right. So what's your question? My question is just put it online so I can read it again. Sure. Sure. It is online Anyone making presentation it would be nice to upload your presentation in pant above Yes, it is there Already I uploaded it any other question. Is there any questions on that thing? So I Know that these things sounds like whoa, I won't ever ever be able to do that In fact, that's why I spend a lot of time to explain it to you Because it seems complicated, but it's not that hard. Okay, and like In fact, you can set up all of that in one machine and it's going to magically work. Okay, so thanks a lot And we'll resume at noon with talk by Gido Trotter for advanced networking, which is especially relevant to retaliation So, thank you


The limits of our language become the limits of our lives because when you have something inside you that you really want to articulate to people that you love and who matter to you but you can't and therefore you have been misunderstood and misjudged and perhaps you have been to some degree excluded because of that misunderstanding. It's frustrating and expensive emotionally because you feel something deeply but it's like a knotted up ball of string inside you that you can't give language to. And so you have to invent language because everyone's life has a language and most people can't interpret the language of their own lives. They are foreigners to their native tongue as it were because they get stuck with not able to language things that matter to them. So they settle into this internal emotional disruption upheaval pain about things that they can never give language to. What words do you need to invent and create so that your world can keep expanding where your language stops, you get stuck and frustrated and knotted internally and I want your world to keep expanding. So go ahead, invent any word you want to invent today that somehow gives language to what you are frustrated about and it matters to you to be able to do that. Invent words, why not?


The next speakers in our lightning round are both from the University of Kansas, Ignacio Carvajal and Neila Tai, and they're going to be speaking to us about their project in Qiché, Digital Resources for Qiché Learning and Instruction. Saqriq, Qiché and Ongel, Buenos días a todos, a todas, a todas. Good morning. This will be a multi-lingual conversation. We're very happy to be here. Neila's joining us all the way from Guatemala, from Isimuleo. And we're going to tell you a little bit about our work and the Seola Palabra, Anela, para que empiecen. Saqriq, Ongel, a laqa. As Neila l'Enobi, quimpe palet dinamit nao alcha, rech le Isimuleo. Kinyahu, Utsalach, Petbalch, Chechalach. Malkyosch, Amo, Shpe, a laqa, Pawe, Qatzihonem. Chirich, Lech, Abal, Qiché. Sebalach, ke kikot, le kanima. Rumas, nim u bandachik, le katzihonem kanik. Masha Rumas, hunkinomas, kiyokan ri eqatat, ekanan. Ri eqatit, ri eqamam. Pawe lo alachuleo. Rumas, ulaq, koch kikodik. Rumas, koch kowinik, koch chichol, chua chalach. Chui, le katzhak, kabanom. Chui, le katzhak, li kakach, kakabarak anuk. Kikot, le wanma. Uts, bahumpet, balalak, pawe, nim alach, chichonem. Ch'anim, kawach, kintzichon, hube, chirich, le katzhak. K'yap, oship, huna, pkanuk. Ch'amachich, le katzhak, aruk, leachtich, eginas, yokar, vachal. Ch'amachitach, le le chak, aretak, ri'are, shu'umachich, le uttichonik, parikhuna, dosmil tresi. Palenim, alach, tichobal, bresch, tehas. Chilak, utt, shu'umachich, le le chak, patan, churich, lech, abas, aretak, shubal, le tichonik, ri'are, shpe, paletilamit, nawalcha. Panawalcha, kabanwi, huna, tichonik, chirich, lech, abas, kawiche, le tichoshe lab, kek ochi, kuk, leachu, bachah, ke tsichonik, ke waik, ke tzanik. Sibalach, nim, lechon, rikoch, ib, kaban, warach, paletichonik, rech, sakih, ri'are, shpe warach, paletilamit, shtobal, palenim, alach, tichonik, rech, sakih, warach, panawalcha. Arela, lechachak, chelak, utt, ki tachik, lechachak, chelak, uchomachik, shbandach, kep ochi, puk, huna, abkanuk. Arela, lechubek, choboch, shiniat, chirich, lechachak. Maldioshne. Maldioshne. I'm putting in the chat, the link to the first resource that we're going to be speaking about, and I'll do this in English, pero las preguntas pueden ser en español al final. I'll talk a little bit about Ketamachle Kachavalskyche, which I've worked on or did work on while I was still at the University of Texas, actually with the help of coral folks as well as Nela and other instructors and students in Nahuatl. And it's an online set of lessons for Ketamachle learning. There's 41 in total so far and they're mostly arranged around grammatical components or cultural components, mostly grammatical components, we worked with an instructor in Vanderbilt who has created a grammar manual, and the sort of base idea was to make that type of grammar manual. So because Ketche, I'll contextualize first, because Ketche is a less commonly taught language, there's a lot fewer examples and input that is available to use for the classes so a lot of it were creating from scratch so that Ketamachle Kachavalskyche, which was a coral project, was basically trying to make that more interactive and more contextualize it more towards the culture we chose to do it with the Nahuatl variety, Ketche has different varieties depending on the place that in Guatemala that is spoken and so we chose to do it with the Nahuatl variety and had helped from the summer institute that Nela was mentioning in the prior slide. A little bit about how the site is set up, each of the lessons deals with either grammatical aspect or cultural component. And it has different sections, including an introduction, a Cichonik, which we call, it's like a speech or it can be a text or it can be a video or it can be an audio or a dialogue that the students read to sort of get a first glance at the the construction or topic or theme that we're looking at in that lesson came Chi, meaning grammar that gives more sort of in-depth grammatical explanations. Kaka Takcich, which are new words literally so like vocab lists, and then homework that the students can do exercises for. This is very rudimentary to be perfectly honest their sentences there's no way for them to plug them in and be corrected but they're basically based on supporting materials that you might use and then go over with an instructor. But that's sort of the format of the course. So this is a little bit more what each section might look like. So for example we have a lesson that is specifically about clothing. And so we have non ship here giving a presentation about the different types of clothings that we feel is, and other what they uses for one of the formal ones where the more common they use once etc. And in the explanations of the grammar what we did do with with another instructor we recorded the sound so that you can listen to the sentences as you read the sample sentences as you go through so most of. Most of the sample sentences will have examples that you can hear. We also built a companion YouTube channel that I think has been expanded now, and have more videos added but every video that's embedded and more is part of this coral kitchen channel. And then that has YouTube videos, most of which, but not all because we have to do it is the art closed caption and so they will have closed caption is in English closed caption is in Spanish and close caption and kitchen. So that students can put even the kitchen ones as they as they learn so this is the project that we've worked on together. I'm still going in there to make corrections sometimes it was done thanks to the support of coral. We did mostly the populating rather than the designing of the of the site. So I do take responsibility for any mistakes that are still in there. I want to talk a little bit about what we're working on towards the future. So I'm going to talk a little bit about what we're working on towards the future. I'm going to talk about what we're working on towards the future. So I'm going to talk a little bit about what we're working on towards the future. So I'm going to talk a little bit about what we're working on towards the future. So I'm going to talk about what we're working on towards the future. Raghawashi kaketama khasche ukochik kakabano, likak atakastak, arechi shakheri, kohkowinik, kakakut lec'abal, ketamatah lec'abal, malinik ahchikwinaq. Ahwaralik takwinaq, onliképe nakhnaqah, arela likakah kakabano, malkiosh. Altyoschoech nela, and so what nela has spoken a little bit about is the sort of new section of the project that we're dealing with that's sort of wanting to center more Mayan voices in the creation of the materials, right? I think a lot of the grammatical materials that we've created are great and they're really useful for a variety of students here in the United States to be the linguist, anthropologist, literary scholars, et cetera, et cetera, et cetera, but we're trying to really shift toward something that serves communities in Ishimuleo and Guatemala and also diaspora communities here and seeing how we can approach that from like a less technical approach of the language and more sort of collaboration, collaboration methods that can sort of serve the stakeholder communities first because I think that the tenet is that we can use those in our classrooms if we design them in that way first, whereas the opposite may not be the case. The thanks could take another 10 minutes, so I will just put the slide up that we have. It includes the folks at Coral, like Natalie and Sarah, who are both present in this room, a list of collaborators from Nau'ala, and Nela, who was my first teacher and I look up to and learn from every day. And so, caca maltiosi, cháwech, chíwech, ché-chélac, y cátils, huecó le cotó chíach. If there are any questions, si hay alguna pregunta, podemos contestarlas ahora en español o en inglés. Maltios. I have one question and just so you know, we have about four minutes left for questions. One person asked, how long have you been having these resources online? Did you see an increase in interest in the language in general because of the resources being OER? Yeah, so the YouTube video has thousands, the YouTube channel has like so many thousands of views. I was just, we're taking aback really. I mean, I was in grad school doing this, putting them up and trying to keep close captioning them and I was so afraid that they might have mistakes and stuff like that. But yeah, I think that the sort of YouTube component especially had a really good reception from folks who don't tend to be able to see indigenous languages and quiches the most widely speaking one in Guatemala. So I think that even in the comments to YouTube questions, people express their gladness to see that type of stuff. The materials themselves, they often make the rounds around like Twitter and things like that where people are sharing them and I think that they are in use in several of the people that I speak with that teach quiche which are not that many in the U.S. but it is being used in a couple of places and it is a collaborative effort. So we've used a lot of the materials that have existed. How many quiche, there's quiche Vanderbilt, there's quiche Tulane has a summer course, we have it here and BYU has it and I think that's it. I see what is it. It's completely unrelated to BASK. There might be some contact post-invasion but I'm not familiar with the influence in the quiche community. That's a really interesting question. This for Bakush, we're collaborating with a language school this year and we're trying to make that not a unilateral creation of materials but a sort of collaborative one and so I think it is to be determined yet. Yeah, I don't go in question. in este proyecto con el profesor Ignacio Carvajal sobre materiales de quiche o la enseñanza. Entonces este es el pequeño resumen del trabajo que hemos hecho y lo que queremos hacer en el futuro. Muchas gracias por haber estado acá.


This one's for the mandem. In the wake of the Weinstein revelations and the hashtag me too movement, the last couple months have seen a global revival in discussions of sexual violence, in particular the relative protection enjoyed by perpetrators at the expense of justice for their victims. Now some are arguing that technology can play a key role in rape prevention and in prosecuting cases of assault. Dutch blockchain company Legal Things is developing an app called Legal Flings. Blockchain saves permanent records and transactions in multiple places. The Legal Flings app would present would-be partners with a legally binding contract, consenting or not consenting to certain sexual activity.  Consent is not a contract. This weekend an article was published in Babe magazine containing detailed allegations of sexual misconduct against comedian and actor Aziz Ansari.  All too many of us have felt trapped in dates gone wrong, held in place by a combination of social embarrassment, reticence to hurt someone's feelings, fear of further harm or a lingering hope that the other person might read our verbal and non-verbal signals and stop what they're doing. What use would an app as oversimplified and binary as Legal Flings have in this circumstance?  Consent isn't just an unequivocal yes, it's a social process. It's the safety to say no or not now, maybe later, not like this, I'm tired or let's watch Thundercats and the confidence that such signals will be respected. Adult relationships require adult responsibilities, listening out for non-verbal cues, having difficult conversations and above all being willing to subordinate the urgency of your own desire and ego to another person's need for comfort and respect. Sound too difficult? Well, there is a tech solution to that. The sex bot.


Hi everybody it's Sam at Mixed Up Craft. Thank you for watching my tutorial today.  So the idea is is that you die cut all of these letters but you leave a tiny bit of it still attached to the card so that you get this effect.  So I'm going to be showing how to make this one but I'm going also show and talk you through this style as well because the dies that I'm using are stamping up the letter dies and I just wanted to make sure that people that don't have those dies but have other letter dies can still create this style card. So to make this one here I've used these one inch dies. So when I talk you through this one to get this effect you can do exactly the same but with one inch dies two inch three inch whatever letter dies it is you've got you can use any but that's what I use for these ones here so that's these here and I'll share any links as well that I've got and basically you can see when it opens up that's where it's cut on the back okay and then it just lifts it up and it's attached to the top of the card. So I'm still going to decorate this one a bit more but I just thought I'd bring that in just to show you what I've been doing. Okay so the one we're going to be doing today is this one here the papers that I used for this one are the free principle downloads from Trimcraft it's their Easter papers that they've done I'll just bring it up there you get the little bunny I've just added some glitter on there as well and hoppy Easter I've got a nice little play on words there as well and again this one stands up the difference with this one is I've put um card on the back here and I'm also going to put another piece inside here because obviously you want to be able to write your sentiment because that's obviously where it was all die cut it just doesn't look so good so that's what I've done to cover that up but I'm going to go through all that now. Okay so you're going to need a piece of main card here which is three and one eighth of an inch by eight and a quarter so it's the standard width of a four card um and then it's just cut down to um six um did I just say three and one eighth it should be six and one eighth of an inch actually let me just bring my scoreboard up just so I know I'm getting them right yes six and one eighth of an inch by eight and a quarter okay then you will also need two more pieces which are eight and a quarter by three and you want two pieces and these are going to be the bits that will stick inside just to make it look more appealing to the eye and then for decorating I've already gone ahead and done most of it here but this matted piece here you'll recognize this paper if you watched my live Facebook live um a couple of weeks ago and I done um I used these downloadable papers from oh gosh um I can't remember the magazine I'll put a little link up now um but I printed them all off and this is eight by two and three quarters and you can see what I've done here because I've put this mesh kind of ribbon along the back first then I've put this brown craft card over the top and then I've put the word Easter there as well and then I'm going to get some of these same rabbits which I fussy cut and I'm going to put a couple of them along the bottom here as well okay so that's the decoration for this card so what you want to do first of all is yeah you don't need the scoreboard at the minute is just grab a ruler and a pencil and along the side here you just want to mark it three inches in now bear in mind it's six and one eighth of an inch you want to mark it three inches and it will all make sense as to why we've got that one eighth of an inch um extra piece here when we get to it but just mark it three inches at the top and at the bottom come up a little bit there okay and then just draw a pencil draw a pencil joining up those two dots like so okay then you'll notice here I've wrote the word cut on one side and I've just put a cross on the other again just do that so it makes sense when I'm talking to you through the tutorial of what bits we are see doing what bit with okay first of all you want to grab your um your die so whatever ones you're doing so I'm going to spell out the word hoppy again along here so just need to make sure so the side where I've wrote cut okay that is the side that we want to put the dies on okay so that should be the three inch side and the three and one eighth of an inch side will be this one here okay so then you want to line up your word basically so in my case it's hoppy this would be good though obviously if you've got happy because you'll have happy Easter happy birthday happy Christmas um any kind of um you know holiday um the word happy fits really comfortably along this width if you've got smaller again you could even if you've got smaller than one inch you could probably have happy birthday running all the way along the top this is a five by seven card but again if you're doing the card this size and the shape that I've got you could easily have happy birthday running right the way along the top so it's just a really nice fun um card to do so just making sure the letters are all the right way up now what you want to do this is the crucial part this pencil line you want to have a little bit of it showing through the top of each of your stamps um each of your dies when you lie them down so I'm going to lie it down just put a bit of washi tape on and then I'm going to bring it up closer so you can see so just taking off some of that sticky from this particular washi because it's quite strong I'm just going to pop that in place another piece there as well and if I just bring this one up you can see that the pencil mark is just inside that I can see it you need to be able to see it you want this to have the very bottom part of whatever letter or whatever it is you're die cutting it needs to be this side of this pencil line it's the most important part of this process and my mum when I was showing her this we had such a giggle and in the end after her third attempt she almost threw the cards across the craft room because it just you have to get this right so this is something that does take a lot of concentration um it is a little bit not fiddly maybe the word I'm not sure it's just you have to make sure that that piece of the bottom part of whatever die is is slightly over this side of this pencil mark okay so that is my H then I'm going to go along and put my next letter in place again you can kind of now if they're all the same height you can make sure they all line up with each other at the top here and then you'll know that you get a bit over but always just make sure you can see a little bit of pencil so again I'm confident that that one's in the right place and then again my P it's about it's literally maybe like two millimeters over that pencil mark so put my P and then because I've only got one P which you will do anyway most of your die sets I'm just going to put a pencil mark there just around that side I'm going to put the Y in place and I'll show you then just to make sure it's all going to line up so I've got a feeling I'm going to move that P a little bit over to the left a bit more pop my Y again making sure a little bit of it's there then take this one back off you want to put it the other side of that pencil mark and I can see it's too close to that Y so I'm actually going to bring it further towards the O about there redo my pencil mark again very pushing down very lightly so it's all easy to rub out and then I can move the P and that is now a much better spacing between my letters so I'll pop the P back get that one cut like so and then I can go back and put it in place in a minute okay let me just bring this all up a bit so you can see the bottom of every one of these letters is just below that pencil mark and the rest of it is all on this piece basically what's going to happen is when we put this through the machine got to place it in a particular way with the plates in a particular position but when you run it through the die machine it will die cut all of everything that's on this side of this pencil mark and this little bit that's overhanging on this side will not cut and that's what keeps it attached to the card and that's why it's called partially die cutting so this is the bit now where my mom she I get saying to her you're not listening to me and we were having a right old laugh because she done it and then she just went oh damn it you know and and I was going to see you haven't done it so everything you want cutting goes between the plates anything you don't want cutting sticks out at the end of the plates now the other reason why I've done this and it works so well is that this is using a A4 cutting machine I have the tattered lace A4 cutting machine and my mom has the A4 spell binders cutting machine again this one here will go through the smaller cutting machines like the big shot which is commonly used so again I've tried to do it so that even if you don't have this size die cutting machine you can still create this lovely partially die cut card okay bottom plate and you've got the piece here and this is what we want cut you're going to bring it right up to the edge of the plate and you need to line up that pencil mark with the top of the plate meaning that that little two mil will hang out at the top so if I just lie that down like so put my plate over the top and then what I'm going to do is bring the plates up put the plates down so they're completely flush and then I can line up the pencil mark from corner to corner and I can see the top of those letters poking out from the top so if I just now bring that you can see there those letters all poking out at the bottom so now I know when I run that through the machine all that's going to cut is everything sandwiched between these plates this tiny little bit that's not will not cut okay so bringing my mum's big one and pop it in and then keeping making sure this does not move I'm pinching it so tightly between with my other hand it's nice and squeaky and again before you even get to it just rearrange make sure you're happy okay so now I'm going to remove carefully my letters and take that one off take that one and the P which I need to put down again and now you can see that they are still connected because they haven't cut past that pencil line so again I'm just going to pop the okay so just get rid of all of this take off that final one now just going to rub out this is going to be covered anyway so I'm not too worried okay now we can just pop out all these other little pieces now you'll see with this H I've got this bit here because it's still attached and I need to remove that piece there so all you want to do is grab a metal ruler and your cutting knife oh gosh that was uh not very good let's come on down let me just pop that one back in so just sit that right over line it up with the pencil mark the ruler with the pencil mark and then just cut that tiny little piece you just want to remove then we can rub out again all of this okay now what we're going to do is create a score line because obviously we haven't burnished this yet and you know I've done it so it was cut this side will be three and one eighth of an inch just because now you're going to score right at the bottom of the cup piece so you're going to start scoring along here which is slightly further down than where the original pencil mark was so roughly where you will score now will be the exact center point and it just means now that when we fold it in half you'll have a nice equal-sided card so basically you want to be scoring along the bottom part of every letter where the the cut the piece that's cut finishes so like so I'll just bring that up now you can see where I've just scored that line you see it goes along the bottom at every single cut letter which is just below where the pencil mark was probably should have left the pencil mark there first and then scored it so you could see but the pencil mark originally was slightly above that okay and now what you can do is just very carefully fold that all down then on this side just go along and burnish very carefully all the top pieces there of that card do not burnish the actual letter again my mum she said oh I don't mind if you say all this in your video but she then went and burnished the letter and then that meant the letter folded over and it kind of then you know you lose the look of the card because now those letters are really firm and rigid and they're not going to fold and bend over do not bend the letters just burnish and fold this piece in between but there you have already a really nice card so the effect and the result is brilliant it's just that little you know you've really got to really concentrate with this one to get you know the perfect result so now it's just all down to the fun stuff of cutting it all sorry decorating it all so these are the two pieces which are three by eight and a quarter and basically I'm going to stick one underneath here and one over the top and it just gives your card visually it just makes it a lot more cleaner and so forth so I'm going to get that all stuck down so just turned it upside down fold this piece back over like so and just put glue around the letters so all the parts you can see there don't put the glue on the letter otherwise you end up sticking it down so it's everywhere in between really concentrate around the edges because obviously that's what really matters and then pop this piece over down here on this side and then bring this down on top of it okay like so and then bring it back up again and you can just make sure but that measurement will give you the exact piece like so and then on this side now you can put glue over all of it and that last piece will go nicely over the top and like I said with the bigger one the only reason I've done it on this is because it's obviously a shorter card and those letters it the back of it did really stand out but with something like this where the letters are smaller and it's such a large background you can still easily write your sentiment there but if you do want to cover it just do exactly the same as I did and just measure this exact piece of whatever size card it is but like I said that was a five by seven for that one and I think that still looks so nice it just gives it a completely different overall you know look okay so flip that over let that all set and then I just need to decorate it so that piece was already cut down which is going to go the right way don't know if I gave you the measurements for this so I will just tell you again it is two and three quarters by seven and seven eighths of an inch I've already put my tape on down again when this goes on it will give you a nice border all the way around again I absolutely love these free papers I think they look so good like so and then I'm just going to pop a few little bunnies on the top okay I've gone a little bit different there actually and I've just put a couple because I love this paper so much so I've put one just stuck on the top of the tee there and I've got this one kind of coming down from the oh some little hopping bunnies so there you have it and then open it up you've obviously got that nice inside to write your sentiment I'm going to put a little happy to stamp there and from the back there it looks obviously much nicer as well on the envelope there you have it this is a eight and a quarter by five card so you have here eight and a half by five which would be the closest measurement so you'll need a piece of paper that's ten and three quarters squared and you're going to cut your first line at four and one eighth of an inch you could also do if you're worried you know if you're maybe not I don't know some people their results on this can be you know they're not they're not always too sure you could also do five and a half by eight and a half which is a piece of 11 by 11 and the first score line is at four and a half okay so there's two envelopes you could do on this which would work for this one as well but there you have it so that is using obviously those stamping up letters love them think they're so good but equally as nice is this one here as well which is that little bit smaller but I've got lots of room we're going to do something nice still there as well which you'll see in the pictures so they have it so I hope you like the Easter card for me today the partially die cut just type that into youtube and you'll see lots of you know other partial die cut cards using butterflies and just any die that you have you can use it in this same way so I hope you've enjoyed it I hope you learned something new um I hope you're enjoying the series and uh yeah please hit the thumbs up button and subscribe to my channel to see more thanks for watching bye


hardware with open source chip design. Who here in the audience uses Linux? Please, a short sign of hands. Feels like almost 100%, I would say. Okay, 100% of people use Linux. So who of you uses it on open hardware? Please, another show of hands. Yeah, that's not too many. Who of you would like to use it on open hardware? And I guess that's why you're here. So I'm glad that we have Drew Fustini here, our new speaker. He's an open source hardware designer and embedded Linux developer and also the vice president of the open source hardware association. And who better to tell you how to run your Linux on open source hardware? Please welcome Drew with a big warm round of applause and have fun with this talk. Thank you very much. Thank you. I'll skip past my introduction. It's Congress, so probably most people are familiar with open source. So before I jump into what open source hardware is, just wanted to frame it in the context if people aren't familiar with open sources. So examples that are Linux. Apparently everyone's running Linux in this room, which is great. Underneath the Android, there's Linux as well. Libre Office, which I used to make this. Presentations also open source. Firefox, the web browser is open source. So we're probably all very familiar with open source software. And open source refers to something that you can modify and share because the design is publicly accessible. So with software, we're talking about that you can inspect and modify and enhance the source code. So in the terms of, when we talk about open source, there's a couple of different terms that people use. They might use free or Libre or open source. And those do have different philosophical backgrounds. For the purposes of this talk, I'm going to conflate those terms, and I'm just going to refer to it as open source hardware. Though some people use the terms free hardware, Libre hardware, open hardware, but I'm just going to be using the term open source hardware for this talk. So open source hardware is hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell that the design or hardware based on the design. So this is a definition that we came up with about 10 years ago at an event called the Open Hardware Summit. People that were making hardware projects we got together and tried to come up with a definition of what we wanted it to mean. So I mostly do electronics, though open hardware and open source hardware is more than just that. It can be mechanical design, basically any physical object where you have design files that you could share. But just to give you an example, in the context of electronics, what we're talking about is the schematic, the board layout, and then the build materials, the parts list. And we're not just talking about an output file like a PDF or a graphic file of the schematic or Gerbers for the board layout. We're talking about the editable source file from the CAD software, so something like Eagle or KeyCAD. And then one of the things that's good to do with the build materials is if you want to enable other people to be able to build your project, it's good to make sure that the components are available in low-quantity. This isn't a strict requirement of the definition of open source hardware, but if you want people to build your project and it's important to make sure that they can build it in low quantities. So how many people have heard of Arduino? Okay, a good number of people in the room. So Arduino was a microcontroller board that was created at a small school in Italy over 10 years ago. And it became super popular because it was good enough at the time to do a lot of different interactive electronics projects, and they shared the hardware design and the code on the internet, and it just kind of achieved critical mass. A lot of people took it and modified it for different projects, different use cases. At the beginning, I had a link there to the slides. Also, if you pull up the talk page, there's a link to the slides as well. I have a lot of links in these slides. One thing that's interesting is there was a documentary back when Arduino was starting about the team. Just wanted to check out to see what things were like when that was starting. So one of the most popular Arduino boards is the UNO, which you see a picture of there. So how do we know that the UNO is open source hardware? Well, if we go to the Arduino website, we can see that the design files from EGLE, which is the CAD software they use, is there, and we can download that zip file, and it has the schematic and the board layout. Now, when we're releasing our design files for a hardware project, we need to choose a license. And there's a lot of different options when it comes to licenses. One is the Creative Commons suite of licenses. So one common one, you might see people use the CCBY, means attribution, and then share like SA. One thing to note is if you add the non-commercial attribute, then that makes it not open source. In the slides, there's a link to a good blog post that kind of explains why if you add non-commercial clause, it no longer conforms to the definition of open source. Other people use things like copy left licenses or reciprocal licenses like GPL, also permissive licenses like Apache and BSD, MIT, and then there's licenses that were created specifically for hardware projects, one of which is the CERN open hardware license, which I wanted to talk more about specifically. So CERN, the physics laboratory here in Europe, they have a open hardware repository. So they're developing these electronics, and actually there was two great talks here at Congress from a couple electronics engineers that work on the electronics there. So they're building electronics for their physics experiments, and they want to share that with other labs around the world. So they have an open hardware repository, and as part of that, they created the open hardware license, and kind of give some background on this. One of the people that runs the team there is Javier Sereno. He gave a cool interview that's linked in the slides where he talks about their motivation behind this and why they have the open hardware repository and created the license. Though this can get kind of confusing, there's not just licenses, there's also copyright and patents. At the open hardware summit a few years ago, Ari Douglas gave a nice talk about this, so you can find that talk in the link there in the slides. He goes over what might be good for your project depending on what purposes you're trying to achieve with your own project and kind of goes over a lot of the different options there. But what's the whole point of all this? So the reason you might want to make your project open source hardware is that you want to enable collaborative development. So we're talking about the idea here is that you're going to share your design files and you're hoping other people will help contribute to your project, contribute to the design of your hardware. So I would say that's like the main reason to release the design files for your project as open source hardware. If you're not interested in other people collaborating on your project, then it might not be the right thing for your project. So it's good to consider whether or not you want to have other people contribute to your project. So I mentioned, or was mentioned at the beginning, I'm part of the open source hardware association. So we're a non-profit based in the US. But though we do have board members around the world, we have Matthias, who's one of our board members in Vienna. I'm actually based in Berlin now as well. So one of the things we do is we host the definition of what open source hardware is. We also have things like best practices guide, a checklist that you can go through to see if you're releasing all the things you need to for an open source hardware project. But the main thing that we do is we help organize this event called the Open Harbor Summit. And that's going to be coming up in March of 2020 in New York City. So hope to see some of you there if you can make it. This will be our 10th one. So we started in 2010. This year, though, we decided to do something a little bit different. So we had Open Harbor Month. So the idea with this is we wanted to have people from around the world do locally organized meetups and talks and workshops. That kicked off with one in some in Vienna and Colorado in the US. And it was really cool. We had 40 events in 14 different countries. And we'll be doing it again in 2020. So hopefully, some of you can get involved with events wherever you're located. And if you're wondering what happens at the Open Harbor Summit, you can check out the talks from our last one, which was in 2018, to give you an idea of what happens there. And kind of some insight into the different sorts of projects people are doing. I do a lot of electronics, but there's a lot more than that. There's people that are doing science and art and design, all sorts of different things. One of the other things we do with the OpenSource Hardware Association is we have a certification program. So this is a self-certification program.  And then you get this logo that you can use. And kind of one of the value of this, if you're making a project is you can put that on your packaging or I put it on the silkscreen on my board. So then people can really easily identify that it's open hardware, and then they can go to that website and they can type in the ID number and be able to pull up the page that links them to the documentation, the design files. And then for people that are looking for, like, I want a certain type of device and I want to find one that's OpenSource Hardware, if you see this logo, you can go and look that up in the database and find out more about it. So if you're interested in know more about the OpenSource Hardware Association, you can go to ashwa.org. You can join as a member of the association. We also have a mailing list and a forum. If you want to check us out on Twitter, the OH Summit is the open hardware Summit account. We have a lot of activity going on right now about that because it's coming up in March. In our executive director, Alicia Gibb, who's one of the people that started this summit, she wrote a book called Building OpenSource Hardware, and it has essays from different people that have built open hardware projects. So it's a good thing to check out if you're wanting to see what different experiences people have with that. So the point of all, the main theme of this talk was about Linux on open source hardware, which is my two favorite things. So one of my favorite projects was developed by Bunny, who gave an awesome talk on the first day here at Congress, in Sean Cross-Obs, who's giving a workshop right now on the FOMU. So this was a completely open source laptop, where everything, including all the electronics, were open source. And at the time when this came out, like four or five years ago, it was a pretty decent system. I have one and I used it for many years. So this was a really cool idea of having a laptop that I can use every day that's open hardware. And it had some cool features like an FPGA and a software-fine radio.  So Lucas from M&T is there. He has this as a completely open source hardware laptop, the electronics, the mechanical design, everything. So I recommend you go check that out. It's really cool. It's in the CDC area, which is the critical decentralized cluster. So one of the other things I'm involved with is Beagleboard.org. So we're a nonprofit organization that helps design open hardware computers. That is everything for people from makers to students to even professionals that are designing into their projects. And what we do is we work with different manufacturers and we also work with the community to come up with designs that are useful. So this started off with the Beagleboard back in 2008. So this was kind of the first low-cost arm development board. And back at that time, a lot of people were needing arm hardware to port their free software and open-source software to ARM. And the board was pretty popular for that. We followed it up with a little of our board called the Beaglebone, which fits into the Altoids tin, if you've seen those mint tins. If you've probably used the Beaglebone, you're probably most familiar with the Beaglebone plaque, which was, I would say, still our most popular board. So kind of the theme here is because it's open-source hardware, there's a whole bunch of different Beaglebones made by different manufacturers with different features and different price points. Like Seed Studio decided probably most people don't care about HDMI, so they took the HDMI off to save some cost. Aero wanted to make one that worked with industrial temp, so they it's a little bit more expensive, but it has industrial temp components on it. And then one of the things that's important with open-source hardware is we want people to be able to take the design files and make derivatives. So we have this smaller one called the Pocket Beagle, and the cool thing about this is it's a pretty simple circuit board. It has something called the system and package that integrates a lot of the chips, so it makes the board layout really simple. So this is just a four layer circuit board and it's available in Beagle and also in KeyCAD, and if you have some experience, like if you go over to the hardware hacking area, you can learn to do surface fun assembly and with a little bit of experience you could order the board, order the parts, and build your own. Or as Kumar did, he wanted to make a logic analyzer board, so he took the design of the Pocket Beagle and he added on the features he needed, like the inputs for the probes, and he also added in gigabit networking. So this is kind of cool to see people take the design of the Pocket Beagle and then modify it for their project, for their use case. And then here's an example of the logo. So the latest board we had was the Beaglebone AI, so we registered that back in the summer. So it's US because it was registered in US as country code and then it's 169, so it's just like a sequential number. So it's easy for people to identify if they go to the GitHub, okay, it's open source hardware certified and it links off to the page on the database with information about it. So I wanted to mention Aliemex, we're here in Europe, and in a Bulgaria is one of the best open hardware companies in my opinion. And they have a line of open source hardware linux computers called the Olinux we know. And the person behind Aliemex, Fetin, has a great blog post about open source hardware and why it matters to them. So a few years ago they wanted to create a 64-bit ARM board that was completely open source and designed in KeyCAD, which is free software, open source circuit design software. And Fetin gave a nice talk at FOSDEM a few years ago about the process of them switching from their proprietary CAD software over to KeyCAD and designing this open source hardware board. So and then if you've not heard of KeyCAD before or KeyCAD, it doesn't really matter what you say. Some people say KeyCAD, some people say KeyCAD. But it's open source software for designing circuit boards. It's cross-platform, it runs on max windows and linux. And one of the cool things about it now is developers, there's developers at CERN that are working on it, and the project leader Wayne is now working on it full time is this job. So it's cool to see a lot of the developers now being able to do it as their day job. So it's kind of getting critical mass in that way. And if you want to try it out, I'd recommend if you search on YouTube for getting the Blinky. It's a nice tutorial about teaches you how to go through and make a little board that Blinks in LED. So Ali-Mex took that board that they designed in KeyCAD, the Olinux Wino A64, and they wanted to make a laptop with it. So that's called the Terus one. And the design files are on GitHub for it. So the idea there is to make a modular laptop that people can put different boards in and things like that. Another interesting open hardware project was the Chip, which you might have heard of. It was billed as a $9 computer. They had a really successful Kickstarter back in 2015. Unfortunately, the company went on a business in 2018, three years later. But the cool thing about it was it was all open source hardware, the schematics, the PCB, the bill of materials. And if you see here, there's this really cool thing called the pocket chip, which was this nice like handheld little Linux computer. It was really cool. But the company went on a business which was unfortunate. But this one person, Christopher, he goes by GroGuard. He designed his own board that plugs into the pocket chip. And if you click on the link in the slides, you can see doom running on it, which is like always the demo that you show with a Linux system. Then you went and designed this other board, which is pretty cool. So this fits into a popular form factor for microcontroller boards called the Adderfruit Feather form factor. And this is a full Linux system. And you can, it's fully open source and there is a crowd funding campaign for it that happened earlier this year. So one of the things I also wanted to talk about, especially here at Congress, is the idea of open source and FPGAs. And then I'll tell you about how that plays into Linux. So one of the really cool things that's happened over the last couple of years, and many of some of the people here at Congress have been a part of that, like Clifford Wolfe and David Shaw and other people have built free software tools that allows you to not have to use the proprietary tools from the FPGA vendors. Kind of wrote an overview of this and recent issue of Hexspace Magazine. You can download the PDF for free if you want to check that out. And one of the talks at Congress a few years ago was from Clifford Wolfe. So this kind of all started off with this one FPGA called the Ice 40. And he wrote, kind of over time wrote different pieces of software that you need to be able to take your design and put it on to an FPGA. So that was for a part called the Ice 40. So that was Project Ice Storm. And then a few years later David Shaw primarily helped develop open source software that let you put it on to a more capable part called the ECP-5. And then most recently there's a there's Project X-Ray and another project called Symbol Flow that's been working on bringing open source tools to higher end FPGAs, these Xilinx Series 7 FPGAs that are going to add a lot more capabilities. So why is this important for Linux? Well, if we have an FPGA that's capable enough we can put a soft core in there and then we can potentially run Linux on that soft core. So Greg is here at Congress and he designed this really cool board. This also in the Adafruit form factor called the Orange Crab. And actually yesterday he got Linux to run on it, which was really fun. So this is an open source hardware board. You can download the designs of the board and it's using a soft core in an FPGA to run Linux. One of the other boards came out of Hacker Space in Croatia, Radeona. That's also using the ECP-5 FPGA and that's capable of running Linux as well. And they're doing about to do a crowd funding campaign now. So you can check that out on CrowdSupply. And then David Shaw was one of the open source developers. He created this ultimate board called the Trellis board, which I think would be probably pretty attractive for running Linux. I think it has like a gigabyte of DDR memory so it's a pretty substantial system for running Linux. And it's open source. You can download the plans and build it. And then recently back in November there was the Hackaday Super Conference and every one at the conference got this badge, which was kind of like this Gameboy form factor, but it has the ECP-5 FPGA that allows us to have a soft core on there and run Linux. So kind of some different options of open hybrid boards that are using soft cores in FPGAs to run Linux. And then one of the people over in the open FPGA assembly here at Congress is a pretty cool picture. So I was talking about like a soft core. Well, what does that look like when it's in an FPGA? So this was kind of a cool picture of what it looks like when all those different gates are laid out inside the FPGA to have a Linux-capable processor core. So one of the ways that we do this is so we talk about a soft core. Well, how do you make that? And one of the important pieces of software that all these boards I was just showing you use is a project called Litex. So this is a pretty interesting way of creating a system on chip inside the FPGA and actually uses a Python based language called MyGen. And if you're interested in it, I would recommend checking out this blog post from Bunny where he talks about the advantages of it.  So you can take those pieces of IP and put them together for what you need for your project. And then in terms of the soft core, we can one of the things that Litex gives you is the ability to run a risk five soft core. So that project is called Litex on Linux or Linux on Litex. And that's what the orange crab is using and the hack of a badge and those other projects, the radio and a board. That's how it's running. There's a couple of projects that are doing similar things as well. But Linux on Litex is one of the ones that a lot of people are using. And a screenshot of what it looks like when it boots up. So I was already kind of talking about risk five a bit. And if you're not familiar with it, you've probably heard of like x86 until x86 or ARM. That's an instruction set. It's the instructions that the processor executes. So you write code, it gets compiled into instructions that run on the processor. So risk five is an instruction set that came out of the University of California, Berkeley. And it's a free and open source instruction set. So anyone can take this instruction set and implement it in a chip, like in an FPGA or actually make an actual silicon chip. So one of these examples of this is there's a university in Columbia and they decided to make their own microcontroller based on risk five called the OpenV. So this was really cool. It was a completely open source chip. The design of the whole chip is open source and it can run the risk five instruction set. However, it's not quite good enough to or it's not capable enough to run Linux, unfortunately. It's more meant for microcontroller applications. Another organization is called Low Risk and they were kind of founded with the idea of being able to create a risk five based system on chip that could do something like be a basic smartphone. So they're still working on that, but I'm pretty excited to see what will happen in the future there. One of the people that started Low Risk is Alex Bradbury and he gave an interesting talk a few months ago about the future of operating systems on risk five. So I recommend checking that out if you're interested in like the ecosystem of the tool chains involved and things like that. So similar to Oshawa, there is a organization for chip design called FOSI which is the free and open source silicon foundation. And they do a great job of pulling together all these different projects into events. They have one called Orconf which happens every year here in Europe. They also have a conference now in the U.S. called LatchUp. That's going to be coming up in April at MIT. They also host a website called LibreCores. So people are designing this open source chip designs or IP blocks for things like Ethernet or memory controllers. And they created LibreCores as a site that you can share those. And so if I'm going to build an open source chip, I can go on there and find different blocks for functionality I need. There was also an event earlier this year called the Week of Open Source Hardware. So this is all hosted by Fosse. They have all the talks online from these conferences if you want to check them out. So one of the companies that was founded by some of the people that created the RISC-5 instruction set is called Sci-5. And they've actually produced a few commercial chips, one of which is this microcontroller here. And one of the co-founders in CTOs has an interesting talk about the RISC-5 ecosystem. And so companies like Western Digital have decided to switch all the cores in their drives over to RISC-5. And NVIDIA has decided to take all the little micro controllers in their GPUs and turn those over to RISC-5 as well. This is a microcontroller board based on that Sci-5 micro controller, which is quite interesting, but unfortunately we can't run Linux on it. So one of the surprises last year at FOSDEM was Palmer from Sci-5 debuted this board called the Hi-5 Unleashed. So this is a multi-core 64-bit board that can run Linux. It runs it really well. The one downside to this is it was meant to be an evaluation board. So it's quite expensive. It's $1,000. So they're not going to ever make it in volume. So a little disappointing. But the other option there, so there's these high-end boards like this one. It's kind of expensive because it's made in low volume. There's also some cheap microcontrollers. One is called from Kendrite, the K210. It is basically a microcontroller with a lot of memory. And there is possibility to run Linux on it. So at Linux Plumbers this year, one of the people from Western Digital gave a talk about running Linux on this kind of essentially a microcontroller. You can check out that link there. There's a talk about it and there's slides from the conference there. Also, in the Linux kernel, they started adding support to be able to run Linux on these RISC-5, essentially microcontrollers. It's not great, but it's kind of like we're going to have to work what we have. We have to work with what we have right now. If you're interested more in more about how Linux runs on RISC-5, then you can check out this talk from Hotchips a few months ago. And it goes into how the Linux kernel works on RISC-5. And the other cool thing is both Debian and Fedora have initial distributions now for RISC-5. And if you don't have hardware like that Unleashed board, you can still try this out on your computer using an emulator called QEMU. So one of the things that's like two weeks ago at the RISC-5 summit in California, NXP announced that there's going to be a chip early next year that's going to be a Linux-capable SOC. So this is quite exciting. This could allow us to make like a board that wouldn't be too expensive and be pretty high performance. So one of the things I want to hopefully maybe be a part of or encourage people to do is make a board that's less than $100 that runs RISC-5. One route is we use FPGAs. Another route is maybe when this chip comes out, that'd be a possibility. And then could we do it by the next CCC? I don't know. If you're interested in this, get in touch. I would like to try and get a community effort going around this idea of making a RISC-5 board that can run Linux. So I don't know if I have any time left, but happy to take questions. Thanks, Ro. Yeah, we actually do have some time left, actually about 10 minutes. So if you do have questions, pile up at the microphones that you see here. And we start with a question from the internet. Sure, take your time. Just start talking into the microphone. Yeah, why is the microphone of the signal angel not working? All right, we just started with a question from microphone number two then, while the signal angel is working out his microphone. There you go. Hi, is this working? Move close to the microphone, though. That's new. It is on. It is on. Hi, thank you very much. Thank you very much for the talk. I've been having a lot of fun using your pocket beagle in combination with the Bella system. Actually been able to get it on stage on the Royal Albert Hall earlier this year. And one of the things I really enthused about that project is that using the Xenomai real-time operating system, it really seems super be a bridge between like the low latency performance of a microprocessor and the octopus connects to everything and low entry to development of Linux world. Have you seen more of these examples using Xenomai or other things? Yeah. So just to give people that aren't familiar with the terms, a little bit of background, Xenomai is essentially this co-kernel that runs alongside Linux and allows you to do like real-time tasks like in this case, audio, like low-latency audio for instruments or other things like doing motor control. The Linux kernel developers have been doing a lot of work of getting the Linux kernel to run great with real-time tasks, but it depends on what your deadlines are. So for things like building instruments, those are pretty latency sensitive and Xenomai is a little run route of doing that. So if you're interested in other projects called machine kit, it's an open source CNC controller. They similarly have deadlines like having to read a motor encoder or send out pulses to a stepper motor. So I think it really... So with real-time things is what you're talking about. It really depends on what your deadlines are like. So in the case of Bella, they're still using Xenomai because they need to be... They need a certain minimum latency that they can still only achieve with that. But I will say, with the Linux kernel, there's been a lot of work that's been going on. And the Linux kernel is much better than it used to be in terms of handling real-time tasks. OK, cool. And if you're interested in Bella, I think there's someone from the team here in the room. So yeah, you can... Yeah, the person identifies themselves here. All right. Thanks for the question. Thanks for the answer. Let's have another try with the internet. Is using open source software hardware design required or enforced to get the open hardware certification? Yeah, that's a really good question, which I probably didn't clarify enough. So according to the open source hardware definition that we have from Ashwa, you can use whatever software you want. One of the reasons is for certain types of things, especially like mechanical design, proprietary software is still the norm. That's also the case with circuit design. KeyCAD has only really gotten really good and stable probably in the last five years. So kind of as a matter of practicality, 10 years ago, most people were still using proprietary software to design mechanical designs and software designs. Ideally, I think, if the idea is you want to enable collaboration, using free software, using open source software would enable as many people as possible to be able to contribute to your project. But it is not, according to our definition that we have hosted on Ashwa, but it's not a requirement. So I'd say best practice, use free software, but it's not required. Thanks. Microphone number one, please. How far is the performance for everyday computing on risk five? Like, can I run my everyday programming tool chain on a risk five processor? You could run it, the one downside to the soft cores on these FPGAs. So like the ECP-5, which I mentioned, it's only running at maybe 50 megahertz, 100 megahertz. One of the reasons I brought up Simpliflow in Project X-ray is that's going to enable us to use open source tools on these higher end Xilinx FPGAs, which will unlock greater performance. Still, with soft cores, it's going to be, if you're looking to be competitive with like ARM and Intel, it's not going to be there. But one of the cool things you have to think about is an FPGA. So you have a lot of flexibility, like in terms of the peripherals you can do. You know, so kind of getting creative in terms of, well, maybe the clock speed is not really fast, but it's an FPGA, so you could add hardware accelerators to do things that you might otherwise be burning cycles on a processor to do. But that's also why I'm hoping people will start making chips. I'm excited about that NXP announcement, because yeah, like, we need silicon to have like the performance that we're used to on like ARM and Intel. Thanks, we have yet another question from the internet. Do you think it's feasible to create a package manager for open hardware, like PIP or NPM? That is a good question. And I think one of the things that I would say like, open hardware is almost kind of like 20 years behind open source software. And I think one of the reasons is a lot of the tools that people use for designing hardware, it's difficult to collaborate on designs. You know, a lot of these CAD programs, like, it's not the same as like source code.  So I think one of the issues we have is for people to collaborate on hardware, like we need better tools that allowed us to track changes and do pull requests and merges in a more meaningful way. So I'm sure everyone here that's used CAD tools and tried to work with our people, it can be difficult. So I think that's an area that can be improved. In terms of like hosting things, you know, I just talked to someone today that talked about the open source hardware observatory where they were trying to like collect lots of different projects. So I think we can definitely have like websites that like show what projects are out there. But in terms of like being able to like collaborate on things, like LibreCores, check out LibreCores, they're trying to do that as well for processor design, being able to go on there and like grab either a internet controller or a memory controller. In a way, actually, chip design is almost better because if you look at the hardware design languages, it's more like source code. But yeah, CAD is difficult to collaborate on still, I think. Alrighty, microphone number one, please. During your presentation, you mentioned that there are several great projects trying to develop software for FPGA, for commercial FPGA devices. I was wondering if you are aware of any project trying to develop open source FPGA architecture, something similar to RISC-5, instruction set, but for FPGA world. Right, so yeah, the other thing here is, so we're talking about open source tools for getting things on to FPGAs, but there's also the idea of like the open source chip design. So don't, personally, I've not heard of any like projects where they're trying to do like an open source FPGA. But I think if you have time, stop by the open FPGA assembly and also over in the hardware hacking area, Tim and Tim Ansel and Zabs are over there and they know a lot about things that are happening there as well. But I think it would be cool. In Bunny's talk here at Congress on the first day was about the idea of like using FPGAs because they're more easier to inspect. And if we can make like an open source FPGA chip, I think that'd be even better. Another question from the internet, please. What about performance per watt? I'm sorry? What about performance per watt? With risk five or FPGAs? Both, I think. Both. Yeah. Probably FPGAs are not great with that because as compared to an ASIC or a silicon design, they're not as power efficient. Risk five, I don't know. I've not seen a whole lot of numbers around that. I think it's still kind of early days when it comes to risk five. Also like a lot of it's still soft cores and FPGAs, which are not gonna be as great in terms of power. But there is a project out of ETH Zurich, the university called Pulp, P-U-L-P and it stands for Parallel Alter Low Power. So that's a family of risk five cores. So check out Pulp from ETH Zurich. I think they're trying to do low power things. Good question though. Microphone number one. Yep, thanks for the great talk. So as you mentioned, there's a lot of NDAing and copyrighting going on in the hardware world. So one of the slides you showed showed the risk five core with an XC4 interface next to it. So my question is, do we have all the components, the peripheral components to make a full processor on open source or is there still gaps in there? I think there's still a lot of work to be done there and that's something that Lidex is trying to do to pull together these different IP blocks that you need to build a system on chip. Same thing with Libre cores. But if you take a look at sci-fi, not everything, so the core is open source but in order to tape out a chip that had a certain functionality, like not all of the IP on there is open source. So I think that's something that hopefully in the future is more people start doing open source IP for chip design. We can hopefully have all the different blocks that we need to make a chip. Like one of the things sci-fi is missing on their chips is USB. Traditionally people will get like USB controller from mentors and ops or something like that. So having good verified proven IP for these common peripherals is important. So yeah, it might be an open core but then it might have proprietary blocks around it. So there's a lot of room there for improvement I think. And with that we're wrapping up. Thank you very much for all of your interesting questions. Also thank you very much for all the angels working here. Thank you very much to all the people from Messer Leipzig, the audio video people who worked. And of course the biggest thank you again to Drew. Thank you very much for the awesome talk. Another big warm round of applause please. Thank you.