 Yeah. Thanks. Right. So I'll start sharing my screen. If it allows me to, there you go. Yeah. So I'll make this a little bit bigger. Can everybody see it? Yes. Yes. All right, cool. So this is about to introduce, I don't have any formal presentation here that we don't, we don't, this is fairly new. So we don't have a lot of material. Maybe, and I thought that there was another presentation going to happen from Julia Muft. Nevertheless, I would like to introduce that. And once we have more material, maybe I'll do an actual, and if there's interest, an actual presentation and prepare for it. All I want to do now is just introduce this initiative. And maybe discussions can start. And this is, as I said, is a community initiative. So we rely on community feedback. And this is for the community. So the initiative is called a triple seven soft landing or triple seven and the flight soft landing. And we have, we have, I'll provide some links as I go along. Let me just find where is it the chat. Yep, there you go. I'll put it in the chat. So this is the main page of the initiative, which is basically the documentation and we have specified the initiative goals and the scope. And, and there's additional pages that will be added here in the future. If you go to the scope. Right. So this is broken down and we are hoping because it's lengthy, we are hoping to break this down further and provide additional links and the same goes for the understanding your options as a triple seven site owner. Pays. So, so they're kind of lengthy. So maybe we'll split them into sub pages, depending on use case. But as I said, this is fairly, fairly new. Who the who just let me go just back to the initial page. So the initiative I take no credit this initial work was done by Irina, Zach's which is a I'll give you credits is a person that is based in the US sees the owner founder and owner of Fibonacci Web Studio. So web developers is very active. She's been a drop of 15 plus years and if I am not mistaken see recently finished some role. I'm not entirely sure in the Drupal Association but she's very active. The other member that is currently a co maintainer is Tim. He's also based in the US. And he runs a company called triple triple sorry. He's been active for almost 13 years now, very active in local Drupal camps and and other contributions as well. And same as me. We are both working with backdrop CMS which is one of the options that will be suggested as an option here for Drupal site, Drupal seven site owners. So I'll quickly show this what this is all about. So this is the official usage stats for Drupal core in Drupal.org. It shows the various versions of Drupal core that are out there. The big red portion here is Drupal seven so we have a good 400,000 websites still running on Drupal seven and for whatever reason. This this line here where it picked was where Drupal eight around when Drupal eight was announced. And enough time was given many years for site owners to switch to Drupal eight, nine or 10, but people seem to not have been doing that. And the initiative is starting with the goal to help these people move on because by the unless something changes by the end of this year and then the 2023. The project will come will become end of life so it means no more bug fixes no more security updates, but this remains to be seen actually it will be officially decided in July this year. At the same time because this is like a huge portion of the Drupal community. So we don't want to leave these people behind for whatever reason they were left behind could be it would could have been budget usually it's most likely that or just the amount of work that needs to be done basically. So yes, people have been more slowly moving to towards the newer versions of Drupal but but not enough people. So this is what this is about only today just a few maybe an hour ago I also started a project to match this initiative. So there is, I'll provide the link for that in the chat as well. So, again I've added the same people as the commentators we are yet to establish a an official time where we meet to discuss the agenda there's no issues open. So what we are planning this there will be no code or releases here. This will just be to provide links to the documentation, the resources, and also so that people can open issues with things that they want to suggest that maybe we have missed that we haven't considered, or maybe offer advice or additional solutions. I should mention also that. So there's, there's multiple solutions that are being offered so it's of course it's the suggestion that people should move as soon as possible to Drupal nine or 10. Right. But for those that for as I said whatever reasons are not ready to move yet. And we would like to suggest that they move to backdrop CMS which is for those that not aware a Drupal seven fork a continuation of Drupal seven. And this will not a lot of information will be here because we are not trying to you know, shamelessly pitch backdrop to here there will be some links and some prawn, a point cons listed, but very high level. I would like to make this about backdrop CMS, although I say I'm a bit biased because I belong in the project management committee of that project. The goal here is to help site owners, the stand what their options are the various options, and, and, you know, help them move from their own, maybe would be tools that allow them to do a site audit on their site and understand the complexity. Maybe it will be providing links or improving the existing channels that we have so that site owners can find a right partner at their partner to help them in that process whatever they decide to go with. So yeah, this is in general the, the goal of the initiative. And yes, I would like to ask everyone to participate. And maybe in another follow up meeting, I will have more of an official presentation with more resources more actual structured information that I can provide. And with that, I would like to maybe open the floor for questions. Yes. So module development and contribute that's come from Drupal seven is that work like one for one in backdrop. Yes. So it's easier to port modules to Drupal seven. If they're just very simplistic modules, there's a Drupal seven compatibility layer. So all your Drupal underscore functions will still keep its own by the ball. They will still work. There's very few comparability backwards comparability breaking changes so chances are that if your module is very simple you just change a single line in the dot info file and it just works. Now, there's more elaborate projects like for example that group module comes to mind, or rules that needed some more, some additional work. But yes, if it's not like this. I don't know like 1000 of the most popular modules already have been ported because backdrop has been around for a long time. Maybe the questions that you're asking is like recently in the past year after multiple extensions of the end of life we had some serious organizations move huge projects and save huge amount of money for the customers. So it was an appealing solution. So we kind of have more people coming in and these organizations have the resources to port even more modules. So if there was if we had 98% of the modules that they needed ported, and they needed to get these organizations across. And so we have supported them and contributed them. And as like figures that come off the top of my head, maybe it's not accurate, I will provide links to those it's like, I think, which is again an agency in the US have moved two of the very complex websites in the family to Stanford University. And if I recall the numbers correctly that like they finished the move the upgrade to backdrop like in three months. And they, the initial sort of like estimate to move them to Drupal eight or nine was around the one million mark, and then they ended up only using like 400,000 out of that like so they they save the customer like 50 60% of the budget so we're talking about huge savings there. And at the same time they moved them to a solution which there may there is discussions in the community that that until the usage of Drupal seven drops to a very serious, like to a very small amount, it will maybe perpetuating the support likes at least security updates, again, not official. There are some people that want their site to the Drupal seven site to run forever as it is so that will be a good option for them. Right. But there's, there's people that want a security supported version of the software that they're running and at the same time they want as, as you know, things evolve they want to add new features to the site at the same time so in that case backdrop CMS is a good solution for them. And I can talk more about backdrop CMS but that was not the goal presentation but yeah sure. Ask away any questions. Don't don't let that discourage you. Yep. Any any other questions. Just like I have a follow up. So, do you do you feel that having this initiative on Drupal contributes to the fragmentation of the community overall instead of getting people to go from seven to eight and focus on Drupal it's sort of like giving them. I will give a clear path away from it. Yes, I will give a short answer the answer is no I don't believe that there's any fragmentation and then I will give a more elaborate answer so when backdrop CMS was announced. It was how it started was silly so the people that founded that started the project we were long term you know Drupal. The names that you usually see the usual suspects as I say chronic Drupal users right. So they started the forecast as a joke like you know when they saw that the eight move happening the changes and what they would mean for their business, the business that they were running. And initially was started like a joke like they said, we can always fork. Right. So, one of them actually did start and fork the project that the seven project and just to see what what amount of work would be required and what it would look like. But because he was a renowned person among the community didn't go unnoticed. And initially there was some concern like you express now. But we have been around for like 10 years now and it was a bit like when we never aimed to be hostile. We meant to be a solution for like the initiative states that maybe that's a good thing. I'm trying to find a link where it's there's a presentation that says that. Yes. So, so the initiative sprung off the presentation that team, one of the maintainers of the initiative currently has done, which has a graphic that I would like to present. And this will come as a as an additional sort of like answer to you. I'll make this a little bit larger. So, this is the graph that I showed you earlier. And this is the graph that was in an original post back like 10 years ago when when backdrop CMS was announced, and this was the goal. So we started noticing as a rough outline of this that the seven was and predicted at the same time that it would decrease and also the way that things are going because the symphony based versions of Drupal were hard, like people needed to be familiar with the composer and symphony it was a whole different thing whatever reasons, we predicted that this decline, it already had started right. And this is the solution that we recommended that we said that we are a friendly product. And I'll specify what I mean afraid of product and we would like to capture people that would otherwise flee to other platforms and other software and continue the upwards trend that Drupal had since the days of the seven, which I personally had the most successful versions was Drupal. Right. So, recently trees has publicly like a thing it was an interview that he's done during one of the Drupal points announced that they, they consider backdrop CMS now as part of the family and that we've with improved things in the community. And I'll, I'll, I'll explain what I mean when I say that we are a friendly product. So if you're from a digital agency perspective right, your developers don't have to learn anything new, if they worked with Drupal seven before, it will be like at home like they won't have maybe a few new things that they will have to learn for example in backdrop CMS we backboarded, or we implemented our own solution of content management, CMI things that we're founded in the eight. So you will get some of the benefits of Drupal eight and beyond, plus the good, you know, old fashioned whatever used to be Drupal seven. So your developers will not have to retrain from a site owner perspective. Your content editors because the UI and the concepts and the structural content entry has not changed. You will not have to retrain completely retrain your content editor team. Right. And I said that the cost is less. Now, trying to keep these people within the Drupal community is useful for the product for the project itself for the software. Right. Because people that are not ready to move to the seven now may be in a few years. Right. And, and moving from backdrop to Drupal 11. I don't know, whatever that is, would be as easy as moving from Drupal seven and in some aspects, maybe easier. Right. So, the goal in general is to a, do not make it seem that we are forgetful and leaving the Drupal seven site owners to their own luck. Right. Destiny. We want to show them that as a community we care for them that we realize and we understand that this, this transition to newer versions of Drupal has been problematic for one reason or the other. We want to respect that and help them maybe that means that Drupal solution or a backdrop solution is not best of them and then maybe they will have to move to something entirely different and that's totally fine. But rather than leave them lingering in a potentially insecure in the future, not supported software, but out of those hundreds of thousands of site owners that are considering a solution if they stay or if they move to backdrop. There's more chances that in the future will still keep them and they will move to a future version of Drupal. So we keep them within the family that's that's the whole goal. So yes, I hope I answered your question there with that. Certainly thoroughly. Yes. Anyone else. I had a question. Great. So, with this initiative, the Drupal enterprise software initiative. What is the main, I know you showed us the main, the main page on Drupal. But what is the main objective of this initiative. Is it just discussions or is it about showing the, like, what are the different options. Yes, all of that is raising awareness. One of the things that is a big, big pet peeve of mine is that Dress Drupal seven has been supported for many years now. It's sessions on trying to, I will use the word forcefully and please excuse for lack of better words to forcefully move people out of Drupal seven and into the nine, regardless of whatever problems they are facing. But we have not had any Drupal specific sessions in any of the big events in Drupal and this is this is not fair to the community that was still using a, I understand that the new thing is the more shiny thing and everybody moves to that right. But we had signs for many years that people, for whatever reason, as I said, we're lingering in Drupal seven, and we have not been doing that much. One of the goals, the main goal is to just help Drupal seven site owners find a solution moving forward, right, but sub tasks of that goal or manifestations of, you know, the efforts that we will make to provide the soft landing is provide tools, provide specific events or sessions within greater Drupal events, if there's need for it, and provide a means for these people that may be considered that that the rest of the community has moved on and left and behind that that is not the case that we are still supporting and we are here for them. Right. Did that answer your question or Yeah, I did. And I understand that this is a very recently started initiative. Yes. And so what is what are the next steps like. So we are seeking to establish maybe a weekly or fortnightly meeting maybe over zoom, or something like that where people can join us. So we need to look down the resources like there's tools like Drupal modules that help you that maybe they need. Like they have a lot of bugs or issues in their cues and they will need to move them forward like the upgrade status module comes to mind right to help people with moving to Drupal nine and 10. So we will plan to to solicit help so that we can drive focus towards these tools that make it easier for people in Drupal seven to move to a platform, provide documentation. And, and once we've established a meeting, maybe we'll outline actionable points. Now, having said that as you said we're only three people and we can only think as much as three people. I today opened the respective Drupal dot org issue queue, so that we can have the community come there and say hey I went through your documentation guide, and I see that you are applying these three solutions, but hey this this additional solution maybe you should suggest that. Now I understand that we are not by saying listing solutions we're not going to specifically list all available CMS is out there right. We have a divorced product that will be mentioned by name with the blessings of Drupal Association and other people that we have told in talked in to in Drupal will be backdrop CMS. And again, there will be no dedicated page for that there as you know outlining all the features that backdrop has no it will be maybe just a list a short high level list of pros and cons of why you should move to that, and then links to the project events or other resources. The other CMS is in solutions will be provided as sort of like a vague. You know, third party solution that you maybe need to move to, like for example people, it may be suited for some sites that like they haven't become ambitious, what we call or the structural the structured way of the entry that happens in Drupal, maybe it's not what should have been planned for that site to begin with and maybe WordPress is a better solution for them or weeks or space still right we want to provide that as a sort of like as an optional solution and maybe, as I said, as as chronic Drupal people, we always try to tailor every project that we have around Drupal, but maybe that's not ideal right we need to have other things to consider. Yeah. I'm a bit confused now I do understand what you're saying but how will this initiative as a community initiative guide people towards something like this because this these things become very project specific so are you expecting as part of the initiative with people will come to you and say, hey, we have this current project and no. Yes. So you will see. There with me. So if you go to the main page already, you will see if I recall correctly is the understanding your options. It's this is sort of like now currently in its current form is that it's sort of like a question and answer thing so does your site work as it's supposed to then this is what you would need to do so there's a lot of to do here. So still, as I said this is this is draft initial drafts to get the initiative going, but it would be see what if you're not ready to upgrade. What are your options so it would be trying to help people understand the current status of their site, what their needs are, and what would be the appropriate solution for them moving forward. So this will be a very long term solution for them, right. So this will be that the path. This is how it will work. Right. So of course, the main drive would be go to a newer supported supported version of Drupal which would be the D9 detaining the deniation of it, or if you're not ready to upgrade for whatever reason, we accept that here the alternatives and backdrop is one of them. So, yes. All right. Thanks for that explanation. If I don't have any questions because I do have one more, not a question but a suggestion or way forward. But if any others have my questions please, or because I don't want to call it the limelight. Yeah, no worries. Anyone else. So shoot away with the next suggestion or question. I mean, basically, again as next steps. Have you gone ahead and created a, for example, a discussion channel on Slack, the Drupal Slack yet or whatever because you need to. I had my comedy hat on now. So, though, you have to make this popular. You need to make sure that people know about this in Michigan. So what are you doing? Yes. So I have to admit that sort of like my passion is backdrop CMS so I linger around that community. It's the same thing with team but Irina recently started like she's been hovering around the community and asking questions for like a year or maybe more. But recently she has been more active in our community and she's the main drive that organized she started this initiative from the Drupal perspective. So one of the tasks that we had one of the few tasks that we had this past week was add myself and team as commentators. This has been done, create a project with some people can start raising issues and also that we have a starting point that took to link people to resources. And then the next thing would be for people that already have access and can create channels in Drupal Slack to start a dedicated channel for this project as well or other resources and also as I said to establish a meeting that is fairly regular so that we can. It will be sort of, we haven't figured out what format it would have but I'm imagining that would be discussion of agenda of items that we need like documentation that we need to work on comms that need to go out or what have you, and also maybe a sprinting where we actually do those things in that half an hour one that the meeting is going to be like, but yes, if, for example, if you want to help if you go to the project here and and start an issue that says, create a Slack channel for this. Right. This will be one of the tasks that we need to do someone needs to do it it's so many things we haven't organized properly again so so yeah. All right. Thanks a lot for this and stop in the recording now.