There we go. All right. Well, good. So good morning, everyone And welcome to the hyperledger health care special interest group or hcc We have a special guest that will be joining us today. His name is Alex Novot Novotny Is that how you pronounce it Alex? So if not me Alex Okay, I'll just call you Alex Yeah, yeah, but we're thrilled to have Alex joining us actually he was he presented his information Quite a few months months ago, and he's he's here to give us an update on the work that he's done So this is fantastic but before we get started as always a reminder that This meeting as is the case for other special interest group meetings through hyperledger is being recorded And as well we have an inter trust policy, and I'm displaying that now Please feel free to read through it the upshot being it's it's all about being a good person So if you have any questions or details, you feel free to take a look at the URL there for details Well, okay, so before we get to Alex I wanted to go through some introductions For anyone that's new on the call It'd be great opportunity to introduce yourself and and tell tell the group a little bit about who you are What you do and where you're calling from and and Jose and I were talking a little bit a little bit earlier And so Jose do you want to introduce yourself? Sure, I'm Jose I'm from Costa Rica and we're currently working in a healthcare project and We're currently using hyperledger, but we're only a start in the project So we want to look for more information on how the community is doing Oh Great to have you and when you say working with hyperledger, have you picked a platform or using fabric or saw? Yeah, we're using fabric. Yeah, excellent. Oh, well very good Well, great to have you on the call and I'm thrilled to have you join us and and of course anyone else on the call feel free to reach out to Jose or Jose contact anybody else either through through zoom here today, or we always have our Our slack like entity that allows us to To communicate and I'm gonna just I'm gonna move this out of the way here So if there's a there's a little link if you can see it here for our chat channel And that takes you over to our hyperledger chat or channel, which allows you to connect it directly that way too And I see Kent Lau on the call Kent. Did you want to introduce yourself? Hi, I'm Kent. I'm in Hong Kong. I'm a pharmacist and I'm dabbling in hyperledger fabric. Oh Outstanding. Oh fantastic And are you new to the group? I've been AWOL for a few months, but I'm back now. Yeah, I'm trying to attend all three different six. So oh Wow, okay. Your name looked very familiar, but yeah, I hadn't seen you. Well, so so great to have you on the call and Just to make a quick sort of introduction. I know Eric Erica is also a pharmacist and so you're in good company with Erica on the call this morning. Thank you already well, so A couple of community a quick community announcements. First of all We are planning for the next HIMS conference, which is happening next year and if you are interested in And speaking we're right now in the process of developing some ideas Where the the sort of initial thought is perhaps to have a Conference panel that talks on the on the topic of blockchain technologies and health care The deadline for that is happening early next week and I do know we're My gut would be that that deadline is probably a very soft deadline I don't honestly don't think the leadership team has done too much on that But if you are interested it would be great to have you to join us if you have ideas feel free to contact me offline and We can get together a small team to sort of think around that And particularly if you're already planning to go to the HIMS conferences might be a great opportunity to get engaged on that level As well, we have our own ravish Juan who is the chair of our payor subgroup He is kicking off their Maryland hyper ledger meetup, which is happening next week Thursday And what's really great about what? What ravish is doing is not only is he kicking off his meetup group that focuses around hyper ledger But as well, he's using that time and opportunity to have a meeting with his HC sick subgroup team Which is a great idea So details are on the link here, which I just brought that up here So feel free if you're in the on the east coast in the Maryland area and you're free next week Thursday Feel free to sign up and head on over there Alrighty, so any comments questions anyone would like to make an announcement of their own to the team here Alrighty, well, I'm thrilled to have Alex on the call again. As I said, he was on the call late last year and he has developed a healthcare application using the sawtooth the hyper ledger sawtooth framework And so We're we're great to have him. We're thrilled to have him back on He's gonna give us a bit of an update on what he has done since November And he's got a great presentation to give to the group here And so I'll ask Alex to sort of take it away Yes Share my screen Perfect and oddly it's in Russian How could that be Actually, I'm from Ukraine Okay. All right. Good. Yes. Yes, and I'm familiar with multiple languages like Russian Ukrainian English and some applications and some of my PC Excellent. Yeah, so Hello everybody Today, I would like to present you an update since Update of current progress since Newton So just a few words about myself I am Alex Rovnovati and Last year's experience in the industry Mostly it is quality assurance About this is about management with different kinds of automation and also I spent Seven years on startups. I found it for projects As CTO and One of this project is basically based on blockchain and this is why I Started learning about chain technology namely hyperlature framework so and Based on this framework, I Developed to proof of concepts one of them Relates to health care, which I would like to present On this meeting So just a few words About What was initially done? on my previous meeting, so I Developed the proof of concept on hip hyperlatures of tools That covered basic use case For a patient who has a claim and visit clinic so Patient comes to clinic and on reception receptionist registers Claim and assign doctor to this claim and then Patient with a maker first visit to doctor and Doctor Suggests some actions to resolve this claim and Finally This patient have used all the suggestions and make another visit so all these actions are stored on blockchain and All the sections started on the chain, so This proof of concept Initially consists of a few components like smart contract itself that handles all such actions and the command line client Which Patient and receptionist may use to store some data Basically So on next slide you may see the main Reasons why I choose blockchain technology to develop this proof of concept Do not spend much time describing this Because I told it about Last time On the next slide you may see You may see As other use cases which can use Such functionality so where This workflow Can be used So If we keep all such data on blockchain we can then Use such data in different cases like Cost It may simply simplify cost calculation between clinics and Service providers and it may help Helpful for clinic and insurance relationships when a patient comes to Want to sign contract For insurance and the insurance company may check real data and check Clients state How he feels Himself, etc before signing contract and the many other cases so about current progress Since previous meeting so We Worked together with Tracy Good and to make as this repository approved and applauded to Hyperlature labs So this repository is available for everybody To Reuse it or update it Also, I added to one more component for this Prototype this is a rest API component This component Allows Allows to add some extra functionality which should not be Basic on blockchain Should be used in different Flows In the health care application And also I added one more component. This is web client This is client that much easier for receptionist and the clients and doctors to make some Changes There So every patient doctor and clinics have their own private keys Which they use to make some changes on blockchain and the last but At least change is about Infrastructure how it is constructed idea is a late at every component In the I move it all infrastructure to docker And is a late at every component for each other This this feature This feature it is much easy to Set up this application on In Clinic environment and also it is simplified Scallion process They want to If you want more clients to join this Application also since our Previous Meeting I check it and turn and turn it and found Couple of at least couple of company computers that Moving similar ways similar way by the way one of them I Use Hyperledger Framework, but there is your might is based on public But anyway Certain competitors exist and moving the same way and also For the moment we have a few Issues Discuss and Solon's it's such issues will help us to move forward this project and Grow up so Hi Yeah, so first item is advisor so basically I am as blockchain developer. I can develop some application I can Program some use case So anything else, but There should be some person who is familiar with health care and the current roses Region particularly in us Who can advise what exit Lee? We should do and point us to the features which useful and Maybe Point on the other features which are not so useful also to Going faster. We need the extra blockchain developers and the not only the blockchain developers 10 developers to make this application beautiful DevOps To manage This application And also the can developers so having If we have for multiple developers this Development of this product will be much faster And also another open issue is that Before we Complete with this prototype we need to find some organization of cost users who potentially agree to try the solution and Give a feedback to us how easy How it is easy to use and does it solve their problems and etc and Last but not least issue is resources like investments and grants and because without investments and grants We can bootstrap this project, but it I assume will not go so fast as it could be Because as far as I can see our potential competitors Move in quite fast and have a progress So basically This is all I wanted to Report you about current progress. Maybe you have some questions Yeah, outstanding. This is really very interesting and From where you were in November to where you are now is is fascinating So thank you so much for giving us status and very much appreciate it And let me get our screen back here So I'll let's open it up to questions. I have a handful questions, but let's let's listen Let's have someone else sort of kick it off. I have a question. I wasn't here. I didn't hear the one meeting that you had a year ago, but By the way, this is Patricia. I'm the CEO of signed and I joined a little bit late But I was very interested in this talk because we're working on on a similar project, you know blockchain for healthcare records and My question to Alex is my first one. I have our others, but is why did he choose sawtooth over fabric? That's a great question. I was gonna ask that question. So thank you, Patricia Yeah Thanks for the question. So Before I started working on this Prototype I evaluated multiple blockchain frameworks including hyperluretile ledger sawtooth, hyper ledger fabric Ethereum and Exonam Ethereum Doesn't work for this because it is Public blockchain and it is too slow. It use proof of work Consensus so it Doesn't fit requirement Also another Exonam, but it is private blockchain, but it is basically Based on rust language, you know, unfortunately, I Not familiar with This language and also there are quite a small community in this That's why I decided not to go this way and also About hyperlature fabric. I found the hybel ledger fabric much More complicated than hyperlature sawtooth and On the current state I Decided that all Benefits provided by fabric are not actually Necessary or required for this kind Prototype And so The final my final decision is was to choose hyperluretile sawtooth because it is much less simple to understand and Study That is my basically all and one more thing Just wanted to know that Blockchain technology is very young for the moment and I believe that Most and so many blockchain frameworks are currently developed in this time and they believe that most of them will die in few years and some of them who Will alive they will Evolucinate it or improve it very Domestic only so I'm not sure even that hyperlatures of truth is the final final approach And the best Choice was this case Well, thank you for that and I'll just add very quickly that most of us Sort of came to the conclusion about sawtooth sawtooth being contributed by Intel that the consensus algorithm called poet our proof of lapse time is is Was originally intended to sort of be very closely wedded to the architecture And that that that consensus mechanism required Intel chipsets There's a chipset sort of embedded called SGX That is no longer the case which is to say that if You're evaluating frameworks be a fabric or sawtooth When you think about sawtooth you don't necessarily have to think about that dependency on Intel chipsets that that dependency was removed oh Gosh, I want to say the the 1.0 version It was probably about a year or so ago and I and oddly I found out about this at the Hems conference in talking with some folks who are developing sawtooth applications similar similar to what Alex is doing and and they they Honestly, they educated me on that because I was under the impression that sawtooth required Intel chipsets and so that is no longer the case Yeah, I just wanted to add Thanks for the hands up about Intel chipsets. This is basically a One of the limitations why Heterolatures of tools cannot be used on Amazon services using Consensus which Works with Intel chipsets. So that is why to use Heterolatures of tools on Amazon we have to use some kind Consensus proof of elastic time Great any other questions I just want to clarify again, so So Richard said that you you can now use the poet consensus. However, Alex I'm just clarifying Alex says you cannot use poet in in Amazon in the Amazon cloud Actually Actually Proof of elastic time This is consensus This is like a virtual consensus or emulation of real consensus Which was planned initially to use in the Heterolatures of tools So if we want to use Heterolatures of tools on Amazon We should use like emulated consensus Yeah, yeah, and and just to clarify that what's one of the nice things about sawtooth is the architecture is much more modular And I've even been told and again, this is third-party or second-hand. I don't know this myself that Because of the modularity in the way that Intel approached their solution It's much easier much cleaner to to pop in or pop out different consensus mechanisms Which is the reason why that dependency is is no longer tightly wedded to the the decision to move to sawtooth Which which is to say if you want to use poet, then you do need the Intel chipset That that dependency because that's how poet works But there are other consensus mechanisms that you can use sort of modularly to plug in to this Framework, and so that's that's where the value lies and in fact, you know my my personal thought Might be that sawtooth gets a lot more traction if it is in fact easier to implement than than fabric But that's you know, that's just my speculation Okay, any any other questions? so so I Okay Go ahead Patricia. I actually have just two more and maybe that I can Put them put them together my question for Alex is I actually looked at the github code and So he has the way he Implemented is is he has a really nice workflow where you have a patient coming to the clinic and so first of all the clinic itself has to be Registered in the blockchain. So you register the clinic you register the doctor And then when the patient come the patient also has to be registered and then There I think the patient in this case. I'm not sure it enters a claim I'm just describing a little bit of what I saw in the code and and then the patient gets treated by the doctor That also is entered everything is entered as a claim I would call it maybe like a transaction, but he calls it claims. It doesn't matter. It's just wording and then when then The Patent gets prescribed pills Which he calls e-pills and then he gets maybe also sent to take some blood test which he calls past test and so my question is I'm guessing that when he says it e-pills it means prescribed drugs My question is where does he store? For example the information about the prescription about the pills Like such as drug name dose And dosage which is like the length of the time that they the patient has to take the drug my guess is he Stores that off-chain Because it's sawtooth. It's a more interesting question because in fabric fabric comes with this couch TV Which is linked to it So so I wonder where he is storing that information in the sec the third question which is linked to the To this is has he run a query? Has he queried the system to score example say find all patients with aspirin prescriptions in the past two months and Has he measured its speed? So one question is where is he storing the actual information of the about prescription and the second it has she query Has he run a query and how fast is it and I'm done with questions Yeah, yeah, thank you very much for these questions so Let me answer about the prescriptions. So in In this particular case in the current to prototype We just keep all data as a description for a transaction and this description is stored in a blockchain as well so In the current implementation or prescription is stored on the chain and link it to Transaction Second question about Query It is not Implemented yet. I agree with you that some data should be implemented on chain but This is not implemented current version but One more layer like In sync to simplify Query Okay, thank you. Thank you for the answer and I have a question for everybody in this panel and I have all the questions. I guess I came with full of questions That's okay. Go. Yeah, excellent. This question is for everybody I always hear anybody who's testing the or not testing actually, there are no many and unfortunately many systems in production but I Go too many blockchain talks and I hear a lot about transaction speed and whenever they talk about transaction speed They're talking about how quickly they can add new information into the blockchain How quickly a new block can be created and consensus can be achieved But I never hear about the speed of a query. What can you query? What if you want even a financial blockchain if you say give me all transactions of More than $100 in the past two months. How quickly can that be done? That's looking at financials as I say it's in this case, it would be medical You give me all patients with aspirin prescriptions in the past two months I wonder if anybody has any information on Anyone doing this queries, how fast are they in you know, how is it done? Is it actually done on the blockchain or are they Quering the off-chain database or how is it linked together? So I'm very curious about that Let me say a few words about it I have many years of experience and quality assurance and huge expertise in the law testing of the different applications and the performance Depends on the quite many Criteria And if you are talking about blockchain, I'm not sure it is Good to say for instance that this blockchain may precede 100,000 transactions per second because it depends on many Cases first case what infrastructure do they use? I mean a number of CPU Memory etc the next point is How Consensus how Faster is how How fast is the consensus for instance ethereum consensus is very slow and proof of Proof of elastic time consensus is a much faster, but still our performance May vary And also this performance depends on number of nodes which used Which work in the consensus for instance if we have a Network blockchain network where two nodes nodes exist and work and Work in consensus in consensus, it will be much faster than for instance 50 nodes nodes if 50 nodes Exist Interacts in consensus So, you know Performance will depend on how many nodes will work in consensus and also performance depends on Network throughput where nodes located Between Each other for instance if one server in the North America and now another server in Africa that performance may depend on this and one more criteria is Communication between Off-chain or we can't and basically blockchain ledger So every this state the criteria may May affect performance so Answer on your question. I think it is not fear to Say about the exact numbers How fast is a particle blockchain is Yeah, yeah, sorry, but not we can just Check test and say is it one blockchain? In the heaven one structure Is faster slower than another blockchain having another? Structure, thank you Alex. I don't know if anyone else can can add to that. I just one Quick comment is that there is a consensus built by hedera hashgraph And they claim they can have 500 transactions a second Based on their consensus and it's scalable to even if you get more nodes It doesn't affect it because of the particular algorithm that they use So you might you want to look at hedera hashgraph However, my question was not about the speed of adding a block but the speed of of Exploring the blockchain of of querying of getting information out that already exists there So I don't know if anybody has an answer to that and any one of the other people in the meeting Hey, this is Ken from Sinterra. We are Using hyper ledger and production for here first MIT security stuff and one of things that without getting into it When we do a query on the blockchain, it's almost instantaneous and I know we probably have 100,000 records in that in that blockchain I mean, we don't do a whole lot of transactions more of it is is a querying the blockchain and it's on for us It's almost instantaneous, but we're only looking for one record out of all those. I don't know if that helps You know, we're not doing any grouping or any calculations. We're just looking to see if this if this Record is there in just a piece of data that's attached to it. That's all So, so can I just just interesting to hear about that? Art do you store data on on the chain or do you link to some other store? This is on change. There's not a whole lot of data on chain Okay, because in my mind it may be yeah, you may have some overhead if you have to follow links to some You know some external stores or whatnot, but it is interesting to hear That the query time is reasonable and that would make sense only because you know, your ledger is local So so that would speed things up quite a bit, but again, if you're if you're having a sort of walk links in the process of You know completing that query it could take Our actually our hyper ledger is actually open Azure and it's been it's been queried from on-site here. Oh Sure. Okay, so I mean it's I mean you got a little bit over a little bit But not much like I said, it's I understand what the release trying to do when it comes to grouping and and That type of searching but if we're just looking for something simple, it's almost instantaneous and it's as fast as any other database And and my my gut would be There's a lot of architectural sort of influence here depending on how you design your solution That kind of obviously have it in it sort of an influence as well Much much as patrice you had noticed noted for fabric, you know, you have couch DB And so you in theory you could use that as a reference other architectures could be designed You know differently and those those would have implications on on on total speed of query Okay, any any other questions So I'd like to ask Alex. So Alex Is anyone Using this right now, are you working with anyone sort of in the field for for a proof of concept? anything on that order or is this you know, is this something that you and your team are working on sort of separately Actually, you know for the moment I'm the only guy who work on this project and I liked very much and It would be great if This project will be successful, but to succeed succeed with this project we need to find advisor and Organization who I want who would be interested to try and It is highly recommended to have such advisor and the organization located somewhere and US because it is quite a big market Yeah, yeah, actually that that so that follows on to my next question, which is It it appears that your solution is not in any way sort of country specific, right? And so the idea would be Someone from from anywhere around the world could take a look at this and use this really as a as a as a foundational component to a workflow and then develop around that Depending on what you know what specific country needs needs are and I think that might be is that correct your approach You're absolutely correct excellent and so One one final question So you talked about Finding a way to grow the team and look for an advisor or what would I would call a subject matter expert to work with? What is what's your what's your view going forward? You know if do you want it? Are you planning to continue to use sawtooth? Are you looking at other options? Do you see? Future growth or features that you'd like to add to this What's what's your thinking going forward? For the moment if we are talking about this prototype Fortunately, I don't see any reasons to add the new features to this prototype until we know some potential use case which can be used By some organization So to proceed with this project we need To find someone who will push this prototype for some organization and once we find such a guy We can Talk to proceed we will know which features we have to add to this prototype and Be ready to work on this project because you know Without Person who will push it with customers There is no chance to succeed. I Spend seven years on startups and Three of four projects fail it because of We couldn't find Investments and Enough clients who Our solution and the confirms that this is really Really solution that solve some problems Okay, well good and and and we certainly have the resources here through the the special interest group You know, we could we could always reach out to the full membership and see if anyone in full membership Has a has an interest in helping you out and I think that might be the next step It's great to have this project under the hyper ledger labs Monica just so that anyone Through hyper ledger has access to this directly And and of course we get the support of hyper ledger leadership to help Manages going forward as well, which is fantastic So any other questions for Alex? Yes, sir close up. Yes. Go ahead. Hi, it's Canton Hong Kong So I'd like to ask Alex. Thank you very much for this presentation I'd like to ask Alex. What sort of things have you customized? From the basic sawtooth package installation So this This project is Based on two other open-source it Products I Use them to implement this prototype and Changes I made first change is that I adopted Workflow for health care needs to cover this use case And the second the most Second major change was I Completely isolated components from each other because you know in regional Implementation In the regional implementation there are as I walk components of the mix it between each other and I Isolated them to have clear structure how it How it presented Did that answer your question Kent? Oh and Kent is on mute Just in case you're trying to answer Thank you for that. I've been talking for about two minutes and I thought Sorry, I was just going to offer some Assistance to Alex because I work as a practicing pharmacist and if he wanted some demo workflows I could give him some prescription data obviously anonymized and Maybe as a pharmacist, we don't just dispense prescriptions. We also sell Medicines over the counter and we do counseling as well So we're not doctors, but if you can't find a doctor then we're probably as close as he can get to do a demo cool, just We can discuss potential what we Our cooperation or something else sure. Thank you Thank you very much yeah, and thank you Kent for for reaching out and Yeah, that that would be fantastic To follow up on that Alrighty anything else. Oh, go ahead Alex. Go ahead Yeah, I just Know I would like to Let you know I Have some experience Expertise and attracting investments basing on my start ups and Last winter we presented Our current startup in Davos during work to come in the forum and During the time I gathered quite many contacts of investors who Potentially interested in Blockchain and health care solutions, you know So this is a most popular area of interest for investors and I have a big Huge base of such investors which we can communicate to and If we find if you can find someone from us Who is interested to push this case? potentially in America in the United States or Europe or Asia we can Maybe prepare some pitch deck and discuss potential potential Cooperation because I believe Blockchain and conjecture health care and conjecture this blockchain we'll Will give a great profit in future In falls care and I see many potential Competitors moving same way, but I Think we can try to Try to work with this project and it make potentially may grow up into something big So if you have some suggestion or feeling you want to attend this project So just feel free Let's discuss and plan our next steps Excellent, all right. Well, yeah, absolutely. And again, we have the resources of the whole of this health care SIG available to us and so One of the things in addition to maybe what Kent has offered is we can always reach out to the full HCC membership as well I just wanted to add that I've seen I'm sure we've all seen quite a lot of health care projects Starting on hyperledger fabric and I just wanted to point out that sawtooth would be quite a novelty at this junction Yeah, I would agree and again again part of my sort of observation at the recent HIMS conference Was that there are there were Quite a few more folks that I would have expected that were using sawtooth and again When I queried them they they felt much like Alex had mentioned earlier in his presentation They felt that sawtooth was easier in some respects to set up than than fabric And so, you know in my mind again, this is very subjective in my mind It may be that sawtooth ends up getting a lot more sort of market share going forward As the community at large understands that there isn't that sort of tight wedding to Intel chipsets Which sawtooth used to have using the poet consensus mechanism. So So, yeah, we may we may see that, you know, there's there's maybe a bit of a shift towards Favour with using sawtooth in the health care space Also, I think another potential feature is integrating the EVM Ethereum virtual machine through hyperledger borrows. So Well, a way back. I was thinking of Once that happens, we can actually cross over with a ERC 20 token to initiate the sawtooth service in the background. Oh Interesting thought. Yeah. Yeah, really cool thought Thank you. I wanted to make it quick. I know we're almost over. I think this Collaboration now I call it like that between Kent and Alex where can't can provide some I don't need my prescription information. It's really interesting So I would like to in a way either participate or at least hear back how you're doing it I especially I'm curious about how you're going to deal with PAI or personal no no more personal health information, you know, the If all this lost the GD, what is it called G DPR GDPR? Yes. Yeah What are you going to store on blockchain what off-chain so that that kind of things I Think probably be a hash redirect. So Yeah, yeah, that's that's I would argue fairly typical, right? But I think Patricia's point earlier on my first thing would be to query the speed of the recall So that was a really good point Patricia Yeah, and I'll just follow on it and Patricia has another great point there, which is as as you move forward with This collaboration. It would be great to find a way for For the for the two of you to sort of status the SIG here because I think many members here would be really interested to understand How you progress going forward? What are the some of the issues that you run into? And the kinds of things that might be helpful for others that are just getting started with with projects somewhere to this Great. I love to Already well, we are coming up to the top of the hour. We just have a minute or two any other comments or thoughts before we Say goodbye. Yes one more comment So I check at multiple blockchain frameworks and Can't say that there is no silver bullet to answer in question what blockchain is the best right and if you choose Hippolyture for So close for this solution. It is not necessary. This is the best way for this case But on my experience as a city war. Yes, for instance, if we spend few months to prepare some prototype and Finally, it will not It will have some obstacles or a bottleneck from technical point of view We can we can easily take another blockchain framework and the rate of Information to you To new to this framework the only reason There is only main reason is that that use case which is handled by this Which is covered by this solution does really work and necessary for users and users want to use this solution. So there is Not a big deal to use one or another blockchain framework Yeah, all ready. Well, we are at the top of the hour and again Thank you so much Alex for for giving us an update and a status on the work that you've done very much appreciated and And Everyone else. Thank you so much for your participation and great questions And have a fantastic weekend. Thank you all. Thanks everyone Thank you


With Los Morteros and Pampa de Los Salinas, early monumentality, environmental transformations and the creation of a pre-ceramic ceremonial landscape. Good morning. First of all, I'd like to thank the Institute of Hawaiian Studies for this opportunity. I am very glad I can share the current status of my research with all of you. And I'm going to make a very tight summary of my work because there is a lot to say. And I might take more than 20 minutes. I apologize for that in advance. Sorry. Well, let's start. I work in the Chau Valley, which is between the Santa Valley and the Viru Valley. And the Chau Valley is a small valley, a narrow valley that is formed by the Chau La Val and Huamansanya rivers. And it's been historically described as a rather arid valley and with always deficit of water. Most of the reculture in historic times have been done in the lower part of the middle part through bookios and artificial wells. And also this valley, for some reasons, I don't know, I don't understand, didn't get much attention from archaeologists. So there were some projects, but not many yet, still until this year. But in 1977, the project of obtención de una cronología del uso de recursos marinos en el antiguo Perú by the people from the Seminario de Arqueología de la Universidad Católica did an exploration of this valley, mostly in the lower part and in the middle part. And they recorded more than 50 archaeological sites in the Chau Valley, and that was the date for future studies in this area. So excavations and exploration were led by Mercedes Cardenas and her team. Their names are right there. My work so far focuses on this part of the lower Chau Valley, which is called the Pampa de las Salinas. This is a satellite photo of this area, this very particular area. It has a paleoembayment and a Pampa area, a relatively flat area surrounded by some Andean foothills. And you see on yellow is the paleo shoreline. The Chau River is from the Pampa area. It's about eight kilometers. That Pampa area is four kilometers from the ocean. This is how it looks now. This is a view of the dry environment from east to west. Equally it's a very dry environment, very salient. Most of the environment is filled with dune fields. And the Pampa looks like this. No vegetation, no water, no fresh water on the surface. Nothing but chicken farms. And despite this current environment, Mercedes Cardenas and her team recorded more than 20 archaeological sites in this area, most of which were ceramic. The best known site in Andean literature in the Chau Valley is perhaps this site, Salinas de Chau. And this is a photo I took last July. But also there are other sites here like Pescadores with a stone architecture, some open areas, but also small rooms and tents of windbreaks. There are show me dance too, like this one. The recorded also by Mercedes Cardenas, Conchal Viejo. Those are their calibrated dates. In 2012 I started my research in this area as a part of my dissertation project for my doctoral dissertation. And I kept coming back to this area since then. So my research focused in the beginning in this site Los Moroteros. The name of this site is because of some stone mortars that Cardenas and her team found on the surface of this mound. It's a mound-shaped archaeological site. It's about 200 by 200 meters and 1500 meters high. Cardenas excavated some test pits mostly on top of the mound and she found some human burials and some refuses that she described as domestic. And later in 2010 a crew from the University of Maine did some GPR exploration of the mound and they found some evidence of architecture of large dimensions, probably something monumental, underneath six layers of Aeolian sand. So in the beginning the question was to... some of the questions of my project were focused on understanding the formation process of this site. What was Moroteros? If there was a monumental architecture and what was the relation between Moroteros and Salim as a chow? At that moment was the earliest example of monumental architecture in the chow vibe. So until 2013 I got three occupational phases for the mound. We explored different areas of the mound. This is an area full of the mound and I found these phases in different parts. Exploring different areas of the site. So the last phase of occupation, the last phase of construction was recorded originally on top of the mound and is related to stone architecture with brown corners, stone platforms and these stunning stones. But I found also remains of the same kind of architecture in different sectors of the mound and this is a very superficial occupation. You have to dig only a few centimeters from the surface to find these walls and also this architecture has these very thick clay floors. The second phase of occupation is related to monumental Adobe architecture found on the north part of the mound and formed by these walls that are 10 x 7 meters with Adobe walls and thick also thick clay floors. Some of the walls had up to two meters high and this was strategically found at this architecture under the stone architecture and this picture shows that. And in a recent excavation of this architecture, this Adobe architecture, last January we found a very interesting context, an offering related to the closing event of the Adobe architecture and we were excavating the central part of one of these Adobe rooms and we found an offering formed by sea lion bones, some fish bones but the most interesting part was this. We found human bodies like this, children and one very particular finding is that the body of a child was completely burnt and intentionally burnt and there were also many human bones that were found that seemed to be isolated, no articulated bones and we just finished the study of this context and we found at least 10 bodies of children, all of them, all of them so far the analysis said that were between 3 and 5 years old and there are evidence of two adult individuals but some part of adult individuals and there is a very clear intention of selecting the individuals that were buried here in this context and as far as I know this is all the evidence I could find about the burning of a body I know about similar cases later in time but this is very intentional there were some other remains that were part of this offering that were burnt but not all of them, it was very clear, the intention of burning this body was very clear and to see this context in a profile view this is the interior of the Adobe room where we found this offering and in the lower level there are the human remains and some animal bones and then this was part of the closing event because the Adobe walls were dismantled actually destroyed, there were pieces of Adobe's but all these pieces of the Adobe walls were inside the room not outside and it was a very clear intention of dismantling the walls and on top of that there was an audience and a deposit with only Cholomitellus shells so to talk about the whole area, since the beginning I understood that I couldn't study morteros without taking into account the whole context there were more than 20 archaeological sites around morteros and previous research indicated that some of them could be contemporary with morteros so I knew to understand the other sites too so I focused my excavations on morteros but I also do some excavations to build the chronology at the area because Carame Sancturati they obtained some dates but there was some controversy about these dates so I decided to build my own chronology so I started digging other sites along with morteros and so far the ceremonial and monumental architecture is just evident in morteros and also Salinas de Chal but also there are some areas of ceremonial activities like these geoglyphs some of the geoglyph areas were recorded by Carame Sancturati in the late 70s but we found two more areas of these archaeological features these are very particular geoglyphs and this is the one recorded by Cardenas it's close to very close to mortenas it's called the Sara Cross or Clos del Sur and it's formed by these circular marks made with stones but the particular things that are inside very large rooms that are about 50 and 100 meters long so for me that this is very similar to the constellation actually but there are more than 5 similar areas so this is geoglyph 4 you have the same team, walls and marks and if you see these circular marks you see some of them appear to be bigger, more larger than others and this is completely intentional this is not a preservation thing it's completely intentional they decided to be some of these circles bigger than others and this is how they look from the ground so circular accumulation of rocks inside these structures and some of these structures have even entrants preserved other features in this area are preserved trails and this one is laid later I think from the Preserve Museum we even found some colonial loza and some coins and there are walls that seem to have function to close the main area where most of the sites were located in Pampaela Salina this is a wall that is close to the Chau site and it's been eroded by water my run of gear you can see the wall so if you see the whole area you have archaeological sites the geoglyphs and the walls there is another wall this is in the south, the south wall is closing a natural path between these small hills and it's a path that connects this part of the Chau Valley with the Santa Valley that is just north of this and this is the late trail, the late road in the beginning I thought there was some of these sites in this area could be domestic because of the size of the architecture the size of the characteristics and some reports from carbon but I haven't found any evidence of domestic occupation or the evidence of a population even in that area yet this is the site of Piedras Negras and we discovered it because Cardinals reported this site as a domestic site but with architecture that doesn't seem to be very domestic big walls, thick clear floors and I don't think this is a very domestic site and so still there is no, I haven't found yet where the population that occupied Morteros and these other sites were staying probably in other parts of the valley and this is another detail and these are the new dates from this site Cardinals reported this site as being contemporary with Morteros but there is no relationship so far so another component of my research was to understand the environment because as I mentioned before the cool environment doesn't have many relationships with all these archaeological sites it's not a very friendly environment and why people was here so in order to understand that question I did some environmental analysis of the area trying to understand what transformation this area went through so we started analyzing the stratigraphy of the dry environment so we did some exploration of the stratigraphy through test pits and these marks are test pits that we opened in this dry environment so pits like this until reaching the groundwater the groundwater is between it's less than a meter mostly in most of the areas so we analyzed the stratigraphy to understand try to understand what environment formed this deposit so to summarize we found this evidence of the deposit that could be interpreted as wetlands close to the Pena shoreline and followed by to go into the ocean by the deposit Laguna deposits and then Open Beach deposits and then the Morter Beach this could be understood it could be like this this is the area in the north of Chico the Aluferas de Medio Mundo and Morteros, Pata y Las Alinas could be like this or larger with a lagoon and some wetlands around but we were missing something and that's the hardest part of this environmental reconstruction is the chronology because we know that this environment was there but we didn't know when and when this transformation happened so our explorations in 2012 found three new shell middens all of them Mesodiasmas Machas shell middens and these were the Memejo, Donoros and three sorry, on the north part of the dry environment so we decided to excavate them because there were some evidence of that these shell middens were in cultura so this is Memejo too and we excavated this last January, January 2017 and we found this cultural evidence a hard stone heart with charcoal and shells matches inside so we did them and this date helped to have the maximum date for ocean recession and also we used mortals this is another view of mortals amount and if you see part of the mountains inside the dry environment in the beginning we saw that this was like a collapse because of the time and because of that some part of the mountain was inside but we explored that area and we found architecture that is very similar than the surface of occupation and this is a stone architecture and it's dated to 5000 years P.P. so what we have so far is this the ocean wasn't there between, I mean this embayment wasn't active around 5000 years ago because mortals was there the ocean wasn't in the middle part of the embayment that's 2700 B.P. because of the shell mutants and probably this wasn't an active embayment I mean the population that occupied this area didn't see an active embayment when they arrived but it's very likely that the wetlands and the lagoon were there around that time that's what the gearcheology tells us so far the whole occupation of the area with the dates that I have until now indicated occupation of the area from 6000 to 3000 B.P. and these seem to be related to some regional changes in the behavior of El Nino but I can talk about this in another time but there is some relationship with that and Mortelo was the oldest site in the area apparently it has the oldest evidence of monumental architecture and some ceremonial activities so far and we recently found some evidence of cultural deposits and there are pre-architecture pre-monumental phases so probably Mortelo's is going to be very old older than 6000 for sure and this is very interesting because we have a very long occupation of the site and we can understand this construction of monumental architecture there because there was a long history of occupation it didn't happen like from nothing so this is another view of this deposit we haven't dated this deposit yet but that's for future research there is a gap between Mortelo's as I said the oldest site with this ceremonial architecture monumental architecture but the occupation ended around 5000 B.P. and then the oldest date for the older monumental site in the area is 4000 there is a gap of 1000 years and I think the answer is there is here in Salinas de Chao Salinas de Chao is it was excavated or it was little excavated so hopefully this year we are going to start a new excavation at this site and something I forgot to tell sorry is that the characteristic of the architecture here indicates that some monumental architecture in this ceremonial space is that repeated in some part of the mount similar and other rooms in different parts of the mount mostly on the north side and also the stone architecture is very similar it was like the same kind of architecture on the top, on the east side on the west side, on the north side indicating that same kind of activities maybe related with some families or small groups but what you see here is a change it's a very interesting change it's a more centralized the activities ceremonial activities are more centralized you have more also a spaces built for larger audience I don't know if there were larger audience but they built that so that's a very interesting change and also, sorry so far Salinas de Chao belongs to the second phase of occupation of Pampaela Salinas and some other sites that we have dated the site that have this larger architecture belong to this part this second phase from 4,000 to 3,000 BP and that's also very interesting to understand how population how the activities change so around 3,000 BP this site was abandoned the whole area was abandoned again this coincides with some changes with the linear activities and more fine sediment coming to this area so the ocean there wasn't like a real recession of the ocean but more than an infilling of the embainment with fine sediment coming from the air and the ocean and so around 3,000 BP there was no wetlands there was no lagoon and that was the end of the occupation but also this abandonment is changing the occupation of Pampaela Salinas and that could be related to other sites in the Chao Valley maybe sites like this one the Iserro Cabra also reported by Cardenas and her team this is in the Miacholo Valley one of the components of the Chao River and this is an interesting site because it's composed by a series of small mounds with sunken circular plasters that can be another site that's theorized at the end of the around the end of the Pampaela Salinas activity and also this I hope in the future in the near future we are going to come to this site and do some excavation to take some dates so to finish what we see here is a very interesting history of this valley very ancient history of this valley and monumental architecture ceremonial architecture that has a long history in this area although Cardenas the Chao can have some characteristic very similar than the northern Chico the presence of this site is understood because of morteros and because of all these people living in this area for a long time so it wasn't just influence from other areas that got this site to be built well thank you very much I think it's a quick question the rectangular adobes that you show are those molded or they hand-modeled? or they are handmade and some particular things that they are made of clay just clay, nothing else they don't have tempered sand or rolls or any other materials I believe that concludes the morning session thank you


All right. I think we can start now. So, good morning, everybody. This is a state of Drupal 10 or getting ready for Drupal 10. This is Matt Glamin. And I am Gabor Hoici. Both of us happened to work at AQUIA now when we submitted the session. Not both of us worked at AQUIA yet. But now both of us work at AQUIA. We tried both of our computers and neither worked. So, this is off of the conference venue computer now. But it should work. So, hi. Drupal 10. I don't know if you know, but Drupal 10 had three possible release dates. One of them was on June 15th and then August 17th and then December 14th. We defined these, I think, last year, maybe a year ago, something like that. And the thinking was that we want to have Drupal 10 out soon enough for everybody to update to, but we also want to make sure that we do all the things that we need to make Drupal 10 available. So, we defined these dates based on whether the beta requirements will be done on time for March 18th and May 13th and September 9th. And although it's not yet May 13th, we now know that things will not be ready by May 13th based on the trajectory that we are going through. So, the release date of Drupal 10 is going to be the last option of the three that we defined last year. So, it's going to be December 14th later this year. And that also means that there's going to be a Drupal 9.5 alongside Drupal 10 at the end of the year. So, we're going to have a 9.4 in June in the original window, the earliest window that was for Drupal 10. And we're going to have a Drupal 9.5 alongside Drupal 10 in December. That also means that Drupal 9 support will end roughly a year after Drupal 10's release because we need to stop Drupal 9 support due to Symphony being going unsupported, Symphony 4 going unsupported that we use in Drupal 9 and also CK Editor 4 going unsupported in Drupal 9. So, there are two major dependencies that will go unsupported and Drupal community does not want to fork Symphony and CK Editor and maintain it for ourselves. That would not be fun. So, we need to stop supporting Drupal 9 towards the end of next year. So, that's why we're releasing Drupal 10 this year. And then we'll go on with Drupal 10. And as you will see on the next slide, Drupal 10 is based on Symphony 6 and is also based on CK Editor 5. So, theoretically it could be supported until like 2027 or something on Symphony 6, but there may be probably other dependencies that will stop us from doing that. So, I don't know how long Drupal 10 line is going to go there. We'll see. An interesting fact is that Drupal 7 will be supported longer than Drupal 8 and it will be supported longer than Drupal 9. So, all the marketing that we did to update to Drupal 8 and Drupal 9 from Drupal 7, I think it was worth it, but we're still going to support Drupal 7 more. Realistically, the support for contributed projects from Drupal 7 is a hit and miss now. So, I would encourage you to start looking at upgrading to Drupal 9 and then eventually Drupal 10. And so, one thing that we will have is we will have the migration path from Drupal 7 and even Drupal 6, I believe, in Drupal 10. So, if you have a Drupal 6 site, the migration path from Drupal 6 is included in Drupal 10. That's quite unprecedented, I think, in the history of Drupal. So, after our session, the Dries node will go into a lot of the details about what's in Drupal 10. So, this is our one slide about what's in Drupal 10, the major points. So, Drupal 10 is now at Alpha 3. We'll release further alphas and then when the beta requirements are done, we'll release the beta, which will be API complete. And so far in the alphas, we managed to get in Symphony 6 in place of Symphony 4. This will be updated to Symphony 6 one in May and will be updated to Symphony 6 two in November before release. That's the expectation. And the trick there is that we would not normally be able to release Drupal 10 on Symphony 6 because Symphony only supports their minor releases for six months and they only support their LTS release for long enough for Drupal. But we made a special agreement with the Symphony team that we have Drupal core committers sitting on the Symphony security team that can make special Symphony releases available for things when it affects our project. They can backport the security fixes to otherwise unsupported Symphony 6 minor releases. So, that's why we can release on Symphony 6 even though it's not long-term support and even though they would not normally support long enough for when Drupal wants to be supported. Cic editor 5 replaces Cic editor 4. So, that means that Cic editor 4 is moving into contrib. It's going to be a contributed project. And Cic editor 5 is going to be the editor in Drupal 10. If you're interested in this, there's a session, I think, at 1 p.m. from Cic source. And they're also in the expo hall. You should talk to them. It's really cool. Cic editor 5 has a lot of cool features. So, you should talk to them about that. Claro will be stable and will be the default in Drupal 10 while 7 moves to contrib. So, this is a pattern. When we get something new in, we move the old thing out to contrib. So, if you rely on 7, you have a custom admin theme based on 7 or just like 7, it's going to be a contributed project. Same thing for... So, Claro is the admin theme in Drupal Core. Same thing for Oliveiro is a new frontend theme in Drupal Core. So, that's already stable. I'm going to be the default in Drupal 10. And Bartik will move to contrib. It's been a long while. It's been a time. There's also a bunch of other modules that we are moving to contrib. Forum tracker, aggregator, caller, HAL, RDF. And we'll probably move more later on in Drupal 11. But for Drupal 10, the plan is to remove these ones. Why are we removing them? They are mostly single-use modules that don't have an ecosystem in contrib. They don't have further modules that depend on them. Most of them are not very well maintained in core. So, like, caller module could do a lot of good things if they would get some love from maintainers in contrib, for example. There's better solutions for aggregator in contrib. So, we don't need to, like, compete with better solutions in contrib. We don't need to have the core solution that's inferior to something better in contrib. Yeah, and we can reduce the maintenance burden in core and set these free and have them better maintained in contrib. They will move to contrib as they are in core. So, if you want to use them as they were in core, you can use that branch. And then the maintainers that we recruit for them, we ask them to release new branches with new features so you don't need to adapt the new features if you don't want to. There's also no support for Internet Explorer in Drupal 10. None of the Internet Explorer is anymore. So, that sets us up for a lot of good front-end things. Olivero is happily adopting a lot of modern approaches, for example, now that we don't support Internet Explorer. Drupal 10 has a minimum requirement of php8.1, which may be sound a bit high, but it will not be high in December by the time it's going to be adopted and PHP 7 is on its way out, so it will not be supported much longer. So, you need to look into updating to php8.1. And the database requirements will be largely unchanged. We already made the major database requirement changes in Drupal 9 to require JSON support in databases, and we do not yet use JSON support in databases to have, like, deeply look into JSON data structures in Drupal Core, but we hope to use it sometimes so we keep the same requirements in Drupal 10 for our databases. And so, as I said, this is how we built Drupal Core, is we basically add the new things into Drupal Core, like the Clio theme, like a new API, like new modules, et cetera, and then we deprecate the old things, like Bartik, like things, ways to do things. And then the change in Drupal 10 is basically removed the deprecated API. So, the way we built Drupal 10 as much as possible is to put everything into Drupal 9, all the features, all the new APIs, everything put into Drupal 9, and mark the things that we'll remove so that you know that this is not going to be available in Drupal 10 anymore. And so, this is what we do on the theme level, on the module level, we do it on the API level, we do it for routes, we do it for a bunch of things. And so, this is how we help you go through this transition. And then the rest of the session will be about going through this transition. And I will hand this over to Matt here. All right, hi everybody. So, we're going to talk about how are things deprecated in this process. So, when we go through, when there's like code methods that are deprecated to class, we use PHP docs and do an at deprecated tag and then give a message. There's actually a standard message that gets flagged by PHP CS. And there's also a runtime error that gets triggered. So, if you go to your database logs, you'll see the error logged in. So, if a code is called, it will say, blah, blah, blah, it's deprecated with the same kind of message. And it's important that we have these two layers, the static analysis tools, can catch PHP doc.  There are services deprecations, and this was added in nine dot, in the nine dot era. So, if a service is fetched, it will log an error. Whenever that service is retrieved, it says, hey, the service is deprecated, use this instead. And that also has its own standard formatted message. Libraries can now be deprecated as Drupal core moves away from having heavy reliance on jQuery. Now, the jQuery libraries have been marked as deprecated. And as we go through, well, wouldn't these trigger, do a trigger error, correct when I load it? Yeah, do a trigger error and we'll go through later on on how we can actually find these without relying on looking at your logs. And modules and themes can also be deprecated now, such as aggregator, HAL, RDF. So, there's a new lifecycle key that's for deprecated, and this is also used for experimental modules, too. So, it helps explain their lifecycle in the experimental process. And then the lifecycle link, so you can go find and read more about why is this in beta deprecated, alpha, et cetera. And the cool part is, if you go to the modules list, as you see in the bottom right, it actually has a link of that lifecycle status and can bring you to that node. The biggest thing of all is all the change records. So, every deprecation, in fact, any major change gets a change record, but it's important to check this out for deprecation notices. They're published at Drupal.org slash list dash change, hyphen changes dash Drupal, or follow the Drupal 8 changes bot on Twitter and get announcements as one of the people who maintains a lot of the upgrade tooling. I monitor this a lot. It's also good to help you plan for your next sprints. So, if you watch this, that we can put in your backlog. So, in your sprint in three weeks that kicks off, you have it ready to go. So, that's how things are deprecated. Now, let's talk about how we find this deprecated code besides just relying on our database logs every time things run. So, first we have PHP stand and PHP stand Drupal. I'm also wearing my PHP stand shirt today. PHP stand stands for PHP static analysis tool. It scans and analyzes your code. Write PHP is a scripted language. It doesn't compile until the web server runs the request. And it's compiled on command. So, PHP stand allows running your code that way to do static analysis without actually running it. PHP stand Drupal is an extension I maintain that makes PHP stand how to auto load Drupal code. Because we don't dump our classes to Composer. We have dynamic namespaces because we have extensions that can be uninstalled and installed. So, it also provides some very Drupal-specific extensions. One to highlight here is if you do a lot of entity queries, before you by default were in to entity access. But in Drupal 10, you must explicitly opt in or opt out of entity access. That's not a deprecation. That's a policy change. So, there's a rule in PHP stand Drupal that works for about two-thirds of the code that we can read. That says, hey, you have an entity query that does not do entity access checks. It does not specify it. So, those are things that aren't quite deprecations but has specific rules that we tell PHP stand to understand how to read the code. And then there's Drupal check, which I think people probably are more familiar with the name of over PHP stand. Drupal was created for Drupalcon Seattle as a much easier way to configure PHP stand. It's a lot easier to configure PHP stand now, but Drupal check is basically a install and run. No configuration required defines all the dependencies. When you run Drupal check, it actually generates a configuration on the fly, uses that and you're good to go. So, you don't have to maintain anything in that regard. It runs PHP stand without any static analysis except for deprecation rules. It's the one thing about it. Upgrade status. Yeah.  So, what Upgrade status does in its core is it runs PHP stand Drupal with the same configuration that Drupal check would run and it collects all the deprecation issues and it runs them on your project to where on your site. So, it runs them for your projects and then it identifies for each project the next step that you should take. It knows about automated fix coverage for your project. So, we'll talk about that a bit later how we automate the fixes. But Upgrade status will let you know if there's automated fixes available for those errors. If all of them are automated, it tells you to just run the tool and then fix it. It also tells you to manually do. It will tell you if you're not using certain projects on your site to uninstall them and just get rid of them instead of keeping them around. It will tell you if there's updates available from Drupal.org that are compatible with the next major version of Drupal in this case Drupal 10. And to tell you to update it will link you to the issues on Drupal.org for updating it to the next major version. So, it facilitates collaboration in the community with the project list of where you are. It also checks for a bunch of things on top of Drupal Check. So, it has a lot of stateful things like checking routes in Drupal or checking your tweak templates that would not be statically checkable with PHP 10 Drupal. So, we'll add those on top of the results from PHP 10 Drupal. And then it has an environment check. So, it checks all of the requirements of the next major version if your current developer environment meets that if it has the right PHP version the right database version if your settings file includes deprecated keys a bunch of these things it will go through and report them so you can fix them and get ready and then it has this pie chart at the end how complete you are with your process and it will congratulate you at the end if you succeeded. So, this is very visual. It's also integrated in Drush so you can run it in your CI system it will fail your CI if there's problems. It has like an XML report that you can put into fancy other display tools so it has a bunch of these nice solutions. So, that's upgrade status. The fun one PHP 8.1 compatibility so I don't know how many people are running Drupal 9 on 8.0 but if you do the breaking changes from 8.0 it's not that bad, there's just a few. So, one of the best ways to do this is I know most projects now have some kind of continuous integration built in set up another workflow that uses PHP 8.0 and run Drupal check PHP stand the Drush command for upgrade status in your CI and see if it explodes that's the easiest way to go for it PHP stand does have a way to set the target level with the PHP version and you can set it to 80 100 which is 8.1 but I spent about a month and a half contributing to PHP stand to try to make it be self-aware of breaking changes in PHP 8 when running on 7 it's hard so you can set that up and try to run it, it will catch some things especially native PHP functions that have signature changes it will catch that but also PHP stand at about level 2 to 6 so if doing it in Drupal check won't necessarily do a lot so one of the best ways to do it is to just get a PHP 8.0 environment and run it I just opened an issue for myself to add a flag on Drupal check to say with PHP 8.0 and it will set that flag to at least try to do something so that's one note on PHP 8.0 compatibility do it in your local, do it in CI see what happens the easiest brush, brute force tracking deprecations so we have all of these tools and we always wanted to know okay so how does Drupal do how does the Drupal ecosystem do in this sense so the Drupal association is running upgrade status on all of the contributed projects thousands of contributed projects every week once a week, it runs on all of them and then it has a incomprehensible zip file of data that nobody would be able to read and so we take that incomprehensible zip file of data and then make a beautiful colorful dashboard out of it that we put it on dev.aquia.com so that takes the data from the Drupal association and digests it so that's on dev.aquia.com Drupal 10 slash deprecation status and it gives you a run down of the general status of the contributed projects we discontinued running this for Drupal 8 to 9 because the Drupal 8 releases that are not yet Drupal 9 compatible were marked unsupported so there's no point in running it anymore there so we have it from Drupal 9 to 10 now and if you've seen this tool before there's a lot of good new things here that you should check out because we've improved a lot of things based on stuff that we learned before so one new thing is that we have next step suggestions for projects here which are very similar to upgrade status so we tell you if we have pre-scanning errors and like there's a machine name problem with you or a malformed info file or a PHP fatal error that we can't run upgrade status on your project then we categorize these and we tell you you need to fix them and we have help text for each next step as to what you should do to fix this in your project and then we are tracking when you need to fix deprecation errors when we find them the automated tools rector or you need to do manual fixes as well and one shortcoming that we had before is once you fixed all of your problems we considered you done but now we don't consider you done at this point because we track your release status for projects as well because having no deprecated code in your project doesn't really help if it's a dev project and people building sites can't use your project yet because it's a dev release so we are trying to encourage the contributed projects to make tag releases available and then improve the stability of releases as well so we suggest these next steps with clear instructions and we track stability beyond zero deprecation errors each project page has a landing page now on the site with the list of the errors, the next step and explanation of the next step so that's the instructions on what to do fixed info files and then there's a UI to filter the errors and then look for how widely this error applies to other projects like how easy it's likely going to be for you to fix it and we also have maintainer search now that was a popular request that people wanted to look at their projects and the status of their projects so they can just search for the maintainer name now and look at the projects for themselves we also do finer segmentation of errors now so one of the things that happens in Drupal 10 is that most of the deprecated errors found in 7000 contributed projects are coming from Drupal 8 to 10 deprecations so these are the bright yellow ones were already deprecated in Drupal 8 so if you don't care about supporting Drupal 8 then half of all of the deprecated API instances that we find in all of the contributed projects on Drupal.org can already be fixed without any incompatibility problems with Drupal 9 and then the other half is Drupal 9 deprecated APIs. We are also tracking third party projects so we have separate tracking for twig API, symphony APIs, guzzle APIs etc and we also know which of the errors have automated fix coverage so this this half of all of the errors is Drupal APIs that are covered by automated fixes and this is the Drupal APIs that are not covered by automated fixes so we are way better in covering the API changes with automated fixes thanks to a lot of funding from Palantir.net and the work of this gentleman that basically built most of it single handedly. So we have this finer segmentation of errors as well there and then the next up is how do we fix them automatically. Now this is the fun part and there is going to be a part where you look at this and I know some eyes are going to glaze over because I did the first time I started working on this. So fixing deprecations automatically Rector has now become a household name. Think of it as a way to automatically upgrade and refactor your code. Drupal Rector is a repository of Rector rules so let's first differentiate PHP stand is a static analysis tool. It reads your codes and reports back problems. Rector you write rules and say this is a problem fix it. So it's reactionary. PHP stand is for discovery. Rector is for reactionary fixes. So that way you don't have to do it manually. So it is great. So the rules target specific nodes in an abstract syntax tree. Now you don't need to know what an abstract syntax tree is. Think of it, you write code, it gets turned into a tree of objects that can be traversed and we can say hey this is a function this is a method. Oh this is the method that I need to fix. Here's the replacement tree syntax. So if you want to write rules here's a quick example that it will go through or just ping me in Drupal Slack and we can hack on it together. So let's take the first example is file create URL was deprecated and it's to be replaced with Drupal with actually not this exact code file URL generator service and invoke the generate absolute string method. But the simplest way to replace it without trying to do dependency injection for you is Drupal service. All right, so this is a rule that was written in over the fall ish time. So the target we say get node, Rector says what node types do you attach to and here we say function calls which also means that every single time Rector finds a function call on your code it's like okay do you work or do you want to go to town and fix this? So in the rule we have to say is this the right one we want to modify because I've written bad logic and next thing you know I rewrote everything in the code base. So don't do it in production please. And then this is the fun mess with it. So the top line is just an assertion for PHP storm so I know it says yes I know we have a function call and another method we said I will only receive a method call. And the first thing that it has to do is it gets the name from the node which is a function call which the name will be file create URL. If it's not file create URL bail out we don't want to modify it and then all of this right here so I'm kind of blocking it is saying to create a static call to the fully qualified name of Drupal and we're calling the service method and passing it a string argument of file URL generator that creates the Drupal service call and then method name is generate absolute string and then we return a method call node. It's one of you look at it and it's like but once you start going through it it's really repetitive we have a lot of base classes that makes a lot of this easier but I didn't want to show a simple base class I want to try this as the simplest straightforward example but there are things that we have a lot of helpers for to help automate next is project update bot which ties into Rector. Yeah so one more thing about Rector is this is how you write Rector rules we have a lot of the Rector rules written now so you very likely don't need to write your Rector rules but if you find areas where something is not doesn't have an automated fix it would really welcome you to help out with writing the Rector rules but you most likely don't need to write much Rector rules at this point so next up is project update bot so the project update bot runs as part of the same job that generates the status results that I've shown before and this runs where after the upgrade status step is run it checks if the errors that upgrade status found are fixable with Rector and if they are then it also runs Rector and generates the patch from Rector for the project and then it posts the patch in the issue queue of the project as a project update bot user so it's automatically posted in the issue queue and then it will post updated patches later on with updated Rectored codebase if there is more fixes available so this is basically automating all the tools that we have running upgrade status on your project running Rector on your project posting it in your queue maintainers only need to look at this patch and understand if it works for them and commit them and fix it up and then make the release we have not updated the project update bot yet to Drupal 9 to 10 so this used to run very happily Drupal 8 to 9 we need a little bit of work to update this to 9 to 10 to make it work again and then we'll kick it off again and we'll run on contributed projects but this will help with getting all of these contributed projects ready it still needs humans to review the patches and to make the releases so that may sound trivial but you need humans to review them but it's a thing that we need to be aware of so because of all of these things that we do then some of these projects will have their releases available that are Drupal 10 compatible and so you can use them with Composer on your Drupal sites but not all of the projects will be Drupal 10 compatible in time for Drupal 10 so that's just the effect of life so we have some solutions for that as well so we for Drupal 8 to 9 we built the lenient Composer facade because there's this problem that thousands of these projects need very simple changes but you need the humans to be involved to commit the change and make the release and I think it's great that a lot of people contribute projects on Drupal.org because we have all that open source code base that people can use and it's also fine that people stop supporting their projects they move on but unfortunately there's a lot of these projects because they stop being supported they don't get to be updated so we built this lenient Composer facade to allow site assemblers if you're assembling your site in Composer to ignore the core requirement in these projects so if a project does not get updated to Drupal 9 in this case or Drupal 10 in the future then you would be able to require it with Composer even though normally it would not be possible to require it with Composer so that was the idea behind the lenient Composer facade. This was the other thing that's not yet updated to Drupal 10 so this was a solution for Drupal 8 to 9 and yesterday we had a discussion with the maintainer of Composer itself and with Ryan from the DEA and other people how do we do this in Drupal 9 to 10 because there's a bunch of technical problems with that process if we apply the same solution and the solution that we came up with is to build a Composer plugin that we put into core so that you can require Composer projects ignoring the core requirement and that would allow to distribute this to people building their sites instead of it being a central service that has some potential technical problems so that's likely how we're going to update the lenient Composer facade is we discontinue the lenient Composer facade and we write a Composer plugin instead that allows you to require projects where the humans did not make the compatible release yet so that's a good step for building your site now you have the codebase but it's still not compatible with Drupal 10 so that's where Composer patches comes in that you can apply the patch from the project update bot or the humans wrote in the issue queue and you can make the project compatible with Drupal 10 on your site so this is a process that is not ideal but it's the best that we could do on the way from Drupal 8 to 9 and we'll apply the same from Drupal 9 to 10 yeah so the question was this allows you to install if the dependency was declared in the Composer JSON file yes this allows you to install dependencies that are not yet compatible with your major version of Drupal but it was only for 8 to 9 so we will discontinue this for 9 to 10 and we'll have a Composer plugin that we didn't build because we just had the discussion yesterday about this but now that the Drupal 10 releases in December we have time to build it and put it in core to support the similar workflow with a Composer plugin on your Drupal site yes yes so once you install it you can patch it that's what you said so this is for getting it with Composer because if it's not yet compatible with your Drupal then Composer will refuse to download it so this is to make a Composer to not refuse to download it and then once you have it downloaded with Composer then you still have to patch the info file at least and then some other things possibly this project is for applying patches to things that you got with Composer so you can apply the patch from the project update bot or from humans in the issue queue that has not yet been committed to the project with Composer patches so these two solutions are for projects where the humans are not making the releases yet or will not make the releases so that's how you get your project in and yeah so I know offhandedly that might seem very convoluted but realize this is not an us problem this is a problem in every ecosystem that has upgrades I don't know if anybody was tracking package updates for PHP 8.1 but there's a scary a lot of Twitter theory about oh it doesn't support 8.1 yet is it locked to PHP 8.0 and dependencies on dependencies that would be patched for 8.0 and a lot of times people are then forking on GitHub and pointing their Composer and same with symphony and symphony bundles so it might seem like there's a lot of work going on here but this tool is like a shortcut from you having to point to a custom repository and forking it and maintaining it in your Composer so no like this isn't just a Drupal problem this is just a software problem period and this is I think this is actually like the best approach that we as Drupalists can approach this from yeah if you look at the readiness data of Contrib around half of Contrib is the bright yellow that only needs an info file fix so around half of Contrib Drupal 9 Contrib only needs an info file fix which means that if the humans are not making the fix and not making the releases then you will need to use this Composer solution and patch the project but they are projects that only need this one line fix to be able to be used so that there's another option of taking over those projects so if you want to be co-maintenors slash maintainers of projects that would also solve the problem but it's needs even more humans so if you want to get involved we have a lot of select channels for the things that we talked about so we have the D10 readiness select channel for all the Contrib tools and the core work that we are working on there's a dedicated channel for PHP 10 for the low level building PHP 10 itself if you're using PHP 10 for Drupal 10 readiness there would be D10 readiness there's the Rector channel for working on the Rector fixes and whatever problems you have with running them there's the Admin UI channel for Claro, the Oliveiro channel for Oliveiro and the CQTDR5 channel for CQTDR5 there's a meeting in the D10 readiness channel every Monday at 11am pacific about Drupal 10 readiness we talked about the tools we talked about core progress we celebrate our progress and we discuss blockers and you can also meet us here at the contribution rooms and there's a bunch of buffs later today about these other things that happen in core that we would love to see you at with this we have 14 minutes for questions if you have any could I show you an example of finding the deprecation status by maintainer yes this is not my computer so I would not be able to do any CLI but web browsers are easy so here's the deprecation status dashboard live and so you want to look at my projects I'm not going to do the accent here so we're going to look at Drizzi's projects why not this is the example so here's Drizzi's projects he owns OG for example he's the OG maintainer of OG I don't know so this is his projects and then you can see the next step is to run Rector to fix some errors and you can look at this next step and here it explains that 920 projects need to run Rector and here's the description of where to get Rector and what to run and all the projects that need to run it so this is how you look for maintainers sure yeah I know next question is there another library that's going to replace jQuery yes and no so jQuery UI was documented to be emeritus which is basically end of life and so we worked a lot on replacing jQuery UI components with other things and we replaced some of them but not all of them and by the time we replaced half of the jQuery UI components then jQuery UI decided not to be emeritus anymore and they released this update and now they have security support so we were like okay that's good but you don't need to replace everything because if they are emeritus and they don't release security fixes anymore if jQuery itself gets updated they become incompatible and that's a whole mess for Drupal Core to update all of your JavaScript overnight in a security release that would be a problem so now they support it again so we stopped replacing the components we would still ideally want to replace them but we stopped halfway because the way that we do the replacements to do these deprecations and a new API and have backwards compatibility it's a lot of additional work for core developers to do this for the benefit of side owners having an easy upgrade path it's a lot more work so we stopped halfway and we're not going to replace jQuery UI we're not going to replace jQuery we may introduce new frameworks so project browser is being proposed for core and the prototype that we have right now is using Svelte.js and we don't know if we're going to add Svelte the prototype with Svelte.js into core or not but that's an option that's on the table so that's a possibility we may use other frameworks in core without dropping jQuery UI or jQuery first next question alright well if there's no more questions then thank you for coming it's been fun see you around


It was your groin that was the issue when exactly did you feel it was it when you hit the bag or before that were you feeling That's what I felt after I stepped on the base and it felt kind of like a kind of like a cramp, you know it's nothing like What it what it had last year, you know the pain is completely different, you know, so Like I said, you know it happened after you know, I stepped on the back Boone thought it could be an interlist thing you optimistic you may be able to avoid that El dirigente mencionó que ve probablemente algo que tal vez te tengan que poner la lista de lesionado Te siente optimista de la lesión hay que esperar un resultado Well, you know tomorrow We gotta wait until tomorrow to have a never-right tomorrow We'll see what kind of results we get and We'll see what kind of decision with they make you know depending on what the result of the test is What's the level of discomfort that you're feeling right now? Oh It just feels a little a little tight, you know, and it's not Preventing me from walking moving my leg freely But like I said before we got away till tomorrow


It is through service delivery and a lot of application has been developed to serve the population. So there are applications for government and applications for business, applications for institutions and we have them in education, in a judicial system, in health All these applications are for helping the population to get better services quickly and also to help them to understand that they have to use this application for their daily life. The challenges are, you see now we are getting service online and the business is online. The main challenge is to address the cyber security issues so that people are secured for their transaction and also their privacy. The second thing is that we need to have adoption of ICT in the day life of the people and we still have people with low income, we still have people with disability. Also all these have to be included and when we have this it will be included and we will have really achieved that and also we need to have a public sector involvement in that ICT development and innovation. When we get this it will be really the achievement of our vision 2020.


First question is from Mason Burnt. Can I or should I train my arms on off days for optimal muscle growth or are compound lifts sufficient in developing arms? You know, frequency, although now, I'm starting to see people really start to play with frequency of training. It's, for a long time, was a variable that was not utilized effectively. I mean, you can train muscle groups quite often throughout the week, so long as you modify the intensity. You've just got to manage your intensity. Yeah, you can't train your arms all the time, super hard, but you can train them often if a lot of those workouts are also easy. So if you're doing two hard workouts a week where your arms are getting a lot of work, can you add more volume, more frequency, and get your arms to respond even more? You can, just keep the intensity kind of low. The best results I ever got with myself and with clients was exactly that, playing with frequency. And so, theoretically, you could work out your arms five days a week, two of them relatively hard, the rest of them kind of easy, giving yourself a pump and feeling the muscles work, and that's about it. But you'll get great results doing that. Now, what are your guys' thoughts on the individual variance here of like, because however, and I can't help but think of Justin, right, in the situation, because I think if you watch the two of us do a bunch of the same lifts, it just looks different. And how he recruits muscle to do a pull-up or a row is different than how I recruit muscle to do a pull-up or a row. And some people, when they do compound lifts, their biceps and triceps develop incredible with just doing that alone. I'm not like that. Like if I just do compound lifts, my arms don't really develop nearly as much as if I put some sort of attention and focus on it. I think Justin's the opposite of that. I think that he can do a lot of the functional training he does and just stick to a lot of the compound lifts he does, and his arms put on size really well. How much do you think of this as, you know, genetic and then the individual variance of how people recruit muscle when they do these lifts? That's hard to say. There's always a huge genetic variance. I mean, regardless, right? But I mean, if you look at like, you look at power lifters who transition to bodybuilding, right? So these are guys who've been lifting heavy, very strong, lots of compound lifts, and they move over to bodybuilding and what are the areas that they typically will lack? Arms. It's usually arms, right? Because they didn't do a lot of isolation and volume for the arms because of power lifting. So I think regardless, you'll get value from doing a little bit more volume of frequency. But you've got to modify the intensity. Yeah, I definitely think there's both. Both provide value. And I think that incorporating both, like especially doing like the gross motor movements and then, you know, like adding the frequency with isolation movements. Obviously that's like a favorite recipe of mine. But yeah, there's the opposite too. Like there's people that only stick with, you know, doing isolation movements all the time and doing bodybuilder style training, but then all of a sudden they'll do, you know, heavy pull-ups, they'll do dead lifts and all of a sudden like their arms get affected like they've never got affected before. So it's just, I think it's just introducing a new variable in the mix that really gets them to respond. And by the way, this is how MAPS aesthetic is designed, right? So we have three foundational days which are mostly your compound lifts where you're kind of hitting the entire body. And then you have two days a week that are focus sessions and the focus sessions are designed to be multiple for the person. So if buys and tries are the area that you want to develop up your arms, then you would have focus sessions where you're doing a lot of these isolation exercises on those other two days. So you have all the compound lifts you normally do and then so all they are are volume builders that we've built into the programming and it's customizable to the person based off of what areas that you want to develop on your body. So if it's your arms, your shoulders, it doesn't matter what muscle, you pick the muscle and then we show you how to build it into the program. That program was designed for somebody who has a question like this where they're like, hey, I want to bring up a body part and that's how you do it. In fact, if you go to mindpumpfree.com, there's a guide there. It's free on how to build bigger arms. So you just download it, it's totally free and we go in a little more detail on some of the things you do to help develop your arms.