He'll be moderating a panel this morning that is going to be talking about some of the non-financial industry uses of blockchain technology. Alright, so hello everybody. And by non-financial, every time somebody is talking blockchain nowadays, they seem to be talking crypto. And by crypto, I don't mean cryptography, which would normally be what people mean by crypto at least a few years ago. Yeah, that's what normal people mean by crypto. It's cryptography. The thing is today everybody uses crypto for cryptocurrencies and then crypto mining and then all the things we're not going to talk about today. So let's get this over. Cryptocurrencies, ICOs, trading, cross-border payments, remittances. I've said it. That's it for today. We're going to be talking about a whole lot of different things. So I've asked four panelists to come here with me and discuss their experience in working on projects that are not strictly related to payment using the blockchain. If you're aware of how a blockchain works, you can use that as a database that allows a group of people, entities that don't necessarily trust each other to work in a trusted manner between each other nevertheless. And that trusted manner allows all kinds of interesting applications way beyond the pure financial world. That's what we're going to talk about today. So let me... I'm going to be doing a little bit of reading here. So in no specific order but the one that I wrote the stuff in, the first one will be Shankar Satish and he leads... Where is Shankar? Please come up to the stage. Shankar leads the AI and data science efforts at Manulife's Research Lab in Quantitative Investment Management and Insurance. Insurance is interesting. We're not going to be talking too much about investment, right? Before this he was a computer scientist in academia and at startups where he built AI and machine learning systems for the autonomous robotics and manufacturing industries. So I'm counting on him to share some experiences in particular in the use of AI and things like that and possibly how it links to blockchain. The second speaker panelist will be Vinay Mohan and he is a management consultant by trade and currently leads Consensus in Singapore and in the wider APAC region. He specializes in delivering enterprise-grade strategy and operations and has worked for global clients in a number of locations and industries. I'm hoping a lot of those are not finance industries. And he's a keen admirer of all things decentralized and working to enhance the blockchain ecosystem and economy in Singapore. So, welcome. Next one is Calvin Cheng and he's a full-stack software engineer with a current interest in data science and distributed ledger technology. He helps SG innovate a government-backed venture capital fund with talent hunting using data and software in his own time. He designed and built all kinds of mobile and web apps for fun and profit. Their current work revolves around DLTs. Anybody want to know DLT or not comfortable with the term DLT? We're not talking just blockchain here, right? You know, hashgraphs and things like that. So his work revolves around DLTs like hyperledger indie fabric quarter hashgraph. And I have a microphone. Yeah, but that's one of the four ones of my panelists, so I still have an issue. If we can have one more. We only have four. We will do time sharing with the microphone. If we can only have four, we'll handle, right? We'll do load balancing. Okay, the last one is Jonas from Daimler. So he holds a diploma in computer science and Japanese studies from the University of Bonn. His main focus topics are metadata and data quality as well as neural networks within Daimler where he currently works. He previously was in lead architecture roles for finance systems and various leadership positions. He's taken a keen interest in new technologies and the open source movement. In his current role, he's shaping the blockchain and DLT activities from the technology perspective with Daimler as a member of the governing board of the hyperledger. He's also representing that role internationally. Okay, so thank you very much. So what I want to do, we're not a huge... We're going to try to make this as interactive as possible. Let me first distribute microphones. Jonas probably will share a microphone because I'm sitting next to you. That's okay. All right, so I have a few questions that I wanted to ask the panelists, but more importantly, if you guys have questions, just raise your hand and shout the question. We'll repeat it for recording purposes and we'll tackle that first. But the first one I have has blockchain become a buzzword. Are people doing blockchain because it's blockchain? If I look at the companies that I work with, roughly 80%, they're doing blockchain because everybody else is and they don't really know what it's going to bring them. So that's kind of the buzzword type thing. I have about 10% of the people who are doing blockchain that have a reasonable idea of why they're doing it and they're doing it because they're already doing some existing process, but they want to optimize it. They want to make it faster, cheaper, more secure, disintermediated. And that's how the computer industry has been working for the last 50 years, right? Every time there's been a new revolution when we went from data center, well, mainframe to client server, all the system integrators had a field day moving everybody to client server. Then when we went from client server to distributed, we did that. We had also the workstation phase. Remember workstations, right? They're dead now. And the next revolution is IoT, okay? But right now we're at the blockchain space, which is going to power the IoT world. So that's those 10%. And there's the last group of 10% who are doing blockchain to change the way the world is going. And these people are really exploring blockchain to create new ways of doing business, new business models, new applications that are not possible without a blockchain, right? And these people sometimes they're doing this project on a blockchain just because they know that they'll get funding for it because of the buzzword aspect. But I like to ask my panelists if they see that as well and how they feel that. So I'll start with Jonas and give him the mic. So the short answer would be yes. The long answer is a little bit more complicated. So usually as we started with the blockchain thing usually you're very alone in the beginning. And you say, there is a technology and you can do stuff with it and I don't know how far it can go, but we can do something. And people would say, ah, nobody needs that. And then it's a buzzword and then everybody comes to you and if you have a little bit of knowledge in it and says we have to do something with blockchain. And you're like, okay, what do you want to do? We don't know, but it has something with blockchain. And then there are these cases where you engage in discussion and they have even an idea, you know, I want to have one central database where I can store people that's not the right case. There are also the cases where I think, yeah, that's definitely a use case for blockchain. And then there are these cases where I first thought and even thought that topic and thought, yeah, stuff. So stupid, you cannot do it. And then after a few discussions and a few days later I thought, wait a second, there's a thing to it and I learned something and maybe you can also apply that topic to it. So it's a very interesting time at the moment and it's a buzzword, yes, you can do a lot with it, yes. Will it save the world? Maybe in some parts, will it change the world? Probably. Will it change all processes? Coming? No. So I have it, having lunches with old friends. Actually, I just had lunch with them. And in this lunches, we have a lot of techies, a lot of technical friends. And a lot of them are building apps, of course. And they are building communities and marketplaces. And a lot of them are interested to continue building the app on blockchain. And when I ask them why, they say, oh, we need a token for our own marketplace. And when I say, do you really need a token for your marketplace? They'll say, well, that's one way of raising money. Because we can raise money easily through ICO. And I think people, they were adjusted by the way that they are approaching their marketplace token through different utility rationale. But at the end of it all, the bottom line is, why don't you just accept IAC? Why do you need IAC to be converted to a token in order for it to be used in your marketplace? There will be a lot of complicated answers given to that question. It's always interesting to have lunch with friends and just talk carefully. And the conclusion is always, hey, actually it is an interesting use case to use token in our marketplace. And we see it as a way to raise a cheap or free funding. And we are not out there for cashback, unlike the rest of the people out there. But after enough lunches, I'm wondering who are the ones that are going for cashback? Because everybody says they are not going for cashback. So, yeah. Hello. Is blockchain and the main ground in the first world and in the first, as the code certainly is, the key difference is I think we, as they justify it, and it is far more understandable to have first and only one set of paradigms than a lot of others before it's time for a couple of reasons. First of all, look at how mainstream blockchain is evolving, right? And even though BLP is continuously computing and Apple has been an evolution, a linear model for the last 20 years or so, Bitcoin, which really kicked off this whole bunch of mainstream blockchain adoption, came from a pseudonymous party called the Pagoshir on the motor. They orbit whatever, whoever that wants. And it seems to sort of solve a very foundational social construct or social problem, or the technological problem. So as opposed to machine learning or AI or other paradigms which are more linear, I would say blockchain is more foundational. So the buzz that you see today is extremely palpable and I think it's quite understandable because it touches so many facets of civilization as not just about financial services but about efficient marketplaces. It is about solving the problem, because it is a 7,000-year-old problem in the history of human civilization which is about to be addressed. So I would say that it is probably understandable and partially justified in my view. And there's always going to be four more ideas. You always have this theory of missing out to be in blockchain, be in robotics, be in new ways of investment and in automotive security, whatever it is. Human greed is always going to follow this. We are always constantly going to the next steps that we can set up. But with blockchain, I think there's a far more far-ranging implication with the sort of buzz. Go. Yes, it most definitely has become a buzzword. And for me, a buzzword is a word which starts out as a technical term and eventually loses that meaning and then it begins to simplify a whole umbrella of things and I think blockchain is certainly easy. However, I do think it is an intimately important innovation that we engage in and for many of the same reasons that you just mentioned, actually. And so the foundational and I think more under-appreciated factor when we discuss blockchain technology is often the economic incentive that plays. And that is how we have now managed to turn human greed towards sort of in our favor collectively. And that is kind of why I'm not a huge believer of having blockchain products succeed if there is not money involved, right? And that's one of the collective things that we all realize is that we can design and have money and we can achieve some really amazing things. The other result of this blockchain explosion has been that now public blockchains are the world's largest department of cryptography. But with cryptography, it's been mostly restricted to research and limited development is a real burden to things that are sophisticated and so on. But that's kind of been the extent to which we deploy in actual cryptography. But blockchains are now our chance to have massive development of cryptography. And as a result of that, a lot of the mind-share and the formation is now moving towards cryptography and security. And you know, security is one of those areas of what it has always been. If you work in security, it's kind of a time-to-job where if you do your job well, nobody notices you. And you're at the end of the line that it gives you to work. And now because people are buying cryptocurrencies and storing them, there is now something to do for the public for the public to know how important security is. And you know, losing money is the fastest way to learn. And that's kind of what's happening at a massive scale right now. And I would say sort of the blockchain in part is now acting as a way to promote the of a lot of cryptography and diversity concepts which are sort of very nice to hear in an academic setting but did not sort of have a place in sort of practical everyday use and in big amount. So for me, one of the signs that slowly out of the buzz phase is when people stop using that name to justify or sell a project. And just to give you an example, because that's kind of my segue into looking at non-financial applications for blockchain. There's another buzzword at this time which is really strong in Europe by the way. It's called GDPR which is the general data protection regulations for all entities doing business or having presence in Europe. So it impacts the whole planet that's trying to deal with Europe. And so everybody is doing GDPR now. And I have a customer that came to me that said, we want to build a GDPR solution. Okay, that's fine. And we want to do it with a blockchain. So, you know, I take a step back and I say, so okay, a blockchain is interesting because we can use it to track all of the transactions which will be events happening on the private data. So for example, when an employee has, I don't know, their passport number that changes, they have to be able to modify that wherever it's being used because there's a right to modifying your data part of the GDPR. So when you want to modify that data, you make a request to the privacy officer, to the data officer, to the HR person, whoever is your contact and that request should be logged and then tracked. So you should know when that request has been sent to whoever needs to process it, when it's been processed and then you should be told that and if somebody needs to audit it from the outside, they should be able to look at all those transactions and check that they've happened in the right kind of timeframe. And that's a very nice use case for a blockchain but honestly, you know, it's an event tracking system. People have been using event tracking systems since we have events to track, so decades, and we've been doing that with databases. Actually two years ago I built an event tracking system for a bank in Switzerland and they were using Cassandra to do the event tracking between entities, right? So I look at them and say, I mean, you can do this with a blockchain. A blockchain is a nice and elegant way to do it but you don't have to use a blockchain for that. So why do you want a blockchain? And they look at me and say, well, because our companies, investors want the company to look at the tip of modernity and we will get funding if we do a blockchain project. Okay, so we'll do blockchain, right? But that's because it's still in the buzzword phase, right? You wouldn't hear this if somebody came and talked to you about doing a Java project. 20 years ago, people would do a Java project because it was the buzzword of the day and another 20 years ago it was AI and, oh, wait, it still is now. People are still, it's again, right? But we have these phases. So what I'd like to explore now using that example of a GDPR solution is what kind of uses of blockchain have you seen out there that are not related to ICOs and getting money or transacting money, but more on using the blockchain as an infrastructure for doing trusted interactions between... Unfortunately... Examples. I have a very big company and this big company has a lot of use cases. I can give you, not all of them I can give you, but one I can maybe explain is it's a thing of trust again. So in the world where maybe I sell you something and I sell you something and give you the invoice for it and you should pay me by means of going to the bank and tell me, okay, this bank, this bank account number and eventually I don't get the money. Why is it happening? Because somebody is actually getting this kind of invoices and fortifying or counter-finding the bank account number. So this is fraud. And since a lot of the invoicing nowadays is still very, very manually or it's automated with AI but the AI is more or less just reading the number and just giving you the money then doing a transaction. And the question we had is how can we, what can you do about it? So think about an open ledger that has my name. I sign it with my personal crypto key. I say my name. This is my bank account number, maybe on a company scale and it's open. Only one has the truth and it's distributed and everybody shares the same view on it because you want to have it distributed. You want your bank account number rightfully recorded and then if you are going to be to give me the money or other way around then before you look at this open ledger and see, okay, this is a spectacular amount and I don't look actually at the invoice I just use this one. And this would be an application I think it has something to do with trust and it has something to do with like public information that should be anyhow somehow recorded. It's kind of linked in of account numbers bank account numbers that is also trusted. Something like this could be done with blockchain and has nothing to do with a token. So in relation to what Jonas has said I think one of the most interesting project out there right now is called Hyperledger Indeed. For those of you familiar with Hyperledger it's not just IBM's Hyperledger fabric nor bands by the end but there are many variants of Hyperledger. Hyperledger Indeed is actually a identity centric decentralized layer and that's a foundation cost-offering organization that runs these nodes Hyperledger Indeed is you can think of Hyperledger Indeed as an sorry you can think of Sovereign as an implementation of Hyperledger Indeed and what it does is that it allows multiple organizations to run their own nodes and validate identities of individuals without needing individuals to store their identity on a central database or even on the ledger itself so it does that by using zero-knowledge proof cryptography and so that actually changes the entire way identity is being done on the internet right now so to me it's a very promising and a very interesting take on logics all of you should be very familiar with what's happening now with Facebook and Cambridge Analytica so the world of decentralized ledgers and the world of centralized authorities like Facebook and Google which we all depend heavily on for our digital identity is on opposite spectrum and human race is very interesting because we live through cycles and the pendulum now is swinging towards the other end there's no right or wrong I'm not here to pass any moral judgment but it is what it is there are episodes in human history where centralized power is cold and important and right now the pendulum is swinging a little bit back to a decentralized world across the political spectrum so I'm not here to judge where communism is good or that's good I'm just here to illustrate that hey there's a lot of interesting projects on DLT's and hyper-ledgerity is a really good way of implementing centralized identities with a W3C endorse new way of identifying individuals using DID if you're doing centralized database you'll be very familiar with UUID so DID is the direct opposite of UUID you get a unique ID but it is essentially collision resistant as well and it is global it doesn't rely on the fact that your issue UUID that you make ID so that coupled with zero knowledge proof cryptography it's going to change the way that people are able to identify themselves online it's going to change how ANL and KYC is done so that you can safely send money across the world without revealing unnecessary information you then are truly in control of your own information but let's say it is a complicated method to manage your own information which is why people become lazy and work hard that is cumulation and rely on third party services to manage your information for you so whether the the population can actually learn to manage their own information safely that's a different topic but zero knowledge proof for identity is interesting from a zero knowledge proof for identity is also interesting from a GDPR perspective because you're never giving out private data but you are proving that you're not going to be able to manage your own information because you're not going to be able to manage your own information for private data but you are proving your identity be very careful and photography usually the proof is okay but if the implementation is bad then there's still a thing to it and then you still have the law in Europe where the right to be forgotten and if the implementation was just bad so we have to be very very sure about that kind of implementation I mean we have this even with hardware where the implementation I don't know from which company was so bad that nowadays in Estonia they had to like spread all of the systems there so if you look at blackchains they can step back and look at the features of what a good blackchain might look like and for me a good blackchain for all the purposes of the Ethereum even though consensus is a protocol of plastic company that is Ethereum we have moved from a network economy or we are moving from a network economy which the internet facilitated to what is now called a shared economy which blackchains are going to facilitate and three you need a beautiful truth there's only one version of that truth so it's completely immutable it has to be true for all of us you don't need or you cannot rather have central intermediaries we don't want to go back to the 7000 year old system of hardware centralation to dominate and control and power play with arbitrage and that sort of thing and most importantly you need a way to bring adversarial stakeholders together sharing works when we can find a basis to agree with one another that's the key thing that blackchains are trying to solve or that's the beauty of this whole paradigm so those three features considered think of use cases such as governance tracking tracking global assets that run across global supply chains that are highly temporal which means they pass through different stages of time and exchange hands hands that don't necessarily agree with one another shippers, buyers, sellers suppliers, intermediaries, processors all of these agents that drive modern commerce truly for dollars happening every day these agents don't agree with one another and we have banks for example you know to be the intermediary to that so problems tracking is a very interesting use case on project and consensus has a very few dozen on-follies concurrently at any point in time one of our most recent ones is a product called bind you can look it up it's a problem tracking solution and there are many others in the market as well basically what problem tracking solutions do is they enable a common in which all of the different parties regardless of what they do or where they stand in the supply chain can reference a common database so you have a single golden source of truth nobody can dispute anything else because in a conventional world where your database and my database are two separate solvable environments you and I can collude or you and I can choose to dispute and that leads to the problem of efficiency it leads to reconciliation issue that delays but with a blockchain with the atomic settlement aspect which is either a yes or a no right now not p plus one or p plus two this dispute mechanism is almost negligible because it's nearly eliminated and the need for reconciliation is nearly eliminated so problems tracking is one you know self-suffering entities is a great new application in the world of blockchain how can you identify yourself and protocols like Ethereum give you the infrastructure to place that beautiful truth and make sure it's scattered across thousands of nodes all over the world making it mathematically feasible to hack because you know the building of the door is sitting right now it's the worst because no one's hacked into it smart contracts are being acted for the blockchain and self-suffering so problems tracking identity systems very interesting end for this one final point consensus just announced two days ago a project called word shoe poker organization for the longest time gambling has been dominated by the house imagine if you can have a truthful way of the four of us playing poker to verify whether it's provably actually correct so completely opposite example it's making ripples around the world so think about any application that means peer-to-peer, immutable truth and golden source of data and if you look at provenance tracking it's the core of the supply chain transparency type of platforms if you take supply chain transparency and add a feature to it like smart contracts you actually get enterprise automation free every time you track an activity on your supply chain you can trigger a smart contract that will trigger activities and sequence your supply chain this can either be used to tap into ERP systems like SAP or replace some of the functionality so that's a game changer it's another area where the disintermediation that blockchain brings is challenging historical ways of doing things right do I need an ERP system now such a complex system like SAP where integration with other system takes years or can I just use a blockchain and have everybody talk on the blockchain and that will trigger operations to for example if I order a batch of 1000 phones that automatically triggers the provisioning of storage in the next warehouse and things like that so that's a way that a blockchain will change the way we do business and interaction between companies consider the fact that blockchains are extremely good at creating a mutable append-only log so you can append anything to a log and you can never change it and blockchains are the best implementation of the best way to provide the guarantee now consider that in light of the principle of the right to be forbidden so if you go and add your customer information into a blockchain and then you receive a letter from a lawyer or even from the customer asking them to erase all of the data from all of your systems and from all of the second party systems that you are using as well and one of those things happen to be a blockchain that you insert into the data and you kind of short yourself in the code so not only is it difficult to use blockchain but it's possible unless you go to some like Accenture use their editable blockchain no please no it is something to bear in mind and what the GDPR is doing is bringing to the forefront what a lot of people who have been sort of deeply embedded into the computational advertising and you know, at the industry sort of knowing their hearts is like a toxic asset so once data gets out of your position it's close to impossible to control who's going to do what with it and who's going to transmit it there and who's going to get sold what's going to happen and then the GDPR quite interestingly written by a group of non-technical people who talk through with a philosophy in the tradition of philosophy that a lot of lawyers have when you read it and then you start to realize that, you know, as a business maybe now you have to start thinking about not just becoming a data-driven or a data science industry but also consider the fact that even if you succeed in your sort of data science endeavor the fact that you are amassing all of this sensitive data and all of that is so the question really is how do you still sort of provide services and do computation while avoiding this liability and let me just sort of hint and stay back after the panel is going to hear more details but you can do things like secure multi-party computation which is essentially a sub-branch of cryptography where what you can do is you can compute functions across multiple parties with that data never leaving said party and each party having no clue about the existence of other parties so, you know there are sort of solutions in cryptography that kind of budding and it requires a lot of thought but a naïve customer data, put it in a blockchain and then you can audit it will probably fail if you end up in the courtroom so that's how I can beat the fact that it's either that open mind and I put that in okay keep in mind that a blockchain while it is a database it's not a general purpose database in which you store everything it's more a database for storing transactions so these transactions can point to data that's stored elsewhere and when you need to delete the data you would delete the data itself and you would put a transaction in a blockchain that data is not there anymore and that resolves the gdpr issue you have a traceability that something has happened to the data and the data has disappeared from where it was stored so it's not accessible anymore but it requires not storing the data in the blockchain itself so we have three minutes for sort of closing comments I would just like to, okay I don't know, I mean like in terms of integrity what's the deal here we cannot change the blockchain but we're going to fork it because the price drop 50% that's just what your opinions are so if I can't speak for the foundation that I represent the community that made that happen but I believe what did happen was a consensus based really stages of the technology and it was done with the spirit of saying look we did not invent a theorem for somebody to walk away with $60 million so there's two things that I think as public perception has been against one is first of all the blockchain did not get hacked it was a poorly smart contract that stalled the current execution of a certain transfer of money which allowed the thieves to walk away with the 60 million unfortunately there was a moratorium of 30 days before which the funds could be taken out of the system and it was hard for within 48 hours it happened through consensus by community personally I'm not really worried about that I think it is controversial because of obvious reasons that somebody says this is decentralized but who gets to choose that you know you can hard fork it but it was a community decision it was not the back of one individual a group of people it was a community-based consensus it then classic still exists as another book you know I'm not I'm not going to try and defend that I'm not going to say that that should have never been done for me this is a fragile early stage it will go through some sort of feeling troubles it is not going to be free of its implications but that remains that we have to look at a larger picture of it I'm not overly concerned about the controversy surrounding that to be honest I mean I find my I find it a little bit weird when you talk about immutability well where is the immutability when you report so maybe that's a little bit sloppy language and you say you can't change the more correct language is to compute the cost of change and that's something that you can compute in terms of dollars compared to any other technology that cost is multiple orders and there's another aspect is that because it's a distributed ledger any change to the ledger is immediately detected by everybody so you cannot change it in a way that it would surprise people and happen without their knowledge and that's also a key element if there's another trail somewhere an admin can modify a record and nobody is the wiser with a blockchain that is just not possible reasonably possible knowledge, there's no such thing as a crack in information flow in the world so as far as people who understand decentralized ledgers are concerned they understand that that's just a small percentage of the rest of the equipment the real problem here is that terminology has present connotation and definition and those terminology are interpreted in a particular context across a particular spectrum so if you say that decentralized ledger is going to take the world and we peer to peer I don't truly buy that because it is a spectrum of governance by the way at one extreme you have authoritarian decisions by singletly everything all the way across to having a community in the side of it but even a community actually is a centralized entity if you think about that it's not registered in any company registry but a community is a fluid definition of a group of people who govern something so is it truly decentralized now if you stick to the strict definition of decentralization well a community is not decentralized I mean there's also a lot of very interesting and philosophical aspect in terms of what is pretty decentralization and do we don't need any intermediaries anymore and so on I think there will still be aggregators and there will still be a lot of people that rely on services of others and don't want to run their own stuff and so on and also you have to think of only a function of time for a certain time it will be mutable so the data is stored somewhere but think of if we would have started a blockchain with any five patches we would probably have some alternative realities right now or yeah of course it's part of what we need there's something to charge to whatever or five whatever then yeah you might also have something there so it's only it's a myth like tool mutability is a myth but at least for a certain period of time okay I guess so one thing is clear here we could continue this discussion for another two or three hours and we still have new subjects to cover and new types of applications to cover unfortunately we're already running three minutes late so thank you first of all to the audience for having listened participated and to my panelists for having provided such insight into applications of blockchain I want to leave you with some homework go google something called the CICDA project C-I-C-A-D-A it's people who are trying to build a government infrastructure on a blockchain think can I trust my government can all the decisions are made by my government being monitored openly on a blockchain with all the citizens participating that's another application have a look at it it's really interesting and I'm not involved in the project at all thank you very much thank you all


Gene Adams and colleagues argue that population interventions that require individuals to use a low level of agency to benefit are likely to be most effective and most equitable. This article was authored by Gene Adams, Oliver Midden, Martin White, and others.


Hello, everyone. Yeah, can you hear me? Yes. As Shane introduced me, I am, I'm Kyung-Hye Kim, and I'm working for over 17 years for Princess Comfort Alliance as electronics. So I am very, a little famous in Korea, but maybe everyone here don't know me yet. Have you ever heard about post-life before Shane and Helio introduced? Oh, yeah, thank you. Post-life is now very famous in Korea, but globally it's not famous, so it's a good opportunity to introduce you guys about post-life. And there is a sewing game is my colleague, and she will introduce post-life demo after me. And we are not sisters, but there are too many games in Korea, so you think we are sisters. Just a colleague. Yes. Post-life is really, really good tool for open source compliance. I explain about post-life briefly. Today I would like to talk about post-life open source project. The presentation is divided into three parts. First, I introduce explain what post-life is, and then we move on the automate how we can automate compliance using post-life. And last, I explain how we can automate security using post-life and conclude this presentation. This is the open source policy and process. It's over 15 years. And as it has been establishing open source policy and process based on Linux Foundation's guidelines, but there is no suitable tool 15 years ago, so we made it. And we needed a tool like Red Star Shores. So as it developed its own tool in 2014 and has been continuously upgraded every year because the process is changed and improved. And in 2021, we open sourced this tool as post-life with the intention of contributing to open source compliance industry and making it easier for other companies to automate their processes like LG. And post-life is named to signify becoming a light for open source compliance, free open source software, and light. If you have any questions about post-life, please visit post-life.org. You will find a list of information on the topic. And you can visit the demo site using this site, and there are many, many documents, and you can find the YouTube content of post-life. Post-life YouTube content is better than my presentation. And post-life consists of scanner and hub. Post-life scanner is a tool that scans dependencies, source code, and binaries. While post-life hub is a system that manages everything related to open source. We automated the open source compliance process in the hub using scanning the result, which says open source BOM, open source bill of materials. And after using post-life hub, we are making the open source software notice and package. I explained this next slide. And post-life hub manages all about open source, license management, open source management, and vulnerability management. As Helio explained that if we started the open source compliance, but we can manage the security vulnerabilities also, and compliance process management, and supply chain management is necessary. So we use the supply chain management using post-life hub. Last one is export management. Post-life hub has many functions such as export management. For example, we can compare to software BOM using project version one and project version two. And post-life scanner consists of pre-check and dependency checker and source code checker and binary checker. And we are using the many open source tools such as pre-checker use is reuse. And so scanner use is named scan code and scan with this open source. And dependency scanner use is a lot of dependency package manager open source. And as it has a lot of specific platforms such as Android and Yocto platform, so we make a platform specific scanner post-life scanner. So we are open or post-life scanner. It's the Python package and you can use it anytime. Post-life hub is a kind of web service to provide open source compliance. We believe that post-life hub is an essential tool for open chain component program. We get the open chain component program. Thanks to post-life hub, such as red lines, we can achieve the open chain spec. So I think it is very good to use, very good for your open chain components. Now it's the compliance automation. This is the, we followed the four step process based on Linux Foundation's guideline to ensure compliance with open source license obligation when developing software. First time is the identification stage. The development team analyzed the open source component used in the software. For example, post-life scanner or other open source scanners or commercial scanners, anything is good. We use a post-life scanner and after analyzing the open source component, we can get the OSS-BOM, open source software bill of materials and it is reported, post-life report type. In the approval stage, the open source list is sent to OSPO, open source program office like us for review and confirmation of the correct license and associated obligations. And this result is on open source BOM again. And in the notice, step three in the notice and verification, and the development team create an open source package and by gathering the source code that needs to be disclosed based on license obligation. After verifying that, the package has been created properly. We review this one and OSPO generated the open source notice. Finally, in the distribution stage, the open source package and notice generated by OSPO are distributed to the designated site. For example, opensource.ag.com, that's done. And this allows customers to view to the open source component used at opensource.ag.com. This is the process of open source compliance and we are automated using post-life scanner and post-life hub. And here are some ways to automate compliance with developers. We are using Jenkins and post-life pre-checker. Here are some ways to automate compliance with copyright and license attribution rules. I think the most important thing is that for developers to check open source component and license by themselves, not OSPO, not other compliance managers. So developers push the source code and Jenkins is operated and repository checker, post-life pre-checker, lint mode means that post-life pre-checker checks. The source code has the right information about copyright and license. So check the license and copyright writing rules and if it's not compliant, developers make up the source code and again, same and compliant okay, it's good. It's the Jenkins example but honestly, we are not just demo so we didn't adapt yet. But our goal is to adapt this one to all source code repositories. And this is another example of post-life scanner. I mean after push the source code to repository and Jenkins is operated and open source BOMs are generally automated, generated and mailing the BOM compared to post-life scanner people and after and reporting to developer and mailing it. Yes. And security automation is, I explained this one. Lastly, let me briefly explain the method of automating vulnerability management using post-life based on the open source BOM we have analyzed. Post-life can automatically send an email like this when new vulnerabilities are discovered in the existing project. I mean vulnerability is changing every day so we completed the one open source project developed and one day the vulnerability is now come and you can develop, can receive this mail by new vulnerabilities coming. And we can adapt this one Jenkins also similar to compliance automation. Vulnerability management can also be automated using Jenkins like this. Post-life scanner and post-life hub API. Actually, post-life hub provided less to API so we when push the repository check and we use the post-life hub API, we can the vulnerability information also. Yes. And as I explained everything about post-life hub but it's the summary of the features provided by post-life hub in addition to open source license management and compliance management, vulnerability management and you can see the supply chain management. Actually, we are using this function supply chain management means that if we get the software from other third party software, third party company and we can get the open source list and we register the post-life hub and we can their open source BOMs and open source vulnerabilities as well. Yeah, that's my end of my presentation and we show the post-life demo. My name is So-im and I will show key and simple demo using post-life. First, I created a project in the events and let's see the identification tab. We can enter open source information and in identification tab and I entered open source information which will include it in my software and you can also upload a scanner result in SPDS format is okay and if you use a post-life scanner, you can upload a post-life scanner result in post-life hub and you can enter the open source information by third party or source or binary and if you go to BOM tab, you can see all the open source information from another tab and you can check the license obligation and also you can check the restriction. If you click our icon, you can check which restriction exists in this license and also you can check the vulnerability of the open source. If you click vulnerability icon, you can see the CVE IDs of that open source and you can also click the CVE ID, you can check the vulnerability information in more detail and let's move on next step. If you entered all the open source information in identification tab, you can check the open source list to be too obligated to disclose source code and after check the list, I uploaded the source code for disclosing and then let's move to notice tab. You can issue the notice for license to licenses are obligated to notify. If you click preview button, you can see deferred html format of notice. There are open source information and it includes license text also and you can select the report notice type various formats like spdx or html or text. Yes, of course, you don't have to do anything else for making the notice and but if you want to hide open source version, you can check those things, you can modify it on the system too and let's move final step distribution. This step is not released to open source version yet but because yes, you can upload issued notice and source code to public site so that users can download those files. In case of edgy, we upload those files to opensource edgy.com. In this case, if you go to opensource edgy.com, you can see the notice of those models like this and customer can download those files and so far I showed how to manage open source compliance process and vulnerabilities on the full site hub. And also you can check vulnerability information in another separately vulnerability list and you can just type open source name and you can search vulnerability information in here too. And that's all I prepared for today. Thank you. Yes, and so it takes too long time to open these two. I mean we made it since 2014 and seven years ago and we open source. Yes, yes, I think so. You mean the distribution page? I think it is a little hard because many companies are using the other their own distribution site so we have to, we can provide the public API but companies are organizing the different sites so it is really difficult to open the distribution station. Yeah, yeah. Yes. Yes, right. Yeah. And also post-race hub is integrated to other commercial tools such as post-id and bretto. Their scanners can, they are their own report type and they, we are open the rest API so there are two commercial tool companies using our APIs and their result to integrate the input post-race hub. Yes, so many commercial tools, if you're using commercial tools you can request the commercial tool companies to using post-race hub integration. Yeah, actually line plus in Korea uses post-id, I can tell. I don't know, I can tell their information and they requested the post-id company and they made the plugin. Yes, yes. Actually I want to demo for you for developers and self-check is for developers and maybe you can create the self-check in that for developers just to input the, you want to analyze for developers. If your source is uploaded in GitHub or public repository and just click this one and analysis result is uploaded. For example, self-check the other, it takes too much time so I show the other result. Yeah, scanning is, it takes too much time to scan, so I can show the other side. Maybe demo site is, after the analyzing this, developer can check this information and developer can check the OSS information like this one and obligations such as the notice obligation. I mean, it's the function for developers not all sports. So yeah, you mean that it's the internal post-race scanner. Yeah, actually post-race scanner uses scan code and scan OSS, so it already integrated. Yes, you can integrate any other scanners to using this URL because we opened all source code of post-race hub so integrate any, any scanners. Actually in Korea at least adopting the other tool that post-race scanner just the other open source, not open source scanner just the other commercial tool. Yes, government laboratories, yes, not common company, research lab such as, yeah, that's all. Yes, yes, yes, yes. You mean that if you bypass or procedures, right? Yes. If you want to skip or procedures, you can using the self-check list also or yes, it's not automated configuration yet. But many companies want to like you, so we are thinking of this and when setting up this post-race hub, we can check, we can configure, skip each process, procedure, but it is not, it is not this year's roadmap. Sorry. Yeah, yes. Yeah, very good question and a little difficult question also. And actually we think we, the scanning result is proper from development team, but we can check the some, actually we can check the open source license exact one now we just from download location. It's similar to Heria's opinion based on PURL. I mean many scanners result are false positive as you know. So I think the sleeping machine is not important to more days go so on. So dependency check is most important I think and actually sometimes we check the false positive because we can get the result, the source tab and there are source directory and open source component is quite different we can check and we can ask the development team, is it the positive, false positive? Sometimes we ask, but sometimes we skip one. Yeah, so it is not 100% perfect I think. Yeah, yes. You mean that development team input 100 of URLs and how we can analyze this one? Yeah, it's a very good question, it's our secret. Actually the development after we run the dependency check it's almost to cases. I mean first of all before dependency check we have only more 10 or 20 components and after dependency check we can one over 100 component URLs. So actually we have the automatic analysis program. It doesn't open yet. We only use the internally and actually we are using the OIT. I mean URL release input and automated analysis is coming so I can show you. Is it recorded? But I believe you don't distribute the content. Yes, yes. Actually it is for example is the auto analysis. I mean that there are too many URLs so if you use auto analysis and analysis result is coming out. We can using this auto automatic analysis so we save our time. It is the result of automatic analysis and we use the OIT and scan code. Only scan code? Yes, sorry. It's not OIT just the scan code and scan code results that license text is MIT and MIT and copyright through top three so we can register this open source by automatically. But it's not open source yet. Yes. Yeah, thank you. Thank you.


Everybody's here. Two board members are not in person. Tiffany is on the phone, though, and Sameer is on the phone as well. Everybody here can see the agenda, but there's a few other people on the phone. I'm not sure they can see it, but basically we're going to do a quick operational update with some Q&A. We're going to do questions from the board committee reports, and we're going to talk about DrupalConAsia. We're going to get a vote on the infrastructure working group chair, and then we're going to get an update on the Drupal8 Accelerators program. Are there any candidates from the last election to see a letter? Good job, you guys. We're in coordinate. So many of you guys are so engaged, so looking forward to the next election. The first one is that our sales team is now here, and we have a sales person. It's definitely a challenge for that sales team to function the way that it should, but we have everyone here at the con as well, and I think we have some really great folks on the team who are really good fit for the community and the work that we're doing, so if you get a chance to meet Jenner, Mark, not Mark. What this role does is after you have achieved a certain number of interactions on Drupal.org, and that can be comments or commits or group posts, other kinds of activities, you then can be a community, you can get this community role. Recognition for folks who are giving so much to the community. Real human is doing great stuff at Drupal, but people with a community role also get to wave a magic wand and bring other people into the community by confirming them on Drupal.org. So once they are confirmed users, you can leave comments on issue queues, et cetera, et cetera. So they're able to help be ambassadors and bring other people into the community. So we're really excited about that chain of events that's happening on the user role side of things towards that overall roadmap. Highlight for us in the last month is that we launched the Try Drupal program, which is pretty new, and we love this program because it does two things that are fantastic. What it does for us is, first of all, it helps us towards our mission of promoting adoption of Drupal. On the page, you can choose from several partners, and the list will continue to expand where you can start go, and without having to pay for it, start at least a 30-day demo of Drupal.  So we're excited about that from an adoption site, and it's had a really great update. Three-day demo. Is it live? I don't see it live. Well, the program has different words on it now. Start a whole digital demo. Just hang on. We have a minimum monthly guarantee with the CPA on top. If there's more traffic, the more traffic we provide to them beyond the threshold, then we all make money together. So at 700, what we're hearing is that 700 is a higher conversion rate than we anticipated coming out of the gates. So strong beginnings. What just three days? It depends on who the partner is, how long they actually make available. Some of our partners have Office for free accounts, so technically it lasts as long as they want to keep it. But for our partners that don't have that sort of structure of a place, we wanted to give them a way so that they could be a part of the program, do a demo that would highlight the best of Drupal, and hopefully it would be a team for them as well. Something like SimplyTestMe, it's 30 minutes, so we felt like three, compared to more of a developer-focused group like SimplyTestMe. And we're still looking at a couple of partners. Our work to watch list is revenue overall. So we went into 2015 with an investment this year is in the sales team so that we can build strong revenue lines and continue to do programs like slightly lower sponsorship numbers than budgeted, and slightly lower ticket sales than budgeted. Mostly on the expense side, thanks to Rachel who's amazing and we love her. We see a net income effect from that, but you know, the real issue has been on the non-con revenue, so advertising and other programs. We have some things that are totally firing and some things that are not, so we're going to continue to really tweak around the revenue lines throughout the year. The bigger picture is that we have to really rethink our overall revenue model, not just some separate revenue lines, and we're going to start to bring that thinking to the board in June. So we'll have some executive sessions around that, because we'll be sharing some financials that you don't do publicly until they're approved, and then we'll be bringing that out. Our two lowlights are revenue-related. Dennis, the supporting partner program, got off to a slow start with a very distracted and overworked salesperson. One remaining salesperson we had. The general supporting partner program was really good for that. We do have the hosting partner program, which that's the salesperson that retired, right? We just got that person back on board, so we're hopefully can catch up some of that revenue, but some of it just may already be lost for the year.  Those two things are, you know, the not-win. I think the next topic was the board committee updates, right? So they're in the pitch. Yep, I don't know if governance or exact. If you guys have anything you want to add? Wrong, but I guess this is... Yeah, it is me. Same thing for the exact. Is there any questions on that? I have one. Sameer, you're on the line, yeah? Do you have time for a governance call while Matthew and I are in a room together still? Sure. Okay, cool. Let's try to schedule something for... We'll do it in mail. I'm sorry, we should have talked about it on the weekend, but thanks. Other questions? Alright, let's move on to Drupalcon Asia. Well, I'm really excited to announce that we are going to have a Drupalcon Asia. We went from SES, which city was the best one, and I'll go into a little bit more information, but I am not revealing where the location is. We're going to have to come to the closing session to hear that big news. So... Did you just say our condom thing? I'm not done with my presentation! Stood out because it is an IT hub, and most of our Drupal.org traffic comes from there. So we wanted to see what we could do to make that work and bring more people into the project there in Bangalore. We went to New Delhi. We were hosted there, and there was even a camp for us. That was pretty exciting. And there is a really strong Drupal community. It's one of the older communities, long-standing communities in India. It's also the government hub for the country. And then we went to Mumbai where they also have a strong Drupal community that's been growing over the years. And they have a strong business hub. So those are the three cities we evaluated. And when we were there, there was a couple things that we were looking at just to make sure we were mitigating our risk. Whenever we go into a new... what's that? That's a giant point. I know, I just like the picture. We're going to a new country. We don't know really what we're going to be dealing with. We've been doing these events in North America and Europe for quite a long time. So we know what to expect. So we really had to pick a city and a location to help reduce our risk. So these are just a few of the things that we had to consider when we were evaluating. So one, we had to make sure we had a strong Drupal community so we could make sure that people will show up for sure for our event. We wanted to make sure it's attractive and easy so people throughout India could come, but also people from beyond, even for us in North America, we have to make it easy for us to get into that city. And of course we want to make sure it's exciting for sponsors to invest because we really are going to need a strong sponsor base. We know that it's going to attract a pretty large crowd. I think a thousand is modest for a goal. So we want to make sure also that Venue has a good brand experience. There's always that can't be too fancy, can't be too much like being in a basement. So that's kind of the right one. And of course the most important thing is that the venue, the catering, the internet, everything has to fit within our budget. So these are some pictures from our tour to all these cities and I just, like I mentioned before, the community really came out in full force and showed us such a warm welcome and really rolled out the red carpet to help us really understand these cities and the community. So a special thank you to everyone who made it so special for us. And when we were there we talked about goals and strategies. So we did a lot of work with the community in India to decide what we really wanted to achieve if we bring Drupal Khan Asia to India. Some of the things we talked about was that we want to unite the Indian community. Right now they have camps and meetups all over but they never get together as one large community within their country. And then of course we want to connect them with the world for knowledge sharing. We have been seeing a strong contribution culture that's been growing in India. We want to accelerate that. There's so many Drupalers that we just really want to bring them in the path to have them be part of our community giving back to the code. So that's going to be a big focus for this event. And then of course with all these developers that are out there we want to make sure we're growing their skill level so that they are really contributing to the project in very meaningful ways and making obviously great websites. And then there's always the need to connect these developers with employers. And so we feel this here in North America very much that we need to have more talent. They feel the same way in India. They have a lot of initiatives going on to grow their talent pools right now. And then in terms of strategy we're going to use this event to attract Drupal developers to our community and just further grow them into this contributing community. That is the strategy for this event in a nutshell. So like I said when we go into a new country we don't necessarily know who's going to show up. So we have to work with the community to get a good sense. And this is what we are anticipating is that it would be 80% Indians coming from the country 20% from outside the country. We feel that we're calling it Drupalcon Asia to make sure people from whether it's from Saudi Arabia, whether it's from Vietnam, all throughout even China make sure they know this is for them too. And just even talking about this event here at Drupalcon Los Angeles we are already hearing so many Americans say yeah we are going to this one. So we'll see how that goes. It's going to be very much a developer event. We see that with the camps in India as well. That's who they're catering to and that's who we should expect. And so we'll also probably see some site builders. And of course we'll have the CXOs from all the Drupal shops there in India and in the surrounding area. And we might see some CIOs coming to evaluate Drupal. This is definitely not a big marketing event to get more businesses to adopt Drupal in India. So that's not a goal but we might see some people that will show up expressing interest. Every time we go into a new country we have to understand what works for their culture and for India what they recommended is that we have the event starting on a Thursday where we'd have trainings, a business summit, and a community summit. We worked with the community on the price points for training, what's typical price points for them. And then Friday and Saturday would be the keynote and sessions. And again we worked with the community on what's the right price point. So it would start at $50 for Early Bird and go up to $100. And then Sunday would be the sprint. And so since the big focus to get everyone to learn how to contribute is the theme within the content that we provide and sprint mentors and just really end with a strong sprint at the end. And so just kind of in a nutshell, just like to be really clear this event is for primarily developers we also will be seeing site builders, the Drupal shop owners, and the community organizers. We really want to also level up all the community organizer skills and programs so that when we leave they can still work within the community to keep it strong and growing. Things that we're going to evaluate along the way. There's a big interest in having a government summit. Drupal is really big in the Indian government so we want to see what we can do to bring people together kind of like the higher ed summit we had here, see if we can do that in India. And saying, well that's government. So same concept for government, something similar for higher ed. The business community did say they might want to pull funds and do their own PR. So when juries went to the camps in 2011 the community did a PR campaign had some good press. So they're looking to do some of that again. And also right now students who cannot pay, right now we do need to have people paying to come because it's an expensive venture for sure. We're trying to find ways to help students come in and bridge the gap since they won't have the funds so we're coming up with maybe we could subsidize some tickets and some companies might want to step up in that area. Right Mike? Yeah. Okay, so as you can see we started working on the budget and just like with DrupalCon Latin America when we go into a new region, a new country, we are willing to run a deficit on the event because this is our investment in the community. We know that over time as things grow that just like in North America and Europe it will pay off and it will become neutral to profitable over time. But that's not our goal. Our goal is to make this happen. And so we are willing to run a deficit. One thing I do want to point out again ticket revenue because the ticket price in India is so low we are really going to be leaning on sponsors to help make this event happen. So I'm really happy that we have a committee forming that we can go out to the Indian provinces, the SIs. That works going to happen the next three weeks. And of course anyone outside of India who wants to sponsor we would welcome that. So tell you where it's going to be. Racheet is on stage today. Racheet and I have been leading Drupal community in Mumbai for the last five years. I've seen it growing from five percent the first meetup that we did was five percent and you know I was just literally thinking that how we can grow it and now it's like more than 650. Last camp that we did Drupal camp in Mumbai. Mike was the keynote in that. We had participation of more than 650. That was awesome and people are so empty about the whole Drupal thing that's happening. And with the Drupal call coming to India they are really excited and we are really going to rock it. Go ahead Ani. Hi I'm Ani. So I'm Racheet from Bombay. I actually started my Drupal journey a long time ago for the Haramchala project. I was an organizer in Delhi and I moved to Bombay and I found it to be a much better city. Yeah so we are extremely excited. I'm actually looking forward to the government thing so I've been working with people because in India there's a massive push for open source and it was great visiting Australia and Donna's great camp over there. It was fantastic to learn about what Australia is doing and how the Gulf Sea mess is working out really well. So we want to kind of use that to maybe provide policy advisory to the government. We use that knowledge to build a base around Drupal. That and Racheet has actually started a Drupal Campus Ambassador program so the student initiative is underway. It's really exciting and the Drupal Con is definitely going to help. Reasons visited 2011 was a watershed. This is going to be the second one. So when Reasons visited Bombay I think that was the point when Drupal can be started great. And after 4 years and he's visiting again it was a good con. It has to feel good. Let's go. Thank you. Okay who else? I don't want to miss anyone. Sundar. Not professor. I think Reasons visited I had to go on the first stop. So he's been instrumental in helping us understand what's happening in higher education and attended the higher ed summit and hopefully we can take that knowledge and repeat the program. We hope to have one day of higher ed and gov together. Let's see if we can bring up some people from the government as well as other institutions. Thank you. Thanks for all your help. And we have Chakrapani who's from Bangalore. Hello everyone. I'm Chakrapani. I'm from Bangalore. I started my Drupal journey in 2009. I was part of the Drupal camp in Hejabar when Reasons visited Hejabar. And I moved on to Bangalore and I was involved with the Drupal community in Bangalore. I've been organizing a lot of events, sports events in Bangalore. And we are going to have the first Drupal camp in Bangalore in July. Really excited to go to India. That's right. It's exciting. Thanks for all your help. Who's planning on going? Ever we do is going to have the right bandwidth in the venue that we have. We'll have people on the ground to make sure that... It's all kinds of different things in different countries. You need generators. And in how there's so much more logistics. He's an expert. Wherever we end up he's going to advise us. He'll travel to that place. Any other questions? Alright so the next item is the Drupal.org infrastructure working group board chair confirmation. Sure. Since I prepared this nice long speech. So we recently had the chair of the infrastructure working group set down. It was his recommendation that we promote up on Ryan Newton who has been on the infrastructure working group since founding to be the chair. And I say I wholeheartedly agree with this and so I close it to the board that we take that forward to a vote. Doran is a rock within our community in terms of keeping our infrastructure up in performance. Helping us get serious really tough transitions. So I think this is a very appropriate transition to make. I would like to put forward a motion to accept Ryan Newton as the chair of the infrastructure working group. You're unmuted if you're talking. I'm unmuted Tiffany. Try now Tiffany. Oh I said I. Thank you for all your hard work. How do we help move Drupal 8 development forward. We did an experiment at the end of last year where we funded a bunch of core again. I want to thank Wondercraft for hosting them while they were there again. Those developers met together for a week and knocked off some digits worth of criticals from that time and we thought okay this could definitely work. The board got together and helped raise 125,000 dollars from some anchor donors including many of the companies represented on the board to basically serve as a match to the community. So the challenge was to the community was can you match this 125,000 to help us get to 200,000. So we launched the actual public campaign we started funding things in January because we knew we had a base to work with but we launched the fundraising campaign in March. So right now as you can see we're at 194,897 dollars not to be too exact about it. If I refresh $50,000 goals we've only got about $55,000 left. So in just two and a half months that means from the community we've raised $50,000. And that includes the gift that we just got this meet from time of $25,000. So if you divide that amount by our $273 the average gift has been $260 but if you take time out it's $168.15.  I need more. You can't get those anymore but if you go to the Drupal store and you get that t-shirt you are able to round up your purchase and put that to AAA Accelerate. So almost at $300 $0.25 at the time right? So now with people that do round up it was $120 by transactions of $130. So wow. I want to find those 11 people who didn't. She did. I got an email and another one today. Another one today? It's really reflective of our community right? People are giving what they can give whether it's big or small and it's all adding up and it's something that's pretty huge. So I just I love it as a metaphor for our community. So do you want me to talk a little bit about what we're spending on now? If I could just ruin that perfect transition though for one second and just say one thing too just for people to appreciate and understand is that when we got we first talked about this and we had our meeting we were talking about raising $100,000 right? We were going to go for it at $100,000 and credit to Kieran who kind of challenged us and said you know if we're going to do this I think we're going way too low right? And so here we are double that and you know so just I think it's worth recognizing that this is a bigger accomplishment than maybe we set out to achieve too. Yeah and so it's exciting that we've raised so much money. We've got a ways to go but we gave ourselves a deadline. But it's the story isn't how much money we've raised it's the impact that that money is having and I don't think that it is a coincidence that people have looked like this since we started funding and that's definitely been affirmed by the folks who are closest to it and do publish all of the grants that are made and the issues that they address and I think you know this list is pretty impressive so Angie you want to talk a little bit more detail about some of the things that have been funded? Yeah I mean the reports are good you can go ahead and read them but they are kind of Greek to people who don't say like I do which I don't understand why you don't but you know so in that big list are things like performance improvements we're doing a lot of really awesome stuff in Drupal 8 to make performance fast by default which is making really poorly done benchmarks makes us look really good because we're like out to here and everyone else is down here. We're also doing things like playing around with rendering caching so we're doing things like Facebook big pipe where we can chuck the initial version of the page out really quickly and then let the dynamic bits filter in as they have time that's going to really improve the perceived speed of Drupal especially mobile devices and we're also doing things to just fix really bad performance regression so we're really aiming for Drupal 8 to be not only fast by default but fast for both anonymous and authenticated users and a ton of work is going into that to make Drupal 8 really really great in that area we're also finding security fixes because nobody wants an insecure Drupal 8 so that's an important thing that we're doing. Just pat it on the back and tell it it's doing a great job. You're doing a great job. Everybody's like stay married and stay married. Yeah so security fixes we're also funding in addition to just like fixing broken stuff in the Drupal 8. If you're curious of what's left and what we might be finding ahead of talking about yesterday but we're also finding some really great community features like the Drupal CI project which is going to be the next generation test bot that is all based on sort of a standard DevOps stack that we can use to do things like test Drupal 8 in multiple environments so we'll know if we commit a patch that breaks PHP 7. For example we can get that all working across any of our supported PHP or database versions and the cool thing about the way that's being architected is we can expand it later to do things like automated coding standards reviews or behavior development testing or all kinds of other cool expansions that we want to get into. We're trying to really be strategic in how we spend this money, not only big impactful things for Drupal itself but also things that help the wider community as well and really forward. That's my field. So I'll just add my just a gigantic thank you to everyone who has contributed to the campaign so far. I know people have been doing that work because it's a lot of hard work so close. The traceability on that page is awesome. I love the connection between the ticket number, the person, and the funds. It's really really cool. It's very transparent and it just makes people realize that this goes to something. Yeah, so on our staff also just to recognize Elise who's been working with Cork Minners to make all this stuff go. She's brought your work on that. Elise is awesome because she does things that we don't know how to do like write checks and all these ideas. We're just like things need to happen and she takes care of it. It's awesome. Where's my hug? Oh, here's your hug. It's exactly twice as much as we've earned. That's how we roll. Something around 87,000. That's what we've spent. I know if you should talk like a little sprints. Outside that is a small amount. Yeah, it looks like there's lots. It's all there. It's the biggest. Nothing smaller than $500 to $12,000. This is several multiple grants that are large numbers, so $3,000 and $6,000. Let's go forward and we can talk about to change the way how we keep the money out because you said like you spent eight hours to fund somebody for five hours. Yeah, I did say that. How did that change? That's a great question. The last public board meeting we talked about, the way that the grant is set up right now is people come to us and they say I would like a certain amount of money to fix this issue. We always start the grants at $500. We can kind of make sure everyone is a wonderful people, but some people do better with deadline based development than others. We want these things to accelerate and not get $500 and eventually fix something. We were doing a thing where we would get these grants or we would go out and find people and say can you work on this for $500 with some of that happening too because we wanted to be respectful of spending the community's money well, but it was a lot of work. Last board meeting we got approval from the board for those individuals who had been successful with the accelerated grants in the past, especially multiple times instead of making them come back to us every two weeks for now. Can I have this much money to work on these things just instead giving them a chunk of money and for a longer period of time and say just work on critical for 20 hours a week for four weeks. I think that overall has been going really well. I think the challenge has been that they're working on Drupalate more than I'm working on Drupalate and so sometimes it's like whoa! We have to do some work to sync up that. We've been talking on the core committer team about how to better coordinate the efforts of people who are working on Drupalate a lot, whether they're funding through D8 Accelerator or otherwise. But that's sort of separate from the D8 Accelerate process. In terms of D8 Accelerator, I think it's been working well. We can see that line going like this, which before was going like this, so it's been really good. We'll have to meet and kind of revisit. We wanted to let the experiment play out for a month and then kind of revisit and see what we wanted to do. I can't tell exactly how that's going to go, but yeah, we were grateful for the opportunity to do that and try to see how it flew. Andre's been fixing a number of upgrade path issues. Daniel's been blazing forward on views and the API integration as well as multi-lingual issues. It's been great to just trust them to get their stuff done and not have to baby them along and do a bunch of discussion about it. Overall, I think positive, but it is a little bit more challenging when there's larger chunks of time and not quite as much oversight as when they tell you, I want to fix these three issues and you say, cool. Does that make sense? What happens with the rest of the money when we hit zero critical before we burn through it all? That's a good question. The question was what happens if we get to zero critical before we spend all of the money? Well the good news is even after we release eight, we'll find you critical. I mean, even today we have criticals in Drupal 7. I guess we could use it towards those criticals. Yeah, we could use it towards there or we could maybe have a discussion about switching it to quarter critical. There's a lot of things. Once Drupal 8 is out, then adoption is dependent on how it passes. I don't know that there will be though because honestly my intent is to spend most of that money soon because the sooner we spend it, the more of an impact it has on the acceleration of the release. But if we do have a big chunk of money or someone decides to write us a $50,000 check at the very end, it's like awesome, we will definitely find it. No more questions? I think that was the last item. It was. Any other questions in general? About anything else? Do we have another question? If there are no other questions, emotion from the floor or a group photo with our Indian contingent and the board? Good. Alright, thank you everybody. Great meeting. I got the sunglasses. Bye everybody. Everyone say paneer. Three, two, one.  Be there with the crown on. So